AWS Compute Blog
Category: Amazon Elastic Container Service
Maintaining Transport Layer Security all the way to your container part 2: Using AWS Certificate Manager Private Certificate Authority
This post contributed by AWS Senior Cloud Infrastructure Architect Anabell St Vincent and AWS Solutions Architect Alex Kimber. The previous post, Maintaining Transport Layer Security All the Way to Your Container, covered how the layer 4 Network Load Balancer can be used to maintain Transport Layer Security (TLS) all the way from the client to […]
Building, deploying, and operating containerized applications with AWS Fargate
This post was contributed by Jason Umiker, AWS Solutions Architect. Whether it’s helping facilitate a journey to microservices or deploying existing tools more easily and repeatably, many customers are moving toward containerized infrastructure and workflows. AWS provides many of the services and mechanisms to help you with that. In this post, I show you how […]
Setting Up an Envoy Front Proxy on Amazon ECS
This post was contributed by Nare Hayrapetyan, Sr. Software Engineer Many customers are excited about new microservices management tools and technologies like service mesh. Specifically, they ask how to get started using Envoy on AWS. In this post, I walk through setting up an Envoy reverse proxy on Amazon Elastic Container Service (Amazon ECS). This example […]
How to Automate Container Instance Draining in Amazon ECS
My colleague Madhuri Peri sent a nice guest post that describes how to use container instance draining to remove tasks from an instance before scaling down a cluster with Auto Scaling Groups. —– There are times when you might need to remove an instance from an Amazon ECS cluster; for example, to perform system updates, […]
Help Secure Container-Enabled Applications with IAM Roles for ECS Tasks
In Amazon ECS, you have always had the benefit of being able to use IAM roles for Amazon EC2 in order to simplify API requests from your containers. This also allows you to follow AWS best practices by not storing your AWS credentials in your code or configuration files, as well as providing benefits such […]