ECS Cluster

An ECS Cluster in AWS is a logical grouping of container instances or serverless tasks where Amazon Elastic Container Service runs applications. It provides the environment to manage and scale containers, whether using EC2 instances or AWS Fargate for serverless compute. Clusters help organize workloads, control capacity, and manage networking and scaling policies for containerized applications.

aws.ecs_cluster

Fields

TitleIDTypeData TypeDescription
_keycorestring
account_idcorestring
active_services_countcoreint64The number of services that are running on the cluster in an ACTIVE state. You can view these services with PListServices.
attachmentscorejsonThe resources attached to a cluster. When using a capacity provider with a cluster, the capacity provider and associated resources are returned as cluster attachments.
attachments_statuscorestringThe status of the capacity providers associated with the cluster. The following are the states that are returned. UPDATE_IN_PROGRESS The available capacity providers for the cluster are updating. UPDATE_COMPLETE The capacity providers have successfully updated. UPDATE_FAILED The capacity provider updates failed.
capacity_providerscorearray<string>The capacity providers associated with the cluster.
cluster_arncorestringThe Amazon Resource Name (ARN) that identifies the cluster. For more information about the ARN format, see Amazon Resource Name (ARN) in the Amazon ECS Developer Guide.
cluster_namecorestringA user-generated string that you use to identify your cluster.
configurationcorejsonThe execute command and managed storage configuration for the cluster.
default_capacity_provider_strategycorejsonThe default capacity provider strategy for the cluster. When services or tasks are run in the cluster with no launch type or capacity provider strategy specified, the default capacity provider strategy is used.
pending_tasks_countcoreint64The number of tasks in the cluster that are in the PENDING state.
registered_container_instances_countcoreint64The number of container instances registered into the cluster. This includes container instances in both ACTIVE and DRAINING status.
running_tasks_countcoreint64The number of tasks in the cluster that are in the RUNNING state.
service_connect_defaultscorejsonUse this parameter to set a default Service Connect namespace. After you set a default Service Connect namespace, any new services with Service Connect turned on that are created in the cluster are added as client services in the namespace. This setting only applies to new services that set the enabled parameter to true in the ServiceConnectConfiguration. You can set the namespace of each service individually in the ServiceConnectConfiguration to override this default parameter. Tasks that run in a namespace can use short names to connect to services in the namespace. Tasks can connect to services across all of the clusters in the namespace. Tasks connect through a managed proxy container that collects logs and metrics for increased visibility. Only the tasks that Amazon ECS services create are supported with Service Connect. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.
settingscorejsonThe settings for the cluster. This parameter indicates whether CloudWatch Container Insights is on or off for a cluster.
statisticscorejsonAdditional information about your clusters that are separated by launch type. They include the following: runningEC2TasksCount RunningFargateTasksCount pendingEC2TasksCount pendingFargateTasksCount activeEC2ServiceCount activeFargateServiceCount drainingEC2ServiceCount drainingFargateServiceCount
statuscorestringThe status of the cluster. The following are the possible states that are returned. ACTIVE The cluster is ready to accept tasks and if applicable you can register container instances with the cluster. PROVISIONING The cluster has capacity providers that are associated with it and the resources needed for the capacity provider are being created. DEPROVISIONING The cluster has capacity providers that are associated with it and the resources needed for the capacity provider are being deleted. FAILED The cluster has capacity providers that are associated with it and the resources needed for the capacity provider have failed to create. INACTIVE The cluster has been deleted. Clusters with an INACTIVE status may remain discoverable in your account for a period of time. However, this behavior is subject to change in the future. We don't recommend that you rely on INACTIVE clusters persisting.
tagscorehstore