AWS

AWS Container Platform

This AWS container platform diagram shows both the deployment path and the runtime request path. CodePipeline publishes an image to Amazon ECR, which supplies an ECS service. Application users enter through an Application Load Balancer, and the running service connects to RDS, ElastiCache and CloudWatch Logs. This level of detail is useful for a platform overview when you need to distinguish container delivery from live traffic without showing task definitions or network topology.

UPDATED 2026-09-24
EXAMPLEAWS Container Platform
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Explaining deployment and request paths for a containerized AWS service.

Key decisions

  • Build delivery: Publish container images from CodePipeline to ECR.
  • Runtime: Deploy the image to an ECS service.
  • Traffic: Send users through an Application Load Balancer.
  • Dependencies: Show database, cache and logs beside the runtime.

When to reuse this

Use it for an ECS service overview before adding cluster, subnet or task details.

FAQ

Frequently asked questions

What is Amazon ECR used for?01
Amazon ECR stores container images that services such as ECS can pull for deployment.
What does ECS do in this architecture?02
ECS runs and manages the containerized application service.
Why include CloudWatch Logs?03
It makes the operational log destination visible in the platform diagram.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.