Skip to content

Latest commit

 

History

History
108 lines (89 loc) · 5.34 KB

ecs.md

File metadata and controls

108 lines (89 loc) · 5.34 KB

ECS

AWS's ecs service · portable interface driver.ECS · AWS index

Operations (41)

Operation Description
CreateCapacityProvider
CreateCluster
CreateService
DeleteAccountSetting
DeleteAttributes
DeleteCapacityProvider
DeleteCluster
DeleteService
DeregisterContainerInstance
DeregisterTaskDefinition
DescribeCapacityProviders
DescribeClusters
DescribeContainerInstances
DescribeServices
DescribeTaskDefinition
DescribeTasks
ExecuteCommand
ListAccountSettings
ListAttributes
ListClusters
ListContainerInstances
ListServices
ListTagsForResource
ListTaskDefinitionFamilies
ListTaskDefinitions
ListTasks
PutAccountSetting
PutAccountSettingDefault
PutAttributes
PutClusterCapacityProviders
RegisterContainerInstance
RegisterTaskDefinition
RunTask
StopTask
TagResource
UntagResource
UpdateCapacityProvider
UpdateCluster
UpdateClusterSettings
UpdateContainerInstancesState
UpdateService

Optional capabilities

Discovered by type assertion; only some providers implement these.

ServiceDeployments

ServiceDeployments exposes the deployment history of ECS-controller services.

Operation Description
DescribeServiceDeployments
DescribeServiceRevisions
ListServiceDeployments
StopServiceDeployment

ServiceNamespaces

ServiceNamespaces lists the services that joined a Service Connect namespace.

Operation Description
ListServicesByNamespace

TaskProtection

TaskProtection reads and changes the scale-in protection of service tasks.

Operation Description
GetTaskProtection
UpdateTaskProtection

TaskSets

TaskSets manages task sets, the task groups of EXTERNAL-controller services.

Operation Description
CreateTaskSet
DeleteTaskSet
DescribeTaskSets
UpdateServicePrimaryTaskSet
UpdateTaskSet

Not in scope

  • No workload runs unless a container engine is attached, so the usage-driven metrics (CPUUtilization, MemoryUtilization, network and storage series) are never published. Only metrics derived from state the emulator holds are: AWS/ECS CPUReservation, MemoryReservation and LiveTaskCount, and the ECS/ContainerInsights task, service, instance, deployment and task-set counts (only for clusters with containerInsights enabled or enhanced, or enabled on the account).
  • Task lifecycle events cover PROVISIONING (awsvpc tasks), PENDING, ACTIVATING, RUNNING, DEACTIVATING, STOPPING, DEPROVISIONING (awsvpc tasks) and STOPPED. The transient DELETED state is not published. A task counts as awsvpc when it has an ENI attachment, which today only Fargate tasks do.
  • Container-instance state-change events omit versionInfo (agent and Docker versions), since the emulator runs no agent.
  • ECS Deployment State Change events are published for the in-progress and completed states. The deployment circuit breaker is stored and echoed but never trips, so SERVICE_DEPLOYMENT_FAILED and automatic rollback do not happen. SERVICE_TASK_PLACEMENT_FAILURE is published when a service create or update leaves tasks unplaced, not when a replacement task cannot be placed.
  • SERVICE_DESIRED_COUNT_UPDATED is not published: it signals scheduler or Service Auto Scaling changes, which the emulator does not model.
  • Service deployments and revisions exist for services that use the ECS deployment controller; they complete immediately, so StopServiceDeployment only succeeds while the deployment is still in progress, which is the --async-settle window. A stop of a completed deployment is a ConflictException. The lifecycle stage is not reported, and blue/green, linear and canary strategies, lifecycle hooks, alarms and ContinueServiceDeployment are not modelled. The newest 100 deployments of a service are kept.
  • Task sets run their tasks directly and replace a stopped task to restore computedDesiredCount. They are not registered with load balancer target groups or service discovery, and a capacity provider strategy on a task set is stored and echoed but not used for placement (the same as for services).
  • ListServicesByNamespace matches a service by the namespace string (name or ARN) it was configured with. There is no Cloud Map in the emulator to resolve one to the other, so an unknown namespace lists nothing instead of returning NamespaceNotFoundException.
  • Where AWS does not document an exact message or exception, the emulator picks the closest documented exception and its own wording: a task-set call on a service that does not use the EXTERNAL controller, an invalid launchType, ExecuteCommand on a task that is not RUNNING, and StopTask on an already-stopped task (it keeps the original reason).
  • DeleteTaskSet drains the set immediately whether or not force is set.
  • CreateCluster on an existing ACTIVE name returns that cluster unchanged and ignores the tags and settings in the new request.