Amazon Elastic Container Services (ECS)

Here’s an overview of the key features of using Amazon ECS:

• A serverless option with AWS Fargate. With AWS Fargate, you don’t need to manage servers, handle capacity planning or isolate container workloads for security. Fargate handles the infrastructure management aspects of your workload for you. You can schedule the placement of your containers across your cluster based on your resource needs, isolation policies and availability requirements.

• Integration with AWS Identity and Access Management (IAM). You can assign granular permissions for each of your containers. This allows for a high level of isolation when building your applications. In other words, you can launch your containers with the security and compliance levels that you’ve come to expect from a partner like Firemind and a provider like AWS.

• AWS managed container orchestration. As a fully managed service, Amazon ECS comes with AWS configuration and operational best practices built-in. This also means that you don’t need to manage control plane, nodes or add-ons. It’s integrated with both AWS and third-party tools, such as Amazon Elastic Container Registry and Docker. This integration makes it easier for your teams to focus on building the applications, not the environment.

• Continuous integration and continuous deployment (CI/CD). This is a common process for micro-service architectures that are based on Docker containers. You can create a CI/CD pipeline that takes the following actions:

– Monitors changes to a source code repository
– Builds a new Docker image from that source
– Pushes the image to an image repository such as Amazon ECR or Docker Hub
– Updates your Amazon ECS services to use the new image in your application