SYSTEM Cited by 2 sources
AWS Fargate¶
What it is¶
AWS Fargate is AWS's serverless container runtime — a compute engine for containers where AWS operates the underlying hosts and the customer provides only the container image + task/pod spec. Supported substrates are ECS tasks and EKS pods. Compared to EC2 launch-type ECS/EKS, Fargate shifts host-level operations (patching, scaling, placement) to AWS and bills per vCPU/GB/sec of container runtime.
Stub page — minimal viable to support the agentic-development ingest. Expand on future Fargate-internals sources.
Role in this wiki — same image runs locally¶
Named by the AWS Architecture Blog's agentic-AI-development essay as the container-workload peer to ECS in the patterns/local-emulation-first ladder:
"Containers offer similar benefits for services that run on Amazon Elastic Container Service (Amazon ECS) or AWS Fargate. By building and running the same container images locally, an agent can validate application behavior before deploying to the cloud." (Source: sources/2026-03-26-aws-architecting-for-agentic-ai-development-on-aws)
The structural property the post leverages: the image is the deliverable, so "build once, run anywhere" lets the agent iterate against a local docker daemon + escalate to Fargate only for scale / integration / config validation. Same Dockerfile, same runtime, same entrypoint — cloud is another execution context, not a rewrite.
Seen in¶
- sources/2026-03-26-aws-architecting-for-agentic-ai-development-on-aws — Fargate named as the serverless-container peer to ECS in the local-emulation-first tier of agentic-development feedback loops; framing: "build and run the same container images locally ... validate application behavior before deploying to the cloud."
- sources/2026-04-08-aws-build-a-multi-tenant-configuration-system-with-tagged-storage-patterns — Fargate runs the NestJS Order + Config services of the multi-tenant tagged-storage architecture in private subnets, with an ALB in front + API Gateway / VPC Link at the edge. Shared IAM execution role is called out as the infrastructure-layer tenant- isolation ceiling — stepping up to per-tenant credentials would require the TVM + STS pattern.
Related¶
- systems/amazon-ecs — ECS tasks can run on Fargate (serverless) or EC2 (customer-managed).
- systems/aws-eks — EKS pods can run on Fargate or EC2 node groups or EKS Auto Mode.
- concepts/local-emulation — umbrella concept for the tier 1 feedback loop.
- patterns/local-emulation-first — the pattern that makes Fargate's image-centric model a feedback-loop win.