What I like most about AWS Firewall Manager is that it lets you centrally manage security policies across multiple AWS accounts and resources. Rather than configuring protections one by one, security teams can define policies once and then enforce them consistently across the organization.

This centralized policy management is the standout capability for me. For example, when onboarding new AWS accounts into AWS Organizations, Firewall Manager can automatically apply predefined WAF and other security policies without requiring manual setup each time. That helps keep security consistent and cuts down on administrative effort.

This is especially valuable in larger AWS environments where governance, oversight, and security standardization really matter. Review collected by and hosted on G2.com.

Policy troubleshooting can be challenging at times, especially when multiple AWS security services are interacting. Figuring out why a resource is marked non-compliant often means reviewing AWS Config, WAF, Organizations, and Firewall Manager policies together to see how they overlap. This service delivers the most value in multi-account AWS environments, where centralized policy visibility and enforcement matter most. In smaller deployments, though, the initial setup and ongoing policy management overhead can feel unnecessary. Getting comfortable with policy inheritance and remediation actions also takes some familiarity with the broader set of AWS security services. Review collected by and hosted on G2.com.

I like how simple and reliable Amazon Elastic Container Service (Amazon ECS) makes running containers. For me, the best part is that I don't have to think much about infrastructure, especially with Fargate. I can just deploy and it handles the rest. I also really like how smoothly it integrates with the AWS ecosystem, like load balancers and monitoring, so everything feels seamless. I appreciate the auto scaling and self-healing because if something crashes, it just replaces it automatically, and the scaling of traffic spikes is pretty effortless. Overall, it just works without a lot of maintenance, which is a big win for me. Review collected by and hosted on G2.com.

For me, ECS works really well overall, but a few things could be better. The UI and debugging experience can feel a bit clunky. I often have to jump between multiple services, like logs and metrics, to figure out issues instead of having everything in one place. Also, the learning curve is a bit steep, especially around task definitions, networking, and IAM roles. It's not super intuitive if you're a new DevOps or SRE guy. Another thing is limited flexibility compared to Kubernetes, or for more complex use cases, ECS can feel a bit restrictive. And sometimes troubleshooting failures like why a task didn't start isn't very straightforward. We have to dig through logs and events. So yeah, I mean, nothing deal-breaking, but definitely some areas where it could be smoother. Review collected by and hosted on G2.com.

I used Amazon ECS to run and manage containerized applications in the cloud. It helps me deploy applications using Docker containers without worrying about managing services. I like most that Amazon ECS makes it easy to run and manage containers without dealing with complex infrastructure. I also appreciate its flexibility, whether using serverless or EC2-based setup, depending on my use case. Overall, it saves time, reduces operational efforts, and helps in building and improving applications. Review collected by and hosted on G2.com.

The learning curve, especially for beginners. Setting up clusters and task definitions is a bit complex for beginners. Debugging and monitoring are also a little challenging. Another area is flexibility as it has little to no advanced features. Review collected by and hosted on G2.com.

I really like being able to run and scale containers without having to deal with the friction of setting up the base infrastructure. I also find the integration with Fargate very useful because it allows me to focus entirely on the application and not on the server configuration. Review collected by and hosted on G2.com.

What I like the least is the initial part of having to bring and sometimes reconfigure the environment like roles, load balancers, and task definitions; that's a generalized part of AWS that sometimes becomes a bit tedious. I think something more intuitive can be done with IAM and AWS permissions in general. Review collected by and hosted on G2.com.

For batch jobs that are scheduled to run periodically, developers can run them without maintaining infrastructure. CI/CD pipelines are integrated as part of the service, which makes it even easier. Review collected by and hosted on G2.com.

The lack of flexibility to choose spot instances would have been a great add-on to ECS. Review collected by and hosted on G2.com.

It's easy to learn and manage, It simple yet has great feature like blue green. Review collected by and hosted on G2.com.

For now I get confuse about container running servies and how they communicate with each other, although I figured it out but it bit confusing. Review collected by and hosted on G2.com.

ECS makes running containerized workloads straightforward - task definitions and service autoscaling let us go from dev to production without hand-holding. Deep integration with IAM, CloudWatch and ALB saved engineering time.

Fargate removed infra ops overhead for many of our microservices. The console + CLI combo is robust and the documentation is practical for implementing CI/CD pipelines. Overall, strong reliability and predictable scaling for production traffic Review collected by and hosted on G2.com.

Pricing can be confusing across EC2 vs Fargate for sustained workloads, and fine-grained networking setup (ENIs, security groups) has a learning curve. Service discovery between clusters required extra config compared to some managed alternatives, and the console UI could be clearer around task failure diagnostics. Support response times vary depending on your support plan. Review collected by and hosted on G2.com.

easy to deal with & product delivery time is good with good services Review collected by and hosted on G2.com.

Sometimes it's not timely to provide services Review collected by and hosted on G2.com.

See there is a option to deploy application on EC2 but why i like ECS is because it easily integrates with CICD tools like Jenkins and the fargate serverless option is really good , no need of patching or overhead to maintain server Review collected by and hosted on G2.com.

One in a while it becomes issue when some error comes as ECS dont give direct access to inside server where containers are hosted but then we have logs option in cluster console which somehow helps to resolve issues Review collected by and hosted on G2.com.

The various services that are available to integrate and build solution softwares. Like codecommit, codebuid, codepipeline to build cicd pipelines. Review collected by and hosted on G2.com.

The New UI which was introduced recently has some bugs that needs to be fixed that includes automatic logout when opening VPC via RDS or Ec2 console page. Review collected by and hosted on G2.com.