# Amazon Elastic Container Service Fully managed container orchestration service for deploying, managing, and scaling containerized applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Bring your own client certificate for backend mTLS in Amazon API Gateway DevFeed: [Bring your own client certificate for backend mTLS in Amazon API Gateway]() Original publisher: [Read original article]() Author: Biswanath Mukherjee Published: 2026-09-08T21:46:39Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [Amazon API Gateway](), [AWS Certificate Manager](), [Amazon Elastic Container Service](), [nginx]() Tags: [amazon-api-gateway](), [amazon-elastic-container-service](), [announcements](), [architecture](), [authentication](), [aws-certificate-manager](), [aws-fargate](), [intermediate-200](), [rest-api](), [tls]() ### AI overview This tutorial shows how to configure Amazon API Gateway to present a third-party or AWS Private CA-issued client certificate for outbound mTLS to an Amazon ECS backend. ### Source excerpt Enterprises that use Amazon API Gateway often want to bring their own client certificate for backend mutual TLS (mTLS) authentication. With API Gateway, you can now use a third-party or AWS Private CA-issued client certificate for the outbound mTLS handshake. In this post, you build a REST API with an outbound mTLS connection to an Amazon ECS backend. ## Serverless vehicle tracking at scale: Bosch L.OS on AWS DevFeed: [Serverless vehicle tracking at scale: Bosch L.OS on AWS]() Original publisher: [Read original article]() Author: Yogish Kutkunje Pai Published: 2026-08-14T10:02:13Z Content type: article Language: en Sources: [AWS Architecture Blog]() Topics: [Amazon Web Services](), [Serverless](), [real-time](), [Amazon Elastic Container Service](), [AWS Lambda](), [cloud-infrastructure](), [data](), [Networks](), [Amazon EC2]() Tags: [amazon-elastic-container-service](), [architecture](), [aws](), [complexity](), [compliance](), [cost](), [customer-solutions](), [data](), [india](), [integration](), [intermediate-200](), [networks](), [operations](), [performance](), [platform](), [real-time](), [scale](), [serverless](), [supply-chain](), [workflows]() ### AI overview Bosch Mobility Platform Solutions built L.OS, a serverless platform on AWS that unifies fragmented vehicle-tracking data across India's spot logistics market. The article describes how the platform standardizes data from multiple providers and supports scalable, real-time visibility through workflows for discovery, tracking, and termination. ### Source excerpt Learn how Bosch Mobility Platform Solutions built L.OS, a serverless vehicle tracking platform on AWS that unifies India's fragmented spot logistics market into a single real-time visibility layer using Amazon ECS, AWS Lambda, and Amazon MSK. ## Centralize cross-account Amazon ECS telemetry with an ADOT gateway DevFeed: [Centralize cross-account Amazon ECS telemetry with an ADOT gateway]() Original publisher: [Read original article]() Author: Rahul Kumar Published: 2026-08-06T16:13:46Z Content type: tutorial Language: en Sources: [Containers]() Topics: [Amazon Elastic Container Service](), [telemetry](), [OpenTelemetry](), [SIEM, Security, Observability](), [Amazon CloudWatch](), [Amazon Web Services](), [Windows](), [.NET Framework](), [Traces](), [log management](), [Amazon Elastic Kubernetes Service]() Tags: [amazon-cloudwatch](), [amazon-eks](), [amazon-elastic-container-service](), [amazon-elastic-kubernetes-service](), [aws](), [intermediate-200](), [logs](), [metrics](), [net-framework](), [observability](), [opentelemetry](), [technical-how-to](), [telemetry](), [traces](), [windows]() ### AI overview This tutorial presents a centralized AWS Distro for OpenTelemetry gateway for collecting telemetry from Amazon ECS workloads across multiple AWS accounts. It replaces per-task sidecars, supports Windows .NET Framework tasks, receives OTLP over private connectivity, and exports traces to AWS X-Ray plus metrics and logs to Amazon CloudWatch. ### Source excerpt Running an OpenTelemetry collector as a sidecar in every Amazon ECS task does not scale across a multi-account estate, and it cannot run at all on Windows. Learn how to replace per-task sidecars with a single centralized ADOT gateway that ingests OTLP from workloads across accounts and exports traces to AWS X-Ray and metrics and logs to Amazon CloudWatch. ## Extending Amazon ECS Express Mode to Build an Optimal Container Environment DevFeed: [Extending Amazon ECS Express Mode to Build an Optimal Container Environment]() Original publisher: [Read original article]() Author: Koichiro Okimura Published: 2026-08-04T15:57:59Z Content type: article Language: en Sources: [Containers]() Topics: [Amazon Elastic Container Service](), [Containers](), [Amazon Web Services](), [Deployment](), [log management](), [configuration](), [networking](), [Security]() Tags: [amazon-elastic-container-service](), [aws](), [containers](), [deployment](), [how-to](), [intermediate-200](), [logging](), [logs](), [network](), [security](), [technical-how-to]() ### AI overview This AWS article explains how to extend Amazon ECS Express Mode beyond its default container deployment configuration. It presents hands-on examples for enabling ECS Exec, adding scheduled scaling, and routing logs through a FireLens sidecar with a custom task definition. ### Source excerpt Amazon ECS Express Mode gives you load balancing, scaling, logging, and networking out of the box. Learn how to extend an Express Mode service beyond its defaults with three hands-on examples: turning on ECS Exec, adding a scheduled scaling policy, and adding a FireLens log router as a sidecar container. ## AWS Weekly Roundup: Local Zone in Athens, Claude Opus 5 on AWS, Lambda durable execution for .NET, and more (July 27, 2026) DevFeed: [AWS Weekly Roundup: Local Zone in Athens, Claude Opus 5 on AWS, Lambda durable execution for .NET, and more (July 27, 2026)]() Original publisher: [Read original article]() Author: Daniel Abib Published: 2026-07-27T14:54:41Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [Amazon Web Services](), [AWS Local Zones](), [Latency](), [Amazon Bedrock](), [Amazon EC2](), [Amazon S3](), [Claude](), [cloud-infrastructure](), [Amazon Elastic Container Service](), [anthropic](), [data-governance]() Tags: [amazon-bedrock](), [amazon-bedrock-agentcore](), [amazon-connect](), [amazon-ec2](), [amazon-s3](), [amazon-sagemaker-ai](), [announcements](), [anthropic](), [aws](), [aws-lambda](), [aws-local-zones](), [claude](), [data-governance](), [latency](), [news](), [week-in-review]() ### AI overview An AWS weekly roundup covering a new Local Zone in Athens, Greece, and selected AWS launches and updates, including Claude Opus 5 on Amazon Bedrock. The article highlights local data processing, data residency, low latency, and infrastructure for regional workloads. ### Source excerpt Last week I had the privilege of spending three days in São Paulo with technical builders from across Latin America, brought together for a regional tech event full of deep-dive sessions, hands-on workshops, and conversations with customers and partners. What struck me most wasn't any single session, it was the energy of a technical community [...] ## Deploying Temporal Workers to Amazon ECS DevFeed: [Deploying Temporal Workers to Amazon ECS]() Original publisher: [Read original article]() Author: Ebenezer Ankrah Published: 2026-04-02T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Amazon Elastic Container Service](), [Deployment](), [AWS IAM](), [Dockerfile](), [container](), [health checks](), [Amazon Web Services]() Tags: [amazon](), [deployment](), [docker](), [docker-image](), [ecs](), [environment-variables](), [health-checks](), [how-to](), [iam]() ### AI overview A guide to deploying Temporal Workers on Amazon ECS with Fargate. It explains container configuration, health checks, graceful shutdown, task definitions, IAM roles, secret injection through SSM Parameter Store, and outbound connectivity requirements. ### Source excerpt A comprehensive guide to deploying Temporal Workers on Amazon ECS with Fargate. Covers container config, IAM roles, scaling, and cost-saving with Fargate Spot. ## ECS on EC2: Covering Gaps in IMDS Hardening DevFeed: [ECS on EC2: Covering Gaps in IMDS Hardening]() Original publisher: [Read original article]() Published: 2025-10-02T18:18:59Z Content type: tutorial Language: en Sources: [Latacora]() Topics: [Amazon Elastic Container Service](), [Amazon EC2](), [Security](), [Amazon Web Services](), [Containers](), [Credential theft]() Tags: [aws](), [containers](), [credential-theft](), [credentials](), [ec2](), [ecs](), [hardening](), [security](), [sensitive-data]() ### AI overview This article examines security gaps in Amazon ECS workloads running on EC2, focusing on task isolation and restricting access to the EC2 Instance Metadata Service. It discusses how weak isolation can expose credentials and sensitive data and outlines the need for more comprehensive hardening guidance. ### Source excerpt Introduction # AWS ECS is a widely-adopted service across industries. To illustrate the scale and ubiquity of this service, over 2.4 billion Amazon Elastic Container Service tasks are launched every week (source) and over 65% of all new AWS containers customers use Amazon ECS (source). There are two primary launch types for ECS: Fargate and EC2. The choice between them depends on factors like cost, performance, operational overhead, and the variability of your workload. ## Cost Optimisation in ECS: Integrating Spot Instances at Scale DevFeed: [Cost Optimisation in ECS: Integrating Spot Instances at Scale]() Original publisher: [Read original article]() Author: Aakash Singhal Published: 2025-09-12T00:00:00Z Content type: article Language: en Sources: [Deliveroo]() Topics: [Amazon Elastic Container Service](), [Amazon EC2](), [Amazon Web Services](), [Cloud](), [Automation](), [Resilience](), [Availability](), [container]() Tags: [automation](), [availability](), [aws](), [container](), [cost](), [cost-optimisation](), [ec2](), [ecs](), [infrastructure](), [load-balancer](), [resilience](), [scale](), [stateless](), [storage]() ### AI overview Deliveroo describes how it integrated EC2 Spot Instances into Amazon ECS to reduce compute costs while maintaining service stability. The approach routes only eligible workloads to Spot capacity and uses criteria such as fast shutdown, task redundancy, statelessness, and load balancer deregistration timing. ### Source excerpt At Deliveroo, we're always refining how we scale - especially when it comes to managing compute costs in the cloud. After optimising our Amazon ECS workloads with Reserved Instances and Savings Plans, we saw an opportunity to push further using EC2 Spot Instances, which offer up to 90% savings compared to On-Demand prices. But Spot comes with challenges: Their availability can fluctuate, and they can be terminated with just a two-minute warning. To unlock these savings without compromising service stability, we had to engineer a robust solution across infrastructure, workload qualification, and automation. The Challenge: Balancing Cost and Reliability Our ECS infrastructure initially relied entirely on On-Demand EC2 instances, provisioned through Auto Scaling Groups (ASGs) connected to ECS Capacity Providers. While reliable, this approach didn't take advantage of AWS's surplus compute capacity. We aimed to layer Spot Instances into our clusters, but selectively. Our goal was clear: route only eligible workloads to Spot capacity while ensuring no service degradation during unexpected terminations. Spot Instances: Power and Pitfalls Spot Instances provide dramatic cost reductions but introduce several operational caveats: Ephemeral by nature: AWS can terminate them at any time with a two-minute warning. Capacity variability: Availability depends on AWS's excess capacity in each AZ and can shift unpredictably. Scaling limitations: Auto Scaling may fail if the desired instance types are not currently available. To avoid introducing fragility into our stack, we established technical eligibility criteria that workloads must meet before being scheduled on Spot. Defining Spot Eligibility We formalised the following criteria to assess whether a workload could safely tolerate Spot interruptions: Fast Shutdown Support Constraint: stopTimeout must be < 120 seconds in the container definition. Reason: Ensures ECS has time to gracefully shut down the task before AWS's 2-minute te ## How to use Teleport Machine ID to provide database access to applications running on EKS without passwords DevFeed: [How to use Teleport Machine ID to provide database access to applications running on EKS without passwords]() Original publisher: [Read original article]() Author: info@goteleport.com (Gavin Frazar) Published: 2024-12-03T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Amazon EKS](), [Kubernetes](), [PostgreSQL](), [Authorization](), [AWS Fargate](), [certificates](), [Access Control](), [Amazon Elastic Container Service](), [TLS (Transport Layer Security)](), [AWS IAM](), [container](), [VPC]() Tags: [access-control](), [api-keys](), [aws-fargate](), [aws-iam](), [certificates](), [container](), [ecs](), [how-to](), [kubernetes](), [passwords](), [postgresql](), [secrets](), [tls](), [vpc]() ### AI overview A tutorial on deploying Temporal on Amazon EKS so it can connect to an AWS RDS PostgreSQL database without passwords or other shared secrets. It uses Teleport Machine & Workload Identity, a sidecar, short-lived X.509 certificates, PostgreSQL role provisioning, and a Teleport Database Service deployed on AWS Fargate. ### Source excerpt Discover how to secure database access in Kubernetes workloads. Eliminate secrets, keep databases in private networks, and improve audit logging with Teleport. ## Containers on AWS: Comparing ECS and EKS DevFeed: [Containers on AWS: Comparing ECS and EKS]() Original publisher: [Read original article]() Author: Guillermo Ojeda Published: 2024-04-22T23:24:13Z Content type: article Language: en Sources: [Guille Ojeda]() Topics: [Amazon Elastic Container Service](), [Amazon Elastic Kubernetes Service](), [Containers](), [Amazon Web Services](), [Orchestration]() Tags: [amazon-elastic-kubernetes-service](), [architecture](), [article](), [aws](), [container](), [containers](), [ecs](), [kubernetes](), [orchestration]() ### AI overview This article compares Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS) for running and scaling containerized applications on AWS. It introduces container orchestration, explains ECS features, components, and EC2 and Fargate launch types, and discusses factors for choosing between the services. ### Source excerpt Containers offer a lightweight, portable, and scalable solution for running software consistently across different environments. But as the number of containers grows, managing them becomes increasingly complex. That's where container orchestration c... ## How to use AWS Fargate and Lambda for long-running processes in a Serverless app DevFeed: [How to use AWS Fargate and Lambda for long-running processes in a Serverless app]() Original publisher: [Read original article]() Author: Rupak Ganguly Published: 2018-01-11T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [AWS Fargate](), [Amazon Elastic Container Service](), [Serverless](), [Processes](), [App]() Tags: [app](), [aws](), [aws-fargate](), [aws-lambda](), [cloud-computing](), [ecs](), [engineering](), [faas](), [function-as-a-service](), [how-to](), [infrastructure-as-code](), [processes](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview A tutorial shows how to process a video file and extract a thumbnail using Amazon ECS with AWS Fargate and Lambda in a Serverless application. ### Source excerpt We'll show you how to process a video file that extracts a thumbnail in Amazon ECS using Fargate and Lambda