Amazon ECS
Amazon Elastic Container Service (ECS) is a fully managed container orchestration service that makes it easy to deploy, manage, and scale containerized applications.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Amazon ECS the way a machine reads it — 176 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon ECS scores 67.5/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amazon ECS
Each block below is one kind of artifact we hold for Amazon ECS. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon ECS Service Connect API
Amazon ECS Service Connect provides management of service-to-service communication as Amazon ECS configuration, building both service discovery and a service mesh for connecting...
Amazon ECS Anywhere API
Amazon ECS Anywhere extends Amazon ECS to support registering external instances such as on-premises servers or virtual machines to your Amazon ECS cluster, allowing you to run ...
AWS Copilot CLI
AWS Copilot is an open source command line interface that simplifies building, releasing, and operating production-ready containerized applications on Amazon ECS and AWS Fargate...
Amazon ECS Capacity Providers API
Operations for managing capacity providers
Amazon ECS Clusters API
Operations for managing ECS clusters
Amazon ECS Container Instances API
Operations for managing container instances
Amazon ECS Task Definitions API
Operations for managing ECS task definitions
Amazon ECS Tasks API
Operations for running and managing ECS tasks
Amazon ECS #X Amz Target=AmazonEC2ContainerServiceV20141113.CreateService API
The #X Amz Target=AmazonEC2ContainerServiceV20141113.CreateService API from Amazon ECS — 1 operation(s) for #x amz target=amazonec2containerservicev20141113.createservice.
Amazon ECS #X Amz Target=AmazonEC2ContainerServiceV20141113.DeleteService API
The #X Amz Target=AmazonEC2ContainerServiceV20141113.DeleteService API from Amazon ECS — 1 operation(s) for #x amz target=amazonec2containerservicev20141113.deleteservice.
Amazon ECS #X Amz Target=AmazonEC2ContainerServiceV20141113.DescribeServices API
The #X Amz Target=AmazonEC2ContainerServiceV20141113.DescribeServices API from Amazon ECS — 1 operation(s) for #x amz target=amazonec2containerservicev20141113.describeservices.
Amazon ECS #X Amz Target=AmazonEC2ContainerServiceV20141113.ListServices API
The #X Amz Target=AmazonEC2ContainerServiceV20141113.ListServices API from Amazon ECS — 1 operation(s) for #x amz target=amazonec2containerservicev20141113.listservices.
Amazon ECS #X Amz Target=AmazonEC2ContainerServiceV20141113.UpdateService API
The #X Amz Target=AmazonEC2ContainerServiceV20141113.UpdateService API from Amazon ECS — 1 operation(s) for #x amz target=amazonec2containerservicev20141113.updateservice.
Scroll within the panel for all 13 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Amazon ECS Amazon Elastic Container Service (ECS) API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amazon Ecs Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amazon Ecs Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Fully Managed Container Orchestration
Run and manage Docker containers at scale without managing the underlying infrastructure or control plane.
AWS Fargate Integration
Run containers serverlessly without provisioning or managing EC2 instances using AWS Fargate launch type.
Service Auto Scaling
Automatically scale container workloads based on CloudWatch metrics, target tracking, or step scaling policies.
Service Connect
Built-in service discovery and service mesh for connecting containerized services within and across clusters.
ECS Anywhere
Extend ECS to on-premises and edge infrastructure to run containers on your own servers and virtual machines.
Capacity Providers
Manage compute capacity with capacity provider strategies for optimal resource allocation across EC2 and Fargate.
Task Definitions
Define containerized applications as task definitions with CPU, memory, networking, and IAM role configurations.
Container Insights
Monitor container performance metrics and logs with CloudWatch Container Insights for operational visibility.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Ecs Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon ECS API Rules
SPECTRALAmazon ECS API Rules
SPECTRALJSON Schema 46
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Attachment
JSON SCHEMAAutoScalingGroupProvider
JSON SCHEMACapacityProvider
JSON SCHEMACapacityProviderStrategyItem
JSON SCHEMAClusterConfiguration
JSON SCHEMACluster
JSON SCHEMAClusterServiceConnectDefaults
JSON SCHEMAClusterSetting
JSON SCHEMAContainerDefinition
JSON SCHEMAContainerInstance
JSON SCHEMAContainer
JSON SCHEMACreateClusterRequest
JSON SCHEMACreateClusterResponse
JSON SCHEMACreateServiceRequest
JSON SCHEMADeploymentConfiguration
JSON SCHEMADeploymentController
JSON SCHEMADeployment
JSON SCHEMAEphemeralStorage
JSON SCHEMAError
JSON SCHEMAFailure
JSON SCHEMAHealthCheck
JSON SCHEMAInferenceAccelerator
JSON SCHEMAKeyValuePair
JSON SCHEMALinuxParameters
JSON SCHEMALoadBalancer
JSON SCHEMALogConfiguration
JSON SCHEMAMountPoint
JSON SCHEMANetworkConfiguration
JSON SCHEMAPlacementConstraint
JSON SCHEMAPlacementStrategy
JSON SCHEMAPortMapping
JSON SCHEMAProxyConfiguration
JSON SCHEMARegisterTaskDefinitionRequest
JSON SCHEMAResource
JSON SCHEMARunTaskRequest
JSON SCHEMARunTaskResponse
JSON SCHEMARuntimePlatform
JSON SCHEMAServiceConnectConfiguration
JSON SCHEMAServiceRegistry
JSON SCHEMAService
JSON SCHEMATag
JSON SCHEMATaskDefinitionPlacementConstraint
JSON SCHEMATaskDefinition
JSON SCHEMATaskOverride
JSON SCHEMATask
JSON SCHEMAVolume
JSON SCHEMAScroll within the panel for all 46 ·
JSON Structure 46
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amazon Ecs Attachment Structure
JSON STRUCTUREAmazon Ecs Auto Scaling Group Provider Structure
JSON STRUCTUREAmazon Ecs Capacity Provider Strategy Item Structure
JSON STRUCTUREAmazon Ecs Capacity Provider Structure
JSON STRUCTUREAmazon Ecs Cluster Configuration Structure
JSON STRUCTUREAmazon Ecs Cluster Service Connect Defaults Structure
JSON STRUCTUREAmazon Ecs Cluster Setting Structure
JSON STRUCTUREAmazon Ecs Cluster Structure
JSON STRUCTUREAmazon Ecs Container Definition Structure
JSON STRUCTUREAmazon Ecs Container Instance Structure
JSON STRUCTUREAmazon Ecs Container Structure
JSON STRUCTUREAmazon Ecs Create Cluster Request Structure
JSON STRUCTUREAmazon Ecs Create Cluster Response Structure
JSON STRUCTUREAmazon Ecs Create Service Request Structure
JSON STRUCTUREAmazon Ecs Deployment Configuration Structure
JSON STRUCTUREAmazon Ecs Deployment Controller Structure
JSON STRUCTUREAmazon Ecs Deployment Structure
JSON STRUCTUREAmazon Ecs Ephemeral Storage Structure
JSON STRUCTUREAmazon Ecs Error Structure
JSON STRUCTUREAmazon Ecs Failure Structure
JSON STRUCTUREAmazon Ecs Health Check Structure
JSON STRUCTUREAmazon Ecs Inference Accelerator Structure
JSON STRUCTUREAmazon Ecs Key Value Pair Structure
JSON STRUCTUREAmazon Ecs Linux Parameters Structure
JSON STRUCTUREAmazon Ecs Load Balancer Structure
JSON STRUCTUREAmazon Ecs Log Configuration Structure
JSON STRUCTUREAmazon Ecs Mount Point Structure
JSON STRUCTUREAmazon Ecs Network Configuration Structure
JSON STRUCTUREAmazon Ecs Placement Constraint Structure
JSON STRUCTUREAmazon Ecs Placement Strategy Structure
JSON STRUCTUREAmazon Ecs Port Mapping Structure
JSON STRUCTUREAmazon Ecs Proxy Configuration Structure
JSON STRUCTUREAmazon Ecs Register Task Definition Request Structure
JSON STRUCTUREAmazon Ecs Resource Structure
JSON STRUCTUREAmazon Ecs Run Task Request Structure
JSON STRUCTUREAmazon Ecs Run Task Response Structure
JSON STRUCTUREAmazon Ecs Runtime Platform Structure
JSON STRUCTUREAmazon Ecs Service Connect Configuration Structure
JSON STRUCTUREAmazon Ecs Service Registry Structure
JSON STRUCTUREAmazon Ecs Service Structure
JSON STRUCTUREAmazon Ecs Tag Structure
JSON STRUCTUREAmazon Ecs Task Definition Structure
JSON STRUCTUREAmazon Ecs Task Override Structure
JSON STRUCTUREAmazon Ecs Task Structure
JSON STRUCTUREAmazon Ecs Volume Structure
JSON STRUCTUREScroll within the panel for all 46 ·
Examples 46
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Amazon Ecs Cluster Example
EXAMPLEAmazon Ecs Container Example
EXAMPLEAmazon Ecs Error Example
EXAMPLEAmazon Ecs Failure Example
EXAMPLEAmazon Ecs Resource Example
EXAMPLEAmazon Ecs Service Example
EXAMPLEAmazon Ecs Tag Example
EXAMPLEAmazon Ecs Task Example
EXAMPLEAmazon Ecs Volume Example
EXAMPLEScroll within the panel for all 46 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Microservices Architecture
Deploy and manage microservices with independent scaling, deployment, and lifecycle management per service.
Batch Processing
Run batch computing workloads using ECS tasks with automatic scaling and job scheduling.
CI/CD Pipeline Deployment
Integrate with AWS CodePipeline and CodeDeploy for automated blue/green and rolling deployments of containerized applications.
Hybrid Cloud Workloads
Run containerized workloads across AWS cloud and on-premises environments using ECS Anywhere.
Machine Learning Inference
Deploy ML models as containerized inference endpoints with auto-scaling based on demand.
Resources
Every other property we hold for Amazon ECS — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amazon-ecs · machine-readable index on apis.io