AWS Container Platform Diagram

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.

類型 方塊圖標準 Ogata / standard controls textbook convention引擎 schematex-blockdiagram更新時間 2026/9/24

需求

“Create an AWS container platform with CodePipeline, Amazon ECR, application users, an Application Load Balancer, an ECS service, RDS, ElastiCache, and CloudWatch Logs.”

接著試試Add an ECS worker service that consumes jobs from SQS.Add AWS WAF before the Application Load Balancer.

這張圖裡有什麼

看懂背後的決策。

01Build delivery

Publish container images from CodePipeline to ECR.

02Runtime

Deploy the image to an ECS service.

03Traffic

Send users through an Application Load Balancer.

04Dependencies

Show database, cache and logs beside the runtime.

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

瀏覽所有方塊圖範本 →

常見問題

What is Amazon ECR used for?

Amazon ECR stores container images that services such as ECS can pull for deployment.

What does ECS do in this architecture?

ECS runs and manages the containerized application service.

Why include CloudWatch Logs?

It makes the operational log destination visible in the platform diagram.