Amazon EC2 Container Service

2022/11/28 - Amazon EC2 Container Service - 1 new 18 updated api methods

Changes  This release adds support for ECS Service Connect, a new capability that simplifies writing and operating resilient distributed applications. This release updates the TaskDefinition, Cluster, Service mutation APIs with Service connect constructs and also adds a new ListServicesByNamespace API.

ListServicesByNamespace (new) Link ¶

This operation lists all of the services that are associated with a Cloud Map namespace. This list might include services in different clusters. In contrast, ListServices can only list services in one cluster at a time. If you need to filter the list of services in a single cluster by various parameters, use ListServices . For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

See also: AWS API Documentation

Request Syntax

client.list_services_by_namespace(
    namespace='string',
    nextToken='string',
    maxResults=123
)
type namespace

string

param namespace

[REQUIRED]

The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace to list the services in.

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 .

type nextToken

string

param nextToken

The nextToken value that's returned from a ListServicesByNamespace request. It indicates that more results are available to fulfill the request and further calls are needed. If maxResults is returned, it is possible the number of results is less than maxResults .

type maxResults

integer

param maxResults

The maximum number of service results that ListServicesByNamespace returns in paginated output. When this parameter is used, ListServicesByNamespace only returns maxResults results in a single page along with a nextToken response element. The remaining results of the initial request can be seen by sending another ListServicesByNamespace request with the returned nextToken value. This value can be between 1 and 100. If this parameter isn't used, then ListServicesByNamespace returns up to 10 results and a nextToken value if applicable.

rtype

dict

returns

Response Syntax

{
    'serviceArns': [
        'string',
    ],
    'nextToken': 'string'
}

Response Structure

  • (dict) --

    • serviceArns (list) --

      The list of full ARN entries for each service that's associated with the specified namespace.

      • (string) --

    • nextToken (string) --

      The nextToken value to include in a future ListServicesByNamespace request. When the results of a ListServicesByNamespace request exceed maxResults , this value can be used to retrieve the next page of results. When there are no more results to return, this value is null .

CreateCluster (updated) Link ¶
Changes (request, response)
Request
{'serviceConnectDefaults': {'namespace': 'string'}}
Response
{'cluster': {'serviceConnectDefaults': {'namespace': 'string'}}}

Creates a new Amazon ECS cluster. By default, your account receives a default cluster when you launch your first container instance. However, you can create your own cluster with a unique name with the CreateCluster action.

Note

When you call the CreateCluster API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for your account. This is so that it can manage required resources in other Amazon Web Services services on your behalf. However, if the IAM user that makes the call doesn't have permissions to create the service-linked role, it isn't created. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide .

See also: AWS API Documentation

Request Syntax

client.create_cluster(
    clusterName='string',
    tags=[
        {
            'key': 'string',
            'value': 'string'
        },
    ],
    settings=[
        {
            'name': 'containerInsights',
            'value': 'string'
        },
    ],
    configuration={
        'executeCommandConfiguration': {
            'kmsKeyId': 'string',
            'logging': 'NONE'|'DEFAULT'|'OVERRIDE',
            'logConfiguration': {
                'cloudWatchLogGroupName': 'string',
                'cloudWatchEncryptionEnabled': True|False,
                's3BucketName': 'string',
                's3EncryptionEnabled': True|False,
                's3KeyPrefix': 'string'
            }
        }
    },
    capacityProviders=[
        'string',
    ],
    defaultCapacityProviderStrategy=[
        {
            'capacityProvider': 'string',
            'weight': 123,
            'base': 123
        },
    ],
    serviceConnectDefaults={
        'namespace': 'string'
    }
)
type clusterName

string

param clusterName

The name of your cluster. If you don't specify a name for your cluster, you create a cluster that's named default . Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed.

type tags

list

param tags

The metadata that you apply to the cluster to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

The following basic restrictions apply to tags:

  • Maximum number of tags per resource - 50

  • For each resource, each tag key must be unique, and each tag key can have only one value.

  • Maximum key length - 128 Unicode characters in UTF-8

  • Maximum value length - 256 Unicode characters in UTF-8

  • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

  • Tag keys and values are case-sensitive.

  • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

  • (dict) --

    The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

    The following basic restrictions apply to tags:

    • Maximum number of tags per resource - 50

    • For each resource, each tag key must be unique, and each tag key can have only one value.

    • Maximum key length - 128 Unicode characters in UTF-8

    • Maximum value length - 256 Unicode characters in UTF-8

    • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

    • Tag keys and values are case-sensitive.

    • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

    • key (string) --

      One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

    • value (string) --

      The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

type settings

list

param settings

The setting to use when creating a cluster. This parameter is used to turn on CloudWatch Container Insights for a cluster. If this value is specified, it overrides the containerInsights value set with PutAccountSetting or PutAccountSettingDefault .

  • (dict) --

    The settings to use when creating a cluster. This parameter is used to turn on CloudWatch Container Insights for a cluster.

    • name (string) --

      The name of the cluster setting. The only supported value is containerInsights .

    • value (string) --

      The value to set for the cluster setting. The supported values are enabled and disabled . If enabled is specified, CloudWatch Container Insights will be enabled for the cluster, otherwise it will be disabled unless the containerInsights account setting is enabled. If a cluster value is specified, it will override the containerInsights value set with PutAccountSetting or PutAccountSettingDefault .

type configuration

dict

param configuration

The execute command configuration for the cluster.

  • executeCommandConfiguration (dict) --

    The details of the execute command configuration.

    • kmsKeyId (string) --

      Specify an Key Management Service key ID to encrypt the data between the local client and the container.

    • logging (string) --

      The log setting to use for redirecting logs for your execute command results. The following log settings are available.

      • NONE : The execute command session is not logged.

      • DEFAULT : The awslogs configuration in the task definition is used. If no logging parameter is specified, it defaults to this value. If no awslogs log driver is configured in the task definition, the output won't be logged.

      • OVERRIDE : Specify the logging details as a part of logConfiguration . If the OVERRIDE logging option is specified, the logConfiguration is required.

    • logConfiguration (dict) --

      The log configuration for the results of the execute command actions. The logs can be sent to CloudWatch Logs or an Amazon S3 bucket. When logging=OVERRIDE is specified, a logConfiguration must be provided.

      • cloudWatchLogGroupName (string) --

        The name of the CloudWatch log group to send logs to.

        Note

        The CloudWatch log group must already be created.

      • cloudWatchEncryptionEnabled (boolean) --

        Determines whether to use encryption on the CloudWatch logs. If not specified, encryption will be disabled.

      • s3BucketName (string) --

        The name of the S3 bucket to send logs to.

        Note

        The S3 bucket must already be created.

      • s3EncryptionEnabled (boolean) --

        Determines whether to use encryption on the S3 logs. If not specified, encryption is not used.

      • s3KeyPrefix (string) --

        An optional folder in the S3 bucket to place logs in.

type capacityProviders

list

param capacityProviders

The short name of one or more capacity providers to associate with the cluster. A capacity provider must be associated with a cluster before it can be included as part of the default capacity provider strategy of the cluster or used in a capacity provider strategy when calling the CreateService or RunTask actions.

If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must be created but not associated with another cluster. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used.

The PutClusterCapacityProviders API operation is used to update the list of available capacity providers for a cluster after the cluster is created.

  • (string) --

type defaultCapacityProviderStrategy

list

param defaultCapacityProviderStrategy

The capacity provider strategy to set as the default for the cluster. After a default capacity provider strategy is set for a cluster, when you call the RunTask or CreateService APIs with no capacity provider strategy or launch type specified, the default capacity provider strategy for the cluster is used.

If a default capacity provider strategy isn't defined for a cluster when it was created, it can be defined later with the PutClusterCapacityProviders API operation.

  • (dict) --

    The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

    Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

    If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

    To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

    A capacity provider strategy may contain a maximum of 6 capacity providers.

    • capacityProvider (string) -- [REQUIRED]

      The short name of the capacity provider.

    • weight (integer) --

      The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

      If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

      An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

    • base (integer) --

      The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

type serviceConnectDefaults

dict

param serviceConnectDefaults

Use 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 .

  • namespace (string) -- [REQUIRED]

    The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace that's used when you create a service and don't specify a Service Connect configuration. Up to 1024 characters are allowed. The name is case-sensitive. The characters can't include hyphens (-), tilde (~), greater than (>), less than (<), or slash (/).

    If you enter an existing namespace name or ARN, then that namespace will be used. Any namespace type is supported. The namespace must be in this account and this Amazon Web Services Region.

    If you enter a new name, a Cloud Map namespace will be created. Amazon ECS creates a Cloud Map namespace with the "API calls" method of instance discovery only. This instance discovery method is the "HTTP" namespace type in the Command Line Interface. Other types of instance discovery aren't used by Service Connect.

    If you update the service with an empty string "" for the namespace name, the cluster configuration for Service Connect is removed. Note that the namespace will remain in Cloud Map and must be deleted separately.

    For more information about Cloud Map, see Working with Services in the Cloud Map Developer Guide .

rtype

dict

returns

Response Syntax

{
    'cluster': {
        'clusterArn': 'string',
        'clusterName': 'string',
        'configuration': {
            'executeCommandConfiguration': {
                'kmsKeyId': 'string',
                'logging': 'NONE'|'DEFAULT'|'OVERRIDE',
                'logConfiguration': {
                    'cloudWatchLogGroupName': 'string',
                    'cloudWatchEncryptionEnabled': True|False,
                    's3BucketName': 'string',
                    's3EncryptionEnabled': True|False,
                    's3KeyPrefix': 'string'
                }
            }
        },
        'status': 'string',
        'registeredContainerInstancesCount': 123,
        'runningTasksCount': 123,
        'pendingTasksCount': 123,
        'activeServicesCount': 123,
        'statistics': [
            {
                'name': 'string',
                'value': 'string'
            },
        ],
        'tags': [
            {
                'key': 'string',
                'value': 'string'
            },
        ],
        'settings': [
            {
                'name': 'containerInsights',
                'value': 'string'
            },
        ],
        'capacityProviders': [
            'string',
        ],
        'defaultCapacityProviderStrategy': [
            {
                'capacityProvider': 'string',
                'weight': 123,
                'base': 123
            },
        ],
        'attachments': [
            {
                'id': 'string',
                'type': 'string',
                'status': 'string',
                'details': [
                    {
                        'name': 'string',
                        'value': 'string'
                    },
                ]
            },
        ],
        'attachmentsStatus': 'string',
        'serviceConnectDefaults': {
            'namespace': 'string'
        }
    }
}

Response Structure

  • (dict) --

    • cluster (dict) --

      The full description of your new cluster.

      • clusterArn (string) --

        The 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 .

      • clusterName (string) --

        A user-generated string that you use to identify your cluster.

      • configuration (dict) --

        The execute command configuration for the cluster.

        • executeCommandConfiguration (dict) --

          The details of the execute command configuration.

          • kmsKeyId (string) --

            Specify an Key Management Service key ID to encrypt the data between the local client and the container.

          • logging (string) --

            The log setting to use for redirecting logs for your execute command results. The following log settings are available.

            • NONE : The execute command session is not logged.

            • DEFAULT : The awslogs configuration in the task definition is used. If no logging parameter is specified, it defaults to this value. If no awslogs log driver is configured in the task definition, the output won't be logged.

            • OVERRIDE : Specify the logging details as a part of logConfiguration . If the OVERRIDE logging option is specified, the logConfiguration is required.

          • logConfiguration (dict) --

            The log configuration for the results of the execute command actions. The logs can be sent to CloudWatch Logs or an Amazon S3 bucket. When logging=OVERRIDE is specified, a logConfiguration must be provided.

            • cloudWatchLogGroupName (string) --

              The name of the CloudWatch log group to send logs to.

              Note

              The CloudWatch log group must already be created.

            • cloudWatchEncryptionEnabled (boolean) --

              Determines whether to use encryption on the CloudWatch logs. If not specified, encryption will be disabled.

            • s3BucketName (string) --

              The name of the S3 bucket to send logs to.

              Note

              The S3 bucket must already be created.

            • s3EncryptionEnabled (boolean) --

              Determines whether to use encryption on the S3 logs. If not specified, encryption is not used.

            • s3KeyPrefix (string) --

              An optional folder in the S3 bucket to place logs in.

      • status (string) --

        The 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.

      • registeredContainerInstancesCount (integer) --

        The number of container instances registered into the cluster. This includes container instances in both ACTIVE and DRAINING status.

      • runningTasksCount (integer) --

        The number of tasks in the cluster that are in the RUNNING state.

      • pendingTasksCount (integer) --

        The number of tasks in the cluster that are in the PENDING state.

      • activeServicesCount (integer) --

        The number of services that are running on the cluster in an ACTIVE state. You can view these services with ListServices .

      • statistics (list) --

        Additional information about your clusters that are separated by launch type. They include the following:

        • runningEC2TasksCount

        • RunningFargateTasksCount

        • pendingEC2TasksCount

        • pendingFargateTasksCount

        • activeEC2ServiceCount

        • activeFargateServiceCount

        • drainingEC2ServiceCount

        • drainingFargateServiceCount

        • (dict) --

          A key-value pair object.

          • name (string) --

            The name of the key-value pair. For environment variables, this is the name of the environment variable.

          • value (string) --

            The value of the key-value pair. For environment variables, this is the value of the environment variable.

      • tags (list) --

        The metadata that you apply to the cluster to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

        The following basic restrictions apply to tags:

        • Maximum number of tags per resource - 50

        • For each resource, each tag key must be unique, and each tag key can have only one value.

        • Maximum key length - 128 Unicode characters in UTF-8

        • Maximum value length - 256 Unicode characters in UTF-8

        • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

        • Tag keys and values are case-sensitive.

        • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

        • (dict) --

          The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

          The following basic restrictions apply to tags:

          • Maximum number of tags per resource - 50

          • For each resource, each tag key must be unique, and each tag key can have only one value.

          • Maximum key length - 128 Unicode characters in UTF-8

          • Maximum value length - 256 Unicode characters in UTF-8

          • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

          • Tag keys and values are case-sensitive.

          • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

          • key (string) --

            One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

          • value (string) --

            The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

      • settings (list) --

        The settings for the cluster. This parameter indicates whether CloudWatch Container Insights is enabled or disabled for a cluster.

        • (dict) --

          The settings to use when creating a cluster. This parameter is used to turn on CloudWatch Container Insights for a cluster.

          • name (string) --

            The name of the cluster setting. The only supported value is containerInsights .

          • value (string) --

            The value to set for the cluster setting. The supported values are enabled and disabled . If enabled is specified, CloudWatch Container Insights will be enabled for the cluster, otherwise it will be disabled unless the containerInsights account setting is enabled. If a cluster value is specified, it will override the containerInsights value set with PutAccountSetting or PutAccountSettingDefault .

      • capacityProviders (list) --

        The capacity providers associated with the cluster.

        • (string) --

      • defaultCapacityProviderStrategy (list) --

        The 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.

        • (dict) --

          The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

          Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

          If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

          To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

          A capacity provider strategy may contain a maximum of 6 capacity providers.

          • capacityProvider (string) --

            The short name of the capacity provider.

          • weight (integer) --

            The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

            If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

            An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

          • base (integer) --

            The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

      • attachments (list) --

        The resources attached to a cluster. When using a capacity provider with a cluster, the capacity provider and associated resources are returned as cluster attachments.

        • (dict) --

          An object representing a container instance or task attachment.

          • id (string) --

            The unique identifier for the attachment.

          • type (string) --

            The type of the attachment, such as ElasticNetworkInterface .

          • status (string) --

            The status of the attachment. Valid values are PRECREATED , CREATED , ATTACHING , ATTACHED , DETACHING , DETACHED , DELETED , and FAILED .

          • details (list) --

            Details of the attachment. For elastic network interfaces, this includes the network interface ID, the MAC address, the subnet ID, and the private IPv4 address.

            • (dict) --

              A key-value pair object.

              • name (string) --

                The name of the key-value pair. For environment variables, this is the name of the environment variable.

              • value (string) --

                The value of the key-value pair. For environment variables, this is the value of the environment variable.

      • attachmentsStatus (string) --

        The 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.

      • serviceConnectDefaults (dict) --

        Use 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 .

        • namespace (string) --

          The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace. When you create a service and don't specify a Service Connect configuration, this namespace is used.

CreateService (updated) Link ¶
Changes (request, response)
Request
{'serviceConnectConfiguration': {'enabled': 'boolean',
                                 'logConfiguration': {'logDriver': 'json-file '
                                                                   '| syslog | '
                                                                   'journald | '
                                                                   'gelf | '
                                                                   'fluentd | '
                                                                   'awslogs | '
                                                                   'splunk | '
                                                                   'awsfirelens',
                                                      'options': {'string': 'string'},
                                                      'secretOptions': [{'name': 'string',
                                                                         'valueFrom': 'string'}]},
                                 'namespace': 'string',
                                 'services': [{'clientAliases': [{'dnsName': 'string',
                                                                  'port': 'integer'}],
                                               'discoveryName': 'string',
                                               'ingressPortOverride': 'integer',
                                               'portName': 'string'}]}}
Response
{'service': {'deployments': {'serviceConnectConfiguration': {'enabled': 'boolean',
                                                             'logConfiguration': {'logDriver': 'json-file '
                                                                                               '| '
                                                                                               'syslog '
                                                                                               '| '
                                                                                               'journald '
                                                                                               '| '
                                                                                               'gelf '
                                                                                               '| '
                                                                                               'fluentd '
                                                                                               '| '
                                                                                               'awslogs '
                                                                                               '| '
                                                                                               'splunk '
                                                                                               '| '
                                                                                               'awsfirelens',
                                                                                  'options': {'string': 'string'},
                                                                                  'secretOptions': [{'name': 'string',
                                                                                                     'valueFrom': 'string'}]},
                                                             'namespace': 'string',
                                                             'services': [{'clientAliases': [{'dnsName': 'string',
                                                                                              'port': 'integer'}],
                                                                           'discoveryName': 'string',
                                                                           'ingressPortOverride': 'integer',
                                                                           'portName': 'string'}]},
                             'serviceConnectResources': [{'discoveryArn': 'string',
                                                          'discoveryName': 'string'}]}}}

Runs and maintains your desired number of tasks from a specified task definition. If the number of tasks running in a service drops below the desiredCount , Amazon ECS runs another copy of the task in the specified cluster. To update an existing service, see the UpdateService action.

In addition to maintaining the desired count of tasks in your service, you can optionally run your service behind one or more load balancers. The load balancers distribute traffic across the tasks that are associated with the service. For more information, see Service load balancing in the Amazon Elastic Container Service Developer Guide .

Tasks for services that don't use a load balancer are considered healthy if they're in the RUNNING state. Tasks for services that use a load balancer are considered healthy if they're in the RUNNING state and are reported as healthy by the load balancer.

There are two service scheduler strategies available:

  • REPLICA - The replica scheduling strategy places and maintains your desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. For more information, see Service scheduler concepts in the Amazon Elastic Container Service Developer Guide .

  • DAEMON - The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks. It also stops tasks that don't meet the placement constraints. When using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. For more information, see Service scheduler concepts in the Amazon Elastic Container Service Developer Guide .

You can optionally specify a deployment configuration for your service. The deployment is initiated by changing properties. For example, the deployment might be initiated by the task definition or by your desired count of a service. This is done with an UpdateService operation. The default value for a replica service for minimumHealthyPercent is 100%. The default value for a daemon service for minimumHealthyPercent is 0%.

If a service uses the ECS deployment controller, the minimum healthy percent represents a lower limit on the number of tasks in a service that must remain in the RUNNING state during a deployment. Specifically, it represents it as a percentage of your desired number of tasks (rounded up to the nearest integer). This happens when any of your container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. Using this parameter, you can deploy without using additional cluster capacity. For example, if you set your service to have desired number of four tasks and a minimum healthy percent of 50%, the scheduler might stop two existing tasks to free up cluster capacity before starting two new tasks. If they're in the RUNNING state, tasks for services that don't use a load balancer are considered healthy . If they're in the RUNNING state and reported as healthy by the load balancer, tasks for services that do use a load balancer are considered healthy . The default value for minimum healthy percent is 100%.

If a service uses the ECS deployment controller, the maximum percent parameter represents an upper limit on the number of tasks in a service that are allowed in the RUNNING or PENDING state during a deployment. Specifically, it represents it as a percentage of the desired number of tasks (rounded down to the nearest integer). This happens when any of your container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. Using this parameter, you can define the deployment batch size. For example, if your service has a desired number of four tasks and a maximum percent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default value for maximum percent is 200%.

If a service uses either the CODE_DEPLOY or EXTERNAL deployment controller types and tasks that use the EC2 launch type, the minimum healthy percent and maximum percent values are used only to define the lower and upper limit on the number of the tasks in the service that remain in the RUNNING state. This is while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the minimum healthy percent and maximum percent values aren't used. This is the case even if they're currently visible when describing your service.

When creating a service that uses the EXTERNAL deployment controller, you can specify only parameters that aren't controlled at the task set level. The only required parameter is the service name. You control your services using the CreateTaskSet operation. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide .

When the service scheduler launches new tasks, it determines task placement. For information about task placement and task placement strategies, see Amazon ECS task placement in the Amazon Elastic Container Service Developer Guide .

See also: AWS API Documentation

Request Syntax

client.create_service(
    cluster='string',
    serviceName='string',
    taskDefinition='string',
    loadBalancers=[
        {
            'targetGroupArn': 'string',
            'loadBalancerName': 'string',
            'containerName': 'string',
            'containerPort': 123
        },
    ],
    serviceRegistries=[
        {
            'registryArn': 'string',
            'port': 123,
            'containerName': 'string',
            'containerPort': 123
        },
    ],
    desiredCount=123,
    clientToken='string',
    launchType='EC2'|'FARGATE'|'EXTERNAL',
    capacityProviderStrategy=[
        {
            'capacityProvider': 'string',
            'weight': 123,
            'base': 123
        },
    ],
    platformVersion='string',
    role='string',
    deploymentConfiguration={
        'deploymentCircuitBreaker': {
            'enable': True|False,
            'rollback': True|False
        },
        'maximumPercent': 123,
        'minimumHealthyPercent': 123
    },
    placementConstraints=[
        {
            'type': 'distinctInstance'|'memberOf',
            'expression': 'string'
        },
    ],
    placementStrategy=[
        {
            'type': 'random'|'spread'|'binpack',
            'field': 'string'
        },
    ],
    networkConfiguration={
        'awsvpcConfiguration': {
            'subnets': [
                'string',
            ],
            'securityGroups': [
                'string',
            ],
            'assignPublicIp': 'ENABLED'|'DISABLED'
        }
    },
    healthCheckGracePeriodSeconds=123,
    schedulingStrategy='REPLICA'|'DAEMON',
    deploymentController={
        'type': 'ECS'|'CODE_DEPLOY'|'EXTERNAL'
    },
    tags=[
        {
            'key': 'string',
            'value': 'string'
        },
    ],
    enableECSManagedTags=True|False,
    propagateTags='TASK_DEFINITION'|'SERVICE'|'NONE',
    enableExecuteCommand=True|False,
    serviceConnectConfiguration={
        'enabled': True|False,
        'namespace': 'string',
        'services': [
            {
                'portName': 'string',
                'discoveryName': 'string',
                'clientAliases': [
                    {
                        'port': 123,
                        'dnsName': 'string'
                    },
                ],
                'ingressPortOverride': 123
            },
        ],
        'logConfiguration': {
            'logDriver': 'json-file'|'syslog'|'journald'|'gelf'|'fluentd'|'awslogs'|'splunk'|'awsfirelens',
            'options': {
                'string': 'string'
            },
            'secretOptions': [
                {
                    'name': 'string',
                    'valueFrom': 'string'
                },
            ]
        }
    }
)
type cluster

string

param cluster

The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.

type serviceName

string

param serviceName

[REQUIRED]

The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster, but you can have similarly named services in multiple clusters within a Region or across multiple Regions.

type taskDefinition

string

param taskDefinition

The family and revision (family:revision ) or full ARN of the task definition to run in your service. If a revision isn't specified, the latest ACTIVE revision is used.

A task definition must be specified if the service uses either the ECS or CODE_DEPLOY deployment controllers.

type loadBalancers

list

param loadBalancers

A load balancer object representing the load balancers to use with your service. For more information, see Service load balancing in the Amazon Elastic Container Service Developer Guide .

If the service uses the rolling update (ECS ) deployment controller and using either an Application Load Balancer or Network Load Balancer, you must specify one or more target group ARNs to attach to the service. The service-linked role is required for services that use multiple target groups. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide .

If the service uses the CODE_DEPLOY deployment controller, the service is required to use either an Application Load Balancer or Network Load Balancer. When creating an CodeDeploy deployment group, you specify two target groups (referred to as a targetGroupPair ). During a deployment, CodeDeploy determines which task set in your service has the status PRIMARY , and it associates one target group with it. Then, it also associates the other target group with the replacement task set. The load balancer can also have up to two listeners: a required listener for production traffic and an optional listener that you can use to perform validation tests with Lambda functions before routing production traffic to it.

If you use the CODE_DEPLOY deployment controller, these values can be changed when updating the service.

For Application Load Balancers and Network Load Balancers, this object must contain the load balancer target group ARN, the container name, and the container port to access from the load balancer. The container name must be as it appears in a container definition. The load balancer name parameter must be omitted. When a task from this service is placed on a container instance, the container instance and port combination is registered as a target in the target group that's specified here.

For Classic Load Balancers, this object must contain the load balancer name, the container name , and the container port to access from the load balancer. The container name must be as it appears in a container definition. The target group ARN parameter must be omitted. When a task from this service is placed on a container instance, the container instance is registered with the load balancer that's specified here.

Services with tasks that use the awsvpc network mode (for example, those with the Fargate launch type) only support Application Load Balancers and Network Load Balancers. Classic Load Balancers aren't supported. Also, when you create any target groups for these services, you must choose ip as the target type, not instance . This is because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance.

  • (dict) --

    The load balancer configuration to use with a service or task set.

    For specific notes and restrictions regarding the use of load balancers with services and task sets, see the CreateService and CreateTaskSet actions.

    When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers.

    We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration.

    A service-linked role is required for services that use multiple target groups. For more information, see Using service-linked roles in the Amazon Elastic Container Service Developer Guide .

    • targetGroupArn (string) --

      The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set.

      A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you're using a Classic Load Balancer, omit the target group ARN.

      For services using the ECS deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide .

      For services using the CODE_DEPLOY deployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide .

      Warning

      If your service's task definition uses the awsvpc network mode, you must choose ip as the target type, not instance . Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.

    • loadBalancerName (string) --

      The name of the load balancer to associate with the Amazon ECS service or task set.

      A load balancer name is only specified when using a Classic Load Balancer. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.

    • containerName (string) --

      The name of the container (as it appears in a container definition) to associate with the load balancer.

    • containerPort (integer) --

      The port on the container to associate with the load balancer. This port must correspond to a containerPort in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on the hostPort of the port mapping.

type serviceRegistries

list

param serviceRegistries

The details of the service discovery registry to associate with this service. For more information, see Service discovery .

Note

Each service may be associated with one service registry. Multiple service registries for each service isn't supported.

  • (dict) --

    The details for the service registry.

    Each service may be associated with one service registry. Multiple service registries for each service are not supported.

    When you add, update, or remove the service registries configuration, Amazon ECS starts a new deployment. New tasks are registered and deregistered to the updated service registry configuration.

    • registryArn (string) --

      The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is Cloud Map. For more information, see CreateService .

    • port (integer) --

      The port value used if your service discovery service specified an SRV record. This field might be used if both the awsvpc network mode and SRV records are used.

    • containerName (string) --

      The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition that your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

    • containerPort (integer) --

      The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

type desiredCount

integer

param desiredCount

The number of instantiations of the specified task definition to place and keep running on your cluster.

This is required if schedulingStrategy is REPLICA or isn't specified. If schedulingStrategy is DAEMON then this isn't required.

type clientToken

string

param clientToken

An identifier that you provide to ensure the idempotency of the request. It must be unique and is case sensitive. Up to 32 ASCII characters are allowed.

type launchType

string

param launchType

The infrastructure that you run your service on. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide .

The FARGATE launch type runs your tasks on Fargate On-Demand infrastructure.

Note

Fargate Spot infrastructure is available for use but a capacity provider strategy must be used. For more information, see Fargate capacity providers in the Amazon ECS User Guide for Fargate .

The EC2 launch type runs your tasks on Amazon EC2 instances registered to your cluster.

The EXTERNAL launch type runs your tasks on your on-premises server or virtual machine (VM) capacity registered to your cluster.

A service can use either a launch type or a capacity provider strategy. If a launchType is specified, the capacityProviderStrategy parameter must be omitted.

type capacityProviderStrategy

list

param capacityProviderStrategy

The capacity provider strategy to use for the service.

If a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for the cluster is used.

A capacity provider strategy may contain a maximum of 6 capacity providers.

  • (dict) --

    The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

    Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

    If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

    To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

    A capacity provider strategy may contain a maximum of 6 capacity providers.

    • capacityProvider (string) -- [REQUIRED]

      The short name of the capacity provider.

    • weight (integer) --

      The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

      If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

      An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

    • base (integer) --

      The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

type platformVersion

string

param platformVersion

The platform version that your tasks in the service are running on. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the LATEST platform version is used. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide .

type role

string

param role

The name or full Amazon Resource Name (ARN) of the IAM role that allows Amazon ECS to make calls to your load balancer on your behalf. This parameter is only permitted if you are using a load balancer with your service and your task definition doesn't use the awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter.

Warning

If your account has already created the Amazon ECS service-linked role, that role is used for your service unless you specify a role here. The service-linked role is required if your task definition uses the awsvpc network mode or if the service is configured to use service discovery, an external deployment controller, multiple target groups, or Elastic Inference accelerators in which case you don't specify a role here. For more information, see Using service-linked roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide .

If your specified role has a path other than / , then you must either specify the full role ARN (this is recommended) or prefix the role name with the path. For example, if a role with the name bar has a path of /foo/ then you would specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide .

type deploymentConfiguration

dict

param deploymentConfiguration

Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.

  • deploymentCircuitBreaker (dict) --

    Note

    The deployment circuit breaker can only be used for services using the rolling update (ECS ) deployment type.

    The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

    • enable (boolean) -- [REQUIRED]

      Determines whether to use the deployment circuit breaker logic for the service.

    • rollback (boolean) -- [REQUIRED]

      Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

  • maximumPercent (integer) --

    If a service is using the rolling update (ECS ) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default maximumPercent value for a service using the REPLICA service scheduler is 200%.

    If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.

  • minimumHealthyPercent (integer) --

    If a service is using the rolling update (ECS ) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.

    For services that do not use a load balancer, the following should be noted:

    • A service is considered healthy if all essential containers within the tasks in the service pass their health checks.

    • If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches a RUNNING state before the task is counted towards the minimum healthy percent total.

    • If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings.

    For services are that do use a load balancer, the following should be noted:

    • If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

    • If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

    If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

type placementConstraints

list

param placementConstraints

An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.

  • (dict) --

    An object representing a constraint on task placement. For more information, see Task placement constraints in the Amazon Elastic Container Service Developer Guide .

    Note

    If you're using the Fargate launch type, task placement constraints aren't supported.

    • type (string) --

      The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to restrict the selection to a group of valid candidates.

    • expression (string) --

      A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is distinctInstance . For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide .

type placementStrategy

list

param placementStrategy

The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules for each service.

  • (dict) --

    The task placement strategy for a task or service. For more information, see Task placement strategies in the Amazon Elastic Container Service Developer Guide .

    • type (string) --

      The type of placement strategy. The random placement strategy randomly places tasks on available candidates. The spread placement strategy spreads placement across available candidates evenly based on the field parameter. The binpack strategy places tasks on available candidates that have the least available amount of the resource that's specified with the field parameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.

    • field (string) --

      The field to apply the placement strategy against. For the spread placement strategy, valid values are instanceId (or host , which has the same effect), or any platform or custom attribute that's applied to a container instance, such as attribute:ecs.availability-zone . For the binpack placement strategy, valid values are cpu and memory . For the random placement strategy, this field is not used.

type networkConfiguration

dict

param networkConfiguration

The network configuration for the service. This parameter is required for task definitions that use the awsvpc network mode to receive their own elastic network interface, and it isn't supported for other network modes. For more information, see Task networking in the Amazon Elastic Container Service Developer Guide .

  • awsvpcConfiguration (dict) --

    The VPC subnets and security groups that are associated with a task.

    Note

    All specified subnets and security groups must be from the same VPC.

    • subnets (list) -- [REQUIRED]

      The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

      Note

      All specified subnets must be from the same VPC.

      • (string) --

    • securityGroups (list) --

      The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

      Note

      All specified security groups must be from the same VPC.

      • (string) --

    • assignPublicIp (string) --

      Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

type healthCheckGracePeriodSeconds

integer

param healthCheckGracePeriodSeconds

The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started. This is only used when your service is configured to use a load balancer. If your service has a load balancer defined and you don't specify a health check grace period value, the default value of 0 is used.

If you do not use an Elastic Load Balancing, we recommend that you use the startPeriod in the task definition health check parameters. For more information, see Health check .

If your service's tasks take a while to start and respond to Elastic Load Balancing health checks, you can specify a health check grace period of up to 2,147,483,647 seconds (about 69 years). During that time, the Amazon ECS service scheduler ignores health check status. This grace period can prevent the service scheduler from marking tasks as unhealthy and stopping them before they have time to come up.

type schedulingStrategy

string

param schedulingStrategy

The scheduling strategy to use for the service. For more information, see Services .

There are two service scheduler strategies available:

  • REPLICA -The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service uses the CODE_DEPLOY or EXTERNAL deployment controller types.

  • DAEMON -The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that don't meet the placement constraints. When you're using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies.

Note

Tasks using the Fargate launch type or the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.

type deploymentController

dict

param deploymentController

The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is used.

  • type (string) -- [REQUIRED]

    The deployment controller type to use.

    There are three deployment controller types available:

    ECS

    The rolling update (ECS ) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration .

    CODE_DEPLOY

    The blue/green (CODE_DEPLOY ) deployment type uses the blue/green deployment model powered by CodeDeploy, which allows you to verify a new deployment of a service before sending production traffic to it.

    EXTERNAL

    The external (EXTERNAL ) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.

type tags

list

param tags

The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. When a service is deleted, the tags are deleted as well.

The following basic restrictions apply to tags:

  • Maximum number of tags per resource - 50

  • For each resource, each tag key must be unique, and each tag key can have only one value.

  • Maximum key length - 128 Unicode characters in UTF-8

  • Maximum value length - 256 Unicode characters in UTF-8

  • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

  • Tag keys and values are case-sensitive.

  • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

  • (dict) --

    The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

    The following basic restrictions apply to tags:

    • Maximum number of tags per resource - 50

    • For each resource, each tag key must be unique, and each tag key can have only one value.

    • Maximum key length - 128 Unicode characters in UTF-8

    • Maximum value length - 256 Unicode characters in UTF-8

    • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

    • Tag keys and values are case-sensitive.

    • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

    • key (string) --

      One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

    • value (string) --

      The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

type enableECSManagedTags

boolean

param enableECSManagedTags

Specifies whether to turn on Amazon ECS managed tags for the tasks within the service. For more information, see Tagging your Amazon ECS resources in the Amazon Elastic Container Service Developer Guide .

type propagateTags

string

param propagateTags

Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags aren't propagated. Tags can only be propagated to the task during task creation. To add tags to a task after task creation, use the TagResource API action.

type enableExecuteCommand

boolean

param enableExecuteCommand

Determines whether the execute command functionality is enabled for the service. If true , this enables execute command functionality on all containers in the service tasks.

type serviceConnectConfiguration

dict

param serviceConnectConfiguration

The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace.

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 .

  • enabled (boolean) -- [REQUIRED]

    Specifies whether to use Service Connect with this service.

  • namespace (string) --

    The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace for use with Service Connect. The namespace must be in the same Amazon Web Services Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about Cloud Map, see Working with Services in the Cloud Map Developer Guide .

  • services (list) --

    The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. You can specify up to X (30?) objects per Amazon ECS service.

    This field is not required for a "client" Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means.

    An object selects a port from the task definition, assigns a name for the Cloud Map service, and a list of aliases (endpoints) and ports for client applications to refer to this service.

    • (dict) --

      The Service Connect service object configuration. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

      • portName (string) -- [REQUIRED]

        The portName must match the name of one of the portMappings from all the containers in the task definition of this Amazon ECS service.

      • discoveryName (string) --

        The discoveryName is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

        If this field isn't specified, portName is used.

      • clientAliases (list) --

        The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1.

        Each alias ("endpoint") is a fully-qualified name and port number that other Amazon ECS tasks ("clients") can use to connect to this service.

        Each name and port mapping must be unique within the namespace.

        For each ServiceConnectService , you must provide at least one clientAlias with one port .

        • (dict) --

          Each alias ("endpoint") is a fully-qualified name and port number that other tasks ("clients") can use to connect to this service.

          Each name and port mapping must be unique within the namespace.

          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 .

          • port (integer) -- [REQUIRED]

            The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace.

            To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

          • dnsName (string) --

            The dnsName is the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. Up to 127 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). A hyphen can't be the first character.

            If this parameter isn't specified, the default value of discoveryName.namespace is used. If the discoveryName isn't specified, the portName.namespace from the task definition is used.

            To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names are database , db , or the lowercase name of a database, such as mysql or redis . For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

      • ingressPortOverride (integer) --

        The port number for the Service Connect proxy to listen on.

        Use the value of this field to bypass the proxy for traffic on the port number specified in the named portMapping in the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service.

        In awsvpc mode and Fargate, the default value is the container port number. The container port number is in the portMapping in the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy.

  • logConfiguration (dict) --

    The log configuration for the container. This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to ` docker run https://docs.docker.com/engine/reference/commandline/run/`__ .

    By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation.

    Understand the following when specifying a log configuration for your containers.

    • Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon (shown in the valid values below). Additional log drivers may be available in future releases of the Amazon ECS container agent.

    • This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.

    • For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide .

    • For tasks that are on Fargate, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.

    • logDriver (string) -- [REQUIRED]

      The log driver to use for the container.

      For tasks on Fargate, the supported log drivers are awslogs , splunk , and awsfirelens .

      For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs , fluentd , gelf , json-file , journald , logentries ,``syslog`` , splunk , and awsfirelens .

      For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide .

      For more information about using the awsfirelens log driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide .

      Note

      If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.

    • options (dict) --

      The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

      • (string) --

        • (string) --

    • secretOptions (list) --

      The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

      • (dict) --

        An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

        • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

        • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

        For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

        • name (string) -- [REQUIRED]

          The name of the secret.

        • valueFrom (string) -- [REQUIRED]

          The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

          For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

          Note

          If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

rtype

dict

returns

Response Syntax

{
    'service': {
        'serviceArn': 'string',
        'serviceName': 'string',
        'clusterArn': 'string',
        'loadBalancers': [
            {
                'targetGroupArn': 'string',
                'loadBalancerName': 'string',
                'containerName': 'string',
                'containerPort': 123
            },
        ],
        'serviceRegistries': [
            {
                'registryArn': 'string',
                'port': 123,
                'containerName': 'string',
                'containerPort': 123
            },
        ],
        'status': 'string',
        'desiredCount': 123,
        'runningCount': 123,
        'pendingCount': 123,
        'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
        'capacityProviderStrategy': [
            {
                'capacityProvider': 'string',
                'weight': 123,
                'base': 123
            },
        ],
        'platformVersion': 'string',
        'platformFamily': 'string',
        'taskDefinition': 'string',
        'deploymentConfiguration': {
            'deploymentCircuitBreaker': {
                'enable': True|False,
                'rollback': True|False
            },
            'maximumPercent': 123,
            'minimumHealthyPercent': 123
        },
        'taskSets': [
            {
                'id': 'string',
                'taskSetArn': 'string',
                'serviceArn': 'string',
                'clusterArn': 'string',
                'startedBy': 'string',
                'externalId': 'string',
                'status': 'string',
                'taskDefinition': 'string',
                'computedDesiredCount': 123,
                'pendingCount': 123,
                'runningCount': 123,
                'createdAt': datetime(2015, 1, 1),
                'updatedAt': datetime(2015, 1, 1),
                'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
                'capacityProviderStrategy': [
                    {
                        'capacityProvider': 'string',
                        'weight': 123,
                        'base': 123
                    },
                ],
                'platformVersion': 'string',
                'platformFamily': 'string',
                'networkConfiguration': {
                    'awsvpcConfiguration': {
                        'subnets': [
                            'string',
                        ],
                        'securityGroups': [
                            'string',
                        ],
                        'assignPublicIp': 'ENABLED'|'DISABLED'
                    }
                },
                'loadBalancers': [
                    {
                        'targetGroupArn': 'string',
                        'loadBalancerName': 'string',
                        'containerName': 'string',
                        'containerPort': 123
                    },
                ],
                'serviceRegistries': [
                    {
                        'registryArn': 'string',
                        'port': 123,
                        'containerName': 'string',
                        'containerPort': 123
                    },
                ],
                'scale': {
                    'value': 123.0,
                    'unit': 'PERCENT'
                },
                'stabilityStatus': 'STEADY_STATE'|'STABILIZING',
                'stabilityStatusAt': datetime(2015, 1, 1),
                'tags': [
                    {
                        'key': 'string',
                        'value': 'string'
                    },
                ]
            },
        ],
        'deployments': [
            {
                'id': 'string',
                'status': 'string',
                'taskDefinition': 'string',
                'desiredCount': 123,
                'pendingCount': 123,
                'runningCount': 123,
                'failedTasks': 123,
                'createdAt': datetime(2015, 1, 1),
                'updatedAt': datetime(2015, 1, 1),
                'capacityProviderStrategy': [
                    {
                        'capacityProvider': 'string',
                        'weight': 123,
                        'base': 123
                    },
                ],
                'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
                'platformVersion': 'string',
                'platformFamily': 'string',
                'networkConfiguration': {
                    'awsvpcConfiguration': {
                        'subnets': [
                            'string',
                        ],
                        'securityGroups': [
                            'string',
                        ],
                        'assignPublicIp': 'ENABLED'|'DISABLED'
                    }
                },
                'rolloutState': 'COMPLETED'|'FAILED'|'IN_PROGRESS',
                'rolloutStateReason': 'string',
                'serviceConnectConfiguration': {
                    'enabled': True|False,
                    'namespace': 'string',
                    'services': [
                        {
                            'portName': 'string',
                            'discoveryName': 'string',
                            'clientAliases': [
                                {
                                    'port': 123,
                                    'dnsName': 'string'
                                },
                            ],
                            'ingressPortOverride': 123
                        },
                    ],
                    'logConfiguration': {
                        'logDriver': 'json-file'|'syslog'|'journald'|'gelf'|'fluentd'|'awslogs'|'splunk'|'awsfirelens',
                        'options': {
                            'string': 'string'
                        },
                        'secretOptions': [
                            {
                                'name': 'string',
                                'valueFrom': 'string'
                            },
                        ]
                    }
                },
                'serviceConnectResources': [
                    {
                        'discoveryName': 'string',
                        'discoveryArn': 'string'
                    },
                ]
            },
        ],
        'roleArn': 'string',
        'events': [
            {
                'id': 'string',
                'createdAt': datetime(2015, 1, 1),
                'message': 'string'
            },
        ],
        'createdAt': datetime(2015, 1, 1),
        'placementConstraints': [
            {
                'type': 'distinctInstance'|'memberOf',
                'expression': 'string'
            },
        ],
        'placementStrategy': [
            {
                'type': 'random'|'spread'|'binpack',
                'field': 'string'
            },
        ],
        'networkConfiguration': {
            'awsvpcConfiguration': {
                'subnets': [
                    'string',
                ],
                'securityGroups': [
                    'string',
                ],
                'assignPublicIp': 'ENABLED'|'DISABLED'
            }
        },
        'healthCheckGracePeriodSeconds': 123,
        'schedulingStrategy': 'REPLICA'|'DAEMON',
        'deploymentController': {
            'type': 'ECS'|'CODE_DEPLOY'|'EXTERNAL'
        },
        'tags': [
            {
                'key': 'string',
                'value': 'string'
            },
        ],
        'createdBy': 'string',
        'enableECSManagedTags': True|False,
        'propagateTags': 'TASK_DEFINITION'|'SERVICE'|'NONE',
        'enableExecuteCommand': True|False
    }
}

Response Structure

  • (dict) --

    • service (dict) --

      The full description of your service following the create call.

      A service will return either a capacityProviderStrategy or launchType parameter, but not both, depending where one was specified when it was created.

      If a service is using the ECS deployment controller, the deploymentController and taskSets parameters will not be returned.

      if the service uses the CODE_DEPLOY deployment controller, the deploymentController , taskSets and deployments parameters will be returned, however the deployments parameter will be an empty list.

      • serviceArn (string) --

        The ARN that identifies the service. For more information about the ARN format, see Amazon Resource Name (ARN) in the Amazon ECS Developer Guide .

      • serviceName (string) --

        The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster. However, you can have similarly named services in multiple clusters within a Region or across multiple Regions.

      • clusterArn (string) --

        The Amazon Resource Name (ARN) of the cluster that hosts the service.

      • loadBalancers (list) --

        A list of Elastic Load Balancing load balancer objects. It contains the load balancer name, the container name, and the container port to access from the load balancer. The container name is as it appears in a container definition.

        • (dict) --

          The load balancer configuration to use with a service or task set.

          For specific notes and restrictions regarding the use of load balancers with services and task sets, see the CreateService and CreateTaskSet actions.

          When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers.

          We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration.

          A service-linked role is required for services that use multiple target groups. For more information, see Using service-linked roles in the Amazon Elastic Container Service Developer Guide .

          • targetGroupArn (string) --

            The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set.

            A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you're using a Classic Load Balancer, omit the target group ARN.

            For services using the ECS deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide .

            For services using the CODE_DEPLOY deployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide .

            Warning

            If your service's task definition uses the awsvpc network mode, you must choose ip as the target type, not instance . Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.

          • loadBalancerName (string) --

            The name of the load balancer to associate with the Amazon ECS service or task set.

            A load balancer name is only specified when using a Classic Load Balancer. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.

          • containerName (string) --

            The name of the container (as it appears in a container definition) to associate with the load balancer.

          • containerPort (integer) --

            The port on the container to associate with the load balancer. This port must correspond to a containerPort in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on the hostPort of the port mapping.

      • serviceRegistries (list) --

        The details for the service discovery registries to assign to this service. For more information, see Service Discovery .

        • (dict) --

          The details for the service registry.

          Each service may be associated with one service registry. Multiple service registries for each service are not supported.

          When you add, update, or remove the service registries configuration, Amazon ECS starts a new deployment. New tasks are registered and deregistered to the updated service registry configuration.

          • registryArn (string) --

            The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is Cloud Map. For more information, see CreateService .

          • port (integer) --

            The port value used if your service discovery service specified an SRV record. This field might be used if both the awsvpc network mode and SRV records are used.

          • containerName (string) --

            The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition that your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

          • containerPort (integer) --

            The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

      • status (string) --

        The status of the service. The valid values are ACTIVE , DRAINING , or INACTIVE .

      • desiredCount (integer) --

        The desired number of instantiations of the task definition to keep running on the service. This value is specified when the service is created with CreateService , and it can be modified with UpdateService .

      • runningCount (integer) --

        The number of tasks in the cluster that are in the RUNNING state.

      • pendingCount (integer) --

        The number of tasks in the cluster that are in the PENDING state.

      • launchType (string) --

        The launch type the service is using. When using the DescribeServices API, this field is omitted if the service was created using a capacity provider strategy.

      • capacityProviderStrategy (list) --

        The capacity provider strategy the service uses. When using the DescribeServices API, this field is omitted if the service was created using a launch type.

        • (dict) --

          The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

          Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

          If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

          To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

          A capacity provider strategy may contain a maximum of 6 capacity providers.

          • capacityProvider (string) --

            The short name of the capacity provider.

          • weight (integer) --

            The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

            If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

            An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

          • base (integer) --

            The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

      • platformVersion (string) --

        The platform version to run your service on. A platform version is only specified for tasks that are hosted on Fargate. If one isn't specified, the LATEST platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide .

      • platformFamily (string) --

        The operating system that your tasks in the service run on. A platform family is specified only for tasks using the Fargate launch type.

        All tasks that run as part of this service must use the same platformFamily value as the service (for example, LINUX ).

      • taskDefinition (string) --

        The task definition to use for tasks in the service. This value is specified when the service is created with CreateService , and it can be modified with UpdateService .

      • deploymentConfiguration (dict) --

        Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.

        • deploymentCircuitBreaker (dict) --

          Note

          The deployment circuit breaker can only be used for services using the rolling update (ECS ) deployment type.

          The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

          • enable (boolean) --

            Determines whether to use the deployment circuit breaker logic for the service.

          • rollback (boolean) --

            Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

        • maximumPercent (integer) --

          If a service is using the rolling update (ECS ) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default maximumPercent value for a service using the REPLICA service scheduler is 200%.

          If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.

        • minimumHealthyPercent (integer) --

          If a service is using the rolling update (ECS ) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.

          For services that do not use a load balancer, the following should be noted:

          • A service is considered healthy if all essential containers within the tasks in the service pass their health checks.

          • If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches a RUNNING state before the task is counted towards the minimum healthy percent total.

          • If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings.

          For services are that do use a load balancer, the following should be noted:

          • If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

          • If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

          If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

      • taskSets (list) --

        Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.

        • (dict) --

          Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.

          • id (string) --

            The ID of the task set.

          • taskSetArn (string) --

            The Amazon Resource Name (ARN) of the task set.

          • serviceArn (string) --

            The Amazon Resource Name (ARN) of the service the task set exists in.

          • clusterArn (string) --

            The Amazon Resource Name (ARN) of the cluster that the service that hosts the task set exists in.

          • startedBy (string) --

            The tag specified when a task set is started. If an CodeDeploy deployment created the task set, the startedBy parameter is CODE_DEPLOY . If an external deployment created the task set, the startedBy field isn't used.

          • externalId (string) --

            The external ID associated with the task set.

            If an CodeDeploy deployment created a task set, the externalId parameter contains the CodeDeploy deployment ID.

            If a task set is created for an external deployment and is associated with a service discovery registry, the externalId parameter contains the ECS_TASK_SET_EXTERNAL_ID Cloud Map attribute.

          • status (string) --

            The status of the task set. The following describes each state.

            PRIMARY

            The task set is serving production traffic.

            ACTIVE

            The task set isn't serving production traffic.

            DRAINING

            The tasks in the task set are being stopped, and their corresponding targets are being deregistered from their target group.

          • taskDefinition (string) --

            The task definition that the task set is using.

          • computedDesiredCount (integer) --

            The computed desired count for the task set. This is calculated by multiplying the service's desiredCount by the task set's scale percentage. The result is always rounded up. For example, if the computed desired count is 1.2, it rounds up to 2 tasks.

          • pendingCount (integer) --

            The number of tasks in the task set that are in the PENDING status during a deployment. A task in the PENDING state is preparing to enter the RUNNING state. A task set enters the PENDING status when it launches for the first time or when it's restarted after being in the STOPPED state.

          • runningCount (integer) --

            The number of tasks in the task set that are in the RUNNING status during a deployment. A task in the RUNNING state is running and ready for use.

          • createdAt (datetime) --

            The Unix timestamp for the time when the task set was created.

          • updatedAt (datetime) --

            The Unix timestamp for the time when the task set was last updated.

          • launchType (string) --

            The launch type the tasks in the task set are using. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide .

          • capacityProviderStrategy (list) --

            The capacity provider strategy that are associated with the task set.

            • (dict) --

              The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

              Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

              If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

              To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

              A capacity provider strategy may contain a maximum of 6 capacity providers.

              • capacityProvider (string) --

                The short name of the capacity provider.

              • weight (integer) --

                The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

                If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

                An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

              • base (integer) --

                The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

          • platformVersion (string) --

            The Fargate platform version where the tasks in the task set are running. A platform version is only specified for tasks run on Fargate. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide .

          • platformFamily (string) --

            The operating system that your tasks in the set are running on. A platform family is specified only for tasks that use the Fargate launch type.

            All tasks in the set must have the same value.

          • networkConfiguration (dict) --

            The network configuration for the task set.

            • awsvpcConfiguration (dict) --

              The VPC subnets and security groups that are associated with a task.

              Note

              All specified subnets and security groups must be from the same VPC.

              • subnets (list) --

                The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

                Note

                All specified subnets must be from the same VPC.

                • (string) --

              • securityGroups (list) --

                The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

                Note

                All specified security groups must be from the same VPC.

                • (string) --

              • assignPublicIp (string) --

                Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

          • loadBalancers (list) --

            Details on a load balancer that are used with a task set.

            • (dict) --

              The load balancer configuration to use with a service or task set.

              For specific notes and restrictions regarding the use of load balancers with services and task sets, see the CreateService and CreateTaskSet actions.

              When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers.

              We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration.

              A service-linked role is required for services that use multiple target groups. For more information, see Using service-linked roles in the Amazon Elastic Container Service Developer Guide .

              • targetGroupArn (string) --

                The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set.

                A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you're using a Classic Load Balancer, omit the target group ARN.

                For services using the ECS deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide .

                For services using the CODE_DEPLOY deployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide .

                Warning

                If your service's task definition uses the awsvpc network mode, you must choose ip as the target type, not instance . Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.

              • loadBalancerName (string) --

                The name of the load balancer to associate with the Amazon ECS service or task set.

                A load balancer name is only specified when using a Classic Load Balancer. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.

              • containerName (string) --

                The name of the container (as it appears in a container definition) to associate with the load balancer.

              • containerPort (integer) --

                The port on the container to associate with the load balancer. This port must correspond to a containerPort in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on the hostPort of the port mapping.

          • serviceRegistries (list) --

            The details for the service discovery registries to assign to this task set. For more information, see Service discovery .

            • (dict) --

              The details for the service registry.

              Each service may be associated with one service registry. Multiple service registries for each service are not supported.

              When you add, update, or remove the service registries configuration, Amazon ECS starts a new deployment. New tasks are registered and deregistered to the updated service registry configuration.

              • registryArn (string) --

                The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is Cloud Map. For more information, see CreateService .

              • port (integer) --

                The port value used if your service discovery service specified an SRV record. This field might be used if both the awsvpc network mode and SRV records are used.

              • containerName (string) --

                The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition that your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

              • containerPort (integer) --

                The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

          • scale (dict) --

            A floating-point percentage of your desired number of tasks to place and keep running in the task set.

            • value (float) --

              The value, specified as a percent total of a service's desiredCount , to scale the task set. Accepted values are numbers between 0 and 100.

            • unit (string) --

              The unit of measure for the scale value.

          • stabilityStatus (string) --

            The stability status. This indicates whether the task set has reached a steady state. If the following conditions are met, the task set are in STEADY_STATE :

            • The task runningCount is equal to the computedDesiredCount .

            • The pendingCount is 0 .

            • There are no tasks that are running on container instances in the DRAINING status.

            • All tasks are reporting a healthy status from the load balancers, service discovery, and container health checks.

            If any of those conditions aren't met, the stability status returns STABILIZING .

          • stabilityStatusAt (datetime) --

            The Unix timestamp for the time when the task set stability status was retrieved.

          • tags (list) --

            The metadata that you apply to the task set to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

            The following basic restrictions apply to tags:

            • Maximum number of tags per resource - 50

            • For each resource, each tag key must be unique, and each tag key can have only one value.

            • Maximum key length - 128 Unicode characters in UTF-8

            • Maximum value length - 256 Unicode characters in UTF-8

            • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

            • Tag keys and values are case-sensitive.

            • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

            • (dict) --

              The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

              The following basic restrictions apply to tags:

              • Maximum number of tags per resource - 50

              • For each resource, each tag key must be unique, and each tag key can have only one value.

              • Maximum key length - 128 Unicode characters in UTF-8

              • Maximum value length - 256 Unicode characters in UTF-8

              • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

              • Tag keys and values are case-sensitive.

              • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

              • key (string) --

                One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

              • value (string) --

                The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

      • deployments (list) --

        The current state of deployments for the service.

        • (dict) --

          The details of an Amazon ECS service deployment. This is used only when a service uses the ECS deployment controller type.

          • id (string) --

            The ID of the deployment.

          • status (string) --

            The status of the deployment. The following describes each state.

            PRIMARY

            The most recent deployment of a service.

            ACTIVE

            A service deployment that still has running tasks, but are in the process of being replaced with a new PRIMARY deployment.

            INACTIVE

            A deployment that has been completely replaced.

          • taskDefinition (string) --

            The most recent task definition that was specified for the tasks in the service to use.

          • desiredCount (integer) --

            The most recent desired count of tasks that was specified for the service to deploy or maintain.

          • pendingCount (integer) --

            The number of tasks in the deployment that are in the PENDING status.

          • runningCount (integer) --

            The number of tasks in the deployment that are in the RUNNING status.

          • failedTasks (integer) --

            The number of consecutively failed tasks in the deployment. A task is considered a failure if the service scheduler can't launch the task, the task doesn't transition to a RUNNING state, or if it fails any of its defined health checks and is stopped.

            Note

            Once a service deployment has one or more successfully running tasks, the failed task count resets to zero and stops being evaluated.

          • createdAt (datetime) --

            The Unix timestamp for the time when the service deployment was created.

          • updatedAt (datetime) --

            The Unix timestamp for the time when the service deployment was last updated.

          • capacityProviderStrategy (list) --

            The capacity provider strategy that the deployment is using.

            • (dict) --

              The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

              Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

              If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

              To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

              A capacity provider strategy may contain a maximum of 6 capacity providers.

              • capacityProvider (string) --

                The short name of the capacity provider.

              • weight (integer) --

                The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

                If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

                An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

              • base (integer) --

                The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

          • launchType (string) --

            The launch type the tasks in the service are using. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide .

          • platformVersion (string) --

            The platform version that your tasks in the service run on. A platform version is only specified for tasks using the Fargate launch type. If one isn't specified, the LATEST platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide .

          • platformFamily (string) --

            The operating system that your tasks in the service, or tasks are running on. A platform family is specified only for tasks using the Fargate launch type.

            All tasks that run as part of this service must use the same platformFamily value as the service, for example, LINUX. .

          • networkConfiguration (dict) --

            The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.

            • awsvpcConfiguration (dict) --

              The VPC subnets and security groups that are associated with a task.

              Note

              All specified subnets and security groups must be from the same VPC.

              • subnets (list) --

                The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

                Note

                All specified subnets must be from the same VPC.

                • (string) --

              • securityGroups (list) --

                The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

                Note

                All specified security groups must be from the same VPC.

                • (string) --

              • assignPublicIp (string) --

                Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

          • rolloutState (string) --

            Note

            The rolloutState of a service is only returned for services that use the rolling update (ECS ) deployment type that aren't behind a Classic Load Balancer.

            The rollout state of the deployment. When a service deployment is started, it begins in an IN_PROGRESS state. When the service reaches a steady state, the deployment transitions to a COMPLETED state. If the service fails to reach a steady state and circuit breaker is enabled, the deployment transitions to a FAILED state. A deployment in FAILED state doesn't launch any new tasks. For more information, see DeploymentCircuitBreaker .

          • rolloutStateReason (string) --

            A description of the rollout state of a deployment.

          • serviceConnectConfiguration (dict) --

            The details of the Service Connect configuration that's used by this deployment. Compare the configuration between multiple deployments when troubleshooting issues with new deployments.

            The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace.

            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 .

            • enabled (boolean) --

              Specifies whether to use Service Connect with this service.

            • namespace (string) --

              The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace for use with Service Connect. The namespace must be in the same Amazon Web Services Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about Cloud Map, see Working with Services in the Cloud Map Developer Guide .

            • services (list) --

              The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. You can specify up to X (30?) objects per Amazon ECS service.

              This field is not required for a "client" Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means.

              An object selects a port from the task definition, assigns a name for the Cloud Map service, and a list of aliases (endpoints) and ports for client applications to refer to this service.

              • (dict) --

                The Service Connect service object configuration. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                • portName (string) --

                  The portName must match the name of one of the portMappings from all the containers in the task definition of this Amazon ECS service.

                • discoveryName (string) --

                  The discoveryName is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                  If this field isn't specified, portName is used.

                • clientAliases (list) --

                  The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1.

                  Each alias ("endpoint") is a fully-qualified name and port number that other Amazon ECS tasks ("clients") can use to connect to this service.

                  Each name and port mapping must be unique within the namespace.

                  For each ServiceConnectService , you must provide at least one clientAlias with one port .

                  • (dict) --

                    Each alias ("endpoint") is a fully-qualified name and port number that other tasks ("clients") can use to connect to this service.

                    Each name and port mapping must be unique within the namespace.

                    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 .

                    • port (integer) --

                      The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace.

                      To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                    • dnsName (string) --

                      The dnsName is the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. Up to 127 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). A hyphen can't be the first character.

                      If this parameter isn't specified, the default value of discoveryName.namespace is used. If the discoveryName isn't specified, the portName.namespace from the task definition is used.

                      To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names are database , db , or the lowercase name of a database, such as mysql or redis . For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                • ingressPortOverride (integer) --

                  The port number for the Service Connect proxy to listen on.

                  Use the value of this field to bypass the proxy for traffic on the port number specified in the named portMapping in the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service.

                  In awsvpc mode and Fargate, the default value is the container port number. The container port number is in the portMapping in the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy.

            • logConfiguration (dict) --

              The log configuration for the container. This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to ` docker run https://docs.docker.com/engine/reference/commandline/run/`__ .

              By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation.

              Understand the following when specifying a log configuration for your containers.

              • Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon (shown in the valid values below). Additional log drivers may be available in future releases of the Amazon ECS container agent.

              • This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.

              • For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide .

              • For tasks that are on Fargate, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.

              • logDriver (string) --

                The log driver to use for the container.

                For tasks on Fargate, the supported log drivers are awslogs , splunk , and awsfirelens .

                For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs , fluentd , gelf , json-file , journald , logentries ,``syslog`` , splunk , and awsfirelens .

                For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide .

                For more information about using the awsfirelens log driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide .

                Note

                If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.

              • options (dict) --

                The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

                • (string) --

                  • (string) --

              • secretOptions (list) --

                The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

                • (dict) --

                  An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

                  • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

                  • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

                  For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

                  • name (string) --

                    The name of the secret.

                  • valueFrom (string) --

                    The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

                    For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

                    Note

                    If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

          • serviceConnectResources (list) --

            The list of Service Connect resources that are associated with this deployment. Each list entry maps a discovery name to a Cloud Map service name.

            • (dict) --

              The Service Connect resource. Each configuration maps a discovery name to a Cloud Map service name. The data is stored in Cloud Map as part of the Service Connect configuration for each discovery name of this Amazon ECS service.

              A task can resolve the dnsName for each of the clientAliases of a service. However a task can't resolve the discovery names. If you want to connect to a service, refer to the ServiceConnectConfiguration of that service for the list of clientAliases that you can use.

              • discoveryName (string) --

                The discovery name of this Service Connect resource.

                The discoveryName is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                If this field isn't specified, portName is used.

              • discoveryArn (string) --

                The Amazon Resource Name (ARN) for the namespace in Cloud Map that matches the discovery name for this Service Connect resource. You can use this ARN in other integrations with Cloud Map. However, Service Connect can't ensure connectivity outside of Amazon ECS.

      • roleArn (string) --

        The ARN of the IAM role that's associated with the service. It allows the Amazon ECS container agent to register container instances with an Elastic Load Balancing load balancer.

      • events (list) --

        The event stream for your service. A maximum of 100 of the latest events are displayed.

        • (dict) --

          The details for an event that's associated with a service.

          • id (string) --

            The ID string for the event.

          • createdAt (datetime) --

            The Unix timestamp for the time when the event was triggered.

          • message (string) --

            The event message.

      • createdAt (datetime) --

        The Unix timestamp for the time when the service was created.

      • placementConstraints (list) --

        The placement constraints for the tasks in the service.

        • (dict) --

          An object representing a constraint on task placement. For more information, see Task placement constraints in the Amazon Elastic Container Service Developer Guide .

          Note

          If you're using the Fargate launch type, task placement constraints aren't supported.

          • type (string) --

            The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to restrict the selection to a group of valid candidates.

          • expression (string) --

            A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is distinctInstance . For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide .

      • placementStrategy (list) --

        The placement strategy that determines how tasks for the service are placed.

        • (dict) --

          The task placement strategy for a task or service. For more information, see Task placement strategies in the Amazon Elastic Container Service Developer Guide .

          • type (string) --

            The type of placement strategy. The random placement strategy randomly places tasks on available candidates. The spread placement strategy spreads placement across available candidates evenly based on the field parameter. The binpack strategy places tasks on available candidates that have the least available amount of the resource that's specified with the field parameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.

          • field (string) --

            The field to apply the placement strategy against. For the spread placement strategy, valid values are instanceId (or host , which has the same effect), or any platform or custom attribute that's applied to a container instance, such as attribute:ecs.availability-zone . For the binpack placement strategy, valid values are cpu and memory . For the random placement strategy, this field is not used.

      • networkConfiguration (dict) --

        The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.

        • awsvpcConfiguration (dict) --

          The VPC subnets and security groups that are associated with a task.

          Note

          All specified subnets and security groups must be from the same VPC.

          • subnets (list) --

            The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

            Note

            All specified subnets must be from the same VPC.

            • (string) --

          • securityGroups (list) --

            The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

            Note

            All specified security groups must be from the same VPC.

            • (string) --

          • assignPublicIp (string) --

            Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

      • healthCheckGracePeriodSeconds (integer) --

        The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started.

      • schedulingStrategy (string) --

        The scheduling strategy to use for the service. For more information, see Services .

        There are two service scheduler strategies available.

        • REPLICA -The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions.

        • DAEMON -The daemon scheduling strategy deploys exactly one task on each active container instance. This task meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks. It stop tasks that don't meet the placement constraints.

        Note

        Fargate tasks don't support the DAEMON scheduling strategy.

      • deploymentController (dict) --

        The deployment controller type the service is using.

        • type (string) --

          The deployment controller type to use.

          There are three deployment controller types available:

          ECS

          The rolling update (ECS ) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration .

          CODE_DEPLOY

          The blue/green (CODE_DEPLOY ) deployment type uses the blue/green deployment model powered by CodeDeploy, which allows you to verify a new deployment of a service before sending production traffic to it.

          EXTERNAL

          The external (EXTERNAL ) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.

      • tags (list) --

        The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value. You define bot the key and value.

        The following basic restrictions apply to tags:

        • Maximum number of tags per resource - 50

        • For each resource, each tag key must be unique, and each tag key can have only one value.

        • Maximum key length - 128 Unicode characters in UTF-8

        • Maximum value length - 256 Unicode characters in UTF-8

        • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

        • Tag keys and values are case-sensitive.

        • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

        • (dict) --

          The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

          The following basic restrictions apply to tags:

          • Maximum number of tags per resource - 50

          • For each resource, each tag key must be unique, and each tag key can have only one value.

          • Maximum key length - 128 Unicode characters in UTF-8

          • Maximum value length - 256 Unicode characters in UTF-8

          • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

          • Tag keys and values are case-sensitive.

          • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

          • key (string) --

            One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

          • value (string) --

            The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

      • createdBy (string) --

        The principal that created the service.

      • enableECSManagedTags (boolean) --

        Determines whether to use Amazon ECS managed tags for the tasks in the service. For more information, see Tagging Your Amazon ECS Resources in the Amazon Elastic Container Service Developer Guide .

      • propagateTags (string) --

        Determines whether to propagate the tags from the task definition or the service to the task. If no value is specified, the tags aren't propagated.

      • enableExecuteCommand (boolean) --

        Determines whether the execute command functionality is enabled for the service. If true , the execute command functionality is enabled for all containers in tasks as part of the service.

DeleteCluster (updated) Link ¶
Changes (response)
{'cluster': {'serviceConnectDefaults': {'namespace': 'string'}}}

Deletes the specified cluster. The cluster transitions to the INACTIVE state. Clusters with an INACTIVE status might 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.

You must deregister all container instances from this cluster before you may delete it. You can list the container instances in a cluster with ListContainerInstances and deregister them with DeregisterContainerInstance .

See also: AWS API Documentation

Request Syntax

client.delete_cluster(
    cluster='string'
)
type cluster

string

param cluster

[REQUIRED]

The short name or full Amazon Resource Name (ARN) of the cluster to delete.

rtype

dict

returns

Response Syntax

{
    'cluster': {
        'clusterArn': 'string',
        'clusterName': 'string',
        'configuration': {
            'executeCommandConfiguration': {
                'kmsKeyId': 'string',
                'logging': 'NONE'|'DEFAULT'|'OVERRIDE',
                'logConfiguration': {
                    'cloudWatchLogGroupName': 'string',
                    'cloudWatchEncryptionEnabled': True|False,
                    's3BucketName': 'string',
                    's3EncryptionEnabled': True|False,
                    's3KeyPrefix': 'string'
                }
            }
        },
        'status': 'string',
        'registeredContainerInstancesCount': 123,
        'runningTasksCount': 123,
        'pendingTasksCount': 123,
        'activeServicesCount': 123,
        'statistics': [
            {
                'name': 'string',
                'value': 'string'
            },
        ],
        'tags': [
            {
                'key': 'string',
                'value': 'string'
            },
        ],
        'settings': [
            {
                'name': 'containerInsights',
                'value': 'string'
            },
        ],
        'capacityProviders': [
            'string',
        ],
        'defaultCapacityProviderStrategy': [
            {
                'capacityProvider': 'string',
                'weight': 123,
                'base': 123
            },
        ],
        'attachments': [
            {
                'id': 'string',
                'type': 'string',
                'status': 'string',
                'details': [
                    {
                        'name': 'string',
                        'value': 'string'
                    },
                ]
            },
        ],
        'attachmentsStatus': 'string',
        'serviceConnectDefaults': {
            'namespace': 'string'
        }
    }
}

Response Structure

  • (dict) --

    • cluster (dict) --

      The full description of the deleted cluster.

      • clusterArn (string) --

        The 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 .

      • clusterName (string) --

        A user-generated string that you use to identify your cluster.

      • configuration (dict) --

        The execute command configuration for the cluster.

        • executeCommandConfiguration (dict) --

          The details of the execute command configuration.

          • kmsKeyId (string) --

            Specify an Key Management Service key ID to encrypt the data between the local client and the container.

          • logging (string) --

            The log setting to use for redirecting logs for your execute command results. The following log settings are available.

            • NONE : The execute command session is not logged.

            • DEFAULT : The awslogs configuration in the task definition is used. If no logging parameter is specified, it defaults to this value. If no awslogs log driver is configured in the task definition, the output won't be logged.

            • OVERRIDE : Specify the logging details as a part of logConfiguration . If the OVERRIDE logging option is specified, the logConfiguration is required.

          • logConfiguration (dict) --

            The log configuration for the results of the execute command actions. The logs can be sent to CloudWatch Logs or an Amazon S3 bucket. When logging=OVERRIDE is specified, a logConfiguration must be provided.

            • cloudWatchLogGroupName (string) --

              The name of the CloudWatch log group to send logs to.

              Note

              The CloudWatch log group must already be created.

            • cloudWatchEncryptionEnabled (boolean) --

              Determines whether to use encryption on the CloudWatch logs. If not specified, encryption will be disabled.

            • s3BucketName (string) --

              The name of the S3 bucket to send logs to.

              Note

              The S3 bucket must already be created.

            • s3EncryptionEnabled (boolean) --

              Determines whether to use encryption on the S3 logs. If not specified, encryption is not used.

            • s3KeyPrefix (string) --

              An optional folder in the S3 bucket to place logs in.

      • status (string) --

        The 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.

      • registeredContainerInstancesCount (integer) --

        The number of container instances registered into the cluster. This includes container instances in both ACTIVE and DRAINING status.

      • runningTasksCount (integer) --

        The number of tasks in the cluster that are in the RUNNING state.

      • pendingTasksCount (integer) --

        The number of tasks in the cluster that are in the PENDING state.

      • activeServicesCount (integer) --

        The number of services that are running on the cluster in an ACTIVE state. You can view these services with ListServices .

      • statistics (list) --

        Additional information about your clusters that are separated by launch type. They include the following:

        • runningEC2TasksCount

        • RunningFargateTasksCount

        • pendingEC2TasksCount

        • pendingFargateTasksCount

        • activeEC2ServiceCount

        • activeFargateServiceCount

        • drainingEC2ServiceCount

        • drainingFargateServiceCount

        • (dict) --

          A key-value pair object.

          • name (string) --

            The name of the key-value pair. For environment variables, this is the name of the environment variable.

          • value (string) --

            The value of the key-value pair. For environment variables, this is the value of the environment variable.

      • tags (list) --

        The metadata that you apply to the cluster to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

        The following basic restrictions apply to tags:

        • Maximum number of tags per resource - 50

        • For each resource, each tag key must be unique, and each tag key can have only one value.

        • Maximum key length - 128 Unicode characters in UTF-8

        • Maximum value length - 256 Unicode characters in UTF-8

        • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

        • Tag keys and values are case-sensitive.

        • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

        • (dict) --

          The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

          The following basic restrictions apply to tags:

          • Maximum number of tags per resource - 50

          • For each resource, each tag key must be unique, and each tag key can have only one value.

          • Maximum key length - 128 Unicode characters in UTF-8

          • Maximum value length - 256 Unicode characters in UTF-8

          • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

          • Tag keys and values are case-sensitive.

          • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

          • key (string) --

            One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

          • value (string) --

            The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

      • settings (list) --

        The settings for the cluster. This parameter indicates whether CloudWatch Container Insights is enabled or disabled for a cluster.

        • (dict) --

          The settings to use when creating a cluster. This parameter is used to turn on CloudWatch Container Insights for a cluster.

          • name (string) --

            The name of the cluster setting. The only supported value is containerInsights .

          • value (string) --

            The value to set for the cluster setting. The supported values are enabled and disabled . If enabled is specified, CloudWatch Container Insights will be enabled for the cluster, otherwise it will be disabled unless the containerInsights account setting is enabled. If a cluster value is specified, it will override the containerInsights value set with PutAccountSetting or PutAccountSettingDefault .

      • capacityProviders (list) --

        The capacity providers associated with the cluster.

        • (string) --

      • defaultCapacityProviderStrategy (list) --

        The 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.

        • (dict) --

          The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

          Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

          If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

          To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

          A capacity provider strategy may contain a maximum of 6 capacity providers.

          • capacityProvider (string) --

            The short name of the capacity provider.

          • weight (integer) --

            The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

            If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

            An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

          • base (integer) --

            The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

      • attachments (list) --

        The resources attached to a cluster. When using a capacity provider with a cluster, the capacity provider and associated resources are returned as cluster attachments.

        • (dict) --

          An object representing a container instance or task attachment.

          • id (string) --

            The unique identifier for the attachment.

          • type (string) --

            The type of the attachment, such as ElasticNetworkInterface .

          • status (string) --

            The status of the attachment. Valid values are PRECREATED , CREATED , ATTACHING , ATTACHED , DETACHING , DETACHED , DELETED , and FAILED .

          • details (list) --

            Details of the attachment. For elastic network interfaces, this includes the network interface ID, the MAC address, the subnet ID, and the private IPv4 address.

            • (dict) --

              A key-value pair object.

              • name (string) --

                The name of the key-value pair. For environment variables, this is the name of the environment variable.

              • value (string) --

                The value of the key-value pair. For environment variables, this is the value of the environment variable.

      • attachmentsStatus (string) --

        The 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.

      • serviceConnectDefaults (dict) --

        Use 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 .

        • namespace (string) --

          The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace. When you create a service and don't specify a Service Connect configuration, this namespace is used.

DeleteService (updated) Link ¶
Changes (response)
{'service': {'deployments': {'serviceConnectConfiguration': {'enabled': 'boolean',
                                                             'logConfiguration': {'logDriver': 'json-file '
                                                                                               '| '
                                                                                               'syslog '
                                                                                               '| '
                                                                                               'journald '
                                                                                               '| '
                                                                                               'gelf '
                                                                                               '| '
                                                                                               'fluentd '
                                                                                               '| '
                                                                                               'awslogs '
                                                                                               '| '
                                                                                               'splunk '
                                                                                               '| '
                                                                                               'awsfirelens',
                                                                                  'options': {'string': 'string'},
                                                                                  'secretOptions': [{'name': 'string',
                                                                                                     'valueFrom': 'string'}]},
                                                             'namespace': 'string',
                                                             'services': [{'clientAliases': [{'dnsName': 'string',
                                                                                              'port': 'integer'}],
                                                                           'discoveryName': 'string',
                                                                           'ingressPortOverride': 'integer',
                                                                           'portName': 'string'}]},
                             'serviceConnectResources': [{'discoveryArn': 'string',
                                                          'discoveryName': 'string'}]}}}

Deletes a specified service within a cluster. You can delete a service if you have no running tasks in it and the desired task count is zero. If the service is actively maintaining tasks, you can't delete it, and you must update the service to a desired task count of zero. For more information, see UpdateService .

Note

When you delete a service, if there are still running tasks that require cleanup, the service status moves from ACTIVE to DRAINING , and the service is no longer visible in the console or in the ListServices API operation. After all tasks have transitioned to either STOPPING or STOPPED status, the service status moves from DRAINING to INACTIVE . Services in the DRAINING or INACTIVE status can still be viewed with the DescribeServices API operation. However, in the future, INACTIVE services may be cleaned up and purged from Amazon ECS record keeping, and DescribeServices calls on those services return a ServiceNotFoundException error.

Warning

If you attempt to create a new service with the same name as an existing service in either ACTIVE or DRAINING status, you receive an error.

See also: AWS API Documentation

Request Syntax

client.delete_service(
    cluster='string',
    service='string',
    force=True|False
)
type cluster

string

param cluster

The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service to delete. If you do not specify a cluster, the default cluster is assumed.

type service

string

param service

[REQUIRED]

The name of the service to delete.

type force

boolean

param force

If true , allows you to delete a service even if it wasn't scaled down to zero tasks. It's only necessary to use this if the service uses the REPLICA scheduling strategy.

rtype

dict

returns

Response Syntax

{
    'service': {
        'serviceArn': 'string',
        'serviceName': 'string',
        'clusterArn': 'string',
        'loadBalancers': [
            {
                'targetGroupArn': 'string',
                'loadBalancerName': 'string',
                'containerName': 'string',
                'containerPort': 123
            },
        ],
        'serviceRegistries': [
            {
                'registryArn': 'string',
                'port': 123,
                'containerName': 'string',
                'containerPort': 123
            },
        ],
        'status': 'string',
        'desiredCount': 123,
        'runningCount': 123,
        'pendingCount': 123,
        'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
        'capacityProviderStrategy': [
            {
                'capacityProvider': 'string',
                'weight': 123,
                'base': 123
            },
        ],
        'platformVersion': 'string',
        'platformFamily': 'string',
        'taskDefinition': 'string',
        'deploymentConfiguration': {
            'deploymentCircuitBreaker': {
                'enable': True|False,
                'rollback': True|False
            },
            'maximumPercent': 123,
            'minimumHealthyPercent': 123
        },
        'taskSets': [
            {
                'id': 'string',
                'taskSetArn': 'string',
                'serviceArn': 'string',
                'clusterArn': 'string',
                'startedBy': 'string',
                'externalId': 'string',
                'status': 'string',
                'taskDefinition': 'string',
                'computedDesiredCount': 123,
                'pendingCount': 123,
                'runningCount': 123,
                'createdAt': datetime(2015, 1, 1),
                'updatedAt': datetime(2015, 1, 1),
                'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
                'capacityProviderStrategy': [
                    {
                        'capacityProvider': 'string',
                        'weight': 123,
                        'base': 123
                    },
                ],
                'platformVersion': 'string',
                'platformFamily': 'string',
                'networkConfiguration': {
                    'awsvpcConfiguration': {
                        'subnets': [
                            'string',
                        ],
                        'securityGroups': [
                            'string',
                        ],
                        'assignPublicIp': 'ENABLED'|'DISABLED'
                    }
                },
                'loadBalancers': [
                    {
                        'targetGroupArn': 'string',
                        'loadBalancerName': 'string',
                        'containerName': 'string',
                        'containerPort': 123
                    },
                ],
                'serviceRegistries': [
                    {
                        'registryArn': 'string',
                        'port': 123,
                        'containerName': 'string',
                        'containerPort': 123
                    },
                ],
                'scale': {
                    'value': 123.0,
                    'unit': 'PERCENT'
                },
                'stabilityStatus': 'STEADY_STATE'|'STABILIZING',
                'stabilityStatusAt': datetime(2015, 1, 1),
                'tags': [
                    {
                        'key': 'string',
                        'value': 'string'
                    },
                ]
            },
        ],
        'deployments': [
            {
                'id': 'string',
                'status': 'string',
                'taskDefinition': 'string',
                'desiredCount': 123,
                'pendingCount': 123,
                'runningCount': 123,
                'failedTasks': 123,
                'createdAt': datetime(2015, 1, 1),
                'updatedAt': datetime(2015, 1, 1),
                'capacityProviderStrategy': [
                    {
                        'capacityProvider': 'string',
                        'weight': 123,
                        'base': 123
                    },
                ],
                'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
                'platformVersion': 'string',
                'platformFamily': 'string',
                'networkConfiguration': {
                    'awsvpcConfiguration': {
                        'subnets': [
                            'string',
                        ],
                        'securityGroups': [
                            'string',
                        ],
                        'assignPublicIp': 'ENABLED'|'DISABLED'
                    }
                },
                'rolloutState': 'COMPLETED'|'FAILED'|'IN_PROGRESS',
                'rolloutStateReason': 'string',
                'serviceConnectConfiguration': {
                    'enabled': True|False,
                    'namespace': 'string',
                    'services': [
                        {
                            'portName': 'string',
                            'discoveryName': 'string',
                            'clientAliases': [
                                {
                                    'port': 123,
                                    'dnsName': 'string'
                                },
                            ],
                            'ingressPortOverride': 123
                        },
                    ],
                    'logConfiguration': {
                        'logDriver': 'json-file'|'syslog'|'journald'|'gelf'|'fluentd'|'awslogs'|'splunk'|'awsfirelens',
                        'options': {
                            'string': 'string'
                        },
                        'secretOptions': [
                            {
                                'name': 'string',
                                'valueFrom': 'string'
                            },
                        ]
                    }
                },
                'serviceConnectResources': [
                    {
                        'discoveryName': 'string',
                        'discoveryArn': 'string'
                    },
                ]
            },
        ],
        'roleArn': 'string',
        'events': [
            {
                'id': 'string',
                'createdAt': datetime(2015, 1, 1),
                'message': 'string'
            },
        ],
        'createdAt': datetime(2015, 1, 1),
        'placementConstraints': [
            {
                'type': 'distinctInstance'|'memberOf',
                'expression': 'string'
            },
        ],
        'placementStrategy': [
            {
                'type': 'random'|'spread'|'binpack',
                'field': 'string'
            },
        ],
        'networkConfiguration': {
            'awsvpcConfiguration': {
                'subnets': [
                    'string',
                ],
                'securityGroups': [
                    'string',
                ],
                'assignPublicIp': 'ENABLED'|'DISABLED'
            }
        },
        'healthCheckGracePeriodSeconds': 123,
        'schedulingStrategy': 'REPLICA'|'DAEMON',
        'deploymentController': {
            'type': 'ECS'|'CODE_DEPLOY'|'EXTERNAL'
        },
        'tags': [
            {
                'key': 'string',
                'value': 'string'
            },
        ],
        'createdBy': 'string',
        'enableECSManagedTags': True|False,
        'propagateTags': 'TASK_DEFINITION'|'SERVICE'|'NONE',
        'enableExecuteCommand': True|False
    }
}

Response Structure

  • (dict) --

    • service (dict) --

      The full description of the deleted service.

      • serviceArn (string) --

        The ARN that identifies the service. For more information about the ARN format, see Amazon Resource Name (ARN) in the Amazon ECS Developer Guide .

      • serviceName (string) --

        The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster. However, you can have similarly named services in multiple clusters within a Region or across multiple Regions.

      • clusterArn (string) --

        The Amazon Resource Name (ARN) of the cluster that hosts the service.

      • loadBalancers (list) --

        A list of Elastic Load Balancing load balancer objects. It contains the load balancer name, the container name, and the container port to access from the load balancer. The container name is as it appears in a container definition.

        • (dict) --

          The load balancer configuration to use with a service or task set.

          For specific notes and restrictions regarding the use of load balancers with services and task sets, see the CreateService and CreateTaskSet actions.

          When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers.

          We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration.

          A service-linked role is required for services that use multiple target groups. For more information, see Using service-linked roles in the Amazon Elastic Container Service Developer Guide .

          • targetGroupArn (string) --

            The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set.

            A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you're using a Classic Load Balancer, omit the target group ARN.

            For services using the ECS deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide .

            For services using the CODE_DEPLOY deployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide .

            Warning

            If your service's task definition uses the awsvpc network mode, you must choose ip as the target type, not instance . Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.

          • loadBalancerName (string) --

            The name of the load balancer to associate with the Amazon ECS service or task set.

            A load balancer name is only specified when using a Classic Load Balancer. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.

          • containerName (string) --

            The name of the container (as it appears in a container definition) to associate with the load balancer.

          • containerPort (integer) --

            The port on the container to associate with the load balancer. This port must correspond to a containerPort in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on the hostPort of the port mapping.

      • serviceRegistries (list) --

        The details for the service discovery registries to assign to this service. For more information, see Service Discovery .

        • (dict) --

          The details for the service registry.

          Each service may be associated with one service registry. Multiple service registries for each service are not supported.

          When you add, update, or remove the service registries configuration, Amazon ECS starts a new deployment. New tasks are registered and deregistered to the updated service registry configuration.

          • registryArn (string) --

            The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is Cloud Map. For more information, see CreateService .

          • port (integer) --

            The port value used if your service discovery service specified an SRV record. This field might be used if both the awsvpc network mode and SRV records are used.

          • containerName (string) --

            The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition that your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

          • containerPort (integer) --

            The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

      • status (string) --

        The status of the service. The valid values are ACTIVE , DRAINING , or INACTIVE .

      • desiredCount (integer) --

        The desired number of instantiations of the task definition to keep running on the service. This value is specified when the service is created with CreateService , and it can be modified with UpdateService .

      • runningCount (integer) --

        The number of tasks in the cluster that are in the RUNNING state.

      • pendingCount (integer) --

        The number of tasks in the cluster that are in the PENDING state.

      • launchType (string) --

        The launch type the service is using. When using the DescribeServices API, this field is omitted if the service was created using a capacity provider strategy.

      • capacityProviderStrategy (list) --

        The capacity provider strategy the service uses. When using the DescribeServices API, this field is omitted if the service was created using a launch type.

        • (dict) --

          The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

          Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

          If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

          To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

          A capacity provider strategy may contain a maximum of 6 capacity providers.

          • capacityProvider (string) --

            The short name of the capacity provider.

          • weight (integer) --

            The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

            If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

            An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

          • base (integer) --

            The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

      • platformVersion (string) --

        The platform version to run your service on. A platform version is only specified for tasks that are hosted on Fargate. If one isn't specified, the LATEST platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide .

      • platformFamily (string) --

        The operating system that your tasks in the service run on. A platform family is specified only for tasks using the Fargate launch type.

        All tasks that run as part of this service must use the same platformFamily value as the service (for example, LINUX ).

      • taskDefinition (string) --

        The task definition to use for tasks in the service. This value is specified when the service is created with CreateService , and it can be modified with UpdateService .

      • deploymentConfiguration (dict) --

        Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.

        • deploymentCircuitBreaker (dict) --

          Note

          The deployment circuit breaker can only be used for services using the rolling update (ECS ) deployment type.

          The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

          • enable (boolean) --

            Determines whether to use the deployment circuit breaker logic for the service.

          • rollback (boolean) --

            Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

        • maximumPercent (integer) --

          If a service is using the rolling update (ECS ) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default maximumPercent value for a service using the REPLICA service scheduler is 200%.

          If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.

        • minimumHealthyPercent (integer) --

          If a service is using the rolling update (ECS ) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.

          For services that do not use a load balancer, the following should be noted:

          • A service is considered healthy if all essential containers within the tasks in the service pass their health checks.

          • If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches a RUNNING state before the task is counted towards the minimum healthy percent total.

          • If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings.

          For services are that do use a load balancer, the following should be noted:

          • If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

          • If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

          If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

      • taskSets (list) --

        Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.

        • (dict) --

          Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.

          • id (string) --

            The ID of the task set.

          • taskSetArn (string) --

            The Amazon Resource Name (ARN) of the task set.

          • serviceArn (string) --

            The Amazon Resource Name (ARN) of the service the task set exists in.

          • clusterArn (string) --

            The Amazon Resource Name (ARN) of the cluster that the service that hosts the task set exists in.

          • startedBy (string) --

            The tag specified when a task set is started. If an CodeDeploy deployment created the task set, the startedBy parameter is CODE_DEPLOY . If an external deployment created the task set, the startedBy field isn't used.

          • externalId (string) --

            The external ID associated with the task set.

            If an CodeDeploy deployment created a task set, the externalId parameter contains the CodeDeploy deployment ID.

            If a task set is created for an external deployment and is associated with a service discovery registry, the externalId parameter contains the ECS_TASK_SET_EXTERNAL_ID Cloud Map attribute.

          • status (string) --

            The status of the task set. The following describes each state.

            PRIMARY

            The task set is serving production traffic.

            ACTIVE

            The task set isn't serving production traffic.

            DRAINING

            The tasks in the task set are being stopped, and their corresponding targets are being deregistered from their target group.

          • taskDefinition (string) --

            The task definition that the task set is using.

          • computedDesiredCount (integer) --

            The computed desired count for the task set. This is calculated by multiplying the service's desiredCount by the task set's scale percentage. The result is always rounded up. For example, if the computed desired count is 1.2, it rounds up to 2 tasks.

          • pendingCount (integer) --

            The number of tasks in the task set that are in the PENDING status during a deployment. A task in the PENDING state is preparing to enter the RUNNING state. A task set enters the PENDING status when it launches for the first time or when it's restarted after being in the STOPPED state.

          • runningCount (integer) --

            The number of tasks in the task set that are in the RUNNING status during a deployment. A task in the RUNNING state is running and ready for use.

          • createdAt (datetime) --

            The Unix timestamp for the time when the task set was created.

          • updatedAt (datetime) --

            The Unix timestamp for the time when the task set was last updated.

          • launchType (string) --

            The launch type the tasks in the task set are using. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide .

          • capacityProviderStrategy (list) --

            The capacity provider strategy that are associated with the task set.

            • (dict) --

              The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

              Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

              If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

              To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

              A capacity provider strategy may contain a maximum of 6 capacity providers.

              • capacityProvider (string) --

                The short name of the capacity provider.

              • weight (integer) --

                The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

                If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

                An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

              • base (integer) --

                The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

          • platformVersion (string) --

            The Fargate platform version where the tasks in the task set are running. A platform version is only specified for tasks run on Fargate. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide .

          • platformFamily (string) --

            The operating system that your tasks in the set are running on. A platform family is specified only for tasks that use the Fargate launch type.

            All tasks in the set must have the same value.

          • networkConfiguration (dict) --

            The network configuration for the task set.

            • awsvpcConfiguration (dict) --

              The VPC subnets and security groups that are associated with a task.

              Note

              All specified subnets and security groups must be from the same VPC.

              • subnets (list) --

                The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

                Note

                All specified subnets must be from the same VPC.

                • (string) --

              • securityGroups (list) --

                The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

                Note

                All specified security groups must be from the same VPC.

                • (string) --

              • assignPublicIp (string) --

                Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

          • loadBalancers (list) --

            Details on a load balancer that are used with a task set.

            • (dict) --

              The load balancer configuration to use with a service or task set.

              For specific notes and restrictions regarding the use of load balancers with services and task sets, see the CreateService and CreateTaskSet actions.

              When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers.

              We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration.

              A service-linked role is required for services that use multiple target groups. For more information, see Using service-linked roles in the Amazon Elastic Container Service Developer Guide .

              • targetGroupArn (string) --

                The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set.

                A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you're using a Classic Load Balancer, omit the target group ARN.

                For services using the ECS deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide .

                For services using the CODE_DEPLOY deployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide .

                Warning

                If your service's task definition uses the awsvpc network mode, you must choose ip as the target type, not instance . Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.

              • loadBalancerName (string) --

                The name of the load balancer to associate with the Amazon ECS service or task set.

                A load balancer name is only specified when using a Classic Load Balancer. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.

              • containerName (string) --

                The name of the container (as it appears in a container definition) to associate with the load balancer.

              • containerPort (integer) --

                The port on the container to associate with the load balancer. This port must correspond to a containerPort in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on the hostPort of the port mapping.

          • serviceRegistries (list) --

            The details for the service discovery registries to assign to this task set. For more information, see Service discovery .

            • (dict) --

              The details for the service registry.

              Each service may be associated with one service registry. Multiple service registries for each service are not supported.

              When you add, update, or remove the service registries configuration, Amazon ECS starts a new deployment. New tasks are registered and deregistered to the updated service registry configuration.

              • registryArn (string) --

                The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is Cloud Map. For more information, see CreateService .

              • port (integer) --

                The port value used if your service discovery service specified an SRV record. This field might be used if both the awsvpc network mode and SRV records are used.

              • containerName (string) --

                The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition that your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

              • containerPort (integer) --

                The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

          • scale (dict) --

            A floating-point percentage of your desired number of tasks to place and keep running in the task set.

            • value (float) --

              The value, specified as a percent total of a service's desiredCount , to scale the task set. Accepted values are numbers between 0 and 100.

            • unit (string) --

              The unit of measure for the scale value.

          • stabilityStatus (string) --

            The stability status. This indicates whether the task set has reached a steady state. If the following conditions are met, the task set are in STEADY_STATE :

            • The task runningCount is equal to the computedDesiredCount .

            • The pendingCount is 0 .

            • There are no tasks that are running on container instances in the DRAINING status.

            • All tasks are reporting a healthy status from the load balancers, service discovery, and container health checks.

            If any of those conditions aren't met, the stability status returns STABILIZING .

          • stabilityStatusAt (datetime) --

            The Unix timestamp for the time when the task set stability status was retrieved.

          • tags (list) --

            The metadata that you apply to the task set to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

            The following basic restrictions apply to tags:

            • Maximum number of tags per resource - 50

            • For each resource, each tag key must be unique, and each tag key can have only one value.

            • Maximum key length - 128 Unicode characters in UTF-8

            • Maximum value length - 256 Unicode characters in UTF-8

            • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

            • Tag keys and values are case-sensitive.

            • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

            • (dict) --

              The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

              The following basic restrictions apply to tags:

              • Maximum number of tags per resource - 50

              • For each resource, each tag key must be unique, and each tag key can have only one value.

              • Maximum key length - 128 Unicode characters in UTF-8

              • Maximum value length - 256 Unicode characters in UTF-8

              • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

              • Tag keys and values are case-sensitive.

              • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

              • key (string) --

                One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

              • value (string) --

                The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

      • deployments (list) --

        The current state of deployments for the service.

        • (dict) --

          The details of an Amazon ECS service deployment. This is used only when a service uses the ECS deployment controller type.

          • id (string) --

            The ID of the deployment.

          • status (string) --

            The status of the deployment. The following describes each state.

            PRIMARY

            The most recent deployment of a service.

            ACTIVE

            A service deployment that still has running tasks, but are in the process of being replaced with a new PRIMARY deployment.

            INACTIVE

            A deployment that has been completely replaced.

          • taskDefinition (string) --

            The most recent task definition that was specified for the tasks in the service to use.

          • desiredCount (integer) --

            The most recent desired count of tasks that was specified for the service to deploy or maintain.

          • pendingCount (integer) --

            The number of tasks in the deployment that are in the PENDING status.

          • runningCount (integer) --

            The number of tasks in the deployment that are in the RUNNING status.

          • failedTasks (integer) --

            The number of consecutively failed tasks in the deployment. A task is considered a failure if the service scheduler can't launch the task, the task doesn't transition to a RUNNING state, or if it fails any of its defined health checks and is stopped.

            Note

            Once a service deployment has one or more successfully running tasks, the failed task count resets to zero and stops being evaluated.

          • createdAt (datetime) --

            The Unix timestamp for the time when the service deployment was created.

          • updatedAt (datetime) --

            The Unix timestamp for the time when the service deployment was last updated.

          • capacityProviderStrategy (list) --

            The capacity provider strategy that the deployment is using.

            • (dict) --

              The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

              Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

              If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

              To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

              A capacity provider strategy may contain a maximum of 6 capacity providers.

              • capacityProvider (string) --

                The short name of the capacity provider.

              • weight (integer) --

                The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

                If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

                An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

              • base (integer) --

                The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

          • launchType (string) --

            The launch type the tasks in the service are using. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide .

          • platformVersion (string) --

            The platform version that your tasks in the service run on. A platform version is only specified for tasks using the Fargate launch type. If one isn't specified, the LATEST platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide .

          • platformFamily (string) --

            The operating system that your tasks in the service, or tasks are running on. A platform family is specified only for tasks using the Fargate launch type.

            All tasks that run as part of this service must use the same platformFamily value as the service, for example, LINUX. .

          • networkConfiguration (dict) --

            The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.

            • awsvpcConfiguration (dict) --

              The VPC subnets and security groups that are associated with a task.

              Note

              All specified subnets and security groups must be from the same VPC.

              • subnets (list) --

                The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

                Note

                All specified subnets must be from the same VPC.

                • (string) --

              • securityGroups (list) --

                The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

                Note

                All specified security groups must be from the same VPC.

                • (string) --

              • assignPublicIp (string) --

                Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

          • rolloutState (string) --

            Note

            The rolloutState of a service is only returned for services that use the rolling update (ECS ) deployment type that aren't behind a Classic Load Balancer.

            The rollout state of the deployment. When a service deployment is started, it begins in an IN_PROGRESS state. When the service reaches a steady state, the deployment transitions to a COMPLETED state. If the service fails to reach a steady state and circuit breaker is enabled, the deployment transitions to a FAILED state. A deployment in FAILED state doesn't launch any new tasks. For more information, see DeploymentCircuitBreaker .

          • rolloutStateReason (string) --

            A description of the rollout state of a deployment.

          • serviceConnectConfiguration (dict) --

            The details of the Service Connect configuration that's used by this deployment. Compare the configuration between multiple deployments when troubleshooting issues with new deployments.

            The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace.

            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 .

            • enabled (boolean) --

              Specifies whether to use Service Connect with this service.

            • namespace (string) --

              The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace for use with Service Connect. The namespace must be in the same Amazon Web Services Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about Cloud Map, see Working with Services in the Cloud Map Developer Guide .

            • services (list) --

              The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. You can specify up to X (30?) objects per Amazon ECS service.

              This field is not required for a "client" Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means.

              An object selects a port from the task definition, assigns a name for the Cloud Map service, and a list of aliases (endpoints) and ports for client applications to refer to this service.

              • (dict) --

                The Service Connect service object configuration. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                • portName (string) --

                  The portName must match the name of one of the portMappings from all the containers in the task definition of this Amazon ECS service.

                • discoveryName (string) --

                  The discoveryName is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                  If this field isn't specified, portName is used.

                • clientAliases (list) --

                  The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1.

                  Each alias ("endpoint") is a fully-qualified name and port number that other Amazon ECS tasks ("clients") can use to connect to this service.

                  Each name and port mapping must be unique within the namespace.

                  For each ServiceConnectService , you must provide at least one clientAlias with one port .

                  • (dict) --

                    Each alias ("endpoint") is a fully-qualified name and port number that other tasks ("clients") can use to connect to this service.

                    Each name and port mapping must be unique within the namespace.

                    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 .

                    • port (integer) --

                      The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace.

                      To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                    • dnsName (string) --

                      The dnsName is the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. Up to 127 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). A hyphen can't be the first character.

                      If this parameter isn't specified, the default value of discoveryName.namespace is used. If the discoveryName isn't specified, the portName.namespace from the task definition is used.

                      To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names are database , db , or the lowercase name of a database, such as mysql or redis . For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                • ingressPortOverride (integer) --

                  The port number for the Service Connect proxy to listen on.

                  Use the value of this field to bypass the proxy for traffic on the port number specified in the named portMapping in the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service.

                  In awsvpc mode and Fargate, the default value is the container port number. The container port number is in the portMapping in the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy.

            • logConfiguration (dict) --

              The log configuration for the container. This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to ` docker run https://docs.docker.com/engine/reference/commandline/run/`__ .

              By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation.

              Understand the following when specifying a log configuration for your containers.

              • Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon (shown in the valid values below). Additional log drivers may be available in future releases of the Amazon ECS container agent.

              • This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.

              • For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide .

              • For tasks that are on Fargate, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.

              • logDriver (string) --

                The log driver to use for the container.

                For tasks on Fargate, the supported log drivers are awslogs , splunk , and awsfirelens .

                For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs , fluentd , gelf , json-file , journald , logentries ,``syslog`` , splunk , and awsfirelens .

                For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide .

                For more information about using the awsfirelens log driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide .

                Note

                If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.

              • options (dict) --

                The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

                • (string) --

                  • (string) --

              • secretOptions (list) --

                The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

                • (dict) --

                  An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

                  • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

                  • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

                  For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

                  • name (string) --

                    The name of the secret.

                  • valueFrom (string) --

                    The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

                    For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

                    Note

                    If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

          • serviceConnectResources (list) --

            The list of Service Connect resources that are associated with this deployment. Each list entry maps a discovery name to a Cloud Map service name.

            • (dict) --

              The Service Connect resource. Each configuration maps a discovery name to a Cloud Map service name. The data is stored in Cloud Map as part of the Service Connect configuration for each discovery name of this Amazon ECS service.

              A task can resolve the dnsName for each of the clientAliases of a service. However a task can't resolve the discovery names. If you want to connect to a service, refer to the ServiceConnectConfiguration of that service for the list of clientAliases that you can use.

              • discoveryName (string) --

                The discovery name of this Service Connect resource.

                The discoveryName is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                If this field isn't specified, portName is used.

              • discoveryArn (string) --

                The Amazon Resource Name (ARN) for the namespace in Cloud Map that matches the discovery name for this Service Connect resource. You can use this ARN in other integrations with Cloud Map. However, Service Connect can't ensure connectivity outside of Amazon ECS.

      • roleArn (string) --

        The ARN of the IAM role that's associated with the service. It allows the Amazon ECS container agent to register container instances with an Elastic Load Balancing load balancer.

      • events (list) --

        The event stream for your service. A maximum of 100 of the latest events are displayed.

        • (dict) --

          The details for an event that's associated with a service.

          • id (string) --

            The ID string for the event.

          • createdAt (datetime) --

            The Unix timestamp for the time when the event was triggered.

          • message (string) --

            The event message.

      • createdAt (datetime) --

        The Unix timestamp for the time when the service was created.

      • placementConstraints (list) --

        The placement constraints for the tasks in the service.

        • (dict) --

          An object representing a constraint on task placement. For more information, see Task placement constraints in the Amazon Elastic Container Service Developer Guide .

          Note

          If you're using the Fargate launch type, task placement constraints aren't supported.

          • type (string) --

            The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to restrict the selection to a group of valid candidates.

          • expression (string) --

            A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is distinctInstance . For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide .

      • placementStrategy (list) --

        The placement strategy that determines how tasks for the service are placed.

        • (dict) --

          The task placement strategy for a task or service. For more information, see Task placement strategies in the Amazon Elastic Container Service Developer Guide .

          • type (string) --

            The type of placement strategy. The random placement strategy randomly places tasks on available candidates. The spread placement strategy spreads placement across available candidates evenly based on the field parameter. The binpack strategy places tasks on available candidates that have the least available amount of the resource that's specified with the field parameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.

          • field (string) --

            The field to apply the placement strategy against. For the spread placement strategy, valid values are instanceId (or host , which has the same effect), or any platform or custom attribute that's applied to a container instance, such as attribute:ecs.availability-zone . For the binpack placement strategy, valid values are cpu and memory . For the random placement strategy, this field is not used.

      • networkConfiguration (dict) --

        The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.

        • awsvpcConfiguration (dict) --

          The VPC subnets and security groups that are associated with a task.

          Note

          All specified subnets and security groups must be from the same VPC.

          • subnets (list) --

            The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

            Note

            All specified subnets must be from the same VPC.

            • (string) --

          • securityGroups (list) --

            The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

            Note

            All specified security groups must be from the same VPC.

            • (string) --

          • assignPublicIp (string) --

            Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

      • healthCheckGracePeriodSeconds (integer) --

        The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started.

      • schedulingStrategy (string) --

        The scheduling strategy to use for the service. For more information, see Services .

        There are two service scheduler strategies available.

        • REPLICA -The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions.

        • DAEMON -The daemon scheduling strategy deploys exactly one task on each active container instance. This task meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks. It stop tasks that don't meet the placement constraints.

        Note

        Fargate tasks don't support the DAEMON scheduling strategy.

      • deploymentController (dict) --

        The deployment controller type the service is using.

        • type (string) --

          The deployment controller type to use.

          There are three deployment controller types available:

          ECS

          The rolling update (ECS ) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration .

          CODE_DEPLOY

          The blue/green (CODE_DEPLOY ) deployment type uses the blue/green deployment model powered by CodeDeploy, which allows you to verify a new deployment of a service before sending production traffic to it.

          EXTERNAL

          The external (EXTERNAL ) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.

      • tags (list) --

        The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value. You define bot the key and value.

        The following basic restrictions apply to tags:

        • Maximum number of tags per resource - 50

        • For each resource, each tag key must be unique, and each tag key can have only one value.

        • Maximum key length - 128 Unicode characters in UTF-8

        • Maximum value length - 256 Unicode characters in UTF-8

        • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

        • Tag keys and values are case-sensitive.

        • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

        • (dict) --

          The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

          The following basic restrictions apply to tags:

          • Maximum number of tags per resource - 50

          • For each resource, each tag key must be unique, and each tag key can have only one value.

          • Maximum key length - 128 Unicode characters in UTF-8

          • Maximum value length - 256 Unicode characters in UTF-8

          • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

          • Tag keys and values are case-sensitive.

          • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

          • key (string) --

            One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

          • value (string) --

            The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

      • createdBy (string) --

        The principal that created the service.

      • enableECSManagedTags (boolean) --

        Determines whether to use Amazon ECS managed tags for the tasks in the service. For more information, see Tagging Your Amazon ECS Resources in the Amazon Elastic Container Service Developer Guide .

      • propagateTags (string) --

        Determines whether to propagate the tags from the task definition or the service to the task. If no value is specified, the tags aren't propagated.

      • enableExecuteCommand (boolean) --

        Determines whether the execute command functionality is enabled for the service. If true , the execute command functionality is enabled for all containers in tasks as part of the service.

DeregisterTaskDefinition (updated) Link ¶
Changes (response)
{'taskDefinition': {'containerDefinitions': {'portMappings': {'appProtocol': 'http '
                                                                             '| '
                                                                             'http2 '
                                                                             '| '
                                                                             'grpc',
                                                              'name': 'string'}}}}

Deregisters the specified task definition by family and revision. Upon deregistration, the task definition is marked as INACTIVE . Existing tasks and services that reference an INACTIVE task definition continue to run without disruption. Existing services that reference an INACTIVE task definition can still scale up or down by modifying the service's desired count.

You can't use an INACTIVE task definition to run new tasks or create new services, and you can't update an existing service to reference an INACTIVE task definition. However, there may be up to a 10-minute window following deregistration where these restrictions have not yet taken effect.

Note

At this time, INACTIVE task definitions remain discoverable in your account indefinitely. However, this behavior is subject to change in the future. We don't recommend that you rely on INACTIVE task definitions persisting beyond the lifecycle of any associated tasks and services.

See also: AWS API Documentation

Request Syntax

client.deregister_task_definition(
    taskDefinition='string'
)
type taskDefinition

string

param taskDefinition

[REQUIRED]

The family and revision (family:revision ) or full Amazon Resource Name (ARN) of the task definition to deregister. You must specify a revision .

rtype

dict

returns

Response Syntax

{
    'taskDefinition': {
        'taskDefinitionArn': 'string',
        'containerDefinitions': [
            {
                'name': 'string',
                'image': 'string',
                'repositoryCredentials': {
                    'credentialsParameter': 'string'
                },
                'cpu': 123,
                'memory': 123,
                'memoryReservation': 123,
                'links': [
                    'string',
                ],
                'portMappings': [
                    {
                        'containerPort': 123,
                        'hostPort': 123,
                        'protocol': 'tcp'|'udp',
                        'name': 'string',
                        'appProtocol': 'http'|'http2'|'grpc'
                    },
                ],
                'essential': True|False,
                'entryPoint': [
                    'string',
                ],
                'command': [
                    'string',
                ],
                'environment': [
                    {
                        'name': 'string',
                        'value': 'string'
                    },
                ],
                'environmentFiles': [
                    {
                        'value': 'string',
                        'type': 's3'
                    },
                ],
                'mountPoints': [
                    {
                        'sourceVolume': 'string',
                        'containerPath': 'string',
                        'readOnly': True|False
                    },
                ],
                'volumesFrom': [
                    {
                        'sourceContainer': 'string',
                        'readOnly': True|False
                    },
                ],
                'linuxParameters': {
                    'capabilities': {
                        'add': [
                            'string',
                        ],
                        'drop': [
                            'string',
                        ]
                    },
                    'devices': [
                        {
                            'hostPath': 'string',
                            'containerPath': 'string',
                            'permissions': [
                                'read'|'write'|'mknod',
                            ]
                        },
                    ],
                    'initProcessEnabled': True|False,
                    'sharedMemorySize': 123,
                    'tmpfs': [
                        {
                            'containerPath': 'string',
                            'size': 123,
                            'mountOptions': [
                                'string',
                            ]
                        },
                    ],
                    'maxSwap': 123,
                    'swappiness': 123
                },
                'secrets': [
                    {
                        'name': 'string',
                        'valueFrom': 'string'
                    },
                ],
                'dependsOn': [
                    {
                        'containerName': 'string',
                        'condition': 'START'|'COMPLETE'|'SUCCESS'|'HEALTHY'
                    },
                ],
                'startTimeout': 123,
                'stopTimeout': 123,
                'hostname': 'string',
                'user': 'string',
                'workingDirectory': 'string',
                'disableNetworking': True|False,
                'privileged': True|False,
                'readonlyRootFilesystem': True|False,
                'dnsServers': [
                    'string',
                ],
                'dnsSearchDomains': [
                    'string',
                ],
                'extraHosts': [
                    {
                        'hostname': 'string',
                        'ipAddress': 'string'
                    },
                ],
                'dockerSecurityOptions': [
                    'string',
                ],
                'interactive': True|False,
                'pseudoTerminal': True|False,
                'dockerLabels': {
                    'string': 'string'
                },
                'ulimits': [
                    {
                        'name': 'core'|'cpu'|'data'|'fsize'|'locks'|'memlock'|'msgqueue'|'nice'|'nofile'|'nproc'|'rss'|'rtprio'|'rttime'|'sigpending'|'stack',
                        'softLimit': 123,
                        'hardLimit': 123
                    },
                ],
                'logConfiguration': {
                    'logDriver': 'json-file'|'syslog'|'journald'|'gelf'|'fluentd'|'awslogs'|'splunk'|'awsfirelens',
                    'options': {
                        'string': 'string'
                    },
                    'secretOptions': [
                        {
                            'name': 'string',
                            'valueFrom': 'string'
                        },
                    ]
                },
                'healthCheck': {
                    'command': [
                        'string',
                    ],
                    'interval': 123,
                    'timeout': 123,
                    'retries': 123,
                    'startPeriod': 123
                },
                'systemControls': [
                    {
                        'namespace': 'string',
                        'value': 'string'
                    },
                ],
                'resourceRequirements': [
                    {
                        'value': 'string',
                        'type': 'GPU'|'InferenceAccelerator'
                    },
                ],
                'firelensConfiguration': {
                    'type': 'fluentd'|'fluentbit',
                    'options': {
                        'string': 'string'
                    }
                }
            },
        ],
        'family': 'string',
        'taskRoleArn': 'string',
        'executionRoleArn': 'string',
        'networkMode': 'bridge'|'host'|'awsvpc'|'none',
        'revision': 123,
        'volumes': [
            {
                'name': 'string',
                'host': {
                    'sourcePath': 'string'
                },
                'dockerVolumeConfiguration': {
                    'scope': 'task'|'shared',
                    'autoprovision': True|False,
                    'driver': 'string',
                    'driverOpts': {
                        'string': 'string'
                    },
                    'labels': {
                        'string': 'string'
                    }
                },
                'efsVolumeConfiguration': {
                    'fileSystemId': 'string',
                    'rootDirectory': 'string',
                    'transitEncryption': 'ENABLED'|'DISABLED',
                    'transitEncryptionPort': 123,
                    'authorizationConfig': {
                        'accessPointId': 'string',
                        'iam': 'ENABLED'|'DISABLED'
                    }
                },
                'fsxWindowsFileServerVolumeConfiguration': {
                    'fileSystemId': 'string',
                    'rootDirectory': 'string',
                    'authorizationConfig': {
                        'credentialsParameter': 'string',
                        'domain': 'string'
                    }
                }
            },
        ],
        'status': 'ACTIVE'|'INACTIVE',
        'requiresAttributes': [
            {
                'name': 'string',
                'value': 'string',
                'targetType': 'container-instance',
                'targetId': 'string'
            },
        ],
        'placementConstraints': [
            {
                'type': 'memberOf',
                'expression': 'string'
            },
        ],
        'compatibilities': [
            'EC2'|'FARGATE'|'EXTERNAL',
        ],
        'runtimePlatform': {
            'cpuArchitecture': 'X86_64'|'ARM64',
            'operatingSystemFamily': 'WINDOWS_SERVER_2019_FULL'|'WINDOWS_SERVER_2019_CORE'|'WINDOWS_SERVER_2016_FULL'|'WINDOWS_SERVER_2004_CORE'|'WINDOWS_SERVER_2022_CORE'|'WINDOWS_SERVER_2022_FULL'|'WINDOWS_SERVER_20H2_CORE'|'LINUX'
        },
        'requiresCompatibilities': [
            'EC2'|'FARGATE'|'EXTERNAL',
        ],
        'cpu': 'string',
        'memory': 'string',
        'inferenceAccelerators': [
            {
                'deviceName': 'string',
                'deviceType': 'string'
            },
        ],
        'pidMode': 'host'|'task',
        'ipcMode': 'host'|'task'|'none',
        'proxyConfiguration': {
            'type': 'APPMESH',
            'containerName': 'string',
            'properties': [
                {
                    'name': 'string',
                    'value': 'string'
                },
            ]
        },
        'registeredAt': datetime(2015, 1, 1),
        'deregisteredAt': datetime(2015, 1, 1),
        'registeredBy': 'string',
        'ephemeralStorage': {
            'sizeInGiB': 123
        }
    }
}

Response Structure

  • (dict) --

    • taskDefinition (dict) --

      The full description of the deregistered task.

      • taskDefinitionArn (string) --

        The full Amazon Resource Name (ARN) of the task definition.

      • containerDefinitions (list) --

        A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide .

        • (dict) --

          Container definitions are used in task definitions to describe the different containers that are launched as part of a task.

          • name (string) --

            The name of a container. If you're linking multiple containers together in a task definition, the name of one container can be entered in the links of another container to connect the containers. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This parameter maps to name in the Create a container section of the Docker Remote API and the --name option to docker run .

          • image (string) --

            The image used to start a container. This string is passed directly to the Docker daemon. By default, images in the Docker Hub registry are available. Other repositories are specified with either `` repository-url /image :tag `` or `` repository-url /image @*digest* `` . Up to 255 letters (uppercase and lowercase), numbers, hyphens, underscores, colons, periods, forward slashes, and number signs are allowed. This parameter maps to Image in the Create a container section of the Docker Remote API and the IMAGE parameter of docker run .

            • When a new task starts, the Amazon ECS container agent pulls the latest version of the specified image and tag for the container to use. However, subsequent updates to a repository image aren't propagated to already running tasks.

            • Images in Amazon ECR repositories can be specified by either using the full registry/repository:tag or registry/repository@digest . For example, 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>:latest or 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>@sha256:94afd1f2e64d908bc90dbca0035a5b567EXAMPLE .

            • Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo ).

            • Images in other repositories on Docker Hub are qualified with an organization name (for example, amazon/amazon-ecs-agent ).

            • Images in other online repositories are qualified further by a domain name (for example, quay.io/assemblyline/ubuntu ).

          • repositoryCredentials (dict) --

            The private repository authentication credentials to use.

            • credentialsParameter (string) --

              The Amazon Resource Name (ARN) of the secret containing the private repository credentials.

              Note

              When you use the Amazon ECS API, CLI, or Amazon Web Services SDK, if the secret exists in the same Region as the task that you're launching then you can use either the full ARN or the name of the secret. When you use the Amazon Web Services Management Console, you must specify the full ARN of the secret.

          • cpu (integer) --

            The number of cpu units reserved for the container. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run .

            This field is optional for tasks using the Fargate launch type, and the only requirement is that the total amount of CPU reserved for all containers within a task be lower than the task-level cpu value.

            Note

            You can determine the number of CPU units that are available per EC2 instance type by multiplying the vCPUs listed for that instance type on the Amazon EC2 Instances detail page by 1,024.

            Linux containers share unallocated CPU units with other containers on the container instance with the same ratio as their allocated amount. For example, if you run a single-container task on a single-core instance type with 512 CPU units specified for that container, and that's the only task running on the container instance, that container could use the full 1,024 CPU unit share at any given time. However, if you launched another copy of the same task on that container instance, each task is guaranteed a minimum of 512 CPU units when needed. Moreover, each container could float to higher CPU usage if the other container was not using it. If both tasks were 100% active all of the time, they would be limited to 512 CPU units.

            On Linux container instances, the Docker daemon on the container instance uses the CPU value to calculate the relative CPU share ratios for running containers. For more information, see CPU share constraint in the Docker documentation. The minimum valid CPU share value that the Linux kernel allows is 2. However, the CPU parameter isn't required, and you can use CPU values below 2 in your container definitions. For CPU values below 2 (including null), the behavior varies based on your Amazon ECS container agent version:

            • Agent versions less than or equal to 1.1.0: Null and zero CPU values are passed to Docker as 0, which Docker then converts to 1,024 CPU shares. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares.

            • Agent versions greater than or equal to 1.2.0: Null, zero, and CPU values of 1 are passed to Docker as 2.

            On Windows container instances, the CPU limit is enforced as an absolute limit, or a quota. Windows containers only have access to the specified amount of CPU that's described in the task definition. A null or zero CPU value is passed to Docker as 0 , which Windows interprets as 1% of one CPU.

          • memory (integer) --

            The amount (in MiB) of memory to present to the container. If your container attempts to exceed the memory specified here, the container is killed. The total amount of memory reserved for all containers within a task must be lower than the task memory value, if one is specified. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run .

            If using the Fargate launch type, this parameter is optional.

            If using the EC2 launch type, you must specify either a task-level memory value or a container-level memory value. If you specify both a container-level memory and memoryReservation value, memory must be greater than memoryReservation . If you specify memoryReservation , then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used.

            The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers.

            The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers.

          • memoryReservation (integer) --

            The soft limit (in MiB) of memory to reserve for the container. When system memory is under heavy contention, Docker attempts to keep the container memory to this soft limit. However, your container can consume more memory when it needs to, up to either the hard limit specified with the memory parameter (if applicable), or all of the available memory on the container instance, whichever comes first. This parameter maps to MemoryReservation in the Create a container section of the Docker Remote API and the --memory-reservation option to docker run .

            If a task-level memory value is not specified, you must specify a non-zero integer for one or both of memory or memoryReservation in a container definition. If you specify both, memory must be greater than memoryReservation . If you specify memoryReservation , then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used.

            For example, if your container normally uses 128 MiB of memory, but occasionally bursts to 256 MiB of memory for short periods of time, you can set a memoryReservation of 128 MiB, and a memory hard limit of 300 MiB. This configuration would allow the container to only reserve 128 MiB of memory from the remaining resources on the container instance, but also allow the container to consume more memory resources when needed.

            The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers.

            The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers.

          • links (list) --

            The links parameter allows containers to communicate with each other without the need for port mappings. This parameter is only supported if the network mode of a task definition is bridge . The name:internalName construct is analogous to name:alias in Docker links. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. For more information about linking Docker containers, go to Legacy container links in the Docker documentation. This parameter maps to Links in the Create a container section of the Docker Remote API and the --link option to docker run .

            Note

            This parameter is not supported for Windows containers.

            Warning

            Containers that are collocated on a single container instance may be able to communicate with each other without requiring links or host port mappings. Network isolation is achieved on the container instance using security groups and VPC settings.

            • (string) --

          • portMappings (list) --

            The list of port mappings for the container. Port mappings allow containers to access ports on the host container instance to send or receive traffic.

            For task definitions that use the awsvpc network mode, only specify the containerPort . The hostPort can be left blank or it must be the same value as the containerPort .

            Port mappings on Windows use the NetNAT gateway address rather than localhost . There's no loopback for port mappings on Windows, so you can't access a container's mapped port from the host itself.

            This parameter maps to PortBindings in the Create a container section of the Docker Remote API and the --publish option to docker run . If the network mode of a task definition is set to none , then you can't specify port mappings. If the network mode of a task definition is set to host , then host ports must either be undefined or they must match the container port in the port mapping.

            Note

            After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the Network Bindings section of a container description for a selected task in the Amazon ECS console. The assignments are also visible in the networkBindings section DescribeTasks responses.

            • (dict) --

              Port mappings allow containers to access ports on the host container instance to send or receive traffic. Port mappings are specified as part of the container definition.

              If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort . The hostPort can be left blank or it must be the same value as the containerPort .

              Note

              You can't expose the same container port for multiple protocols. If you attempt this, an error is returned.

              After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the networkBindings section of DescribeTasks API responses.

              • containerPort (integer) --

                The port number on the container that's bound to the user-specified or automatically assigned host port.

                If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort .

                If you use containers in a task with the bridge network mode and you specify a container port and not a host port, your container automatically receives a host port in the ephemeral port range. For more information, see hostPort . Port mappings that are automatically assigned in this way do not count toward the 100 reserved ports limit of a container instance.

              • hostPort (integer) --

                The port number on the container instance to reserve for your container.

                If you use containers in a task with the awsvpc or host network mode, the hostPort can either be left blank or set to the same value as the containerPort .

                If you use containers in a task with the bridge network mode, you can specify a non-reserved host port for your container port mapping, or you can omit the hostPort (or set it to 0 ) while specifying a containerPort and your container automatically receives a port in the ephemeral port range for your container instance operating system and Docker version.

                The default ephemeral port range for Docker version 1.6.0 and later is listed on the instance under /proc/sys/net/ipv4/ip_local_port_range . If this kernel parameter is unavailable, the default ephemeral port range from 49153 through 65535 is used. Do not attempt to specify a host port in the ephemeral port range as these are reserved for automatic assignment. In general, ports below 32768 are outside of the ephemeral port range.

                The default reserved ports are 22 for SSH, the Docker ports 2375 and 2376, and the Amazon ECS container agent ports 51678-51680. Any host port that was previously specified in a running task is also reserved while the task is running. That is, after a task stops, the host port is released. The current reserved ports are displayed in the remainingResources of DescribeContainerInstances output. A container instance can have up to 100 reserved ports at a time. This number includes the default reserved ports. Automatically assigned ports aren't included in the 100 reserved ports quota.

              • protocol (string) --

                The protocol used for the port mapping. Valid values are tcp and udp . The default is tcp .

              • name (string) --

                The name that's used for the port mapping. This parameter only applies to Service Connect. This parameter is the name that you use in the serviceConnectConfiguration of a service. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

              • appProtocol (string) --

                The application protocol that's used for the port mapping. This parameter only applies to Service Connect. We recommend that you set this parameter to be consistent with the protocol that your application uses. If you set this parameter, Amazon ECS adds protocol-specific connection handling to the Service Connect proxy. If you set this parameter, Amazon ECS adds protocol-specific telemetry in the Amazon ECS console and CloudWatch.

                If you don't set a value for this parameter, then TCP is used. However, Amazon ECS doesn't add protocol-specific telemetry for TCP.

                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 .

          • essential (boolean) --

            If the essential parameter of a container is marked as true , and that container fails or stops for any reason, all other containers that are part of the task are stopped. If the essential parameter of a container is marked as false , its failure doesn't affect the rest of the containers in a task. If this parameter is omitted, a container is assumed to be essential.

            All tasks must have at least one essential container. If you have an application that's composed of multiple containers, group containers that are used for a common purpose into components, and separate the different components into multiple task definitions. For more information, see Application Architecture in the Amazon Elastic Container Service Developer Guide .

          • entryPoint (list) --

            Warning

            Early versions of the Amazon ECS container agent don't properly handle entryPoint parameters. If you have problems using entryPoint , update your container agent or enter your commands and arguments as command array items instead.

            The entry point that's passed to the container. This parameter maps to Entrypoint in the Create a container section of the Docker Remote API and the --entrypoint option to docker run . For more information, see https://docs.docker.com/engine/reference/builder/#entrypoint .

            • (string) --

          • command (list) --

            The command that's passed to the container. This parameter maps to Cmd in the Create a container section of the Docker Remote API and the COMMAND parameter to docker run . For more information, see https://docs.docker.com/engine/reference/builder/#cmd . If there are multiple arguments, each argument is a separated string in the array.

            • (string) --

          • environment (list) --

            The environment variables to pass to a container. This parameter maps to Env in the Create a container section of the Docker Remote API and the --env option to docker run .

            Warning

            We don't recommend that you use plaintext environment variables for sensitive information, such as credential data.

            • (dict) --

              A key-value pair object.

              • name (string) --

                The name of the key-value pair. For environment variables, this is the name of the environment variable.

              • value (string) --

                The value of the key-value pair. For environment variables, this is the value of the environment variable.

          • environmentFiles (list) --

            A list of files containing the environment variables to pass to a container. This parameter maps to the --env-file option to docker run .

            You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file contains an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

            If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying Environment Variables in the Amazon Elastic Container Service Developer Guide .

            • (dict) --

              A list of files containing the environment variables to pass to a container. You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file should contain an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

              If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying environment variables in the Amazon Elastic Container Service Developer Guide .

              This parameter is only supported for tasks hosted on Fargate using the following platform versions:

              • Linux platform version 1.4.0 or later.

              • Windows platform version 1.0.0 or later.

              • value (string) --

                The Amazon Resource Name (ARN) of the Amazon S3 object containing the environment variable file.

              • type (string) --

                The file type to use. The only supported value is s3 .

          • mountPoints (list) --

            The mount points for data volumes in your container.

            This parameter maps to Volumes in the Create a container section of the Docker Remote API and the --volume option to docker run .

            Windows containers can mount whole directories on the same drive as $env:ProgramData . Windows containers can't mount directories on a different drive, and mount point can't be across drives.

            • (dict) --

              Details for a volume mount point that's used in a container definition.

              • sourceVolume (string) --

                The name of the volume to mount. Must be a volume name referenced in the name parameter of task definition volume .

              • containerPath (string) --

                The path on the container to mount the host volume at.

              • readOnly (boolean) --

                If this value is true , the container has read-only access to the volume. If this value is false , then the container can write to the volume. The default value is false .

          • volumesFrom (list) --

            Data volumes to mount from another container. This parameter maps to VolumesFrom in the Create a container section of the Docker Remote API and the --volumes-from option to docker run .

            • (dict) --

              Details on a data volume from another container in the same task definition.

              • sourceContainer (string) --

                The name of another container within the same task definition to mount volumes from.

              • readOnly (boolean) --

                If this value is true , the container has read-only access to the volume. If this value is false , then the container can write to the volume. The default value is false .

          • linuxParameters (dict) --

            Linux-specific modifications that are applied to the container, such as Linux kernel capabilities. For more information see KernelCapabilities .

            Note

            This parameter is not supported for Windows containers.

            • capabilities (dict) --

              The Linux capabilities for the container that are added to or dropped from the default configuration provided by Docker.

              Note

              For tasks that use the Fargate launch type, capabilities is supported for all platform versions but the add parameter is only supported if using platform version 1.4.0 or later.

              • add (list) --

                The Linux capabilities for the container that have been added to the default configuration provided by Docker. This parameter maps to CapAdd in the Create a container section of the Docker Remote API and the --cap-add option to docker run .

                Note

                Tasks launched on Fargate only support adding the SYS_PTRACE kernel capability.

                Valid values: "ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" | "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" | "FOWNER" | "FSETID" | "IPC_LOCK" | "IPC_OWNER" | "KILL" | "LEASE" | "LINUX_IMMUTABLE" | "MAC_ADMIN" | "MAC_OVERRIDE" | "MKNOD" | "NET_ADMIN" | "NET_BIND_SERVICE" | "NET_BROADCAST" | "NET_RAW" | "SETFCAP" | "SETGID" | "SETPCAP" | "SETUID" | "SYS_ADMIN" | "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT" | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" | "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"

                • (string) --

              • drop (list) --

                The Linux capabilities for the container that have been removed from the default configuration provided by Docker. This parameter maps to CapDrop in the Create a container section of the Docker Remote API and the --cap-drop option to docker run .

                Valid values: "ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" | "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" | "FOWNER" | "FSETID" | "IPC_LOCK" | "IPC_OWNER" | "KILL" | "LEASE" | "LINUX_IMMUTABLE" | "MAC_ADMIN" | "MAC_OVERRIDE" | "MKNOD" | "NET_ADMIN" | "NET_BIND_SERVICE" | "NET_BROADCAST" | "NET_RAW" | "SETFCAP" | "SETGID" | "SETPCAP" | "SETUID" | "SYS_ADMIN" | "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT" | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" | "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"

                • (string) --

            • devices (list) --

              Any host devices to expose to the container. This parameter maps to Devices in the Create a container section of the Docker Remote API and the --device option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the devices parameter isn't supported.

              • (dict) --

                An object representing a container instance host device.

                • hostPath (string) --

                  The path for the device on the host container instance.

                • containerPath (string) --

                  The path inside the container at which to expose the host device.

                • permissions (list) --

                  The explicit permissions to provide to the container for the device. By default, the container has permissions for read , write , and mknod for the device.

                  • (string) --

            • initProcessEnabled (boolean) --

              Run an init process inside the container that forwards signals and reaps processes. This parameter maps to the --init option to docker run . This parameter requires version 1.25 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            • sharedMemorySize (integer) --

              The value for the size (in MiB) of the /dev/shm volume. This parameter maps to the --shm-size option to docker run .

              Note

              If you are using tasks that use the Fargate launch type, the sharedMemorySize parameter is not supported.

            • tmpfs (list) --

              The container path, mount options, and size (in MiB) of the tmpfs mount. This parameter maps to the --tmpfs option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the tmpfs parameter isn't supported.

              • (dict) --

                The container path, mount options, and size of the tmpfs mount.

                • containerPath (string) --

                  The absolute file path where the tmpfs volume is to be mounted.

                • size (integer) --

                  The maximum size (in MiB) of the tmpfs volume.

                • mountOptions (list) --

                  The list of tmpfs volume mount options.

                  Valid values: "defaults" | "ro" | "rw" | "suid" | "nosuid" | "dev" | "nodev" | "exec" | "noexec" | "sync" | "async" | "dirsync" | "remount" | "mand" | "nomand" | "atime" | "noatime" | "diratime" | "nodiratime" | "bind" | "rbind" | "unbindable" | "runbindable" | "private" | "rprivate" | "shared" | "rshared" | "slave" | "rslave" | "relatime" | "norelatime" | "strictatime" | "nostrictatime" | "mode" | "uid" | "gid" | "nr_inodes" | "nr_blocks" | "mpol"

                  • (string) --

            • maxSwap (integer) --

              The total amount of swap memory (in MiB) a container can use. This parameter will be translated to the --memory-swap option to docker run where the value would be the sum of the container memory plus the maxSwap value.

              If a maxSwap value of 0 is specified, the container will not use swap. Accepted values are 0 or any positive integer. If the maxSwap parameter is omitted, the container will use the swap configuration for the container instance it is running on. A maxSwap value must be set for the swappiness parameter to be used.

              Note

              If you're using tasks that use the Fargate launch type, the maxSwap parameter isn't supported.

            • swappiness (integer) --

              This allows you to tune a container's memory swappiness behavior. A swappiness value of 0 will cause swapping to not happen unless absolutely necessary. A swappiness value of 100 will cause pages to be swapped very aggressively. Accepted values are whole numbers between 0 and 100 . If the swappiness parameter is not specified, a default value of 60 is used. If a value is not specified for maxSwap then this parameter is ignored. This parameter maps to the --memory-swappiness option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the swappiness parameter isn't supported.

          • secrets (list) --

            The secrets to pass to the container. For more information, see Specifying Sensitive Data in the Amazon Elastic Container Service Developer Guide .

            • (dict) --

              An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

              • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

              • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

              For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

              • name (string) --

                The name of the secret.

              • valueFrom (string) --

                The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

                For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

                Note

                If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

          • dependsOn (list) --

            The dependencies defined for container startup and shutdown. A container can contain multiple dependencies on other containers in a task definition. When a dependency is defined for container startup, for container shutdown it is reversed.

            For tasks using the EC2 launch type, the container instances require at least version 1.26.0 of the container agent to turn on container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            • (dict) --

              The dependencies defined for container startup and shutdown. A container can contain multiple dependencies. When a dependency is defined for container startup, for container shutdown it is reversed.

              Your Amazon ECS container instances require at least version 1.26.0 of the container agent to use container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

              Note

              For tasks that use the Fargate launch type, the task or service requires the following platforms:

              • Linux platform version 1.3.0 or later.

              • Windows platform version 1.0.0 or later.

              • containerName (string) --

                The name of a container.

              • condition (string) --

                The dependency condition of the container. The following are the available conditions and their behavior:

                • START - This condition emulates the behavior of links and volumes today. It validates that a dependent container is started before permitting other containers to start.

                • COMPLETE - This condition validates that a dependent container runs to completion (exits) before permitting other containers to start. This can be useful for nonessential containers that run a script and then exit. This condition can't be set on an essential container.

                • SUCCESS - This condition is the same as COMPLETE , but it also requires that the container exits with a zero status. This condition can't be set on an essential container.

                • HEALTHY - This condition validates that the dependent container passes its Docker health check before permitting other containers to start. This requires that the dependent container has health checks configured. This condition is confirmed only at task startup.

          • startTimeout (integer) --

            Time duration (in seconds) to wait before giving up on resolving dependencies for a container. For example, you specify two containers in a task definition with containerA having a dependency on containerB reaching a COMPLETE , SUCCESS , or HEALTHY status. If a startTimeout value is specified for containerB and it doesn't reach the desired status within that time then containerA gives up and not start. This results in the task transitioning to a STOPPED state.

            Note

            When the ECS_CONTAINER_START_TIMEOUT container agent configuration variable is used, it's enforced independently from this start timeout value.

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            For tasks using the EC2 launch type, your container instances require at least version 1.26.0 of the container agent to use a container start timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

          • stopTimeout (integer) --

            Time duration (in seconds) to wait before the container is forcefully killed if it doesn't exit normally on its own.

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            The max stop timeout value is 120 seconds and if the parameter is not specified, the default value of 30 seconds is used.

            For tasks that use the EC2 launch type, if the stopTimeout parameter isn't specified, the value set for the Amazon ECS container agent configuration variable ECS_CONTAINER_STOP_TIMEOUT is used. If neither the stopTimeout parameter or the ECS_CONTAINER_STOP_TIMEOUT agent configuration variable are set, then the default values of 30 seconds for Linux containers and 30 seconds on Windows containers are used. Your container instances require at least version 1.26.0 of the container agent to use a container stop timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

          • hostname (string) --

            The hostname to use for your container. This parameter maps to Hostname in the Create a container section of the Docker Remote API and the --hostname option to docker run .

            Note

            The hostname parameter is not supported if you're using the awsvpc network mode.

          • user (string) --

            The user to use inside the container. This parameter maps to User in the Create a container section of the Docker Remote API and the --user option to docker run .

            Warning

            When running tasks using the host network mode, don't run containers using the root user (UID 0). We recommend using a non-root user for better security.

            You can specify the user using the following formats. If specifying a UID or GID, you must specify it as a positive integer.

            • user

            • user:group

            • uid

            • uid:gid

            • user:gid

            • uid:group

            Note

            This parameter is not supported for Windows containers.

          • workingDirectory (string) --

            The working directory to run commands inside the container in. This parameter maps to WorkingDir in the Create a container section of the Docker Remote API and the --workdir option to docker run .

          • disableNetworking (boolean) --

            When this parameter is true, networking is disabled within the container. This parameter maps to NetworkDisabled in the Create a container section of the Docker Remote API .

            Note

            This parameter is not supported for Windows containers.

          • privileged (boolean) --

            When this parameter is true, the container is given elevated privileges on the host container instance (similar to the root user). This parameter maps to Privileged in the Create a container section of the Docker Remote API and the --privileged option to docker run .

            Note

            This parameter is not supported for Windows containers or tasks run on Fargate.

          • readonlyRootFilesystem (boolean) --

            When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs in the Create a container section of the Docker Remote API and the --read-only option to docker run .

            Note

            This parameter is not supported for Windows containers.

          • dnsServers (list) --

            A list of DNS servers that are presented to the container. This parameter maps to Dns in the Create a container section of the Docker Remote API and the --dns option to docker run .

            Note

            This parameter is not supported for Windows containers.

            • (string) --

          • dnsSearchDomains (list) --

            A list of DNS search domains that are presented to the container. This parameter maps to DnsSearch in the Create a container section of the Docker Remote API and the --dns-search option to docker run .

            Note

            This parameter is not supported for Windows containers.

            • (string) --

          • extraHosts (list) --

            A list of hostnames and IP address mappings to append to the /etc/hosts file on the container. This parameter maps to ExtraHosts in the Create a container section of the Docker Remote API and the --add-host option to docker run .

            Note

            This parameter isn't supported for Windows containers or tasks that use the awsvpc network mode.

            • (dict) --

              Hostnames and IP address entries that are added to the /etc/hosts file of a container via the extraHosts parameter of its ContainerDefinition .

              • hostname (string) --

                The hostname to use in the /etc/hosts entry.

              • ipAddress (string) --

                The IP address to use in the /etc/hosts entry.

          • dockerSecurityOptions (list) --

            A list of strings to provide custom labels for SELinux and AppArmor multi-level security systems. This field isn't valid for containers in tasks using the Fargate launch type.

            With Windows containers, this parameter can be used to reference a credential spec file when configuring a container for Active Directory authentication. For more information, see Using gMSAs for Windows Containers in the Amazon Elastic Container Service Developer Guide .

            This parameter maps to SecurityOpt in the Create a container section of the Docker Remote API and the --security-opt option to docker run .

            Note

            The Amazon ECS container agent running on a container instance must register with the ECS_SELINUX_CAPABLE=true or ECS_APPARMOR_CAPABLE=true environment variables before containers placed on that instance can use these security options. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide .

            For more information about valid values, see Docker Run Security Configuration .

            Valid values: "no-new-privileges" | "apparmor:PROFILE" | "label:value" | "credentialspec:CredentialSpecFilePath"

            • (string) --

          • interactive (boolean) --

            When this parameter is true , you can deploy containerized applications that require stdin or a tty to be allocated. This parameter maps to OpenStdin in the Create a container section of the Docker Remote API and the --interactive option to docker run .

          • pseudoTerminal (boolean) --

            When this parameter is true , a TTY is allocated. This parameter maps to Tty in the Create a container section of the Docker Remote API and the --tty option to docker run .

          • dockerLabels (dict) --

            A key/value map of labels to add to the container. This parameter maps to Labels in the Create a container section of the Docker Remote API and the --label option to docker run . This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            • (string) --

              • (string) --

          • ulimits (list) --

            A list of ulimits to set in the container. If a ulimit value is specified in a task definition, it overrides the default values set by Docker. This parameter maps to Ulimits in the Create a container section of the Docker Remote API and the --ulimit option to docker run . Valid naming values are displayed in the Ulimit data type.

            Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and hard limit is 4096 .

            This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            Note

            This parameter is not supported for Windows containers.

            • (dict) --

              The ulimit settings to pass to the container.

              Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and hard limit is 4096 .

              • name (string) --

                The type of the ulimit .

              • softLimit (integer) --

                The soft limit for the ulimit type.

              • hardLimit (integer) --

                The hard limit for the ulimit type.

          • logConfiguration (dict) --

            The log configuration specification for the container.

            This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to docker run . By default, containers use the same logging driver that the Docker daemon uses. However the container can use a different logging driver than the Docker daemon by specifying a log driver with this parameter in the container definition. To use a different logging driver for a container, the log system must be configured properly on the container instance (or on a different log server for remote logging options). For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation.

            Note

            Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type). Additional log drivers may be available in future releases of the Amazon ECS container agent.

            This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            Note

            The Amazon ECS container agent running on a container instance must register the logging drivers available on that instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide .

            • logDriver (string) --

              The log driver to use for the container.

              For tasks on Fargate, the supported log drivers are awslogs , splunk , and awsfirelens .

              For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs , fluentd , gelf , json-file , journald , logentries ,``syslog`` , splunk , and awsfirelens .

              For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide .

              For more information about using the awsfirelens log driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide .

              Note

              If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.

            • options (dict) --

              The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

              • (string) --

                • (string) --

            • secretOptions (list) --

              The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

              • (dict) --

                An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

                • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

                • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

                For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

                • name (string) --

                  The name of the secret.

                • valueFrom (string) --

                  The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

                  For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

                  Note

                  If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

          • healthCheck (dict) --

            The container health check command and associated configuration parameters for the container. This parameter maps to HealthCheck in the Create a container section of the Docker Remote API and the HEALTHCHECK parameter of docker run .

            • command (list) --

              A string array representing the command that the container runs to determine if it is healthy. The string array must start with CMD to run the command arguments directly, or CMD-SHELL to run the command with the container's default shell.

              When you use the Amazon Web Services Management Console JSON panel, the Command Line Interface, or the APIs, enclose the list of commands in brackets.

              [ "CMD-SHELL", "curl -f http://localhost/ || exit 1" ]

              You don't need to include the brackets when you use the Amazon Web Services Management Console.

              "CMD-SHELL", "curl -f http://localhost/ || exit 1"

              An exit code of 0 indicates success, and non-zero exit code indicates failure. For more information, see HealthCheck in the Create a container section of the Docker Remote API .

              • (string) --

            • interval (integer) --

              The time period in seconds between each health check execution. You may specify between 5 and 300 seconds. The default value is 30 seconds.

            • timeout (integer) --

              The time period in seconds to wait for a health check to succeed before it is considered a failure. You may specify between 2 and 60 seconds. The default value is 5.

            • retries (integer) --

              The number of times to retry a failed health check before the container is considered unhealthy. You may specify between 1 and 10 retries. The default value is 3.

            • startPeriod (integer) --

              The optional grace period to provide containers time to bootstrap before failed health checks count towards the maximum number of retries. You can specify between 0 and 300 seconds. By default, the startPeriod is disabled.

              Note

              If a health check succeeds within the startPeriod , then the container is considered healthy and any subsequent failures count toward the maximum number of retries.

          • systemControls (list) --

            A list of namespaced kernel parameters to set in the container. This parameter maps to Sysctls in the Create a container section of the Docker Remote API and the --sysctl option to docker run .

            Note

            We don't recommended that you specify network-related systemControls parameters for multiple containers in a single task that also uses either the awsvpc or host network modes. For tasks that use the awsvpc network mode, the container that's started last determines which systemControls parameters take effect. For tasks that use the host network mode, it changes the container instance's namespaced kernel parameters as well as the containers.

            • (dict) --

              A list of namespaced kernel parameters to set in the container. This parameter maps to Sysctls in the Create a container section of the Docker Remote API and the --sysctl option to docker run .

              We don't recommend that you specify network-related systemControls parameters for multiple containers in a single task. This task also uses either the awsvpc or host network mode. It does it for the following reasons.

              • For tasks that use the awsvpc network mode, if you set systemControls for any container, it applies to all containers in the task. If you set different systemControls for multiple containers in a single task, the container that's started last determines which systemControls take effect.

              • For tasks that use the host network mode, the systemControls parameter applies to the container instance's kernel parameter and that of all containers of any tasks running on that container instance.

              • namespace (string) --

                The namespaced kernel parameter to set a value for.

              • value (string) --

                The value for the namespaced kernel parameter that's specified in namespace .

          • resourceRequirements (list) --

            The type and amount of a resource to assign to a container. The only supported resource is a GPU.

            • (dict) --

              The type and amount of a resource to assign to a container. The supported resource types are GPUs and Elastic Inference accelerators. For more information, see Working with GPUs on Amazon ECS or Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide

              • value (string) --

                The value for the specified resource type.

                If the GPU type is used, the value is the number of physical GPUs the Amazon ECS container agent reserves for the container. The number of GPUs that's reserved for all containers in a task can't exceed the number of available GPUs on the container instance that the task is launched on.

                If the InferenceAccelerator type is used, the value matches the deviceName for an InferenceAccelerator specified in a task definition.

              • type (string) --

                The type of resource to assign to a container. The supported values are GPU or InferenceAccelerator .

          • firelensConfiguration (dict) --

            The FireLens configuration for the container. This is used to specify and configure a log router for container logs. For more information, see Custom Log Routing in the Amazon Elastic Container Service Developer Guide .

            • type (string) --

              The log router to use. The valid values are fluentd or fluentbit .

            • options (dict) --

              The options to use when configuring the log router. This field is optional and can be used to specify a custom configuration file or to add additional metadata, such as the task, task definition, cluster, and container instance details to the log event. If specified, the syntax to use is "options":{"enable-ecs-log-metadata":"true|false","config-file-type:"s3|file","config-file-value":"arn:aws:s3:::mybucket/fluent.conf|filepath"} . For more information, see Creating a task definition that uses a FireLens configuration in the Amazon Elastic Container Service Developer Guide .

              Note

              Tasks hosted on Fargate only support the file configuration file type.

              • (string) --

                • (string) --

      • family (string) --

        The name of a family that this task definition is registered to. Up to 255 characters are allowed. Letters (both uppercase and lowercase letters), numbers, hyphens (-), and underscores (_) are allowed.

        A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.

      • taskRoleArn (string) --

        The short name or full Amazon Resource Name (ARN) of the Identity and Access Management role that grants containers in the task permission to call Amazon Web Services APIs on your behalf. For more information, see Amazon ECS Task Role in the Amazon Elastic Container Service Developer Guide .

        IAM roles for tasks on Windows require that the -EnableTaskIAMRole option is set when you launch the Amazon ECS-optimized Windows AMI. Your containers must also run some configuration code to use the feature. For more information, see Windows IAM roles for tasks in the Amazon Elastic Container Service Developer Guide .

      • executionRoleArn (string) --

        The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make Amazon Web Services API calls on your behalf. The task execution IAM role is required depending on the requirements of your task. For more information, see Amazon ECS task execution IAM role in the Amazon Elastic Container Service Developer Guide .

      • networkMode (string) --

        The Docker networking mode to use for the containers in the task. The valid values are none , bridge , awsvpc , and host . If no network mode is specified, the default is bridge .

        For Amazon ECS tasks on Fargate, the awsvpc network mode is required. For Amazon ECS tasks on Amazon EC2 Linux instances, any network mode can be used. For Amazon ECS tasks on Amazon EC2 Windows instances, <default> or awsvpc can be used. If the network mode is set to none , you cannot specify port mappings in your container definitions, and the tasks containers do not have external connectivity. The host and awsvpc network modes offer the highest networking performance for containers because they use the EC2 network stack instead of the virtualized network stack provided by the bridge mode.

        With the host and awsvpc network modes, exposed container ports are mapped directly to the corresponding host port (for the host network mode) or the attached elastic network interface port (for the awsvpc network mode), so you cannot take advantage of dynamic host port mappings.

        Warning

        When using the host network mode, you should not run containers using the root user (UID 0). It is considered best practice to use a non-root user.

        If the network mode is awsvpc , the task is allocated an elastic network interface, and you must specify a NetworkConfiguration value when you create a service or run a task with the task definition. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide .

        If the network mode is host , you cannot run multiple instantiations of the same task on a single container instance when port mappings are used.

        For more information, see Network settings in the Docker run reference .

      • revision (integer) --

        The revision of the task in a particular family. The revision is a version number of a task definition in a family. When you register a task definition for the first time, the revision is 1 . Each time that you register a new revision of a task definition in the same family, the revision value always increases by one. This is even if you deregistered previous revisions in this family.

      • volumes (list) --

        The list of data volume definitions for the task. For more information, see Using data volumes in tasks in the Amazon Elastic Container Service Developer Guide .

        Note

        The host and sourcePath parameters aren't supported for tasks run on Fargate.

        • (dict) --

          A data volume that's used in a task definition. For tasks that use the Amazon Elastic File System (Amazon EFS), specify an efsVolumeConfiguration . For Windows tasks that use Amazon FSx for Windows File Server file system, specify a fsxWindowsFileServerVolumeConfiguration . For tasks that use a Docker volume, specify a DockerVolumeConfiguration . For tasks that use a bind mount host volume, specify a host and optional sourcePath . For more information, see Using Data Volumes in Tasks .

          • name (string) --

            The name of the volume. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This name is referenced in the sourceVolume parameter of container definition mountPoints .

          • host (dict) --

            This parameter is specified when you use bind mount host volumes. The contents of the host parameter determine whether your bind mount host volume persists on the host container instance and where it's stored. If the host parameter is empty, then the Docker daemon assigns a host path for your data volume. However, the data isn't guaranteed to persist after the containers that are associated with it stop running.

            Windows containers can mount whole directories on the same drive as $env:ProgramData . Windows containers can't mount directories on a different drive, and mount point can't be across drives. For example, you can mount C:\my\path:C:\my\path and D:\:D:\ , but not D:\my\path:C:\my\path or D:\:C:\my\path .

            • sourcePath (string) --

              When the host parameter is used, specify a sourcePath to declare the path on the host container instance that's presented to the container. If this parameter is empty, then the Docker daemon has assigned a host path for you. If the host parameter contains a sourcePath file location, then the data volume persists at the specified location on the host container instance until you delete it manually. If the sourcePath value doesn't exist on the host container instance, the Docker daemon creates it. If the location does exist, the contents of the source path folder are exported.

              If you're using the Fargate launch type, the sourcePath parameter is not supported.

          • dockerVolumeConfiguration (dict) --

            This parameter is specified when you use Docker volumes.

            Windows containers only support the use of the local driver. To use bind mounts, specify the host parameter instead.

            Note

            Docker volumes aren't supported by tasks run on Fargate.

            • scope (string) --

              The scope for the Docker volume that determines its lifecycle. Docker volumes that are scoped to a task are automatically provisioned when the task starts and destroyed when the task stops. Docker volumes that are scoped as shared persist after the task stops.

            • autoprovision (boolean) --

              If this value is true , the Docker volume is created if it doesn't already exist.

              Note

              This field is only used if the scope is shared .

            • driver (string) --

              The Docker volume driver to use. The driver value must match the driver name provided by Docker because it is used for task placement. If the driver was installed using the Docker plugin CLI, use docker plugin ls to retrieve the driver name from your container instance. If the driver was installed using another method, use Docker plugin discovery to retrieve the driver name. For more information, see Docker plugin discovery . This parameter maps to Driver in the Create a volume section of the Docker Remote API and the xxdriver option to docker volume create .

            • driverOpts (dict) --

              A map of Docker driver-specific options passed through. This parameter maps to DriverOpts in the Create a volume section of the Docker Remote API and the xxopt option to docker volume create .

              • (string) --

                • (string) --

            • labels (dict) --

              Custom metadata to add to your Docker volume. This parameter maps to Labels in the Create a volume section of the Docker Remote API and the xxlabel option to docker volume create .

              • (string) --

                • (string) --

          • efsVolumeConfiguration (dict) --

            This parameter is specified when you use an Amazon Elastic File System file system for task storage.

            • fileSystemId (string) --

              The Amazon EFS file system ID to use.

            • rootDirectory (string) --

              The directory within the Amazon EFS file system to mount as the root directory inside the host. If this parameter is omitted, the root of the Amazon EFS volume will be used. Specifying / will have the same effect as omitting this parameter.

              Warning

              If an EFS access point is specified in the authorizationConfig , the root directory parameter must either be omitted or set to / which will enforce the path set on the EFS access point.

            • transitEncryption (string) --

              Determines whether to use encryption for Amazon EFS data in transit between the Amazon ECS host and the Amazon EFS server. Transit encryption must be enabled if Amazon EFS IAM authorization is used. If this parameter is omitted, the default value of DISABLED is used. For more information, see Encrypting data in transit in the Amazon Elastic File System User Guide .

            • transitEncryptionPort (integer) --

              The port to use when sending encrypted data between the Amazon ECS host and the Amazon EFS server. If you do not specify a transit encryption port, it will use the port selection strategy that the Amazon EFS mount helper uses. For more information, see EFS mount helper in the Amazon Elastic File System User Guide .

            • authorizationConfig (dict) --

              The authorization configuration details for the Amazon EFS file system.

              • accessPointId (string) --

                The Amazon EFS access point ID to use. If an access point is specified, the root directory value specified in the EFSVolumeConfiguration must either be omitted or set to / which will enforce the path set on the EFS access point. If an access point is used, transit encryption must be enabled in the EFSVolumeConfiguration . For more information, see Working with Amazon EFS access points in the Amazon Elastic File System User Guide .

              • iam (string) --

                Determines whether to use the Amazon ECS task IAM role defined in a task definition when mounting the Amazon EFS file system. If enabled, transit encryption must be enabled in the EFSVolumeConfiguration . If this parameter is omitted, the default value of DISABLED is used. For more information, see Using Amazon EFS access points in the Amazon Elastic Container Service Developer Guide .

          • fsxWindowsFileServerVolumeConfiguration (dict) --

            This parameter is specified when you use Amazon FSx for Windows File Server file system for task storage.

            • fileSystemId (string) --

              The Amazon FSx for Windows File Server file system ID to use.

            • rootDirectory (string) --

              The directory within the Amazon FSx for Windows File Server file system to mount as the root directory inside the host.

            • authorizationConfig (dict) --

              The authorization configuration details for the Amazon FSx for Windows File Server file system.

              • credentialsParameter (string) --

                The authorization credential option to use. The authorization credential options can be provided using either the Amazon Resource Name (ARN) of an Secrets Manager secret or SSM Parameter Store parameter. The ARN refers to the stored credentials.

              • domain (string) --

                A fully qualified domain name hosted by an Directory Service Managed Microsoft AD (Active Directory) or self-hosted AD on Amazon EC2.

      • status (string) --

        The status of the task definition.

      • requiresAttributes (list) --

        The container instance attributes required by your task. When an Amazon EC2 instance is registered to your cluster, the Amazon ECS container agent assigns some standard attributes to the instance. You can apply custom attributes. These are specified as key-value pairs using the Amazon ECS console or the PutAttributes API. These attributes are used when determining task placement for tasks hosted on Amazon EC2 instances. For more information, see Attributes in the Amazon Elastic Container Service Developer Guide .

        Note

        This parameter isn't supported for tasks run on Fargate.

        • (dict) --

          An attribute is a name-value pair that's associated with an Amazon ECS object. Use attributes to extend the Amazon ECS data model by adding custom metadata to your resources. For more information, see Attributes in the Amazon Elastic Container Service Developer Guide .

          • name (string) --

            The name of the attribute. The name must contain between 1 and 128 characters. The name may contain letters (uppercase and lowercase), numbers, hyphens (-), underscores (_), forward slashes (/), back slashes (), or periods (.).

          • value (string) --

            The value of the attribute. The value must contain between 1 and 128 characters. It can contain letters (uppercase and lowercase), numbers, hyphens (-), underscores (_), periods (.), at signs (@), forward slashes (/), back slashes (), colons (:), or spaces. The value can't start or end with a space.

          • targetType (string) --

            The type of the target to attach the attribute with. This parameter is required if you use the short form ID for a resource instead of the full ARN.

          • targetId (string) --

            The ID of the target. You can specify the short form ID for a resource or the full Amazon Resource Name (ARN).

      • placementConstraints (list) --

        An array of placement constraint objects to use for tasks.

        Note

        This parameter isn't supported for tasks run on Fargate.

        • (dict) --

          An object representing a constraint on task placement in the task definition. For more information, see Task placement constraints in the Amazon Elastic Container Service Developer Guide .

          Note

          Task placement constraints aren't supported for tasks run on Fargate.

          • type (string) --

            The type of constraint. The MemberOf constraint restricts selection to be from a group of valid candidates.

          • expression (string) --

            A cluster query language expression to apply to the constraint. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide .

      • compatibilities (list) --

        The task launch types the task definition validated against during task definition registration. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide .

        • (string) --

      • runtimePlatform (dict) --

        The operating system that your task definitions are running on. A platform family is specified only for tasks using the Fargate launch type.

        When you specify a task in a service, this value must match the runtimePlatform value of the service.

        • cpuArchitecture (string) --

          The CPU architecture.

          You can run your Linux tasks on an ARM-based platform by setting the value to ARM64 . This option is available for tasks that run on Linux Amazon EC2 instance or Linux containers on Fargate.

        • operatingSystemFamily (string) --

          The operating system.

      • requiresCompatibilities (list) --

        The task launch types the task definition was validated against. To determine which task launch types the task definition is validated for, see the TaskDefinition$compatibilities parameter.

        • (string) --

      • cpu (string) --

        The number of cpu units used by the task. If you use the EC2 launch type, this field is optional. Any value can be used. If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines your range of valid values for the memory parameter.

        The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.

        • 256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)

        • 512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)

        • 1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)

        • 2048 (2 vCPU) - Available memory values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)

        • 4096 (4 vCPU) - Available memory values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)

        • 8192 (8 vCPU) - Available memory values: 16 GB and 60 GB in 4 GB increments This option requires Linux platform 1.4.0 or later.

        • 16384 (16vCPU) - Available memory values: 32GB and 120 GB in 8 GB increments This option requires Linux platform 1.4.0 or later.

      • memory (string) --

        The amount (in MiB) of memory used by the task.

        If your tasks runs on Amazon EC2 instances, you must specify either a task-level memory value or a container-level memory value. This field is optional and any value can be used. If a task-level memory value is specified, the container-level memory value is optional. For more information regarding container-level memory and memory reservation, see ContainerDefinition .

        If your tasks runs on Fargate, this field is required. You must use one of the following values. The value you choose determines your range of valid values for the cpu parameter.

        • 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)

        • 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)

        • 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available cpu values: 1024 (1 vCPU)

        • Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values: 2048 (2 vCPU)

        • Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values: 4096 (4 vCPU)

        • Between 16 GB and 60 GB in 4 GB increments - Available cpu values: 8192 (8 vCPU) This option requires Linux platform 1.4.0 or later.

        • Between 32GB and 120 GB in 8 GB increments - Available cpu values: 16384 (16 vCPU) This option requires Linux platform 1.4.0 or later.

      • inferenceAccelerators (list) --

        The Elastic Inference accelerator that's associated with the task.

        • (dict) --

          Details on an Elastic Inference accelerator. For more information, see Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide .

          • deviceName (string) --

            The Elastic Inference accelerator device name. The deviceName must also be referenced in a container definition as a ResourceRequirement .

          • deviceType (string) --

            The Elastic Inference accelerator type to use.

      • pidMode (string) --

        The process namespace to use for the containers in the task. The valid values are host or task . If host is specified, then all containers within the tasks that specified the host PID mode on the same container instance share the same process namespace with the host Amazon EC2 instance. If task is specified, all containers within the specified task share the same process namespace. If no value is specified, the default is a private namespace. For more information, see PID settings in the Docker run reference .

        If the host PID mode is used, be aware that there is a heightened risk of undesired process namespace expose. For more information, see Docker security .

        Note

        This parameter is not supported for Windows containers or tasks run on Fargate.

      • ipcMode (string) --

        The IPC resource namespace to use for the containers in the task. The valid values are host , task , or none . If host is specified, then all containers within the tasks that specified the host IPC mode on the same container instance share the same IPC resources with the host Amazon EC2 instance. If task is specified, all containers within the specified task share the same IPC resources. If none is specified, then IPC resources within the containers of a task are private and not shared with other containers in a task or on the container instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more information, see IPC settings in the Docker run reference .

        If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace expose. For more information, see Docker security .

        If you are setting namespaced kernel parameters using systemControls for the containers in the task, the following will apply to your IPC resource namespace. For more information, see System Controls in the Amazon Elastic Container Service Developer Guide .

        • For tasks that use the host IPC mode, IPC namespace related systemControls are not supported.

        • For tasks that use the task IPC mode, IPC namespace related systemControls will apply to all containers within a task.

        Note

        This parameter is not supported for Windows containers or tasks run on Fargate.

      • proxyConfiguration (dict) --

        The configuration details for the App Mesh proxy.

        Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least version 1.26.0-1 of the ecs-init package to use a proxy configuration. If your container instances are launched from the Amazon ECS optimized AMI version 20190301 or later, they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

        • type (string) --

          The proxy type. The only supported value is APPMESH .

        • containerName (string) --

          The name of the container that will serve as the App Mesh proxy.

        • properties (list) --

          The set of network configuration parameters to provide the Container Network Interface (CNI) plugin, specified as key-value pairs.

          • IgnoredUID - (Required) The user ID (UID) of the proxy container as defined by the user parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If IgnoredGID is specified, this field can be empty.

          • IgnoredGID - (Required) The group ID (GID) of the proxy container as defined by the user parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If IgnoredUID is specified, this field can be empty.

          • AppPorts - (Required) The list of ports that the application uses. Network traffic to these ports is forwarded to the ProxyIngressPort and ProxyEgressPort .

          • ProxyIngressPort - (Required) Specifies the port that incoming traffic to the AppPorts is directed to.

          • ProxyEgressPort - (Required) Specifies the port that outgoing traffic from the AppPorts is directed to.

          • EgressIgnoredPorts - (Required) The egress traffic going to the specified ports is ignored and not redirected to the ProxyEgressPort . It can be an empty list.

          • EgressIgnoredIPs - (Required) The egress traffic going to the specified IP addresses is ignored and not redirected to the ProxyEgressPort . It can be an empty list.

          • (dict) --

            A key-value pair object.

            • name (string) --

              The name of the key-value pair. For environment variables, this is the name of the environment variable.

            • value (string) --

              The value of the key-value pair. For environment variables, this is the value of the environment variable.

      • registeredAt (datetime) --

        The Unix timestamp for the time when the task definition was registered.

      • deregisteredAt (datetime) --

        The Unix timestamp for the time when the task definition was deregistered.

      • registeredBy (string) --

        The principal that registered the task definition.

      • ephemeralStorage (dict) --

        The ephemeral storage settings to use for tasks run with the task definition.

        • sizeInGiB (integer) --

          The total amount, in GiB, of ephemeral storage to set for the task. The minimum supported value is 21 GiB and the maximum supported value is 200 GiB.

DescribeClusters (updated) Link ¶
Changes (response)
{'clusters': {'serviceConnectDefaults': {'namespace': 'string'}}}

Describes one or more of your clusters.

See also: AWS API Documentation

Request Syntax

client.describe_clusters(
    clusters=[
        'string',
    ],
    include=[
        'ATTACHMENTS'|'CONFIGURATIONS'|'SETTINGS'|'STATISTICS'|'TAGS',
    ]
)
type clusters

list

param clusters

A list of up to 100 cluster names or full cluster Amazon Resource Name (ARN) entries. If you do not specify a cluster, the default cluster is assumed.

  • (string) --

type include

list

param include

Determines whether to include additional information about the clusters in the response. If this field is omitted, this information isn't included.

If ATTACHMENTS is specified, the attachments for the container instances or tasks within the cluster are included, for example the capacity providers.

If SETTINGS is specified, the settings for the cluster are included.

If CONFIGURATIONS is specified, the configuration for the cluster is included.

If STATISTICS is specified, the task and service count is included, separated by launch type.

If TAGS is specified, the metadata tags associated with the cluster are included.

  • (string) --

rtype

dict

returns

Response Syntax

{
    'clusters': [
        {
            'clusterArn': 'string',
            'clusterName': 'string',
            'configuration': {
                'executeCommandConfiguration': {
                    'kmsKeyId': 'string',
                    'logging': 'NONE'|'DEFAULT'|'OVERRIDE',
                    'logConfiguration': {
                        'cloudWatchLogGroupName': 'string',
                        'cloudWatchEncryptionEnabled': True|False,
                        's3BucketName': 'string',
                        's3EncryptionEnabled': True|False,
                        's3KeyPrefix': 'string'
                    }
                }
            },
            'status': 'string',
            'registeredContainerInstancesCount': 123,
            'runningTasksCount': 123,
            'pendingTasksCount': 123,
            'activeServicesCount': 123,
            'statistics': [
                {
                    'name': 'string',
                    'value': 'string'
                },
            ],
            'tags': [
                {
                    'key': 'string',
                    'value': 'string'
                },
            ],
            'settings': [
                {
                    'name': 'containerInsights',
                    'value': 'string'
                },
            ],
            'capacityProviders': [
                'string',
            ],
            'defaultCapacityProviderStrategy': [
                {
                    'capacityProvider': 'string',
                    'weight': 123,
                    'base': 123
                },
            ],
            'attachments': [
                {
                    'id': 'string',
                    'type': 'string',
                    'status': 'string',
                    'details': [
                        {
                            'name': 'string',
                            'value': 'string'
                        },
                    ]
                },
            ],
            'attachmentsStatus': 'string',
            'serviceConnectDefaults': {
                'namespace': 'string'
            }
        },
    ],
    'failures': [
        {
            'arn': 'string',
            'reason': 'string',
            'detail': 'string'
        },
    ]
}

Response Structure

  • (dict) --

    • clusters (list) --

      The list of clusters.

      • (dict) --

        A regional grouping of one or more container instances where you can run task requests. Each account receives a default cluster the first time you use the Amazon ECS service, but you may also create other clusters. Clusters may contain more than one instance type simultaneously.

        • clusterArn (string) --

          The 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 .

        • clusterName (string) --

          A user-generated string that you use to identify your cluster.

        • configuration (dict) --

          The execute command configuration for the cluster.

          • executeCommandConfiguration (dict) --

            The details of the execute command configuration.

            • kmsKeyId (string) --

              Specify an Key Management Service key ID to encrypt the data between the local client and the container.

            • logging (string) --

              The log setting to use for redirecting logs for your execute command results. The following log settings are available.

              • NONE : The execute command session is not logged.

              • DEFAULT : The awslogs configuration in the task definition is used. If no logging parameter is specified, it defaults to this value. If no awslogs log driver is configured in the task definition, the output won't be logged.

              • OVERRIDE : Specify the logging details as a part of logConfiguration . If the OVERRIDE logging option is specified, the logConfiguration is required.

            • logConfiguration (dict) --

              The log configuration for the results of the execute command actions. The logs can be sent to CloudWatch Logs or an Amazon S3 bucket. When logging=OVERRIDE is specified, a logConfiguration must be provided.

              • cloudWatchLogGroupName (string) --

                The name of the CloudWatch log group to send logs to.

                Note

                The CloudWatch log group must already be created.

              • cloudWatchEncryptionEnabled (boolean) --

                Determines whether to use encryption on the CloudWatch logs. If not specified, encryption will be disabled.

              • s3BucketName (string) --

                The name of the S3 bucket to send logs to.

                Note

                The S3 bucket must already be created.

              • s3EncryptionEnabled (boolean) --

                Determines whether to use encryption on the S3 logs. If not specified, encryption is not used.

              • s3KeyPrefix (string) --

                An optional folder in the S3 bucket to place logs in.

        • status (string) --

          The 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.

        • registeredContainerInstancesCount (integer) --

          The number of container instances registered into the cluster. This includes container instances in both ACTIVE and DRAINING status.

        • runningTasksCount (integer) --

          The number of tasks in the cluster that are in the RUNNING state.

        • pendingTasksCount (integer) --

          The number of tasks in the cluster that are in the PENDING state.

        • activeServicesCount (integer) --

          The number of services that are running on the cluster in an ACTIVE state. You can view these services with ListServices .

        • statistics (list) --

          Additional information about your clusters that are separated by launch type. They include the following:

          • runningEC2TasksCount

          • RunningFargateTasksCount

          • pendingEC2TasksCount

          • pendingFargateTasksCount

          • activeEC2ServiceCount

          • activeFargateServiceCount

          • drainingEC2ServiceCount

          • drainingFargateServiceCount

          • (dict) --

            A key-value pair object.

            • name (string) --

              The name of the key-value pair. For environment variables, this is the name of the environment variable.

            • value (string) --

              The value of the key-value pair. For environment variables, this is the value of the environment variable.

        • tags (list) --

          The metadata that you apply to the cluster to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

          The following basic restrictions apply to tags:

          • Maximum number of tags per resource - 50

          • For each resource, each tag key must be unique, and each tag key can have only one value.

          • Maximum key length - 128 Unicode characters in UTF-8

          • Maximum value length - 256 Unicode characters in UTF-8

          • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

          • Tag keys and values are case-sensitive.

          • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

          • (dict) --

            The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

            The following basic restrictions apply to tags:

            • Maximum number of tags per resource - 50

            • For each resource, each tag key must be unique, and each tag key can have only one value.

            • Maximum key length - 128 Unicode characters in UTF-8

            • Maximum value length - 256 Unicode characters in UTF-8

            • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

            • Tag keys and values are case-sensitive.

            • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

            • key (string) --

              One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

            • value (string) --

              The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

        • settings (list) --

          The settings for the cluster. This parameter indicates whether CloudWatch Container Insights is enabled or disabled for a cluster.

          • (dict) --

            The settings to use when creating a cluster. This parameter is used to turn on CloudWatch Container Insights for a cluster.

            • name (string) --

              The name of the cluster setting. The only supported value is containerInsights .

            • value (string) --

              The value to set for the cluster setting. The supported values are enabled and disabled . If enabled is specified, CloudWatch Container Insights will be enabled for the cluster, otherwise it will be disabled unless the containerInsights account setting is enabled. If a cluster value is specified, it will override the containerInsights value set with PutAccountSetting or PutAccountSettingDefault .

        • capacityProviders (list) --

          The capacity providers associated with the cluster.

          • (string) --

        • defaultCapacityProviderStrategy (list) --

          The 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.

          • (dict) --

            The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

            Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

            If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

            To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

            A capacity provider strategy may contain a maximum of 6 capacity providers.

            • capacityProvider (string) --

              The short name of the capacity provider.

            • weight (integer) --

              The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

              If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

              An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

            • base (integer) --

              The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

        • attachments (list) --

          The resources attached to a cluster. When using a capacity provider with a cluster, the capacity provider and associated resources are returned as cluster attachments.

          • (dict) --

            An object representing a container instance or task attachment.

            • id (string) --

              The unique identifier for the attachment.

            • type (string) --

              The type of the attachment, such as ElasticNetworkInterface .

            • status (string) --

              The status of the attachment. Valid values are PRECREATED , CREATED , ATTACHING , ATTACHED , DETACHING , DETACHED , DELETED , and FAILED .

            • details (list) --

              Details of the attachment. For elastic network interfaces, this includes the network interface ID, the MAC address, the subnet ID, and the private IPv4 address.

              • (dict) --

                A key-value pair object.

                • name (string) --

                  The name of the key-value pair. For environment variables, this is the name of the environment variable.

                • value (string) --

                  The value of the key-value pair. For environment variables, this is the value of the environment variable.

        • attachmentsStatus (string) --

          The 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.

        • serviceConnectDefaults (dict) --

          Use 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 .

          • namespace (string) --

            The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace. When you create a service and don't specify a Service Connect configuration, this namespace is used.

    • failures (list) --

      Any failures associated with the call.

      • (dict) --

        A failed resource. For a list of common causes, see API failure reasons in the Amazon Elastic Container Service Developer Guide .

        • arn (string) --

          The Amazon Resource Name (ARN) of the failed resource.

        • reason (string) --

          The reason for the failure.

        • detail (string) --

          The details of the failure.

DescribeServices (updated) Link ¶
Changes (response)
{'services': {'deployments': {'serviceConnectConfiguration': {'enabled': 'boolean',
                                                              'logConfiguration': {'logDriver': 'json-file '
                                                                                                '| '
                                                                                                'syslog '
                                                                                                '| '
                                                                                                'journald '
                                                                                                '| '
                                                                                                'gelf '
                                                                                                '| '
                                                                                                'fluentd '
                                                                                                '| '
                                                                                                'awslogs '
                                                                                                '| '
                                                                                                'splunk '
                                                                                                '| '
                                                                                                'awsfirelens',
                                                                                   'options': {'string': 'string'},
                                                                                   'secretOptions': [{'name': 'string',
                                                                                                      'valueFrom': 'string'}]},
                                                              'namespace': 'string',
                                                              'services': [{'clientAliases': [{'dnsName': 'string',
                                                                                               'port': 'integer'}],
                                                                            'discoveryName': 'string',
                                                                            'ingressPortOverride': 'integer',
                                                                            'portName': 'string'}]},
                              'serviceConnectResources': [{'discoveryArn': 'string',
                                                           'discoveryName': 'string'}]}}}

Describes the specified services running in your cluster.

See also: AWS API Documentation

Request Syntax

client.describe_services(
    cluster='string',
    services=[
        'string',
    ],
    include=[
        'TAGS',
    ]
)
type cluster

string

param cluster

The short name or full Amazon Resource Name (ARN)the cluster that hosts the service to describe. If you do not specify a cluster, the default cluster is assumed. This parameter is required if the service or services you are describing were launched in any cluster other than the default cluster.

type services

list

param services

[REQUIRED]

A list of services to describe. You may specify up to 10 services to describe in a single operation.

  • (string) --

type include

list

param include

Determines whether you want to see the resource tags for the service. If TAGS is specified, the tags are included in the response. If this field is omitted, tags aren't included in the response.

  • (string) --

rtype

dict

returns

Response Syntax

{
    'services': [
        {
            'serviceArn': 'string',
            'serviceName': 'string',
            'clusterArn': 'string',
            'loadBalancers': [
                {
                    'targetGroupArn': 'string',
                    'loadBalancerName': 'string',
                    'containerName': 'string',
                    'containerPort': 123
                },
            ],
            'serviceRegistries': [
                {
                    'registryArn': 'string',
                    'port': 123,
                    'containerName': 'string',
                    'containerPort': 123
                },
            ],
            'status': 'string',
            'desiredCount': 123,
            'runningCount': 123,
            'pendingCount': 123,
            'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
            'capacityProviderStrategy': [
                {
                    'capacityProvider': 'string',
                    'weight': 123,
                    'base': 123
                },
            ],
            'platformVersion': 'string',
            'platformFamily': 'string',
            'taskDefinition': 'string',
            'deploymentConfiguration': {
                'deploymentCircuitBreaker': {
                    'enable': True|False,
                    'rollback': True|False
                },
                'maximumPercent': 123,
                'minimumHealthyPercent': 123
            },
            'taskSets': [
                {
                    'id': 'string',
                    'taskSetArn': 'string',
                    'serviceArn': 'string',
                    'clusterArn': 'string',
                    'startedBy': 'string',
                    'externalId': 'string',
                    'status': 'string',
                    'taskDefinition': 'string',
                    'computedDesiredCount': 123,
                    'pendingCount': 123,
                    'runningCount': 123,
                    'createdAt': datetime(2015, 1, 1),
                    'updatedAt': datetime(2015, 1, 1),
                    'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
                    'capacityProviderStrategy': [
                        {
                            'capacityProvider': 'string',
                            'weight': 123,
                            'base': 123
                        },
                    ],
                    'platformVersion': 'string',
                    'platformFamily': 'string',
                    'networkConfiguration': {
                        'awsvpcConfiguration': {
                            'subnets': [
                                'string',
                            ],
                            'securityGroups': [
                                'string',
                            ],
                            'assignPublicIp': 'ENABLED'|'DISABLED'
                        }
                    },
                    'loadBalancers': [
                        {
                            'targetGroupArn': 'string',
                            'loadBalancerName': 'string',
                            'containerName': 'string',
                            'containerPort': 123
                        },
                    ],
                    'serviceRegistries': [
                        {
                            'registryArn': 'string',
                            'port': 123,
                            'containerName': 'string',
                            'containerPort': 123
                        },
                    ],
                    'scale': {
                        'value': 123.0,
                        'unit': 'PERCENT'
                    },
                    'stabilityStatus': 'STEADY_STATE'|'STABILIZING',
                    'stabilityStatusAt': datetime(2015, 1, 1),
                    'tags': [
                        {
                            'key': 'string',
                            'value': 'string'
                        },
                    ]
                },
            ],
            'deployments': [
                {
                    'id': 'string',
                    'status': 'string',
                    'taskDefinition': 'string',
                    'desiredCount': 123,
                    'pendingCount': 123,
                    'runningCount': 123,
                    'failedTasks': 123,
                    'createdAt': datetime(2015, 1, 1),
                    'updatedAt': datetime(2015, 1, 1),
                    'capacityProviderStrategy': [
                        {
                            'capacityProvider': 'string',
                            'weight': 123,
                            'base': 123
                        },
                    ],
                    'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
                    'platformVersion': 'string',
                    'platformFamily': 'string',
                    'networkConfiguration': {
                        'awsvpcConfiguration': {
                            'subnets': [
                                'string',
                            ],
                            'securityGroups': [
                                'string',
                            ],
                            'assignPublicIp': 'ENABLED'|'DISABLED'
                        }
                    },
                    'rolloutState': 'COMPLETED'|'FAILED'|'IN_PROGRESS',
                    'rolloutStateReason': 'string',
                    'serviceConnectConfiguration': {
                        'enabled': True|False,
                        'namespace': 'string',
                        'services': [
                            {
                                'portName': 'string',
                                'discoveryName': 'string',
                                'clientAliases': [
                                    {
                                        'port': 123,
                                        'dnsName': 'string'
                                    },
                                ],
                                'ingressPortOverride': 123
                            },
                        ],
                        'logConfiguration': {
                            'logDriver': 'json-file'|'syslog'|'journald'|'gelf'|'fluentd'|'awslogs'|'splunk'|'awsfirelens',
                            'options': {
                                'string': 'string'
                            },
                            'secretOptions': [
                                {
                                    'name': 'string',
                                    'valueFrom': 'string'
                                },
                            ]
                        }
                    },
                    'serviceConnectResources': [
                        {
                            'discoveryName': 'string',
                            'discoveryArn': 'string'
                        },
                    ]
                },
            ],
            'roleArn': 'string',
            'events': [
                {
                    'id': 'string',
                    'createdAt': datetime(2015, 1, 1),
                    'message': 'string'
                },
            ],
            'createdAt': datetime(2015, 1, 1),
            'placementConstraints': [
                {
                    'type': 'distinctInstance'|'memberOf',
                    'expression': 'string'
                },
            ],
            'placementStrategy': [
                {
                    'type': 'random'|'spread'|'binpack',
                    'field': 'string'
                },
            ],
            'networkConfiguration': {
                'awsvpcConfiguration': {
                    'subnets': [
                        'string',
                    ],
                    'securityGroups': [
                        'string',
                    ],
                    'assignPublicIp': 'ENABLED'|'DISABLED'
                }
            },
            'healthCheckGracePeriodSeconds': 123,
            'schedulingStrategy': 'REPLICA'|'DAEMON',
            'deploymentController': {
                'type': 'ECS'|'CODE_DEPLOY'|'EXTERNAL'
            },
            'tags': [
                {
                    'key': 'string',
                    'value': 'string'
                },
            ],
            'createdBy': 'string',
            'enableECSManagedTags': True|False,
            'propagateTags': 'TASK_DEFINITION'|'SERVICE'|'NONE',
            'enableExecuteCommand': True|False
        },
    ],
    'failures': [
        {
            'arn': 'string',
            'reason': 'string',
            'detail': 'string'
        },
    ]
}

Response Structure

  • (dict) --

    • services (list) --

      The list of services described.

      • (dict) --

        Details on a service within a cluster

        • serviceArn (string) --

          The ARN that identifies the service. For more information about the ARN format, see Amazon Resource Name (ARN) in the Amazon ECS Developer Guide .

        • serviceName (string) --

          The name of your service. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. Service names must be unique within a cluster. However, you can have similarly named services in multiple clusters within a Region or across multiple Regions.

        • clusterArn (string) --

          The Amazon Resource Name (ARN) of the cluster that hosts the service.

        • loadBalancers (list) --

          A list of Elastic Load Balancing load balancer objects. It contains the load balancer name, the container name, and the container port to access from the load balancer. The container name is as it appears in a container definition.

          • (dict) --

            The load balancer configuration to use with a service or task set.

            For specific notes and restrictions regarding the use of load balancers with services and task sets, see the CreateService and CreateTaskSet actions.

            When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers.

            We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration.

            A service-linked role is required for services that use multiple target groups. For more information, see Using service-linked roles in the Amazon Elastic Container Service Developer Guide .

            • targetGroupArn (string) --

              The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set.

              A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you're using a Classic Load Balancer, omit the target group ARN.

              For services using the ECS deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide .

              For services using the CODE_DEPLOY deployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide .

              Warning

              If your service's task definition uses the awsvpc network mode, you must choose ip as the target type, not instance . Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.

            • loadBalancerName (string) --

              The name of the load balancer to associate with the Amazon ECS service or task set.

              A load balancer name is only specified when using a Classic Load Balancer. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.

            • containerName (string) --

              The name of the container (as it appears in a container definition) to associate with the load balancer.

            • containerPort (integer) --

              The port on the container to associate with the load balancer. This port must correspond to a containerPort in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on the hostPort of the port mapping.

        • serviceRegistries (list) --

          The details for the service discovery registries to assign to this service. For more information, see Service Discovery .

          • (dict) --

            The details for the service registry.

            Each service may be associated with one service registry. Multiple service registries for each service are not supported.

            When you add, update, or remove the service registries configuration, Amazon ECS starts a new deployment. New tasks are registered and deregistered to the updated service registry configuration.

            • registryArn (string) --

              The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is Cloud Map. For more information, see CreateService .

            • port (integer) --

              The port value used if your service discovery service specified an SRV record. This field might be used if both the awsvpc network mode and SRV records are used.

            • containerName (string) --

              The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition that your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

            • containerPort (integer) --

              The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

        • status (string) --

          The status of the service. The valid values are ACTIVE , DRAINING , or INACTIVE .

        • desiredCount (integer) --

          The desired number of instantiations of the task definition to keep running on the service. This value is specified when the service is created with CreateService , and it can be modified with UpdateService .

        • runningCount (integer) --

          The number of tasks in the cluster that are in the RUNNING state.

        • pendingCount (integer) --

          The number of tasks in the cluster that are in the PENDING state.

        • launchType (string) --

          The launch type the service is using. When using the DescribeServices API, this field is omitted if the service was created using a capacity provider strategy.

        • capacityProviderStrategy (list) --

          The capacity provider strategy the service uses. When using the DescribeServices API, this field is omitted if the service was created using a launch type.

          • (dict) --

            The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

            Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

            If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

            To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

            A capacity provider strategy may contain a maximum of 6 capacity providers.

            • capacityProvider (string) --

              The short name of the capacity provider.

            • weight (integer) --

              The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

              If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

              An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

            • base (integer) --

              The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

        • platformVersion (string) --

          The platform version to run your service on. A platform version is only specified for tasks that are hosted on Fargate. If one isn't specified, the LATEST platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide .

        • platformFamily (string) --

          The operating system that your tasks in the service run on. A platform family is specified only for tasks using the Fargate launch type.

          All tasks that run as part of this service must use the same platformFamily value as the service (for example, LINUX ).

        • taskDefinition (string) --

          The task definition to use for tasks in the service. This value is specified when the service is created with CreateService , and it can be modified with UpdateService .

        • deploymentConfiguration (dict) --

          Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.

          • deploymentCircuitBreaker (dict) --

            Note

            The deployment circuit breaker can only be used for services using the rolling update (ECS ) deployment type.

            The deployment circuit breaker determines whether a service deployment will fail if the service can't reach a steady state. If deployment circuit breaker is enabled, a service deployment will transition to a failed state and stop launching new tasks. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

            • enable (boolean) --

              Determines whether to use the deployment circuit breaker logic for the service.

            • rollback (boolean) --

              Determines whether to configure Amazon ECS to roll back the service if a service deployment fails. If rollback is enabled, when a service deployment fails, the service is rolled back to the last deployment that completed successfully.

          • maximumPercent (integer) --

            If a service is using the rolling update (ECS ) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default maximumPercent value for a service using the REPLICA service scheduler is 200%.

            If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and tasks that use the EC2 launch type, the maximum percent value is set to the default value and is used to define the upper limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If the tasks in the service use the Fargate launch type, the maximum percent value is not used, although it is returned when describing your service.

          • minimumHealthyPercent (integer) --

            If a service is using the rolling update (ECS ) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.

            For services that do not use a load balancer, the following should be noted:

            • A service is considered healthy if all essential containers within the tasks in the service pass their health checks.

            • If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches a RUNNING state before the task is counted towards the minimum healthy percent total.

            • If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings.

            For services are that do use a load balancer, the following should be noted:

            • If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

            • If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

            If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY ) or EXTERNAL deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

        • taskSets (list) --

          Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.

          • (dict) --

            Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL deployment. An Amazon ECS task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.

            • id (string) --

              The ID of the task set.

            • taskSetArn (string) --

              The Amazon Resource Name (ARN) of the task set.

            • serviceArn (string) --

              The Amazon Resource Name (ARN) of the service the task set exists in.

            • clusterArn (string) --

              The Amazon Resource Name (ARN) of the cluster that the service that hosts the task set exists in.

            • startedBy (string) --

              The tag specified when a task set is started. If an CodeDeploy deployment created the task set, the startedBy parameter is CODE_DEPLOY . If an external deployment created the task set, the startedBy field isn't used.

            • externalId (string) --

              The external ID associated with the task set.

              If an CodeDeploy deployment created a task set, the externalId parameter contains the CodeDeploy deployment ID.

              If a task set is created for an external deployment and is associated with a service discovery registry, the externalId parameter contains the ECS_TASK_SET_EXTERNAL_ID Cloud Map attribute.

            • status (string) --

              The status of the task set. The following describes each state.

              PRIMARY

              The task set is serving production traffic.

              ACTIVE

              The task set isn't serving production traffic.

              DRAINING

              The tasks in the task set are being stopped, and their corresponding targets are being deregistered from their target group.

            • taskDefinition (string) --

              The task definition that the task set is using.

            • computedDesiredCount (integer) --

              The computed desired count for the task set. This is calculated by multiplying the service's desiredCount by the task set's scale percentage. The result is always rounded up. For example, if the computed desired count is 1.2, it rounds up to 2 tasks.

            • pendingCount (integer) --

              The number of tasks in the task set that are in the PENDING status during a deployment. A task in the PENDING state is preparing to enter the RUNNING state. A task set enters the PENDING status when it launches for the first time or when it's restarted after being in the STOPPED state.

            • runningCount (integer) --

              The number of tasks in the task set that are in the RUNNING status during a deployment. A task in the RUNNING state is running and ready for use.

            • createdAt (datetime) --

              The Unix timestamp for the time when the task set was created.

            • updatedAt (datetime) --

              The Unix timestamp for the time when the task set was last updated.

            • launchType (string) --

              The launch type the tasks in the task set are using. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide .

            • capacityProviderStrategy (list) --

              The capacity provider strategy that are associated with the task set.

              • (dict) --

                The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

                Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

                If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

                To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

                A capacity provider strategy may contain a maximum of 6 capacity providers.

                • capacityProvider (string) --

                  The short name of the capacity provider.

                • weight (integer) --

                  The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

                  If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

                  An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

                • base (integer) --

                  The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

            • platformVersion (string) --

              The Fargate platform version where the tasks in the task set are running. A platform version is only specified for tasks run on Fargate. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide .

            • platformFamily (string) --

              The operating system that your tasks in the set are running on. A platform family is specified only for tasks that use the Fargate launch type.

              All tasks in the set must have the same value.

            • networkConfiguration (dict) --

              The network configuration for the task set.

              • awsvpcConfiguration (dict) --

                The VPC subnets and security groups that are associated with a task.

                Note

                All specified subnets and security groups must be from the same VPC.

                • subnets (list) --

                  The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

                  Note

                  All specified subnets must be from the same VPC.

                  • (string) --

                • securityGroups (list) --

                  The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

                  Note

                  All specified security groups must be from the same VPC.

                  • (string) --

                • assignPublicIp (string) --

                  Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

            • loadBalancers (list) --

              Details on a load balancer that are used with a task set.

              • (dict) --

                The load balancer configuration to use with a service or task set.

                For specific notes and restrictions regarding the use of load balancers with services and task sets, see the CreateService and CreateTaskSet actions.

                When you add, update, or remove a load balancer configuration, Amazon ECS starts a new deployment with the updated Elastic Load Balancing configuration. This causes tasks to register to and deregister from load balancers.

                We recommend that you verify this on a test environment before you update the Elastic Load Balancing configuration.

                A service-linked role is required for services that use multiple target groups. For more information, see Using service-linked roles in the Amazon Elastic Container Service Developer Guide .

                • targetGroupArn (string) --

                  The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set.

                  A target group ARN is only specified when using an Application Load Balancer or Network Load Balancer. If you're using a Classic Load Balancer, omit the target group ARN.

                  For services using the ECS deployment controller, you can specify one or multiple target groups. For more information, see Registering multiple target groups with a service in the Amazon Elastic Container Service Developer Guide .

                  For services using the CODE_DEPLOY deployment controller, you're required to define two target groups for the load balancer. For more information, see Blue/green deployment with CodeDeploy in the Amazon Elastic Container Service Developer Guide .

                  Warning

                  If your service's task definition uses the awsvpc network mode, you must choose ip as the target type, not instance . Do this when creating your target groups because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance. This network mode is required for the Fargate launch type.

                • loadBalancerName (string) --

                  The name of the load balancer to associate with the Amazon ECS service or task set.

                  A load balancer name is only specified when using a Classic Load Balancer. If you are using an Application Load Balancer or a Network Load Balancer the load balancer name parameter should be omitted.

                • containerName (string) --

                  The name of the container (as it appears in a container definition) to associate with the load balancer.

                • containerPort (integer) --

                  The port on the container to associate with the load balancer. This port must correspond to a containerPort in the task definition the tasks in the service are using. For tasks that use the EC2 launch type, the container instance they're launched on must allow ingress traffic on the hostPort of the port mapping.

            • serviceRegistries (list) --

              The details for the service discovery registries to assign to this task set. For more information, see Service discovery .

              • (dict) --

                The details for the service registry.

                Each service may be associated with one service registry. Multiple service registries for each service are not supported.

                When you add, update, or remove the service registries configuration, Amazon ECS starts a new deployment. New tasks are registered and deregistered to the updated service registry configuration.

                • registryArn (string) --

                  The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is Cloud Map. For more information, see CreateService .

                • port (integer) --

                  The port value used if your service discovery service specified an SRV record. This field might be used if both the awsvpc network mode and SRV records are used.

                • containerName (string) --

                  The container name value to be used for your service discovery service. It's already specified in the task definition. If the task definition that your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition that your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

                • containerPort (integer) --

                  The port value to be used for your service discovery service. It's already specified in the task definition. If the task definition your service task specifies uses the bridge or host network mode, you must specify a containerName and containerPort combination from the task definition. If the task definition your service task specifies uses the awsvpc network mode and a type SRV DNS record is used, you must specify either a containerName and containerPort combination or a port value. However, you can't specify both.

            • scale (dict) --

              A floating-point percentage of your desired number of tasks to place and keep running in the task set.

              • value (float) --

                The value, specified as a percent total of a service's desiredCount , to scale the task set. Accepted values are numbers between 0 and 100.

              • unit (string) --

                The unit of measure for the scale value.

            • stabilityStatus (string) --

              The stability status. This indicates whether the task set has reached a steady state. If the following conditions are met, the task set are in STEADY_STATE :

              • The task runningCount is equal to the computedDesiredCount .

              • The pendingCount is 0 .

              • There are no tasks that are running on container instances in the DRAINING status.

              • All tasks are reporting a healthy status from the load balancers, service discovery, and container health checks.

              If any of those conditions aren't met, the stability status returns STABILIZING .

            • stabilityStatusAt (datetime) --

              The Unix timestamp for the time when the task set stability status was retrieved.

            • tags (list) --

              The metadata that you apply to the task set to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

              The following basic restrictions apply to tags:

              • Maximum number of tags per resource - 50

              • For each resource, each tag key must be unique, and each tag key can have only one value.

              • Maximum key length - 128 Unicode characters in UTF-8

              • Maximum value length - 256 Unicode characters in UTF-8

              • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

              • Tag keys and values are case-sensitive.

              • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

              • (dict) --

                The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

                The following basic restrictions apply to tags:

                • Maximum number of tags per resource - 50

                • For each resource, each tag key must be unique, and each tag key can have only one value.

                • Maximum key length - 128 Unicode characters in UTF-8

                • Maximum value length - 256 Unicode characters in UTF-8

                • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

                • Tag keys and values are case-sensitive.

                • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

                • key (string) --

                  One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

                • value (string) --

                  The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

        • deployments (list) --

          The current state of deployments for the service.

          • (dict) --

            The details of an Amazon ECS service deployment. This is used only when a service uses the ECS deployment controller type.

            • id (string) --

              The ID of the deployment.

            • status (string) --

              The status of the deployment. The following describes each state.

              PRIMARY

              The most recent deployment of a service.

              ACTIVE

              A service deployment that still has running tasks, but are in the process of being replaced with a new PRIMARY deployment.

              INACTIVE

              A deployment that has been completely replaced.

            • taskDefinition (string) --

              The most recent task definition that was specified for the tasks in the service to use.

            • desiredCount (integer) --

              The most recent desired count of tasks that was specified for the service to deploy or maintain.

            • pendingCount (integer) --

              The number of tasks in the deployment that are in the PENDING status.

            • runningCount (integer) --

              The number of tasks in the deployment that are in the RUNNING status.

            • failedTasks (integer) --

              The number of consecutively failed tasks in the deployment. A task is considered a failure if the service scheduler can't launch the task, the task doesn't transition to a RUNNING state, or if it fails any of its defined health checks and is stopped.

              Note

              Once a service deployment has one or more successfully running tasks, the failed task count resets to zero and stops being evaluated.

            • createdAt (datetime) --

              The Unix timestamp for the time when the service deployment was created.

            • updatedAt (datetime) --

              The Unix timestamp for the time when the service deployment was last updated.

            • capacityProviderStrategy (list) --

              The capacity provider strategy that the deployment is using.

              • (dict) --

                The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

                Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

                If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

                To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

                A capacity provider strategy may contain a maximum of 6 capacity providers.

                • capacityProvider (string) --

                  The short name of the capacity provider.

                • weight (integer) --

                  The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

                  If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

                  An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

                • base (integer) --

                  The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

            • launchType (string) --

              The launch type the tasks in the service are using. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide .

            • platformVersion (string) --

              The platform version that your tasks in the service run on. A platform version is only specified for tasks using the Fargate launch type. If one isn't specified, the LATEST platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide .

            • platformFamily (string) --

              The operating system that your tasks in the service, or tasks are running on. A platform family is specified only for tasks using the Fargate launch type.

              All tasks that run as part of this service must use the same platformFamily value as the service, for example, LINUX. .

            • networkConfiguration (dict) --

              The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.

              • awsvpcConfiguration (dict) --

                The VPC subnets and security groups that are associated with a task.

                Note

                All specified subnets and security groups must be from the same VPC.

                • subnets (list) --

                  The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

                  Note

                  All specified subnets must be from the same VPC.

                  • (string) --

                • securityGroups (list) --

                  The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

                  Note

                  All specified security groups must be from the same VPC.

                  • (string) --

                • assignPublicIp (string) --

                  Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

            • rolloutState (string) --

              Note

              The rolloutState of a service is only returned for services that use the rolling update (ECS ) deployment type that aren't behind a Classic Load Balancer.

              The rollout state of the deployment. When a service deployment is started, it begins in an IN_PROGRESS state. When the service reaches a steady state, the deployment transitions to a COMPLETED state. If the service fails to reach a steady state and circuit breaker is enabled, the deployment transitions to a FAILED state. A deployment in FAILED state doesn't launch any new tasks. For more information, see DeploymentCircuitBreaker .

            • rolloutStateReason (string) --

              A description of the rollout state of a deployment.

            • serviceConnectConfiguration (dict) --

              The details of the Service Connect configuration that's used by this deployment. Compare the configuration between multiple deployments when troubleshooting issues with new deployments.

              The configuration for this service to discover and connect to services, and be discovered by, and connected from, other services within a namespace.

              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 .

              • enabled (boolean) --

                Specifies whether to use Service Connect with this service.

              • namespace (string) --

                The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace for use with Service Connect. The namespace must be in the same Amazon Web Services Region as the Amazon ECS service and cluster. The type of namespace doesn't affect Service Connect. For more information about Cloud Map, see Working with Services in the Cloud Map Developer Guide .

              • services (list) --

                The list of Service Connect service objects. These are names and aliases (also known as endpoints) that are used by other Amazon ECS services to connect to this service. You can specify up to X (30?) objects per Amazon ECS service.

                This field is not required for a "client" Amazon ECS service that's a member of a namespace only to connect to other services within the namespace. An example of this would be a frontend application that accepts incoming requests from either a load balancer that's attached to the service or by other means.

                An object selects a port from the task definition, assigns a name for the Cloud Map service, and a list of aliases (endpoints) and ports for client applications to refer to this service.

                • (dict) --

                  The Service Connect service object configuration. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                  • portName (string) --

                    The portName must match the name of one of the portMappings from all the containers in the task definition of this Amazon ECS service.

                  • discoveryName (string) --

                    The discoveryName is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                    If this field isn't specified, portName is used.

                  • clientAliases (list) --

                    The list of client aliases for this Service Connect service. You use these to assign names that can be used by client applications. The maximum number of client aliases that you can have in this list is 1.

                    Each alias ("endpoint") is a fully-qualified name and port number that other Amazon ECS tasks ("clients") can use to connect to this service.

                    Each name and port mapping must be unique within the namespace.

                    For each ServiceConnectService , you must provide at least one clientAlias with one port .

                    • (dict) --

                      Each alias ("endpoint") is a fully-qualified name and port number that other tasks ("clients") can use to connect to this service.

                      Each name and port mapping must be unique within the namespace.

                      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 .

                      • port (integer) --

                        The listening port number for the Service Connect proxy. This port is available inside of all of the tasks within the same namespace.

                        To avoid changing your applications in client Amazon ECS services, set this to the same port that the client application uses by default. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                      • dnsName (string) --

                        The dnsName is the name that you use in the applications of client tasks to connect to this service. The name must be a valid DNS name but doesn't need to be fully-qualified. Up to 127 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), hyphens (-), and periods (.). A hyphen can't be the first character.

                        If this parameter isn't specified, the default value of discoveryName.namespace is used. If the discoveryName isn't specified, the portName.namespace from the task definition is used.

                        To avoid changing your applications in client Amazon ECS services, set this to the same name that the client application uses by default. For example, a few common names are database , db , or the lowercase name of a database, such as mysql or redis . For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

                  • ingressPortOverride (integer) --

                    The port number for the Service Connect proxy to listen on.

                    Use the value of this field to bypass the proxy for traffic on the port number specified in the named portMapping in the task definition of this application, and then use it in your VPC security groups to allow traffic into the proxy for this Amazon ECS service.

                    In awsvpc mode and Fargate, the default value is the container port number. The container port number is in the portMapping in the task definition. In bridge mode, the default value is the ephemeral port of the Service Connect proxy.

              • logConfiguration (dict) --

                The log configuration for the container. This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to ` docker run https://docs.docker.com/engine/reference/commandline/run/`__ .

                By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver configuration in the container definition. For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation.

                Understand the following when specifying a log configuration for your containers.

                • Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon (shown in the valid values below). Additional log drivers may be available in future releases of the Amazon ECS container agent.

                • This parameter requires version 1.18 of the Docker Remote API or greater on your container instance.

                • For tasks that are hosted on Amazon EC2 instances, the Amazon ECS container agent must register the available logging drivers with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide .

                • For tasks that are on Fargate, because you don't have access to the underlying infrastructure your tasks are hosted on, any additional software needed must be installed outside of the task. For example, the Fluentd output aggregators or a remote host running Logstash to send Gelf logs to.

                • logDriver (string) --

                  The log driver to use for the container.

                  For tasks on Fargate, the supported log drivers are awslogs , splunk , and awsfirelens .

                  For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs , fluentd , gelf , json-file , journald , logentries ,``syslog`` , splunk , and awsfirelens .

                  For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide .

                  For more information about using the awsfirelens log driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide .

                  Note

                  If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.

                • options (dict) --

                  The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

                  • (string) --

                    • (string) --

                • secretOptions (list) --

                  The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

                  • (dict) --

                    An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

                    • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

                    • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

                    For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

                    • name (string) --

                      The name of the secret.

                    • valueFrom (string) --

                      The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

                      For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

                      Note

                      If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

            • serviceConnectResources (list) --

              The list of Service Connect resources that are associated with this deployment. Each list entry maps a discovery name to a Cloud Map service name.

              • (dict) --

                The Service Connect resource. Each configuration maps a discovery name to a Cloud Map service name. The data is stored in Cloud Map as part of the Service Connect configuration for each discovery name of this Amazon ECS service.

                A task can resolve the dnsName for each of the clientAliases of a service. However a task can't resolve the discovery names. If you want to connect to a service, refer to the ServiceConnectConfiguration of that service for the list of clientAliases that you can use.

                • discoveryName (string) --

                  The discovery name of this Service Connect resource.

                  The discoveryName is the name of the new Cloud Map service that Amazon ECS creates for this Amazon ECS service. This must be unique within the Cloud Map namespace. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                  If this field isn't specified, portName is used.

                • discoveryArn (string) --

                  The Amazon Resource Name (ARN) for the namespace in Cloud Map that matches the discovery name for this Service Connect resource. You can use this ARN in other integrations with Cloud Map. However, Service Connect can't ensure connectivity outside of Amazon ECS.

        • roleArn (string) --

          The ARN of the IAM role that's associated with the service. It allows the Amazon ECS container agent to register container instances with an Elastic Load Balancing load balancer.

        • events (list) --

          The event stream for your service. A maximum of 100 of the latest events are displayed.

          • (dict) --

            The details for an event that's associated with a service.

            • id (string) --

              The ID string for the event.

            • createdAt (datetime) --

              The Unix timestamp for the time when the event was triggered.

            • message (string) --

              The event message.

        • createdAt (datetime) --

          The Unix timestamp for the time when the service was created.

        • placementConstraints (list) --

          The placement constraints for the tasks in the service.

          • (dict) --

            An object representing a constraint on task placement. For more information, see Task placement constraints in the Amazon Elastic Container Service Developer Guide .

            Note

            If you're using the Fargate launch type, task placement constraints aren't supported.

            • type (string) --

              The type of constraint. Use distinctInstance to ensure that each task in a particular group is running on a different container instance. Use memberOf to restrict the selection to a group of valid candidates.

            • expression (string) --

              A cluster query language expression to apply to the constraint. The expression can have a maximum length of 2000 characters. You can't specify an expression if the constraint type is distinctInstance . For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide .

        • placementStrategy (list) --

          The placement strategy that determines how tasks for the service are placed.

          • (dict) --

            The task placement strategy for a task or service. For more information, see Task placement strategies in the Amazon Elastic Container Service Developer Guide .

            • type (string) --

              The type of placement strategy. The random placement strategy randomly places tasks on available candidates. The spread placement strategy spreads placement across available candidates evenly based on the field parameter. The binpack strategy places tasks on available candidates that have the least available amount of the resource that's specified with the field parameter. For example, if you binpack on memory, a task is placed on the instance with the least amount of remaining memory but still enough to run the task.

            • field (string) --

              The field to apply the placement strategy against. For the spread placement strategy, valid values are instanceId (or host , which has the same effect), or any platform or custom attribute that's applied to a container instance, such as attribute:ecs.availability-zone . For the binpack placement strategy, valid values are cpu and memory . For the random placement strategy, this field is not used.

        • networkConfiguration (dict) --

          The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.

          • awsvpcConfiguration (dict) --

            The VPC subnets and security groups that are associated with a task.

            Note

            All specified subnets and security groups must be from the same VPC.

            • subnets (list) --

              The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified per AwsVpcConfiguration .

              Note

              All specified subnets must be from the same VPC.

              • (string) --

            • securityGroups (list) --

              The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified per AwsVpcConfiguration .

              Note

              All specified security groups must be from the same VPC.

              • (string) --

            • assignPublicIp (string) --

              Whether the task's elastic network interface receives a public IP address. The default value is DISABLED .

        • healthCheckGracePeriodSeconds (integer) --

          The period of time, in seconds, that the Amazon ECS service scheduler ignores unhealthy Elastic Load Balancing target health checks after a task has first started.

        • schedulingStrategy (string) --

          The scheduling strategy to use for the service. For more information, see Services .

          There are two service scheduler strategies available.

          • REPLICA -The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions.

          • DAEMON -The daemon scheduling strategy deploys exactly one task on each active container instance. This task meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks. It stop tasks that don't meet the placement constraints.

          Note

          Fargate tasks don't support the DAEMON scheduling strategy.

        • deploymentController (dict) --

          The deployment controller type the service is using.

          • type (string) --

            The deployment controller type to use.

            There are three deployment controller types available:

            ECS

            The rolling update (ECS ) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the DeploymentConfiguration .

            CODE_DEPLOY

            The blue/green (CODE_DEPLOY ) deployment type uses the blue/green deployment model powered by CodeDeploy, which allows you to verify a new deployment of a service before sending production traffic to it.

            EXTERNAL

            The external (EXTERNAL ) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.

        • tags (list) --

          The metadata that you apply to the service to help you categorize and organize them. Each tag consists of a key and an optional value. You define bot the key and value.

          The following basic restrictions apply to tags:

          • Maximum number of tags per resource - 50

          • For each resource, each tag key must be unique, and each tag key can have only one value.

          • Maximum key length - 128 Unicode characters in UTF-8

          • Maximum value length - 256 Unicode characters in UTF-8

          • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

          • Tag keys and values are case-sensitive.

          • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

          • (dict) --

            The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

            The following basic restrictions apply to tags:

            • Maximum number of tags per resource - 50

            • For each resource, each tag key must be unique, and each tag key can have only one value.

            • Maximum key length - 128 Unicode characters in UTF-8

            • Maximum value length - 256 Unicode characters in UTF-8

            • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

            • Tag keys and values are case-sensitive.

            • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

            • key (string) --

              One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

            • value (string) --

              The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

        • createdBy (string) --

          The principal that created the service.

        • enableECSManagedTags (boolean) --

          Determines whether to use Amazon ECS managed tags for the tasks in the service. For more information, see Tagging Your Amazon ECS Resources in the Amazon Elastic Container Service Developer Guide .

        • propagateTags (string) --

          Determines whether to propagate the tags from the task definition or the service to the task. If no value is specified, the tags aren't propagated.

        • enableExecuteCommand (boolean) --

          Determines whether the execute command functionality is enabled for the service. If true , the execute command functionality is enabled for all containers in tasks as part of the service.

    • failures (list) --

      Any failures associated with the call.

      • (dict) --

        A failed resource. For a list of common causes, see API failure reasons in the Amazon Elastic Container Service Developer Guide .

        • arn (string) --

          The Amazon Resource Name (ARN) of the failed resource.

        • reason (string) --

          The reason for the failure.

        • detail (string) --

          The details of the failure.

DescribeTaskDefinition (updated) Link ¶
Changes (response)
{'taskDefinition': {'containerDefinitions': {'portMappings': {'appProtocol': 'http '
                                                                             '| '
                                                                             'http2 '
                                                                             '| '
                                                                             'grpc',
                                                              'name': 'string'}}}}

Describes a task definition. You can specify a family and revision to find information about a specific task definition, or you can simply specify the family to find the latest ACTIVE revision in that family.

Note

You can only describe INACTIVE task definitions while an active task or service references them.

See also: AWS API Documentation

Request Syntax

client.describe_task_definition(
    taskDefinition='string',
    include=[
        'TAGS',
    ]
)
type taskDefinition

string

param taskDefinition

[REQUIRED]

The family for the latest ACTIVE revision, family and revision (family:revision ) for a specific revision in the family, or full Amazon Resource Name (ARN) of the task definition to describe.

type include

list

param include

Determines whether to see the resource tags for the task definition. If TAGS is specified, the tags are included in the response. If this field is omitted, tags aren't included in the response.

  • (string) --

rtype

dict

returns

Response Syntax

{
    'taskDefinition': {
        'taskDefinitionArn': 'string',
        'containerDefinitions': [
            {
                'name': 'string',
                'image': 'string',
                'repositoryCredentials': {
                    'credentialsParameter': 'string'
                },
                'cpu': 123,
                'memory': 123,
                'memoryReservation': 123,
                'links': [
                    'string',
                ],
                'portMappings': [
                    {
                        'containerPort': 123,
                        'hostPort': 123,
                        'protocol': 'tcp'|'udp',
                        'name': 'string',
                        'appProtocol': 'http'|'http2'|'grpc'
                    },
                ],
                'essential': True|False,
                'entryPoint': [
                    'string',
                ],
                'command': [
                    'string',
                ],
                'environment': [
                    {
                        'name': 'string',
                        'value': 'string'
                    },
                ],
                'environmentFiles': [
                    {
                        'value': 'string',
                        'type': 's3'
                    },
                ],
                'mountPoints': [
                    {
                        'sourceVolume': 'string',
                        'containerPath': 'string',
                        'readOnly': True|False
                    },
                ],
                'volumesFrom': [
                    {
                        'sourceContainer': 'string',
                        'readOnly': True|False
                    },
                ],
                'linuxParameters': {
                    'capabilities': {
                        'add': [
                            'string',
                        ],
                        'drop': [
                            'string',
                        ]
                    },
                    'devices': [
                        {
                            'hostPath': 'string',
                            'containerPath': 'string',
                            'permissions': [
                                'read'|'write'|'mknod',
                            ]
                        },
                    ],
                    'initProcessEnabled': True|False,
                    'sharedMemorySize': 123,
                    'tmpfs': [
                        {
                            'containerPath': 'string',
                            'size': 123,
                            'mountOptions': [
                                'string',
                            ]
                        },
                    ],
                    'maxSwap': 123,
                    'swappiness': 123
                },
                'secrets': [
                    {
                        'name': 'string',
                        'valueFrom': 'string'
                    },
                ],
                'dependsOn': [
                    {
                        'containerName': 'string',
                        'condition': 'START'|'COMPLETE'|'SUCCESS'|'HEALTHY'
                    },
                ],
                'startTimeout': 123,
                'stopTimeout': 123,
                'hostname': 'string',
                'user': 'string',
                'workingDirectory': 'string',
                'disableNetworking': True|False,
                'privileged': True|False,
                'readonlyRootFilesystem': True|False,
                'dnsServers': [
                    'string',
                ],
                'dnsSearchDomains': [
                    'string',
                ],
                'extraHosts': [
                    {
                        'hostname': 'string',
                        'ipAddress': 'string'
                    },
                ],
                'dockerSecurityOptions': [
                    'string',
                ],
                'interactive': True|False,
                'pseudoTerminal': True|False,
                'dockerLabels': {
                    'string': 'string'
                },
                'ulimits': [
                    {
                        'name': 'core'|'cpu'|'data'|'fsize'|'locks'|'memlock'|'msgqueue'|'nice'|'nofile'|'nproc'|'rss'|'rtprio'|'rttime'|'sigpending'|'stack',
                        'softLimit': 123,
                        'hardLimit': 123
                    },
                ],
                'logConfiguration': {
                    'logDriver': 'json-file'|'syslog'|'journald'|'gelf'|'fluentd'|'awslogs'|'splunk'|'awsfirelens',
                    'options': {
                        'string': 'string'
                    },
                    'secretOptions': [
                        {
                            'name': 'string',
                            'valueFrom': 'string'
                        },
                    ]
                },
                'healthCheck': {
                    'command': [
                        'string',
                    ],
                    'interval': 123,
                    'timeout': 123,
                    'retries': 123,
                    'startPeriod': 123
                },
                'systemControls': [
                    {
                        'namespace': 'string',
                        'value': 'string'
                    },
                ],
                'resourceRequirements': [
                    {
                        'value': 'string',
                        'type': 'GPU'|'InferenceAccelerator'
                    },
                ],
                'firelensConfiguration': {
                    'type': 'fluentd'|'fluentbit',
                    'options': {
                        'string': 'string'
                    }
                }
            },
        ],
        'family': 'string',
        'taskRoleArn': 'string',
        'executionRoleArn': 'string',
        'networkMode': 'bridge'|'host'|'awsvpc'|'none',
        'revision': 123,
        'volumes': [
            {
                'name': 'string',
                'host': {
                    'sourcePath': 'string'
                },
                'dockerVolumeConfiguration': {
                    'scope': 'task'|'shared',
                    'autoprovision': True|False,
                    'driver': 'string',
                    'driverOpts': {
                        'string': 'string'
                    },
                    'labels': {
                        'string': 'string'
                    }
                },
                'efsVolumeConfiguration': {
                    'fileSystemId': 'string',
                    'rootDirectory': 'string',
                    'transitEncryption': 'ENABLED'|'DISABLED',
                    'transitEncryptionPort': 123,
                    'authorizationConfig': {
                        'accessPointId': 'string',
                        'iam': 'ENABLED'|'DISABLED'
                    }
                },
                'fsxWindowsFileServerVolumeConfiguration': {
                    'fileSystemId': 'string',
                    'rootDirectory': 'string',
                    'authorizationConfig': {
                        'credentialsParameter': 'string',
                        'domain': 'string'
                    }
                }
            },
        ],
        'status': 'ACTIVE'|'INACTIVE',
        'requiresAttributes': [
            {
                'name': 'string',
                'value': 'string',
                'targetType': 'container-instance',
                'targetId': 'string'
            },
        ],
        'placementConstraints': [
            {
                'type': 'memberOf',
                'expression': 'string'
            },
        ],
        'compatibilities': [
            'EC2'|'FARGATE'|'EXTERNAL',
        ],
        'runtimePlatform': {
            'cpuArchitecture': 'X86_64'|'ARM64',
            'operatingSystemFamily': 'WINDOWS_SERVER_2019_FULL'|'WINDOWS_SERVER_2019_CORE'|'WINDOWS_SERVER_2016_FULL'|'WINDOWS_SERVER_2004_CORE'|'WINDOWS_SERVER_2022_CORE'|'WINDOWS_SERVER_2022_FULL'|'WINDOWS_SERVER_20H2_CORE'|'LINUX'
        },
        'requiresCompatibilities': [
            'EC2'|'FARGATE'|'EXTERNAL',
        ],
        'cpu': 'string',
        'memory': 'string',
        'inferenceAccelerators': [
            {
                'deviceName': 'string',
                'deviceType': 'string'
            },
        ],
        'pidMode': 'host'|'task',
        'ipcMode': 'host'|'task'|'none',
        'proxyConfiguration': {
            'type': 'APPMESH',
            'containerName': 'string',
            'properties': [
                {
                    'name': 'string',
                    'value': 'string'
                },
            ]
        },
        'registeredAt': datetime(2015, 1, 1),
        'deregisteredAt': datetime(2015, 1, 1),
        'registeredBy': 'string',
        'ephemeralStorage': {
            'sizeInGiB': 123
        }
    },
    'tags': [
        {
            'key': 'string',
            'value': 'string'
        },
    ]
}

Response Structure

  • (dict) --

    • taskDefinition (dict) --

      The full task definition description.

      • taskDefinitionArn (string) --

        The full Amazon Resource Name (ARN) of the task definition.

      • containerDefinitions (list) --

        A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide .

        • (dict) --

          Container definitions are used in task definitions to describe the different containers that are launched as part of a task.

          • name (string) --

            The name of a container. If you're linking multiple containers together in a task definition, the name of one container can be entered in the links of another container to connect the containers. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This parameter maps to name in the Create a container section of the Docker Remote API and the --name option to docker run .

          • image (string) --

            The image used to start a container. This string is passed directly to the Docker daemon. By default, images in the Docker Hub registry are available. Other repositories are specified with either `` repository-url /image :tag `` or `` repository-url /image @*digest* `` . Up to 255 letters (uppercase and lowercase), numbers, hyphens, underscores, colons, periods, forward slashes, and number signs are allowed. This parameter maps to Image in the Create a container section of the Docker Remote API and the IMAGE parameter of docker run .

            • When a new task starts, the Amazon ECS container agent pulls the latest version of the specified image and tag for the container to use. However, subsequent updates to a repository image aren't propagated to already running tasks.

            • Images in Amazon ECR repositories can be specified by either using the full registry/repository:tag or registry/repository@digest . For example, 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>:latest or 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>@sha256:94afd1f2e64d908bc90dbca0035a5b567EXAMPLE .

            • Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo ).

            • Images in other repositories on Docker Hub are qualified with an organization name (for example, amazon/amazon-ecs-agent ).

            • Images in other online repositories are qualified further by a domain name (for example, quay.io/assemblyline/ubuntu ).

          • repositoryCredentials (dict) --

            The private repository authentication credentials to use.

            • credentialsParameter (string) --

              The Amazon Resource Name (ARN) of the secret containing the private repository credentials.

              Note

              When you use the Amazon ECS API, CLI, or Amazon Web Services SDK, if the secret exists in the same Region as the task that you're launching then you can use either the full ARN or the name of the secret. When you use the Amazon Web Services Management Console, you must specify the full ARN of the secret.

          • cpu (integer) --

            The number of cpu units reserved for the container. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run .

            This field is optional for tasks using the Fargate launch type, and the only requirement is that the total amount of CPU reserved for all containers within a task be lower than the task-level cpu value.

            Note

            You can determine the number of CPU units that are available per EC2 instance type by multiplying the vCPUs listed for that instance type on the Amazon EC2 Instances detail page by 1,024.

            Linux containers share unallocated CPU units with other containers on the container instance with the same ratio as their allocated amount. For example, if you run a single-container task on a single-core instance type with 512 CPU units specified for that container, and that's the only task running on the container instance, that container could use the full 1,024 CPU unit share at any given time. However, if you launched another copy of the same task on that container instance, each task is guaranteed a minimum of 512 CPU units when needed. Moreover, each container could float to higher CPU usage if the other container was not using it. If both tasks were 100% active all of the time, they would be limited to 512 CPU units.

            On Linux container instances, the Docker daemon on the container instance uses the CPU value to calculate the relative CPU share ratios for running containers. For more information, see CPU share constraint in the Docker documentation. The minimum valid CPU share value that the Linux kernel allows is 2. However, the CPU parameter isn't required, and you can use CPU values below 2 in your container definitions. For CPU values below 2 (including null), the behavior varies based on your Amazon ECS container agent version:

            • Agent versions less than or equal to 1.1.0: Null and zero CPU values are passed to Docker as 0, which Docker then converts to 1,024 CPU shares. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares.

            • Agent versions greater than or equal to 1.2.0: Null, zero, and CPU values of 1 are passed to Docker as 2.

            On Windows container instances, the CPU limit is enforced as an absolute limit, or a quota. Windows containers only have access to the specified amount of CPU that's described in the task definition. A null or zero CPU value is passed to Docker as 0 , which Windows interprets as 1% of one CPU.

          • memory (integer) --

            The amount (in MiB) of memory to present to the container. If your container attempts to exceed the memory specified here, the container is killed. The total amount of memory reserved for all containers within a task must be lower than the task memory value, if one is specified. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run .

            If using the Fargate launch type, this parameter is optional.

            If using the EC2 launch type, you must specify either a task-level memory value or a container-level memory value. If you specify both a container-level memory and memoryReservation value, memory must be greater than memoryReservation . If you specify memoryReservation , then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used.

            The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers.

            The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers.

          • memoryReservation (integer) --

            The soft limit (in MiB) of memory to reserve for the container. When system memory is under heavy contention, Docker attempts to keep the container memory to this soft limit. However, your container can consume more memory when it needs to, up to either the hard limit specified with the memory parameter (if applicable), or all of the available memory on the container instance, whichever comes first. This parameter maps to MemoryReservation in the Create a container section of the Docker Remote API and the --memory-reservation option to docker run .

            If a task-level memory value is not specified, you must specify a non-zero integer for one or both of memory or memoryReservation in a container definition. If you specify both, memory must be greater than memoryReservation . If you specify memoryReservation , then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used.

            For example, if your container normally uses 128 MiB of memory, but occasionally bursts to 256 MiB of memory for short periods of time, you can set a memoryReservation of 128 MiB, and a memory hard limit of 300 MiB. This configuration would allow the container to only reserve 128 MiB of memory from the remaining resources on the container instance, but also allow the container to consume more memory resources when needed.

            The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers.

            The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers.

          • links (list) --

            The links parameter allows containers to communicate with each other without the need for port mappings. This parameter is only supported if the network mode of a task definition is bridge . The name:internalName construct is analogous to name:alias in Docker links. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. For more information about linking Docker containers, go to Legacy container links in the Docker documentation. This parameter maps to Links in the Create a container section of the Docker Remote API and the --link option to docker run .

            Note

            This parameter is not supported for Windows containers.

            Warning

            Containers that are collocated on a single container instance may be able to communicate with each other without requiring links or host port mappings. Network isolation is achieved on the container instance using security groups and VPC settings.

            • (string) --

          • portMappings (list) --

            The list of port mappings for the container. Port mappings allow containers to access ports on the host container instance to send or receive traffic.

            For task definitions that use the awsvpc network mode, only specify the containerPort . The hostPort can be left blank or it must be the same value as the containerPort .

            Port mappings on Windows use the NetNAT gateway address rather than localhost . There's no loopback for port mappings on Windows, so you can't access a container's mapped port from the host itself.

            This parameter maps to PortBindings in the Create a container section of the Docker Remote API and the --publish option to docker run . If the network mode of a task definition is set to none , then you can't specify port mappings. If the network mode of a task definition is set to host , then host ports must either be undefined or they must match the container port in the port mapping.

            Note

            After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the Network Bindings section of a container description for a selected task in the Amazon ECS console. The assignments are also visible in the networkBindings section DescribeTasks responses.

            • (dict) --

              Port mappings allow containers to access ports on the host container instance to send or receive traffic. Port mappings are specified as part of the container definition.

              If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort . The hostPort can be left blank or it must be the same value as the containerPort .

              Note

              You can't expose the same container port for multiple protocols. If you attempt this, an error is returned.

              After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the networkBindings section of DescribeTasks API responses.

              • containerPort (integer) --

                The port number on the container that's bound to the user-specified or automatically assigned host port.

                If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort .

                If you use containers in a task with the bridge network mode and you specify a container port and not a host port, your container automatically receives a host port in the ephemeral port range. For more information, see hostPort . Port mappings that are automatically assigned in this way do not count toward the 100 reserved ports limit of a container instance.

              • hostPort (integer) --

                The port number on the container instance to reserve for your container.

                If you use containers in a task with the awsvpc or host network mode, the hostPort can either be left blank or set to the same value as the containerPort .

                If you use containers in a task with the bridge network mode, you can specify a non-reserved host port for your container port mapping, or you can omit the hostPort (or set it to 0 ) while specifying a containerPort and your container automatically receives a port in the ephemeral port range for your container instance operating system and Docker version.

                The default ephemeral port range for Docker version 1.6.0 and later is listed on the instance under /proc/sys/net/ipv4/ip_local_port_range . If this kernel parameter is unavailable, the default ephemeral port range from 49153 through 65535 is used. Do not attempt to specify a host port in the ephemeral port range as these are reserved for automatic assignment. In general, ports below 32768 are outside of the ephemeral port range.

                The default reserved ports are 22 for SSH, the Docker ports 2375 and 2376, and the Amazon ECS container agent ports 51678-51680. Any host port that was previously specified in a running task is also reserved while the task is running. That is, after a task stops, the host port is released. The current reserved ports are displayed in the remainingResources of DescribeContainerInstances output. A container instance can have up to 100 reserved ports at a time. This number includes the default reserved ports. Automatically assigned ports aren't included in the 100 reserved ports quota.

              • protocol (string) --

                The protocol used for the port mapping. Valid values are tcp and udp . The default is tcp .

              • name (string) --

                The name that's used for the port mapping. This parameter only applies to Service Connect. This parameter is the name that you use in the serviceConnectConfiguration of a service. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

              • appProtocol (string) --

                The application protocol that's used for the port mapping. This parameter only applies to Service Connect. We recommend that you set this parameter to be consistent with the protocol that your application uses. If you set this parameter, Amazon ECS adds protocol-specific connection handling to the Service Connect proxy. If you set this parameter, Amazon ECS adds protocol-specific telemetry in the Amazon ECS console and CloudWatch.

                If you don't set a value for this parameter, then TCP is used. However, Amazon ECS doesn't add protocol-specific telemetry for TCP.

                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 .

          • essential (boolean) --

            If the essential parameter of a container is marked as true , and that container fails or stops for any reason, all other containers that are part of the task are stopped. If the essential parameter of a container is marked as false , its failure doesn't affect the rest of the containers in a task. If this parameter is omitted, a container is assumed to be essential.

            All tasks must have at least one essential container. If you have an application that's composed of multiple containers, group containers that are used for a common purpose into components, and separate the different components into multiple task definitions. For more information, see Application Architecture in the Amazon Elastic Container Service Developer Guide .

          • entryPoint (list) --

            Warning

            Early versions of the Amazon ECS container agent don't properly handle entryPoint parameters. If you have problems using entryPoint , update your container agent or enter your commands and arguments as command array items instead.

            The entry point that's passed to the container. This parameter maps to Entrypoint in the Create a container section of the Docker Remote API and the --entrypoint option to docker run . For more information, see https://docs.docker.com/engine/reference/builder/#entrypoint .

            • (string) --

          • command (list) --

            The command that's passed to the container. This parameter maps to Cmd in the Create a container section of the Docker Remote API and the COMMAND parameter to docker run . For more information, see https://docs.docker.com/engine/reference/builder/#cmd . If there are multiple arguments, each argument is a separated string in the array.

            • (string) --

          • environment (list) --

            The environment variables to pass to a container. This parameter maps to Env in the Create a container section of the Docker Remote API and the --env option to docker run .

            Warning

            We don't recommend that you use plaintext environment variables for sensitive information, such as credential data.

            • (dict) --

              A key-value pair object.

              • name (string) --

                The name of the key-value pair. For environment variables, this is the name of the environment variable.

              • value (string) --

                The value of the key-value pair. For environment variables, this is the value of the environment variable.

          • environmentFiles (list) --

            A list of files containing the environment variables to pass to a container. This parameter maps to the --env-file option to docker run .

            You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file contains an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

            If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying Environment Variables in the Amazon Elastic Container Service Developer Guide .

            • (dict) --

              A list of files containing the environment variables to pass to a container. You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file should contain an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

              If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying environment variables in the Amazon Elastic Container Service Developer Guide .

              This parameter is only supported for tasks hosted on Fargate using the following platform versions:

              • Linux platform version 1.4.0 or later.

              • Windows platform version 1.0.0 or later.

              • value (string) --

                The Amazon Resource Name (ARN) of the Amazon S3 object containing the environment variable file.

              • type (string) --

                The file type to use. The only supported value is s3 .

          • mountPoints (list) --

            The mount points for data volumes in your container.

            This parameter maps to Volumes in the Create a container section of the Docker Remote API and the --volume option to docker run .

            Windows containers can mount whole directories on the same drive as $env:ProgramData . Windows containers can't mount directories on a different drive, and mount point can't be across drives.

            • (dict) --

              Details for a volume mount point that's used in a container definition.

              • sourceVolume (string) --

                The name of the volume to mount. Must be a volume name referenced in the name parameter of task definition volume .

              • containerPath (string) --

                The path on the container to mount the host volume at.

              • readOnly (boolean) --

                If this value is true , the container has read-only access to the volume. If this value is false , then the container can write to the volume. The default value is false .

          • volumesFrom (list) --

            Data volumes to mount from another container. This parameter maps to VolumesFrom in the Create a container section of the Docker Remote API and the --volumes-from option to docker run .

            • (dict) --

              Details on a data volume from another container in the same task definition.

              • sourceContainer (string) --

                The name of another container within the same task definition to mount volumes from.

              • readOnly (boolean) --

                If this value is true , the container has read-only access to the volume. If this value is false , then the container can write to the volume. The default value is false .

          • linuxParameters (dict) --

            Linux-specific modifications that are applied to the container, such as Linux kernel capabilities. For more information see KernelCapabilities .

            Note

            This parameter is not supported for Windows containers.

            • capabilities (dict) --

              The Linux capabilities for the container that are added to or dropped from the default configuration provided by Docker.

              Note

              For tasks that use the Fargate launch type, capabilities is supported for all platform versions but the add parameter is only supported if using platform version 1.4.0 or later.

              • add (list) --

                The Linux capabilities for the container that have been added to the default configuration provided by Docker. This parameter maps to CapAdd in the Create a container section of the Docker Remote API and the --cap-add option to docker run .

                Note

                Tasks launched on Fargate only support adding the SYS_PTRACE kernel capability.

                Valid values: "ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" | "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" | "FOWNER" | "FSETID" | "IPC_LOCK" | "IPC_OWNER" | "KILL" | "LEASE" | "LINUX_IMMUTABLE" | "MAC_ADMIN" | "MAC_OVERRIDE" | "MKNOD" | "NET_ADMIN" | "NET_BIND_SERVICE" | "NET_BROADCAST" | "NET_RAW" | "SETFCAP" | "SETGID" | "SETPCAP" | "SETUID" | "SYS_ADMIN" | "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT" | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" | "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"

                • (string) --

              • drop (list) --

                The Linux capabilities for the container that have been removed from the default configuration provided by Docker. This parameter maps to CapDrop in the Create a container section of the Docker Remote API and the --cap-drop option to docker run .

                Valid values: "ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" | "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" | "FOWNER" | "FSETID" | "IPC_LOCK" | "IPC_OWNER" | "KILL" | "LEASE" | "LINUX_IMMUTABLE" | "MAC_ADMIN" | "MAC_OVERRIDE" | "MKNOD" | "NET_ADMIN" | "NET_BIND_SERVICE" | "NET_BROADCAST" | "NET_RAW" | "SETFCAP" | "SETGID" | "SETPCAP" | "SETUID" | "SYS_ADMIN" | "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT" | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" | "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"

                • (string) --

            • devices (list) --

              Any host devices to expose to the container. This parameter maps to Devices in the Create a container section of the Docker Remote API and the --device option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the devices parameter isn't supported.

              • (dict) --

                An object representing a container instance host device.

                • hostPath (string) --

                  The path for the device on the host container instance.

                • containerPath (string) --

                  The path inside the container at which to expose the host device.

                • permissions (list) --

                  The explicit permissions to provide to the container for the device. By default, the container has permissions for read , write , and mknod for the device.

                  • (string) --

            • initProcessEnabled (boolean) --

              Run an init process inside the container that forwards signals and reaps processes. This parameter maps to the --init option to docker run . This parameter requires version 1.25 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            • sharedMemorySize (integer) --

              The value for the size (in MiB) of the /dev/shm volume. This parameter maps to the --shm-size option to docker run .

              Note

              If you are using tasks that use the Fargate launch type, the sharedMemorySize parameter is not supported.

            • tmpfs (list) --

              The container path, mount options, and size (in MiB) of the tmpfs mount. This parameter maps to the --tmpfs option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the tmpfs parameter isn't supported.

              • (dict) --

                The container path, mount options, and size of the tmpfs mount.

                • containerPath (string) --

                  The absolute file path where the tmpfs volume is to be mounted.

                • size (integer) --

                  The maximum size (in MiB) of the tmpfs volume.

                • mountOptions (list) --

                  The list of tmpfs volume mount options.

                  Valid values: "defaults" | "ro" | "rw" | "suid" | "nosuid" | "dev" | "nodev" | "exec" | "noexec" | "sync" | "async" | "dirsync" | "remount" | "mand" | "nomand" | "atime" | "noatime" | "diratime" | "nodiratime" | "bind" | "rbind" | "unbindable" | "runbindable" | "private" | "rprivate" | "shared" | "rshared" | "slave" | "rslave" | "relatime" | "norelatime" | "strictatime" | "nostrictatime" | "mode" | "uid" | "gid" | "nr_inodes" | "nr_blocks" | "mpol"

                  • (string) --

            • maxSwap (integer) --

              The total amount of swap memory (in MiB) a container can use. This parameter will be translated to the --memory-swap option to docker run where the value would be the sum of the container memory plus the maxSwap value.

              If a maxSwap value of 0 is specified, the container will not use swap. Accepted values are 0 or any positive integer. If the maxSwap parameter is omitted, the container will use the swap configuration for the container instance it is running on. A maxSwap value must be set for the swappiness parameter to be used.

              Note

              If you're using tasks that use the Fargate launch type, the maxSwap parameter isn't supported.

            • swappiness (integer) --

              This allows you to tune a container's memory swappiness behavior. A swappiness value of 0 will cause swapping to not happen unless absolutely necessary. A swappiness value of 100 will cause pages to be swapped very aggressively. Accepted values are whole numbers between 0 and 100 . If the swappiness parameter is not specified, a default value of 60 is used. If a value is not specified for maxSwap then this parameter is ignored. This parameter maps to the --memory-swappiness option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the swappiness parameter isn't supported.

          • secrets (list) --

            The secrets to pass to the container. For more information, see Specifying Sensitive Data in the Amazon Elastic Container Service Developer Guide .

            • (dict) --

              An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

              • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

              • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

              For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

              • name (string) --

                The name of the secret.

              • valueFrom (string) --

                The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

                For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

                Note

                If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

          • dependsOn (list) --

            The dependencies defined for container startup and shutdown. A container can contain multiple dependencies on other containers in a task definition. When a dependency is defined for container startup, for container shutdown it is reversed.

            For tasks using the EC2 launch type, the container instances require at least version 1.26.0 of the container agent to turn on container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            • (dict) --

              The dependencies defined for container startup and shutdown. A container can contain multiple dependencies. When a dependency is defined for container startup, for container shutdown it is reversed.

              Your Amazon ECS container instances require at least version 1.26.0 of the container agent to use container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

              Note

              For tasks that use the Fargate launch type, the task or service requires the following platforms:

              • Linux platform version 1.3.0 or later.

              • Windows platform version 1.0.0 or later.

              • containerName (string) --

                The name of a container.

              • condition (string) --

                The dependency condition of the container. The following are the available conditions and their behavior:

                • START - This condition emulates the behavior of links and volumes today. It validates that a dependent container is started before permitting other containers to start.

                • COMPLETE - This condition validates that a dependent container runs to completion (exits) before permitting other containers to start. This can be useful for nonessential containers that run a script and then exit. This condition can't be set on an essential container.

                • SUCCESS - This condition is the same as COMPLETE , but it also requires that the container exits with a zero status. This condition can't be set on an essential container.

                • HEALTHY - This condition validates that the dependent container passes its Docker health check before permitting other containers to start. This requires that the dependent container has health checks configured. This condition is confirmed only at task startup.

          • startTimeout (integer) --

            Time duration (in seconds) to wait before giving up on resolving dependencies for a container. For example, you specify two containers in a task definition with containerA having a dependency on containerB reaching a COMPLETE , SUCCESS , or HEALTHY status. If a startTimeout value is specified for containerB and it doesn't reach the desired status within that time then containerA gives up and not start. This results in the task transitioning to a STOPPED state.

            Note

            When the ECS_CONTAINER_START_TIMEOUT container agent configuration variable is used, it's enforced independently from this start timeout value.

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            For tasks using the EC2 launch type, your container instances require at least version 1.26.0 of the container agent to use a container start timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

          • stopTimeout (integer) --

            Time duration (in seconds) to wait before the container is forcefully killed if it doesn't exit normally on its own.

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            The max stop timeout value is 120 seconds and if the parameter is not specified, the default value of 30 seconds is used.

            For tasks that use the EC2 launch type, if the stopTimeout parameter isn't specified, the value set for the Amazon ECS container agent configuration variable ECS_CONTAINER_STOP_TIMEOUT is used. If neither the stopTimeout parameter or the ECS_CONTAINER_STOP_TIMEOUT agent configuration variable are set, then the default values of 30 seconds for Linux containers and 30 seconds on Windows containers are used. Your container instances require at least version 1.26.0 of the container agent to use a container stop timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

          • hostname (string) --

            The hostname to use for your container. This parameter maps to Hostname in the Create a container section of the Docker Remote API and the --hostname option to docker run .

            Note

            The hostname parameter is not supported if you're using the awsvpc network mode.

          • user (string) --

            The user to use inside the container. This parameter maps to User in the Create a container section of the Docker Remote API and the --user option to docker run .

            Warning

            When running tasks using the host network mode, don't run containers using the root user (UID 0). We recommend using a non-root user for better security.

            You can specify the user using the following formats. If specifying a UID or GID, you must specify it as a positive integer.

            • user

            • user:group

            • uid

            • uid:gid

            • user:gid

            • uid:group

            Note

            This parameter is not supported for Windows containers.

          • workingDirectory (string) --

            The working directory to run commands inside the container in. This parameter maps to WorkingDir in the Create a container section of the Docker Remote API and the --workdir option to docker run .

          • disableNetworking (boolean) --

            When this parameter is true, networking is disabled within the container. This parameter maps to NetworkDisabled in the Create a container section of the Docker Remote API .

            Note

            This parameter is not supported for Windows containers.

          • privileged (boolean) --

            When this parameter is true, the container is given elevated privileges on the host container instance (similar to the root user). This parameter maps to Privileged in the Create a container section of the Docker Remote API and the --privileged option to docker run .

            Note

            This parameter is not supported for Windows containers or tasks run on Fargate.

          • readonlyRootFilesystem (boolean) --

            When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs in the Create a container section of the Docker Remote API and the --read-only option to docker run .

            Note

            This parameter is not supported for Windows containers.

          • dnsServers (list) --

            A list of DNS servers that are presented to the container. This parameter maps to Dns in the Create a container section of the Docker Remote API and the --dns option to docker run .

            Note

            This parameter is not supported for Windows containers.

            • (string) --

          • dnsSearchDomains (list) --

            A list of DNS search domains that are presented to the container. This parameter maps to DnsSearch in the Create a container section of the Docker Remote API and the --dns-search option to docker run .

            Note

            This parameter is not supported for Windows containers.

            • (string) --

          • extraHosts (list) --

            A list of hostnames and IP address mappings to append to the /etc/hosts file on the container. This parameter maps to ExtraHosts in the Create a container section of the Docker Remote API and the --add-host option to docker run .

            Note

            This parameter isn't supported for Windows containers or tasks that use the awsvpc network mode.

            • (dict) --

              Hostnames and IP address entries that are added to the /etc/hosts file of a container via the extraHosts parameter of its ContainerDefinition .

              • hostname (string) --

                The hostname to use in the /etc/hosts entry.

              • ipAddress (string) --

                The IP address to use in the /etc/hosts entry.

          • dockerSecurityOptions (list) --

            A list of strings to provide custom labels for SELinux and AppArmor multi-level security systems. This field isn't valid for containers in tasks using the Fargate launch type.

            With Windows containers, this parameter can be used to reference a credential spec file when configuring a container for Active Directory authentication. For more information, see Using gMSAs for Windows Containers in the Amazon Elastic Container Service Developer Guide .

            This parameter maps to SecurityOpt in the Create a container section of the Docker Remote API and the --security-opt option to docker run .

            Note

            The Amazon ECS container agent running on a container instance must register with the ECS_SELINUX_CAPABLE=true or ECS_APPARMOR_CAPABLE=true environment variables before containers placed on that instance can use these security options. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide .

            For more information about valid values, see Docker Run Security Configuration .

            Valid values: "no-new-privileges" | "apparmor:PROFILE" | "label:value" | "credentialspec:CredentialSpecFilePath"

            • (string) --

          • interactive (boolean) --

            When this parameter is true , you can deploy containerized applications that require stdin or a tty to be allocated. This parameter maps to OpenStdin in the Create a container section of the Docker Remote API and the --interactive option to docker run .

          • pseudoTerminal (boolean) --

            When this parameter is true , a TTY is allocated. This parameter maps to Tty in the Create a container section of the Docker Remote API and the --tty option to docker run .

          • dockerLabels (dict) --

            A key/value map of labels to add to the container. This parameter maps to Labels in the Create a container section of the Docker Remote API and the --label option to docker run . This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            • (string) --

              • (string) --

          • ulimits (list) --

            A list of ulimits to set in the container. If a ulimit value is specified in a task definition, it overrides the default values set by Docker. This parameter maps to Ulimits in the Create a container section of the Docker Remote API and the --ulimit option to docker run . Valid naming values are displayed in the Ulimit data type.

            Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and hard limit is 4096 .

            This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            Note

            This parameter is not supported for Windows containers.

            • (dict) --

              The ulimit settings to pass to the container.

              Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and hard limit is 4096 .

              • name (string) --

                The type of the ulimit .

              • softLimit (integer) --

                The soft limit for the ulimit type.

              • hardLimit (integer) --

                The hard limit for the ulimit type.

          • logConfiguration (dict) --

            The log configuration specification for the container.

            This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to docker run . By default, containers use the same logging driver that the Docker daemon uses. However the container can use a different logging driver than the Docker daemon by specifying a log driver with this parameter in the container definition. To use a different logging driver for a container, the log system must be configured properly on the container instance (or on a different log server for remote logging options). For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation.

            Note

            Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type). Additional log drivers may be available in future releases of the Amazon ECS container agent.

            This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            Note

            The Amazon ECS container agent running on a container instance must register the logging drivers available on that instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide .

            • logDriver (string) --

              The log driver to use for the container.

              For tasks on Fargate, the supported log drivers are awslogs , splunk , and awsfirelens .

              For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs , fluentd , gelf , json-file , journald , logentries ,``syslog`` , splunk , and awsfirelens .

              For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide .

              For more information about using the awsfirelens log driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide .

              Note

              If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.

            • options (dict) --

              The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

              • (string) --

                • (string) --

            • secretOptions (list) --

              The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

              • (dict) --

                An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

                • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

                • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

                For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

                • name (string) --

                  The name of the secret.

                • valueFrom (string) --

                  The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

                  For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

                  Note

                  If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

          • healthCheck (dict) --

            The container health check command and associated configuration parameters for the container. This parameter maps to HealthCheck in the Create a container section of the Docker Remote API and the HEALTHCHECK parameter of docker run .

            • command (list) --

              A string array representing the command that the container runs to determine if it is healthy. The string array must start with CMD to run the command arguments directly, or CMD-SHELL to run the command with the container's default shell.

              When you use the Amazon Web Services Management Console JSON panel, the Command Line Interface, or the APIs, enclose the list of commands in brackets.

              [ "CMD-SHELL", "curl -f http://localhost/ || exit 1" ]

              You don't need to include the brackets when you use the Amazon Web Services Management Console.

              "CMD-SHELL", "curl -f http://localhost/ || exit 1"

              An exit code of 0 indicates success, and non-zero exit code indicates failure. For more information, see HealthCheck in the Create a container section of the Docker Remote API .

              • (string) --

            • interval (integer) --

              The time period in seconds between each health check execution. You may specify between 5 and 300 seconds. The default value is 30 seconds.

            • timeout (integer) --

              The time period in seconds to wait for a health check to succeed before it is considered a failure. You may specify between 2 and 60 seconds. The default value is 5.

            • retries (integer) --

              The number of times to retry a failed health check before the container is considered unhealthy. You may specify between 1 and 10 retries. The default value is 3.

            • startPeriod (integer) --

              The optional grace period to provide containers time to bootstrap before failed health checks count towards the maximum number of retries. You can specify between 0 and 300 seconds. By default, the startPeriod is disabled.

              Note

              If a health check succeeds within the startPeriod , then the container is considered healthy and any subsequent failures count toward the maximum number of retries.

          • systemControls (list) --

            A list of namespaced kernel parameters to set in the container. This parameter maps to Sysctls in the Create a container section of the Docker Remote API and the --sysctl option to docker run .

            Note

            We don't recommended that you specify network-related systemControls parameters for multiple containers in a single task that also uses either the awsvpc or host network modes. For tasks that use the awsvpc network mode, the container that's started last determines which systemControls parameters take effect. For tasks that use the host network mode, it changes the container instance's namespaced kernel parameters as well as the containers.

            • (dict) --

              A list of namespaced kernel parameters to set in the container. This parameter maps to Sysctls in the Create a container section of the Docker Remote API and the --sysctl option to docker run .

              We don't recommend that you specify network-related systemControls parameters for multiple containers in a single task. This task also uses either the awsvpc or host network mode. It does it for the following reasons.

              • For tasks that use the awsvpc network mode, if you set systemControls for any container, it applies to all containers in the task. If you set different systemControls for multiple containers in a single task, the container that's started last determines which systemControls take effect.

              • For tasks that use the host network mode, the systemControls parameter applies to the container instance's kernel parameter and that of all containers of any tasks running on that container instance.

              • namespace (string) --

                The namespaced kernel parameter to set a value for.

              • value (string) --

                The value for the namespaced kernel parameter that's specified in namespace .

          • resourceRequirements (list) --

            The type and amount of a resource to assign to a container. The only supported resource is a GPU.

            • (dict) --

              The type and amount of a resource to assign to a container. The supported resource types are GPUs and Elastic Inference accelerators. For more information, see Working with GPUs on Amazon ECS or Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide

              • value (string) --

                The value for the specified resource type.

                If the GPU type is used, the value is the number of physical GPUs the Amazon ECS container agent reserves for the container. The number of GPUs that's reserved for all containers in a task can't exceed the number of available GPUs on the container instance that the task is launched on.

                If the InferenceAccelerator type is used, the value matches the deviceName for an InferenceAccelerator specified in a task definition.

              • type (string) --

                The type of resource to assign to a container. The supported values are GPU or InferenceAccelerator .

          • firelensConfiguration (dict) --

            The FireLens configuration for the container. This is used to specify and configure a log router for container logs. For more information, see Custom Log Routing in the Amazon Elastic Container Service Developer Guide .

            • type (string) --

              The log router to use. The valid values are fluentd or fluentbit .

            • options (dict) --

              The options to use when configuring the log router. This field is optional and can be used to specify a custom configuration file or to add additional metadata, such as the task, task definition, cluster, and container instance details to the log event. If specified, the syntax to use is "options":{"enable-ecs-log-metadata":"true|false","config-file-type:"s3|file","config-file-value":"arn:aws:s3:::mybucket/fluent.conf|filepath"} . For more information, see Creating a task definition that uses a FireLens configuration in the Amazon Elastic Container Service Developer Guide .

              Note

              Tasks hosted on Fargate only support the file configuration file type.

              • (string) --

                • (string) --

      • family (string) --

        The name of a family that this task definition is registered to. Up to 255 characters are allowed. Letters (both uppercase and lowercase letters), numbers, hyphens (-), and underscores (_) are allowed.

        A family groups multiple versions of a task definition. Amazon ECS gives the first task definition that you registered to a family a revision number of 1. Amazon ECS gives sequential revision numbers to each task definition that you add.

      • taskRoleArn (string) --

        The short name or full Amazon Resource Name (ARN) of the Identity and Access Management role that grants containers in the task permission to call Amazon Web Services APIs on your behalf. For more information, see Amazon ECS Task Role in the Amazon Elastic Container Service Developer Guide .

        IAM roles for tasks on Windows require that the -EnableTaskIAMRole option is set when you launch the Amazon ECS-optimized Windows AMI. Your containers must also run some configuration code to use the feature. For more information, see Windows IAM roles for tasks in the Amazon Elastic Container Service Developer Guide .

      • executionRoleArn (string) --

        The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make Amazon Web Services API calls on your behalf. The task execution IAM role is required depending on the requirements of your task. For more information, see Amazon ECS task execution IAM role in the Amazon Elastic Container Service Developer Guide .

      • networkMode (string) --

        The Docker networking mode to use for the containers in the task. The valid values are none , bridge , awsvpc , and host . If no network mode is specified, the default is bridge .

        For Amazon ECS tasks on Fargate, the awsvpc network mode is required. For Amazon ECS tasks on Amazon EC2 Linux instances, any network mode can be used. For Amazon ECS tasks on Amazon EC2 Windows instances, <default> or awsvpc can be used. If the network mode is set to none , you cannot specify port mappings in your container definitions, and the tasks containers do not have external connectivity. The host and awsvpc network modes offer the highest networking performance for containers because they use the EC2 network stack instead of the virtualized network stack provided by the bridge mode.

        With the host and awsvpc network modes, exposed container ports are mapped directly to the corresponding host port (for the host network mode) or the attached elastic network interface port (for the awsvpc network mode), so you cannot take advantage of dynamic host port mappings.

        Warning

        When using the host network mode, you should not run containers using the root user (UID 0). It is considered best practice to use a non-root user.

        If the network mode is awsvpc , the task is allocated an elastic network interface, and you must specify a NetworkConfiguration value when you create a service or run a task with the task definition. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide .

        If the network mode is host , you cannot run multiple instantiations of the same task on a single container instance when port mappings are used.

        For more information, see Network settings in the Docker run reference .

      • revision (integer) --

        The revision of the task in a particular family. The revision is a version number of a task definition in a family. When you register a task definition for the first time, the revision is 1 . Each time that you register a new revision of a task definition in the same family, the revision value always increases by one. This is even if you deregistered previous revisions in this family.

      • volumes (list) --

        The list of data volume definitions for the task. For more information, see Using data volumes in tasks in the Amazon Elastic Container Service Developer Guide .

        Note

        The host and sourcePath parameters aren't supported for tasks run on Fargate.

        • (dict) --

          A data volume that's used in a task definition. For tasks that use the Amazon Elastic File System (Amazon EFS), specify an efsVolumeConfiguration . For Windows tasks that use Amazon FSx for Windows File Server file system, specify a fsxWindowsFileServerVolumeConfiguration . For tasks that use a Docker volume, specify a DockerVolumeConfiguration . For tasks that use a bind mount host volume, specify a host and optional sourcePath . For more information, see Using Data Volumes in Tasks .

          • name (string) --

            The name of the volume. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This name is referenced in the sourceVolume parameter of container definition mountPoints .

          • host (dict) --

            This parameter is specified when you use bind mount host volumes. The contents of the host parameter determine whether your bind mount host volume persists on the host container instance and where it's stored. If the host parameter is empty, then the Docker daemon assigns a host path for your data volume. However, the data isn't guaranteed to persist after the containers that are associated with it stop running.

            Windows containers can mount whole directories on the same drive as $env:ProgramData . Windows containers can't mount directories on a different drive, and mount point can't be across drives. For example, you can mount C:\my\path:C:\my\path and D:\:D:\ , but not D:\my\path:C:\my\path or D:\:C:\my\path .

            • sourcePath (string) --

              When the host parameter is used, specify a sourcePath to declare the path on the host container instance that's presented to the container. If this parameter is empty, then the Docker daemon has assigned a host path for you. If the host parameter contains a sourcePath file location, then the data volume persists at the specified location on the host container instance until you delete it manually. If the sourcePath value doesn't exist on the host container instance, the Docker daemon creates it. If the location does exist, the contents of the source path folder are exported.

              If you're using the Fargate launch type, the sourcePath parameter is not supported.

          • dockerVolumeConfiguration (dict) --

            This parameter is specified when you use Docker volumes.

            Windows containers only support the use of the local driver. To use bind mounts, specify the host parameter instead.

            Note

            Docker volumes aren't supported by tasks run on Fargate.

            • scope (string) --

              The scope for the Docker volume that determines its lifecycle. Docker volumes that are scoped to a task are automatically provisioned when the task starts and destroyed when the task stops. Docker volumes that are scoped as shared persist after the task stops.

            • autoprovision (boolean) --

              If this value is true , the Docker volume is created if it doesn't already exist.

              Note

              This field is only used if the scope is shared .

            • driver (string) --

              The Docker volume driver to use. The driver value must match the driver name provided by Docker because it is used for task placement. If the driver was installed using the Docker plugin CLI, use docker plugin ls to retrieve the driver name from your container instance. If the driver was installed using another method, use Docker plugin discovery to retrieve the driver name. For more information, see Docker plugin discovery . This parameter maps to Driver in the Create a volume section of the Docker Remote API and the xxdriver option to docker volume create .

            • driverOpts (dict) --

              A map of Docker driver-specific options passed through. This parameter maps to DriverOpts in the Create a volume section of the Docker Remote API and the xxopt option to docker volume create .

              • (string) --

                • (string) --

            • labels (dict) --

              Custom metadata to add to your Docker volume. This parameter maps to Labels in the Create a volume section of the Docker Remote API and the xxlabel option to docker volume create .

              • (string) --

                • (string) --

          • efsVolumeConfiguration (dict) --

            This parameter is specified when you use an Amazon Elastic File System file system for task storage.

            • fileSystemId (string) --

              The Amazon EFS file system ID to use.

            • rootDirectory (string) --

              The directory within the Amazon EFS file system to mount as the root directory inside the host. If this parameter is omitted, the root of the Amazon EFS volume will be used. Specifying / will have the same effect as omitting this parameter.

              Warning

              If an EFS access point is specified in the authorizationConfig , the root directory parameter must either be omitted or set to / which will enforce the path set on the EFS access point.

            • transitEncryption (string) --

              Determines whether to use encryption for Amazon EFS data in transit between the Amazon ECS host and the Amazon EFS server. Transit encryption must be enabled if Amazon EFS IAM authorization is used. If this parameter is omitted, the default value of DISABLED is used. For more information, see Encrypting data in transit in the Amazon Elastic File System User Guide .

            • transitEncryptionPort (integer) --

              The port to use when sending encrypted data between the Amazon ECS host and the Amazon EFS server. If you do not specify a transit encryption port, it will use the port selection strategy that the Amazon EFS mount helper uses. For more information, see EFS mount helper in the Amazon Elastic File System User Guide .

            • authorizationConfig (dict) --

              The authorization configuration details for the Amazon EFS file system.

              • accessPointId (string) --

                The Amazon EFS access point ID to use. If an access point is specified, the root directory value specified in the EFSVolumeConfiguration must either be omitted or set to / which will enforce the path set on the EFS access point. If an access point is used, transit encryption must be enabled in the EFSVolumeConfiguration . For more information, see Working with Amazon EFS access points in the Amazon Elastic File System User Guide .

              • iam (string) --

                Determines whether to use the Amazon ECS task IAM role defined in a task definition when mounting the Amazon EFS file system. If enabled, transit encryption must be enabled in the EFSVolumeConfiguration . If this parameter is omitted, the default value of DISABLED is used. For more information, see Using Amazon EFS access points in the Amazon Elastic Container Service Developer Guide .

          • fsxWindowsFileServerVolumeConfiguration (dict) --

            This parameter is specified when you use Amazon FSx for Windows File Server file system for task storage.

            • fileSystemId (string) --

              The Amazon FSx for Windows File Server file system ID to use.

            • rootDirectory (string) --

              The directory within the Amazon FSx for Windows File Server file system to mount as the root directory inside the host.

            • authorizationConfig (dict) --

              The authorization configuration details for the Amazon FSx for Windows File Server file system.

              • credentialsParameter (string) --

                The authorization credential option to use. The authorization credential options can be provided using either the Amazon Resource Name (ARN) of an Secrets Manager secret or SSM Parameter Store parameter. The ARN refers to the stored credentials.

              • domain (string) --

                A fully qualified domain name hosted by an Directory Service Managed Microsoft AD (Active Directory) or self-hosted AD on Amazon EC2.

      • status (string) --

        The status of the task definition.

      • requiresAttributes (list) --

        The container instance attributes required by your task. When an Amazon EC2 instance is registered to your cluster, the Amazon ECS container agent assigns some standard attributes to the instance. You can apply custom attributes. These are specified as key-value pairs using the Amazon ECS console or the PutAttributes API. These attributes are used when determining task placement for tasks hosted on Amazon EC2 instances. For more information, see Attributes in the Amazon Elastic Container Service Developer Guide .

        Note

        This parameter isn't supported for tasks run on Fargate.

        • (dict) --

          An attribute is a name-value pair that's associated with an Amazon ECS object. Use attributes to extend the Amazon ECS data model by adding custom metadata to your resources. For more information, see Attributes in the Amazon Elastic Container Service Developer Guide .

          • name (string) --

            The name of the attribute. The name must contain between 1 and 128 characters. The name may contain letters (uppercase and lowercase), numbers, hyphens (-), underscores (_), forward slashes (/), back slashes (), or periods (.).

          • value (string) --

            The value of the attribute. The value must contain between 1 and 128 characters. It can contain letters (uppercase and lowercase), numbers, hyphens (-), underscores (_), periods (.), at signs (@), forward slashes (/), back slashes (), colons (:), or spaces. The value can't start or end with a space.

          • targetType (string) --

            The type of the target to attach the attribute with. This parameter is required if you use the short form ID for a resource instead of the full ARN.

          • targetId (string) --

            The ID of the target. You can specify the short form ID for a resource or the full Amazon Resource Name (ARN).

      • placementConstraints (list) --

        An array of placement constraint objects to use for tasks.

        Note

        This parameter isn't supported for tasks run on Fargate.

        • (dict) --

          An object representing a constraint on task placement in the task definition. For more information, see Task placement constraints in the Amazon Elastic Container Service Developer Guide .

          Note

          Task placement constraints aren't supported for tasks run on Fargate.

          • type (string) --

            The type of constraint. The MemberOf constraint restricts selection to be from a group of valid candidates.

          • expression (string) --

            A cluster query language expression to apply to the constraint. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide .

      • compatibilities (list) --

        The task launch types the task definition validated against during task definition registration. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide .

        • (string) --

      • runtimePlatform (dict) --

        The operating system that your task definitions are running on. A platform family is specified only for tasks using the Fargate launch type.

        When you specify a task in a service, this value must match the runtimePlatform value of the service.

        • cpuArchitecture (string) --

          The CPU architecture.

          You can run your Linux tasks on an ARM-based platform by setting the value to ARM64 . This option is available for tasks that run on Linux Amazon EC2 instance or Linux containers on Fargate.

        • operatingSystemFamily (string) --

          The operating system.

      • requiresCompatibilities (list) --

        The task launch types the task definition was validated against. To determine which task launch types the task definition is validated for, see the TaskDefinition$compatibilities parameter.

        • (string) --

      • cpu (string) --

        The number of cpu units used by the task. If you use the EC2 launch type, this field is optional. Any value can be used. If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines your range of valid values for the memory parameter.

        The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.

        • 256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)

        • 512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)

        • 1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)

        • 2048 (2 vCPU) - Available memory values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)

        • 4096 (4 vCPU) - Available memory values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)

        • 8192 (8 vCPU) - Available memory values: 16 GB and 60 GB in 4 GB increments This option requires Linux platform 1.4.0 or later.

        • 16384 (16vCPU) - Available memory values: 32GB and 120 GB in 8 GB increments This option requires Linux platform 1.4.0 or later.

      • memory (string) --

        The amount (in MiB) of memory used by the task.

        If your tasks runs on Amazon EC2 instances, you must specify either a task-level memory value or a container-level memory value. This field is optional and any value can be used. If a task-level memory value is specified, the container-level memory value is optional. For more information regarding container-level memory and memory reservation, see ContainerDefinition .

        If your tasks runs on Fargate, this field is required. You must use one of the following values. The value you choose determines your range of valid values for the cpu parameter.

        • 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)

        • 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)

        • 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available cpu values: 1024 (1 vCPU)

        • Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values: 2048 (2 vCPU)

        • Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values: 4096 (4 vCPU)

        • Between 16 GB and 60 GB in 4 GB increments - Available cpu values: 8192 (8 vCPU) This option requires Linux platform 1.4.0 or later.

        • Between 32GB and 120 GB in 8 GB increments - Available cpu values: 16384 (16 vCPU) This option requires Linux platform 1.4.0 or later.

      • inferenceAccelerators (list) --

        The Elastic Inference accelerator that's associated with the task.

        • (dict) --

          Details on an Elastic Inference accelerator. For more information, see Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide .

          • deviceName (string) --

            The Elastic Inference accelerator device name. The deviceName must also be referenced in a container definition as a ResourceRequirement .

          • deviceType (string) --

            The Elastic Inference accelerator type to use.

      • pidMode (string) --

        The process namespace to use for the containers in the task. The valid values are host or task . If host is specified, then all containers within the tasks that specified the host PID mode on the same container instance share the same process namespace with the host Amazon EC2 instance. If task is specified, all containers within the specified task share the same process namespace. If no value is specified, the default is a private namespace. For more information, see PID settings in the Docker run reference .

        If the host PID mode is used, be aware that there is a heightened risk of undesired process namespace expose. For more information, see Docker security .

        Note

        This parameter is not supported for Windows containers or tasks run on Fargate.

      • ipcMode (string) --

        The IPC resource namespace to use for the containers in the task. The valid values are host , task , or none . If host is specified, then all containers within the tasks that specified the host IPC mode on the same container instance share the same IPC resources with the host Amazon EC2 instance. If task is specified, all containers within the specified task share the same IPC resources. If none is specified, then IPC resources within the containers of a task are private and not shared with other containers in a task or on the container instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more information, see IPC settings in the Docker run reference .

        If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace expose. For more information, see Docker security .

        If you are setting namespaced kernel parameters using systemControls for the containers in the task, the following will apply to your IPC resource namespace. For more information, see System Controls in the Amazon Elastic Container Service Developer Guide .

        • For tasks that use the host IPC mode, IPC namespace related systemControls are not supported.

        • For tasks that use the task IPC mode, IPC namespace related systemControls will apply to all containers within a task.

        Note

        This parameter is not supported for Windows containers or tasks run on Fargate.

      • proxyConfiguration (dict) --

        The configuration details for the App Mesh proxy.

        Your Amazon ECS container instances require at least version 1.26.0 of the container agent and at least version 1.26.0-1 of the ecs-init package to use a proxy configuration. If your container instances are launched from the Amazon ECS optimized AMI version 20190301 or later, they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

        • type (string) --

          The proxy type. The only supported value is APPMESH .

        • containerName (string) --

          The name of the container that will serve as the App Mesh proxy.

        • properties (list) --

          The set of network configuration parameters to provide the Container Network Interface (CNI) plugin, specified as key-value pairs.

          • IgnoredUID - (Required) The user ID (UID) of the proxy container as defined by the user parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If IgnoredGID is specified, this field can be empty.

          • IgnoredGID - (Required) The group ID (GID) of the proxy container as defined by the user parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If IgnoredUID is specified, this field can be empty.

          • AppPorts - (Required) The list of ports that the application uses. Network traffic to these ports is forwarded to the ProxyIngressPort and ProxyEgressPort .

          • ProxyIngressPort - (Required) Specifies the port that incoming traffic to the AppPorts is directed to.

          • ProxyEgressPort - (Required) Specifies the port that outgoing traffic from the AppPorts is directed to.

          • EgressIgnoredPorts - (Required) The egress traffic going to the specified ports is ignored and not redirected to the ProxyEgressPort . It can be an empty list.

          • EgressIgnoredIPs - (Required) The egress traffic going to the specified IP addresses is ignored and not redirected to the ProxyEgressPort . It can be an empty list.

          • (dict) --

            A key-value pair object.

            • name (string) --

              The name of the key-value pair. For environment variables, this is the name of the environment variable.

            • value (string) --

              The value of the key-value pair. For environment variables, this is the value of the environment variable.

      • registeredAt (datetime) --

        The Unix timestamp for the time when the task definition was registered.

      • deregisteredAt (datetime) --

        The Unix timestamp for the time when the task definition was deregistered.

      • registeredBy (string) --

        The principal that registered the task definition.

      • ephemeralStorage (dict) --

        The ephemeral storage settings to use for tasks run with the task definition.

        • sizeInGiB (integer) --

          The total amount, in GiB, of ephemeral storage to set for the task. The minimum supported value is 21 GiB and the maximum supported value is 200 GiB.

    • tags (list) --

      The metadata that's applied to the task definition to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

      The following basic restrictions apply to tags:

      • Maximum number of tags per resource - 50

      • For each resource, each tag key must be unique, and each tag key can have only one value.

      • Maximum key length - 128 Unicode characters in UTF-8

      • Maximum value length - 256 Unicode characters in UTF-8

      • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

      • Tag keys and values are case-sensitive.

      • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

      • (dict) --

        The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

        The following basic restrictions apply to tags:

        • Maximum number of tags per resource - 50

        • For each resource, each tag key must be unique, and each tag key can have only one value.

        • Maximum key length - 128 Unicode characters in UTF-8

        • Maximum value length - 256 Unicode characters in UTF-8

        • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

        • Tag keys and values are case-sensitive.

        • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

        • key (string) --

          One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

        • value (string) --

          The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

DescribeTasks (updated) Link ¶
Changes (response)
{'tasks': {'stopCode': {'ServiceSchedulerInitiated',
                        'SpotInterruption',
                        'TerminationNotice'}}}

Describes a specified task or tasks.

Currently, stopped tasks appear in the returned results for at least one hour.

See also: AWS API Documentation

Request Syntax

client.describe_tasks(
    cluster='string',
    tasks=[
        'string',
    ],
    include=[
        'TAGS',
    ]
)
type cluster

string

param cluster

The short name or full Amazon Resource Name (ARN) of the cluster that hosts the task or tasks to describe. If you do not specify a cluster, the default cluster is assumed. This parameter is required if the task or tasks you are describing were launched in any cluster other than the default cluster.

type tasks

list

param tasks

[REQUIRED]

A list of up to 100 task IDs or full ARN entries.

  • (string) --

type include

list

param include

Specifies whether you want to see the resource tags for the task. If TAGS is specified, the tags are included in the response. If this field is omitted, tags aren't included in the response.

  • (string) --

rtype

dict

returns

Response Syntax

{
    'tasks': [
        {
            'attachments': [
                {
                    'id': 'string',
                    'type': 'string',
                    'status': 'string',
                    'details': [
                        {
                            'name': 'string',
                            'value': 'string'
                        },
                    ]
                },
            ],
            'attributes': [
                {
                    'name': 'string',
                    'value': 'string',
                    'targetType': 'container-instance',
                    'targetId': 'string'
                },
            ],
            'availabilityZone': 'string',
            'capacityProviderName': 'string',
            'clusterArn': 'string',
            'connectivity': 'CONNECTED'|'DISCONNECTED',
            'connectivityAt': datetime(2015, 1, 1),
            'containerInstanceArn': 'string',
            'containers': [
                {
                    'containerArn': 'string',
                    'taskArn': 'string',
                    'name': 'string',
                    'image': 'string',
                    'imageDigest': 'string',
                    'runtimeId': 'string',
                    'lastStatus': 'string',
                    'exitCode': 123,
                    'reason': 'string',
                    'networkBindings': [
                        {
                            'bindIP': 'string',
                            'containerPort': 123,
                            'hostPort': 123,
                            'protocol': 'tcp'|'udp'
                        },
                    ],
                    'networkInterfaces': [
                        {
                            'attachmentId': 'string',
                            'privateIpv4Address': 'string',
                            'ipv6Address': 'string'
                        },
                    ],
                    'healthStatus': 'HEALTHY'|'UNHEALTHY'|'UNKNOWN',
                    'managedAgents': [
                        {
                            'lastStartedAt': datetime(2015, 1, 1),
                            'name': 'ExecuteCommandAgent',
                            'reason': 'string',
                            'lastStatus': 'string'
                        },
                    ],
                    'cpu': 'string',
                    'memory': 'string',
                    'memoryReservation': 'string',
                    'gpuIds': [
                        'string',
                    ]
                },
            ],
            'cpu': 'string',
            'createdAt': datetime(2015, 1, 1),
            'desiredStatus': 'string',
            'enableExecuteCommand': True|False,
            'executionStoppedAt': datetime(2015, 1, 1),
            'group': 'string',
            'healthStatus': 'HEALTHY'|'UNHEALTHY'|'UNKNOWN',
            'inferenceAccelerators': [
                {
                    'deviceName': 'string',
                    'deviceType': 'string'
                },
            ],
            'lastStatus': 'string',
            'launchType': 'EC2'|'FARGATE'|'EXTERNAL',
            'memory': 'string',
            'overrides': {
                'containerOverrides': [
                    {
                        'name': 'string',
                        'command': [
                            'string',
                        ],
                        'environment': [
                            {
                                'name': 'string',
                                'value': 'string'
                            },
                        ],
                        'environmentFiles': [
                            {
                                'value': 'string',
                                'type': 's3'
                            },
                        ],
                        'cpu': 123,
                        'memory': 123,
                        'memoryReservation': 123,
                        'resourceRequirements': [
                            {
                                'value': 'string',
                                'type': 'GPU'|'InferenceAccelerator'
                            },
                        ]
                    },
                ],
                'cpu': 'string',
                'inferenceAcceleratorOverrides': [
                    {
                        'deviceName': 'string',
                        'deviceType': 'string'
                    },
                ],
                'executionRoleArn': 'string',
                'memory': 'string',
                'taskRoleArn': 'string',
                'ephemeralStorage': {
                    'sizeInGiB': 123
                }
            },
            'platformVersion': 'string',
            'platformFamily': 'string',
            'pullStartedAt': datetime(2015, 1, 1),
            'pullStoppedAt': datetime(2015, 1, 1),
            'startedAt': datetime(2015, 1, 1),
            'startedBy': 'string',
            'stopCode': 'TaskFailedToStart'|'EssentialContainerExited'|'UserInitiated'|'ServiceSchedulerInitiated'|'SpotInterruption'|'TerminationNotice',
            'stoppedAt': datetime(2015, 1, 1),
            'stoppedReason': 'string',
            'stoppingAt': datetime(2015, 1, 1),
            'tags': [
                {
                    'key': 'string',
                    'value': 'string'
                },
            ],
            'taskArn': 'string',
            'taskDefinitionArn': 'string',
            'version': 123,
            'ephemeralStorage': {
                'sizeInGiB': 123
            }
        },
    ],
    'failures': [
        {
            'arn': 'string',
            'reason': 'string',
            'detail': 'string'
        },
    ]
}

Response Structure

  • (dict) --

    • tasks (list) --

      The list of tasks.

      • (dict) --

        Details on a task in a cluster.

        • attachments (list) --

          The Elastic Network Adapter that's associated with the task if the task uses the awsvpc network mode.

          • (dict) --

            An object representing a container instance or task attachment.

            • id (string) --

              The unique identifier for the attachment.

            • type (string) --

              The type of the attachment, such as ElasticNetworkInterface .

            • status (string) --

              The status of the attachment. Valid values are PRECREATED , CREATED , ATTACHING , ATTACHED , DETACHING , DETACHED , DELETED , and FAILED .

            • details (list) --

              Details of the attachment. For elastic network interfaces, this includes the network interface ID, the MAC address, the subnet ID, and the private IPv4 address.

              • (dict) --

                A key-value pair object.

                • name (string) --

                  The name of the key-value pair. For environment variables, this is the name of the environment variable.

                • value (string) --

                  The value of the key-value pair. For environment variables, this is the value of the environment variable.

        • attributes (list) --

          The attributes of the task

          • (dict) --

            An attribute is a name-value pair that's associated with an Amazon ECS object. Use attributes to extend the Amazon ECS data model by adding custom metadata to your resources. For more information, see Attributes in the Amazon Elastic Container Service Developer Guide .

            • name (string) --

              The name of the attribute. The name must contain between 1 and 128 characters. The name may contain letters (uppercase and lowercase), numbers, hyphens (-), underscores (_), forward slashes (/), back slashes (), or periods (.).

            • value (string) --

              The value of the attribute. The value must contain between 1 and 128 characters. It can contain letters (uppercase and lowercase), numbers, hyphens (-), underscores (_), periods (.), at signs (@), forward slashes (/), back slashes (), colons (:), or spaces. The value can't start or end with a space.

            • targetType (string) --

              The type of the target to attach the attribute with. This parameter is required if you use the short form ID for a resource instead of the full ARN.

            • targetId (string) --

              The ID of the target. You can specify the short form ID for a resource or the full Amazon Resource Name (ARN).

        • availabilityZone (string) --

          The Availability Zone for the task.

        • capacityProviderName (string) --

          The capacity provider that's associated with the task.

        • clusterArn (string) --

          The ARN of the cluster that hosts the task.

        • connectivity (string) --

          The connectivity status of a task.

        • connectivityAt (datetime) --

          The Unix timestamp for the time when the task last went into CONNECTED status.

        • containerInstanceArn (string) --

          The ARN of the container instances that host the task.

        • containers (list) --

          The containers that's associated with the task.

          • (dict) --

            A Docker container that's part of a task.

            • containerArn (string) --

              The Amazon Resource Name (ARN) of the container.

            • taskArn (string) --

              The ARN of the task.

            • name (string) --

              The name of the container.

            • image (string) --

              The image used for the container.

            • imageDigest (string) --

              The container image manifest digest.

              Note

              The imageDigest is only returned if the container is using an image hosted in Amazon ECR, otherwise it is omitted.

            • runtimeId (string) --

              The ID of the Docker container.

            • lastStatus (string) --

              The last known status of the container.

            • exitCode (integer) --

              The exit code returned from the container.

            • reason (string) --

              A short (255 max characters) human-readable string to provide additional details about a running or stopped container.

            • networkBindings (list) --

              The network bindings associated with the container.

              • (dict) --

                Details on the network bindings between a container and its host container instance. After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the networkBindings section of DescribeTasks API responses.

                • bindIP (string) --

                  The IP address that the container is bound to on the container instance.

                • containerPort (integer) --

                  The port number on the container that's used with the network binding.

                • hostPort (integer) --

                  The port number on the host that's used with the network binding.

                • protocol (string) --

                  The protocol used for the network binding.

            • networkInterfaces (list) --

              The network interfaces associated with the container.

              • (dict) --

                An object representing the elastic network interface for tasks that use the awsvpc network mode.

                • attachmentId (string) --

                  The attachment ID for the network interface.

                • privateIpv4Address (string) --

                  The private IPv4 address for the network interface.

                • ipv6Address (string) --

                  The private IPv6 address for the network interface.

            • healthStatus (string) --

              The health status of the container. If health checks aren't configured for this container in its task definition, then it reports the health status as UNKNOWN .

            • managedAgents (list) --

              The details of any Amazon ECS managed agents associated with the container.

              • (dict) --

                Details about the managed agent status for the container.

                • lastStartedAt (datetime) --

                  The Unix timestamp for the time when the managed agent was last started.

                • name (string) --

                  The name of the managed agent. When the execute command feature is enabled, the managed agent name is ExecuteCommandAgent .

                • reason (string) --

                  The reason for why the managed agent is in the state it is in.

                • lastStatus (string) --

                  The last known status of the managed agent.

            • cpu (string) --

              The number of CPU units set for the container. The value is 0 if no value was specified in the container definition when the task definition was registered.

            • memory (string) --

              The hard limit (in MiB) of memory set for the container.

            • memoryReservation (string) --

              The soft limit (in MiB) of memory set for the container.

            • gpuIds (list) --

              The IDs of each GPU assigned to the container.

              • (string) --

        • cpu (string) --

          The number of CPU units used by the task as expressed in a task definition. It can be expressed as an integer using CPU units (for example, 1024 ). It can also be expressed as a string using vCPUs (for example, 1 vCPU or 1 vcpu ). String values are converted to an integer that indicates the CPU units when the task definition is registered.

          If you use the EC2 launch type, this field is optional. Supported values are between 128 CPU units (0.125 vCPUs) and 10240 CPU units (10 vCPUs).

          If you use the Fargate launch type, this field is required. You must use one of the following values. These values determine the range of supported values for the memory parameter:

          The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.

          • 256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)

          • 512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)

          • 1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)

          • 2048 (2 vCPU) - Available memory values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)

          • 4096 (4 vCPU) - Available memory values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)

          • 8192 (8 vCPU) - Available memory values: 16 GB and 60 GB in 4 GB increments This option requires Linux platform 1.4.0 or later.

          • 16384 (16vCPU) - Available memory values: 32GB and 120 GB in 8 GB increments This option requires Linux platform 1.4.0 or later.

        • createdAt (datetime) --

          The Unix timestamp for the time when the task was created. More specifically, it's for the time when the task entered the PENDING state.

        • desiredStatus (string) --

          The desired status of the task. For more information, see Task Lifecycle .

        • enableExecuteCommand (boolean) --

          Determines whether execute command functionality is enabled for this task. If true , execute command functionality is enabled on all the containers in the task.

        • executionStoppedAt (datetime) --

          The Unix timestamp for the time when the task execution stopped.

        • group (string) --

          The name of the task group that's associated with the task.

        • healthStatus (string) --

          The health status for the task. It's determined by the health of the essential containers in the task. If all essential containers in the task are reporting as HEALTHY , the task status also reports as HEALTHY . If any essential containers in the task are reporting as UNHEALTHY or UNKNOWN , the task status also reports as UNHEALTHY or UNKNOWN .

          Note

          The Amazon ECS container agent doesn't monitor or report on Docker health checks that are embedded in a container image and not specified in the container definition. For example, this includes those specified in a parent image or from the image's Dockerfile. Health check parameters that are specified in a container definition override any Docker health checks that are found in the container image.

        • inferenceAccelerators (list) --

          The Elastic Inference accelerator that's associated with the task.

          • (dict) --

            Details on an Elastic Inference accelerator. For more information, see Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide .

            • deviceName (string) --

              The Elastic Inference accelerator device name. The deviceName must also be referenced in a container definition as a ResourceRequirement .

            • deviceType (string) --

              The Elastic Inference accelerator type to use.

        • lastStatus (string) --

          The last known status for the task. For more information, see Task Lifecycle .

        • launchType (string) --

          The infrastructure where your task runs on. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide .

        • memory (string) --

          The amount of memory (in MiB) that the task uses as expressed in a task definition. It can be expressed as an integer using MiB (for example, 1024 ). If it's expressed as a string using GB (for example, 1GB or 1 GB ), it's converted to an integer indicating the MiB when the task definition is registered.

          If you use the EC2 launch type, this field is optional.

          If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines the range of supported values for the cpu parameter.

          • 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)

          • 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)

          • 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available cpu values: 1024 (1 vCPU)

          • Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values: 2048 (2 vCPU)

          • Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values: 4096 (4 vCPU)

          • Between 16 GB and 60 GB in 4 GB increments - Available cpu values: 8192 (8 vCPU) This option requires Linux platform 1.4.0 or later.

          • Between 32GB and 120 GB in 8 GB increments - Available cpu values: 16384 (16 vCPU) This option requires Linux platform 1.4.0 or later.

        • overrides (dict) --

          One or more container overrides.

          • containerOverrides (list) --

            One or more container overrides that are sent to a task.

            • (dict) --

              The overrides that are sent to a container. An empty container override can be passed in. An example of an empty container override is {"containerOverrides": [ ] } . If a non-empty container override is specified, the name parameter must be included.

              • name (string) --

                The name of the container that receives the override. This parameter is required if any override is specified.

              • command (list) --

                The command to send to the container that overrides the default command from the Docker image or the task definition. You must also specify a container name.

                • (string) --

              • environment (list) --

                The environment variables to send to the container. You can add new environment variables, which are added to the container at launch, or you can override the existing environment variables from the Docker image or the task definition. You must also specify a container name.

                • (dict) --

                  A key-value pair object.

                  • name (string) --

                    The name of the key-value pair. For environment variables, this is the name of the environment variable.

                  • value (string) --

                    The value of the key-value pair. For environment variables, this is the value of the environment variable.

              • environmentFiles (list) --

                A list of files containing the environment variables to pass to a container, instead of the value from the container definition.

                • (dict) --

                  A list of files containing the environment variables to pass to a container. You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file should contain an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

                  If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying environment variables in the Amazon Elastic Container Service Developer Guide .

                  This parameter is only supported for tasks hosted on Fargate using the following platform versions:

                  • Linux platform version 1.4.0 or later.

                  • Windows platform version 1.0.0 or later.

                  • value (string) --

                    The Amazon Resource Name (ARN) of the Amazon S3 object containing the environment variable file.

                  • type (string) --

                    The file type to use. The only supported value is s3 .

              • cpu (integer) --

                The number of cpu units reserved for the container, instead of the default value from the task definition. You must also specify a container name.

              • memory (integer) --

                The hard limit (in MiB) of memory to present to the container, instead of the default value from the task definition. If your container attempts to exceed the memory specified here, the container is killed. You must also specify a container name.

              • memoryReservation (integer) --

                The soft limit (in MiB) of memory to reserve for the container, instead of the default value from the task definition. You must also specify a container name.

              • resourceRequirements (list) --

                The type and amount of a resource to assign to a container, instead of the default value from the task definition. The only supported resource is a GPU.

                • (dict) --

                  The type and amount of a resource to assign to a container. The supported resource types are GPUs and Elastic Inference accelerators. For more information, see Working with GPUs on Amazon ECS or Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide

                  • value (string) --

                    The value for the specified resource type.

                    If the GPU type is used, the value is the number of physical GPUs the Amazon ECS container agent reserves for the container. The number of GPUs that's reserved for all containers in a task can't exceed the number of available GPUs on the container instance that the task is launched on.

                    If the InferenceAccelerator type is used, the value matches the deviceName for an InferenceAccelerator specified in a task definition.

                  • type (string) --

                    The type of resource to assign to a container. The supported values are GPU or InferenceAccelerator .

          • cpu (string) --

            The CPU override for the task.

          • inferenceAcceleratorOverrides (list) --

            The Elastic Inference accelerator override for the task.

            • (dict) --

              Details on an Elastic Inference accelerator task override. This parameter is used to override the Elastic Inference accelerator specified in the task definition. For more information, see Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide .

              • deviceName (string) --

                The Elastic Inference accelerator device name to override for the task. This parameter must match a deviceName specified in the task definition.

              • deviceType (string) --

                The Elastic Inference accelerator type to use.

          • executionRoleArn (string) --

            The Amazon Resource Name (ARN) of the task execution IAM role override for the task. For more information, see Amazon ECS task execution IAM role in the Amazon Elastic Container Service Developer Guide .

          • memory (string) --

            The memory override for the task.

          • taskRoleArn (string) --

            The Amazon Resource Name (ARN) of the IAM role that containers in this task can assume. All containers in this task are granted the permissions that are specified in this role. For more information, see IAM Role for Tasks in the Amazon Elastic Container Service Developer Guide .

          • ephemeralStorage (dict) --

            The ephemeral storage setting override for the task.

            Note

            This parameter is only supported for tasks hosted on Fargate that use the following platform versions:

            • Linux platform version 1.4.0 or later.

            • Windows platform version 1.0.0 or later.

            • sizeInGiB (integer) --

              The total amount, in GiB, of ephemeral storage to set for the task. The minimum supported value is 21 GiB and the maximum supported value is 200 GiB.

        • platformVersion (string) --

          The platform version where your task runs on. A platform version is only specified for tasks that use the Fargate launch type. If you didn't specify one, the LATEST platform version is used. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide .

        • platformFamily (string) --

          The operating system that your tasks are running on. A platform family is specified only for tasks that use the Fargate launch type.

          All tasks that run as part of this service must use the same platformFamily value as the service (for example, LINUX. ).

        • pullStartedAt (datetime) --

          The Unix timestamp for the time when the container image pull began.

        • pullStoppedAt (datetime) --

          The Unix timestamp for the time when the container image pull completed.

        • startedAt (datetime) --

          The Unix timestamp for the time when the task started. More specifically, it's for the time when the task transitioned from the PENDING state to the RUNNING state.

        • startedBy (string) --

          The tag specified when a task is started. If an Amazon ECS service started the task, the startedBy parameter contains the deployment ID of that service.

        • stopCode (string) --

          The stop code indicating why a task was stopped. The stoppedReason might contain additional details.

          The following are valid values:

          • TaskFailedToStart

          • EssentialContainerExited

          • UserInitiated

          • TerminationNotice

          • ServiceSchedulerInitiated

          • SpotInterruption

        • stoppedAt (datetime) --

          The Unix timestamp for the time when the task was stopped. More specifically, it's for the time when the task transitioned from the RUNNING state to the STOPPED state.

        • stoppedReason (string) --

          The reason that the task was stopped.

        • stoppingAt (datetime) --

          The Unix timestamp for the time when the task stops. More specifically, it's for the time when the task transitions from the RUNNING state to STOPPED .

        • tags (list) --

          The metadata that you apply to the task to help you categorize and organize the task. Each tag consists of a key and an optional value. You define both the key and value.

          The following basic restrictions apply to tags:

          • Maximum number of tags per resource - 50

          • For each resource, each tag key must be unique, and each tag key can have only one value.

          • Maximum key length - 128 Unicode characters in UTF-8

          • Maximum value length - 256 Unicode characters in UTF-8

          • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

          • Tag keys and values are case-sensitive.

          • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

          • (dict) --

            The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

            The following basic restrictions apply to tags:

            • Maximum number of tags per resource - 50

            • For each resource, each tag key must be unique, and each tag key can have only one value.

            • Maximum key length - 128 Unicode characters in UTF-8

            • Maximum value length - 256 Unicode characters in UTF-8

            • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

            • Tag keys and values are case-sensitive.

            • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

            • key (string) --

              One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

            • value (string) --

              The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

        • taskArn (string) --

          The Amazon Resource Name (ARN) of the task.

        • taskDefinitionArn (string) --

          The ARN of the task definition that creates the task.

        • version (integer) --

          The version counter for the task. Every time a task experiences a change that starts a CloudWatch event, the version counter is incremented. If you replicate your Amazon ECS task state with CloudWatch Events, you can compare the version of a task reported by the Amazon ECS API actions with the version reported in CloudWatch Events for the task (inside the detail object) to verify that the version in your event stream is current.

        • ephemeralStorage (dict) --

          The ephemeral storage settings for the task.

          • sizeInGiB (integer) --

            The total amount, in GiB, of ephemeral storage to set for the task. The minimum supported value is 21 GiB and the maximum supported value is 200 GiB.

    • failures (list) --

      Any failures associated with the call.

      • (dict) --

        A failed resource. For a list of common causes, see API failure reasons in the Amazon Elastic Container Service Developer Guide .

        • arn (string) --

          The Amazon Resource Name (ARN) of the failed resource.

        • reason (string) --

          The reason for the failure.

        • detail (string) --

          The details of the failure.

DiscoverPollEndpoint (updated) Link ¶
Changes (response)
{'serviceConnectEndpoint': 'string'}

Note

This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.

Returns an endpoint for the Amazon ECS agent to poll for updates.

See also: AWS API Documentation

Request Syntax

client.discover_poll_endpoint(
    containerInstance='string',
    cluster='string'
)
type containerInstance

string

param containerInstance

The container instance ID or full ARN of the container instance. For more information about the ARN format, see Amazon Resource Name (ARN) in the Amazon ECS Developer Guide .

type cluster

string

param cluster

The short name or full Amazon Resource Name (ARN) of the cluster that the container instance belongs to.

rtype

dict

returns

Response Syntax

{
    'endpoint': 'string',
    'telemetryEndpoint': 'string',
    'serviceConnectEndpoint': 'string'
}

Response Structure

  • (dict) --

    • endpoint (string) --

      The endpoint for the Amazon ECS agent to poll.

    • telemetryEndpoint (string) --

      The telemetry endpoint for the Amazon ECS agent.

    • serviceConnectEndpoint (string) --

      The endpoint for the Amazon ECS agent to poll for Service Connect configuration. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

PutClusterCapacityProviders (updated) Link ¶
Changes (response)
{'cluster': {'serviceConnectDefaults': {'namespace': 'string'}}}

Modifies the available capacity providers and the default capacity provider strategy for a cluster.

You must specify both the available capacity providers and a default capacity provider strategy for the cluster. If the specified cluster has existing capacity providers associated with it, you must specify all existing capacity providers in addition to any new ones you want to add. Any existing capacity providers that are associated with a cluster that are omitted from a PutClusterCapacityProviders API call will be disassociated with the cluster. You can only disassociate an existing capacity provider from a cluster if it's not being used by any existing tasks.

When creating a service or running a task on a cluster, if no capacity provider or launch type is specified, then the cluster's default capacity provider strategy is used. We recommend that you define a default capacity provider strategy for your cluster. However, you must specify an empty array ([] ) to bypass defining a default strategy.

See also: AWS API Documentation

Request Syntax

client.put_cluster_capacity_providers(
    cluster='string',
    capacityProviders=[
        'string',
    ],
    defaultCapacityProviderStrategy=[
        {
            'capacityProvider': 'string',
            'weight': 123,
            'base': 123
        },
    ]
)
type cluster

string

param cluster

[REQUIRED]

The short name or full Amazon Resource Name (ARN) of the cluster to modify the capacity provider settings for. If you don't specify a cluster, the default cluster is assumed.

type capacityProviders

list

param capacityProviders

[REQUIRED]

The name of one or more capacity providers to associate with the cluster.

If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New capacity providers can be created with the CreateCapacityProvider API operation.

To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used.

  • (string) --

type defaultCapacityProviderStrategy

list

param defaultCapacityProviderStrategy

[REQUIRED]

The capacity provider strategy to use by default for the cluster.

When creating a service or running a task on a cluster, if no capacity provider or launch type is specified then the default capacity provider strategy for the cluster is used.

A capacity provider strategy consists of one or more capacity providers along with the base and weight to assign to them. A capacity provider must be associated with the cluster to be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster. Only capacity providers with an ACTIVE or UPDATING status can be used.

If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New capacity providers can be created with the CreateCapacityProvider API operation.

To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used.

  • (dict) --

    The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

    Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

    If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

    To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

    A capacity provider strategy may contain a maximum of 6 capacity providers.

    • capacityProvider (string) -- [REQUIRED]

      The short name of the capacity provider.

    • weight (integer) --

      The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

      If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

      An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

    • base (integer) --

      The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

rtype

dict

returns

Response Syntax

{
    'cluster': {
        'clusterArn': 'string',
        'clusterName': 'string',
        'configuration': {
            'executeCommandConfiguration': {
                'kmsKeyId': 'string',
                'logging': 'NONE'|'DEFAULT'|'OVERRIDE',
                'logConfiguration': {
                    'cloudWatchLogGroupName': 'string',
                    'cloudWatchEncryptionEnabled': True|False,
                    's3BucketName': 'string',
                    's3EncryptionEnabled': True|False,
                    's3KeyPrefix': 'string'
                }
            }
        },
        'status': 'string',
        'registeredContainerInstancesCount': 123,
        'runningTasksCount': 123,
        'pendingTasksCount': 123,
        'activeServicesCount': 123,
        'statistics': [
            {
                'name': 'string',
                'value': 'string'
            },
        ],
        'tags': [
            {
                'key': 'string',
                'value': 'string'
            },
        ],
        'settings': [
            {
                'name': 'containerInsights',
                'value': 'string'
            },
        ],
        'capacityProviders': [
            'string',
        ],
        'defaultCapacityProviderStrategy': [
            {
                'capacityProvider': 'string',
                'weight': 123,
                'base': 123
            },
        ],
        'attachments': [
            {
                'id': 'string',
                'type': 'string',
                'status': 'string',
                'details': [
                    {
                        'name': 'string',
                        'value': 'string'
                    },
                ]
            },
        ],
        'attachmentsStatus': 'string',
        'serviceConnectDefaults': {
            'namespace': 'string'
        }
    }
}

Response Structure

  • (dict) --

    • cluster (dict) --

      Details about the cluster.

      • clusterArn (string) --

        The 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 .

      • clusterName (string) --

        A user-generated string that you use to identify your cluster.

      • configuration (dict) --

        The execute command configuration for the cluster.

        • executeCommandConfiguration (dict) --

          The details of the execute command configuration.

          • kmsKeyId (string) --

            Specify an Key Management Service key ID to encrypt the data between the local client and the container.

          • logging (string) --

            The log setting to use for redirecting logs for your execute command results. The following log settings are available.

            • NONE : The execute command session is not logged.

            • DEFAULT : The awslogs configuration in the task definition is used. If no logging parameter is specified, it defaults to this value. If no awslogs log driver is configured in the task definition, the output won't be logged.

            • OVERRIDE : Specify the logging details as a part of logConfiguration . If the OVERRIDE logging option is specified, the logConfiguration is required.

          • logConfiguration (dict) --

            The log configuration for the results of the execute command actions. The logs can be sent to CloudWatch Logs or an Amazon S3 bucket. When logging=OVERRIDE is specified, a logConfiguration must be provided.

            • cloudWatchLogGroupName (string) --

              The name of the CloudWatch log group to send logs to.

              Note

              The CloudWatch log group must already be created.

            • cloudWatchEncryptionEnabled (boolean) --

              Determines whether to use encryption on the CloudWatch logs. If not specified, encryption will be disabled.

            • s3BucketName (string) --

              The name of the S3 bucket to send logs to.

              Note

              The S3 bucket must already be created.

            • s3EncryptionEnabled (boolean) --

              Determines whether to use encryption on the S3 logs. If not specified, encryption is not used.

            • s3KeyPrefix (string) --

              An optional folder in the S3 bucket to place logs in.

      • status (string) --

        The 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.

      • registeredContainerInstancesCount (integer) --

        The number of container instances registered into the cluster. This includes container instances in both ACTIVE and DRAINING status.

      • runningTasksCount (integer) --

        The number of tasks in the cluster that are in the RUNNING state.

      • pendingTasksCount (integer) --

        The number of tasks in the cluster that are in the PENDING state.

      • activeServicesCount (integer) --

        The number of services that are running on the cluster in an ACTIVE state. You can view these services with ListServices .

      • statistics (list) --

        Additional information about your clusters that are separated by launch type. They include the following:

        • runningEC2TasksCount

        • RunningFargateTasksCount

        • pendingEC2TasksCount

        • pendingFargateTasksCount

        • activeEC2ServiceCount

        • activeFargateServiceCount

        • drainingEC2ServiceCount

        • drainingFargateServiceCount

        • (dict) --

          A key-value pair object.

          • name (string) --

            The name of the key-value pair. For environment variables, this is the name of the environment variable.

          • value (string) --

            The value of the key-value pair. For environment variables, this is the value of the environment variable.

      • tags (list) --

        The metadata that you apply to the cluster to help you categorize and organize them. Each tag consists of a key and an optional value. You define both.

        The following basic restrictions apply to tags:

        • Maximum number of tags per resource - 50

        • For each resource, each tag key must be unique, and each tag key can have only one value.

        • Maximum key length - 128 Unicode characters in UTF-8

        • Maximum value length - 256 Unicode characters in UTF-8

        • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

        • Tag keys and values are case-sensitive.

        • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

        • (dict) --

          The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

          The following basic restrictions apply to tags:

          • Maximum number of tags per resource - 50

          • For each resource, each tag key must be unique, and each tag key can have only one value.

          • Maximum key length - 128 Unicode characters in UTF-8

          • Maximum value length - 256 Unicode characters in UTF-8

          • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

          • Tag keys and values are case-sensitive.

          • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

          • key (string) --

            One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

          • value (string) --

            The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

      • settings (list) --

        The settings for the cluster. This parameter indicates whether CloudWatch Container Insights is enabled or disabled for a cluster.

        • (dict) --

          The settings to use when creating a cluster. This parameter is used to turn on CloudWatch Container Insights for a cluster.

          • name (string) --

            The name of the cluster setting. The only supported value is containerInsights .

          • value (string) --

            The value to set for the cluster setting. The supported values are enabled and disabled . If enabled is specified, CloudWatch Container Insights will be enabled for the cluster, otherwise it will be disabled unless the containerInsights account setting is enabled. If a cluster value is specified, it will override the containerInsights value set with PutAccountSetting or PutAccountSettingDefault .

      • capacityProviders (list) --

        The capacity providers associated with the cluster.

        • (string) --

      • defaultCapacityProviderStrategy (list) --

        The 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.

        • (dict) --

          The details of a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API.

          Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster.

          If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation.

          To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.

          A capacity provider strategy may contain a maximum of 6 capacity providers.

          • capacityProvider (string) --

            The short name of the capacity provider.

          • weight (integer) --

            The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The weight value is taken into consideration after the base value, if defined, is satisfied.

            If no weight value is specified, the default value of 0 is used. When multiple capacity providers are specified within a capacity provider strategy, at least one of the capacity providers must have a weight value greater than zero and any capacity providers with a weight of 0 can't be used to place tasks. If you specify multiple capacity providers in a strategy that all have a weight of 0 , any RunTask or CreateService actions using the capacity provider strategy will fail.

            An example scenario for using weights is defining a strategy that contains two capacity providers and both have a weight of 1 , then when the base is satisfied, the tasks will be split evenly across the two capacity providers. Using that same logic, if you specify a weight of 1 for capacityProviderA and a weight of 4 for capacityProviderB , then for every one task that's run using capacityProviderA , four tasks would use capacityProviderB .

          • base (integer) --

            The base value designates how many tasks, at a minimum, to run on the specified capacity provider. Only one capacity provider in a capacity provider strategy can have a base defined. If no value is specified, the default value of 0 is used.

      • attachments (list) --

        The resources attached to a cluster. When using a capacity provider with a cluster, the capacity provider and associated resources are returned as cluster attachments.

        • (dict) --

          An object representing a container instance or task attachment.

          • id (string) --

            The unique identifier for the attachment.

          • type (string) --

            The type of the attachment, such as ElasticNetworkInterface .

          • status (string) --

            The status of the attachment. Valid values are PRECREATED , CREATED , ATTACHING , ATTACHED , DETACHING , DETACHED , DELETED , and FAILED .

          • details (list) --

            Details of the attachment. For elastic network interfaces, this includes the network interface ID, the MAC address, the subnet ID, and the private IPv4 address.

            • (dict) --

              A key-value pair object.

              • name (string) --

                The name of the key-value pair. For environment variables, this is the name of the environment variable.

              • value (string) --

                The value of the key-value pair. For environment variables, this is the value of the environment variable.

      • attachmentsStatus (string) --

        The 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.

      • serviceConnectDefaults (dict) --

        Use 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 .

        • namespace (string) --

          The namespace name or full Amazon Resource Name (ARN) of the Cloud Map namespace. When you create a service and don't specify a Service Connect configuration, this namespace is used.

RegisterTaskDefinition (updated) Link ¶
Changes (request, response)
Request
{'containerDefinitions': {'portMappings': {'appProtocol': 'http | http2 | grpc',
                                           'name': 'string'}}}
Response
{'taskDefinition': {'containerDefinitions': {'portMappings': {'appProtocol': 'http '
                                                                             '| '
                                                                             'http2 '
                                                                             '| '
                                                                             'grpc',
                                                              'name': 'string'}}}}

Registers a new task definition from the supplied family and containerDefinitions . Optionally, you can add data volumes to your containers with the volumes parameter. For more information about task definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide .

You can specify an IAM role for your task with the taskRoleArn parameter. When you specify an IAM role for a task, its containers can then use the latest versions of the CLI or SDKs to make API requests to the Amazon Web Services services that are specified in the IAM policy that's associated with the role. For more information, see IAM Roles for Tasks in the Amazon Elastic Container Service Developer Guide .

You can specify a Docker networking mode for the containers in your task definition with the networkMode parameter. The available network modes correspond to those described in Network settings in the Docker run reference. If you specify the awsvpc network mode, the task is allocated an elastic network interface, and you must specify a NetworkConfiguration when you create a service or run a task with the task definition. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide .

See also: AWS API Documentation

Request Syntax

client.register_task_definition(
    family='string',
    taskRoleArn='string',
    executionRoleArn='string',
    networkMode='bridge'|'host'|'awsvpc'|'none',
    containerDefinitions=[
        {
            'name': 'string',
            'image': 'string',
            'repositoryCredentials': {
                'credentialsParameter': 'string'
            },
            'cpu': 123,
            'memory': 123,
            'memoryReservation': 123,
            'links': [
                'string',
            ],
            'portMappings': [
                {
                    'containerPort': 123,
                    'hostPort': 123,
                    'protocol': 'tcp'|'udp',
                    'name': 'string',
                    'appProtocol': 'http'|'http2'|'grpc'
                },
            ],
            'essential': True|False,
            'entryPoint': [
                'string',
            ],
            'command': [
                'string',
            ],
            'environment': [
                {
                    'name': 'string',
                    'value': 'string'
                },
            ],
            'environmentFiles': [
                {
                    'value': 'string',
                    'type': 's3'
                },
            ],
            'mountPoints': [
                {
                    'sourceVolume': 'string',
                    'containerPath': 'string',
                    'readOnly': True|False
                },
            ],
            'volumesFrom': [
                {
                    'sourceContainer': 'string',
                    'readOnly': True|False
                },
            ],
            'linuxParameters': {
                'capabilities': {
                    'add': [
                        'string',
                    ],
                    'drop': [
                        'string',
                    ]
                },
                'devices': [
                    {
                        'hostPath': 'string',
                        'containerPath': 'string',
                        'permissions': [
                            'read'|'write'|'mknod',
                        ]
                    },
                ],
                'initProcessEnabled': True|False,
                'sharedMemorySize': 123,
                'tmpfs': [
                    {
                        'containerPath': 'string',
                        'size': 123,
                        'mountOptions': [
                            'string',
                        ]
                    },
                ],
                'maxSwap': 123,
                'swappiness': 123
            },
            'secrets': [
                {
                    'name': 'string',
                    'valueFrom': 'string'
                },
            ],
            'dependsOn': [
                {
                    'containerName': 'string',
                    'condition': 'START'|'COMPLETE'|'SUCCESS'|'HEALTHY'
                },
            ],
            'startTimeout': 123,
            'stopTimeout': 123,
            'hostname': 'string',
            'user': 'string',
            'workingDirectory': 'string',
            'disableNetworking': True|False,
            'privileged': True|False,
            'readonlyRootFilesystem': True|False,
            'dnsServers': [
                'string',
            ],
            'dnsSearchDomains': [
                'string',
            ],
            'extraHosts': [
                {
                    'hostname': 'string',
                    'ipAddress': 'string'
                },
            ],
            'dockerSecurityOptions': [
                'string',
            ],
            'interactive': True|False,
            'pseudoTerminal': True|False,
            'dockerLabels': {
                'string': 'string'
            },
            'ulimits': [
                {
                    'name': 'core'|'cpu'|'data'|'fsize'|'locks'|'memlock'|'msgqueue'|'nice'|'nofile'|'nproc'|'rss'|'rtprio'|'rttime'|'sigpending'|'stack',
                    'softLimit': 123,
                    'hardLimit': 123
                },
            ],
            'logConfiguration': {
                'logDriver': 'json-file'|'syslog'|'journald'|'gelf'|'fluentd'|'awslogs'|'splunk'|'awsfirelens',
                'options': {
                    'string': 'string'
                },
                'secretOptions': [
                    {
                        'name': 'string',
                        'valueFrom': 'string'
                    },
                ]
            },
            'healthCheck': {
                'command': [
                    'string',
                ],
                'interval': 123,
                'timeout': 123,
                'retries': 123,
                'startPeriod': 123
            },
            'systemControls': [
                {
                    'namespace': 'string',
                    'value': 'string'
                },
            ],
            'resourceRequirements': [
                {
                    'value': 'string',
                    'type': 'GPU'|'InferenceAccelerator'
                },
            ],
            'firelensConfiguration': {
                'type': 'fluentd'|'fluentbit',
                'options': {
                    'string': 'string'
                }
            }
        },
    ],
    volumes=[
        {
            'name': 'string',
            'host': {
                'sourcePath': 'string'
            },
            'dockerVolumeConfiguration': {
                'scope': 'task'|'shared',
                'autoprovision': True|False,
                'driver': 'string',
                'driverOpts': {
                    'string': 'string'
                },
                'labels': {
                    'string': 'string'
                }
            },
            'efsVolumeConfiguration': {
                'fileSystemId': 'string',
                'rootDirectory': 'string',
                'transitEncryption': 'ENABLED'|'DISABLED',
                'transitEncryptionPort': 123,
                'authorizationConfig': {
                    'accessPointId': 'string',
                    'iam': 'ENABLED'|'DISABLED'
                }
            },
            'fsxWindowsFileServerVolumeConfiguration': {
                'fileSystemId': 'string',
                'rootDirectory': 'string',
                'authorizationConfig': {
                    'credentialsParameter': 'string',
                    'domain': 'string'
                }
            }
        },
    ],
    placementConstraints=[
        {
            'type': 'memberOf',
            'expression': 'string'
        },
    ],
    requiresCompatibilities=[
        'EC2'|'FARGATE'|'EXTERNAL',
    ],
    cpu='string',
    memory='string',
    tags=[
        {
            'key': 'string',
            'value': 'string'
        },
    ],
    pidMode='host'|'task',
    ipcMode='host'|'task'|'none',
    proxyConfiguration={
        'type': 'APPMESH',
        'containerName': 'string',
        'properties': [
            {
                'name': 'string',
                'value': 'string'
            },
        ]
    },
    inferenceAccelerators=[
        {
            'deviceName': 'string',
            'deviceType': 'string'
        },
    ],
    ephemeralStorage={
        'sizeInGiB': 123
    },
    runtimePlatform={
        'cpuArchitecture': 'X86_64'|'ARM64',
        'operatingSystemFamily': 'WINDOWS_SERVER_2019_FULL'|'WINDOWS_SERVER_2019_CORE'|'WINDOWS_SERVER_2016_FULL'|'WINDOWS_SERVER_2004_CORE'|'WINDOWS_SERVER_2022_CORE'|'WINDOWS_SERVER_2022_FULL'|'WINDOWS_SERVER_20H2_CORE'|'LINUX'
    }
)
type family

string

param family

[REQUIRED]

You must specify a family for a task definition. You can use it track multiple versions of the same task definition. The family is used as a name for your task definition. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed.

type taskRoleArn

string

param taskRoleArn

The short name or full Amazon Resource Name (ARN) of the IAM role that containers in this task can assume. All containers in this task are granted the permissions that are specified in this role. For more information, see IAM Roles for Tasks in the Amazon Elastic Container Service Developer Guide .

type executionRoleArn

string

param executionRoleArn

The Amazon Resource Name (ARN) of the task execution role that grants the Amazon ECS container agent permission to make Amazon Web Services API calls on your behalf. The task execution IAM role is required depending on the requirements of your task. For more information, see Amazon ECS task execution IAM role in the Amazon Elastic Container Service Developer Guide .

type networkMode

string

param networkMode

The Docker networking mode to use for the containers in the task. The valid values are none , bridge , awsvpc , and host . If no network mode is specified, the default is bridge .

For Amazon ECS tasks on Fargate, the awsvpc network mode is required. For Amazon ECS tasks on Amazon EC2 Linux instances, any network mode can be used. For Amazon ECS tasks on Amazon EC2 Windows instances, <default> or awsvpc can be used. If the network mode is set to none , you cannot specify port mappings in your container definitions, and the tasks containers do not have external connectivity. The host and awsvpc network modes offer the highest networking performance for containers because they use the EC2 network stack instead of the virtualized network stack provided by the bridge mode.

With the host and awsvpc network modes, exposed container ports are mapped directly to the corresponding host port (for the host network mode) or the attached elastic network interface port (for the awsvpc network mode), so you cannot take advantage of dynamic host port mappings.

Warning

When using the host network mode, you should not run containers using the root user (UID 0). It is considered best practice to use a non-root user.

If the network mode is awsvpc , the task is allocated an elastic network interface, and you must specify a NetworkConfiguration value when you create a service or run a task with the task definition. For more information, see Task Networking in the Amazon Elastic Container Service Developer Guide .

If the network mode is host , you cannot run multiple instantiations of the same task on a single container instance when port mappings are used.

For more information, see Network settings in the Docker run reference .

type containerDefinitions

list

param containerDefinitions

[REQUIRED]

A list of container definitions in JSON format that describe the different containers that make up your task.

  • (dict) --

    Container definitions are used in task definitions to describe the different containers that are launched as part of a task.

    • name (string) --

      The name of a container. If you're linking multiple containers together in a task definition, the name of one container can be entered in the links of another container to connect the containers. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This parameter maps to name in the Create a container section of the Docker Remote API and the --name option to docker run .

    • image (string) --

      The image used to start a container. This string is passed directly to the Docker daemon. By default, images in the Docker Hub registry are available. Other repositories are specified with either `` repository-url /image :tag `` or `` repository-url /image @*digest* `` . Up to 255 letters (uppercase and lowercase), numbers, hyphens, underscores, colons, periods, forward slashes, and number signs are allowed. This parameter maps to Image in the Create a container section of the Docker Remote API and the IMAGE parameter of docker run .

      • When a new task starts, the Amazon ECS container agent pulls the latest version of the specified image and tag for the container to use. However, subsequent updates to a repository image aren't propagated to already running tasks.

      • Images in Amazon ECR repositories can be specified by either using the full registry/repository:tag or registry/repository@digest . For example, 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>:latest or 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>@sha256:94afd1f2e64d908bc90dbca0035a5b567EXAMPLE .

      • Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo ).

      • Images in other repositories on Docker Hub are qualified with an organization name (for example, amazon/amazon-ecs-agent ).

      • Images in other online repositories are qualified further by a domain name (for example, quay.io/assemblyline/ubuntu ).

    • repositoryCredentials (dict) --

      The private repository authentication credentials to use.

      • credentialsParameter (string) -- [REQUIRED]

        The Amazon Resource Name (ARN) of the secret containing the private repository credentials.

        Note

        When you use the Amazon ECS API, CLI, or Amazon Web Services SDK, if the secret exists in the same Region as the task that you're launching then you can use either the full ARN or the name of the secret. When you use the Amazon Web Services Management Console, you must specify the full ARN of the secret.

    • cpu (integer) --

      The number of cpu units reserved for the container. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run .

      This field is optional for tasks using the Fargate launch type, and the only requirement is that the total amount of CPU reserved for all containers within a task be lower than the task-level cpu value.

      Note

      You can determine the number of CPU units that are available per EC2 instance type by multiplying the vCPUs listed for that instance type on the Amazon EC2 Instances detail page by 1,024.

      Linux containers share unallocated CPU units with other containers on the container instance with the same ratio as their allocated amount. For example, if you run a single-container task on a single-core instance type with 512 CPU units specified for that container, and that's the only task running on the container instance, that container could use the full 1,024 CPU unit share at any given time. However, if you launched another copy of the same task on that container instance, each task is guaranteed a minimum of 512 CPU units when needed. Moreover, each container could float to higher CPU usage if the other container was not using it. If both tasks were 100% active all of the time, they would be limited to 512 CPU units.

      On Linux container instances, the Docker daemon on the container instance uses the CPU value to calculate the relative CPU share ratios for running containers. For more information, see CPU share constraint in the Docker documentation. The minimum valid CPU share value that the Linux kernel allows is 2. However, the CPU parameter isn't required, and you can use CPU values below 2 in your container definitions. For CPU values below 2 (including null), the behavior varies based on your Amazon ECS container agent version:

      • Agent versions less than or equal to 1.1.0: Null and zero CPU values are passed to Docker as 0, which Docker then converts to 1,024 CPU shares. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares.

      • Agent versions greater than or equal to 1.2.0: Null, zero, and CPU values of 1 are passed to Docker as 2.

      On Windows container instances, the CPU limit is enforced as an absolute limit, or a quota. Windows containers only have access to the specified amount of CPU that's described in the task definition. A null or zero CPU value is passed to Docker as 0 , which Windows interprets as 1% of one CPU.

    • memory (integer) --

      The amount (in MiB) of memory to present to the container. If your container attempts to exceed the memory specified here, the container is killed. The total amount of memory reserved for all containers within a task must be lower than the task memory value, if one is specified. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run .

      If using the Fargate launch type, this parameter is optional.

      If using the EC2 launch type, you must specify either a task-level memory value or a container-level memory value. If you specify both a container-level memory and memoryReservation value, memory must be greater than memoryReservation . If you specify memoryReservation , then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used.

      The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers.

      The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers.

    • memoryReservation (integer) --

      The soft limit (in MiB) of memory to reserve for the container. When system memory is under heavy contention, Docker attempts to keep the container memory to this soft limit. However, your container can consume more memory when it needs to, up to either the hard limit specified with the memory parameter (if applicable), or all of the available memory on the container instance, whichever comes first. This parameter maps to MemoryReservation in the Create a container section of the Docker Remote API and the --memory-reservation option to docker run .

      If a task-level memory value is not specified, you must specify a non-zero integer for one or both of memory or memoryReservation in a container definition. If you specify both, memory must be greater than memoryReservation . If you specify memoryReservation , then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used.

      For example, if your container normally uses 128 MiB of memory, but occasionally bursts to 256 MiB of memory for short periods of time, you can set a memoryReservation of 128 MiB, and a memory hard limit of 300 MiB. This configuration would allow the container to only reserve 128 MiB of memory from the remaining resources on the container instance, but also allow the container to consume more memory resources when needed.

      The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers.

      The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers.

    • links (list) --

      The links parameter allows containers to communicate with each other without the need for port mappings. This parameter is only supported if the network mode of a task definition is bridge . The name:internalName construct is analogous to name:alias in Docker links. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. For more information about linking Docker containers, go to Legacy container links in the Docker documentation. This parameter maps to Links in the Create a container section of the Docker Remote API and the --link option to docker run .

      Note

      This parameter is not supported for Windows containers.

      Warning

      Containers that are collocated on a single container instance may be able to communicate with each other without requiring links or host port mappings. Network isolation is achieved on the container instance using security groups and VPC settings.

      • (string) --

    • portMappings (list) --

      The list of port mappings for the container. Port mappings allow containers to access ports on the host container instance to send or receive traffic.

      For task definitions that use the awsvpc network mode, only specify the containerPort . The hostPort can be left blank or it must be the same value as the containerPort .

      Port mappings on Windows use the NetNAT gateway address rather than localhost . There's no loopback for port mappings on Windows, so you can't access a container's mapped port from the host itself.

      This parameter maps to PortBindings in the Create a container section of the Docker Remote API and the --publish option to docker run . If the network mode of a task definition is set to none , then you can't specify port mappings. If the network mode of a task definition is set to host , then host ports must either be undefined or they must match the container port in the port mapping.

      Note

      After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the Network Bindings section of a container description for a selected task in the Amazon ECS console. The assignments are also visible in the networkBindings section DescribeTasks responses.

      • (dict) --

        Port mappings allow containers to access ports on the host container instance to send or receive traffic. Port mappings are specified as part of the container definition.

        If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort . The hostPort can be left blank or it must be the same value as the containerPort .

        Note

        You can't expose the same container port for multiple protocols. If you attempt this, an error is returned.

        After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the networkBindings section of DescribeTasks API responses.

        • containerPort (integer) --

          The port number on the container that's bound to the user-specified or automatically assigned host port.

          If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort .

          If you use containers in a task with the bridge network mode and you specify a container port and not a host port, your container automatically receives a host port in the ephemeral port range. For more information, see hostPort . Port mappings that are automatically assigned in this way do not count toward the 100 reserved ports limit of a container instance.

        • hostPort (integer) --

          The port number on the container instance to reserve for your container.

          If you use containers in a task with the awsvpc or host network mode, the hostPort can either be left blank or set to the same value as the containerPort .

          If you use containers in a task with the bridge network mode, you can specify a non-reserved host port for your container port mapping, or you can omit the hostPort (or set it to 0 ) while specifying a containerPort and your container automatically receives a port in the ephemeral port range for your container instance operating system and Docker version.

          The default ephemeral port range for Docker version 1.6.0 and later is listed on the instance under /proc/sys/net/ipv4/ip_local_port_range . If this kernel parameter is unavailable, the default ephemeral port range from 49153 through 65535 is used. Do not attempt to specify a host port in the ephemeral port range as these are reserved for automatic assignment. In general, ports below 32768 are outside of the ephemeral port range.

          The default reserved ports are 22 for SSH, the Docker ports 2375 and 2376, and the Amazon ECS container agent ports 51678-51680. Any host port that was previously specified in a running task is also reserved while the task is running. That is, after a task stops, the host port is released. The current reserved ports are displayed in the remainingResources of DescribeContainerInstances output. A container instance can have up to 100 reserved ports at a time. This number includes the default reserved ports. Automatically assigned ports aren't included in the 100 reserved ports quota.

        • protocol (string) --

          The protocol used for the port mapping. Valid values are tcp and udp . The default is tcp .

        • name (string) --

          The name that's used for the port mapping. This parameter only applies to Service Connect. This parameter is the name that you use in the serviceConnectConfiguration of a service. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

          For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

        • appProtocol (string) --

          The application protocol that's used for the port mapping. This parameter only applies to Service Connect. We recommend that you set this parameter to be consistent with the protocol that your application uses. If you set this parameter, Amazon ECS adds protocol-specific connection handling to the Service Connect proxy. If you set this parameter, Amazon ECS adds protocol-specific telemetry in the Amazon ECS console and CloudWatch.

          If you don't set a value for this parameter, then TCP is used. However, Amazon ECS doesn't add protocol-specific telemetry for TCP.

          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 .

    • essential (boolean) --

      If the essential parameter of a container is marked as true , and that container fails or stops for any reason, all other containers that are part of the task are stopped. If the essential parameter of a container is marked as false , its failure doesn't affect the rest of the containers in a task. If this parameter is omitted, a container is assumed to be essential.

      All tasks must have at least one essential container. If you have an application that's composed of multiple containers, group containers that are used for a common purpose into components, and separate the different components into multiple task definitions. For more information, see Application Architecture in the Amazon Elastic Container Service Developer Guide .

    • entryPoint (list) --

      Warning

      Early versions of the Amazon ECS container agent don't properly handle entryPoint parameters. If you have problems using entryPoint , update your container agent or enter your commands and arguments as command array items instead.

      The entry point that's passed to the container. This parameter maps to Entrypoint in the Create a container section of the Docker Remote API and the --entrypoint option to docker run . For more information, see https://docs.docker.com/engine/reference/builder/#entrypoint .

      • (string) --

    • command (list) --

      The command that's passed to the container. This parameter maps to Cmd in the Create a container section of the Docker Remote API and the COMMAND parameter to docker run . For more information, see https://docs.docker.com/engine/reference/builder/#cmd . If there are multiple arguments, each argument is a separated string in the array.

      • (string) --

    • environment (list) --

      The environment variables to pass to a container. This parameter maps to Env in the Create a container section of the Docker Remote API and the --env option to docker run .

      Warning

      We don't recommend that you use plaintext environment variables for sensitive information, such as credential data.

      • (dict) --

        A key-value pair object.

        • name (string) --

          The name of the key-value pair. For environment variables, this is the name of the environment variable.

        • value (string) --

          The value of the key-value pair. For environment variables, this is the value of the environment variable.

    • environmentFiles (list) --

      A list of files containing the environment variables to pass to a container. This parameter maps to the --env-file option to docker run .

      You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file contains an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

      If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying Environment Variables in the Amazon Elastic Container Service Developer Guide .

      • (dict) --

        A list of files containing the environment variables to pass to a container. You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file should contain an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

        If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying environment variables in the Amazon Elastic Container Service Developer Guide .

        This parameter is only supported for tasks hosted on Fargate using the following platform versions:

        • Linux platform version 1.4.0 or later.

        • Windows platform version 1.0.0 or later.

        • value (string) -- [REQUIRED]

          The Amazon Resource Name (ARN) of the Amazon S3 object containing the environment variable file.

        • type (string) -- [REQUIRED]

          The file type to use. The only supported value is s3 .

    • mountPoints (list) --

      The mount points for data volumes in your container.

      This parameter maps to Volumes in the Create a container section of the Docker Remote API and the --volume option to docker run .

      Windows containers can mount whole directories on the same drive as $env:ProgramData . Windows containers can't mount directories on a different drive, and mount point can't be across drives.

      • (dict) --

        Details for a volume mount point that's used in a container definition.

        • sourceVolume (string) --

          The name of the volume to mount. Must be a volume name referenced in the name parameter of task definition volume .

        • containerPath (string) --

          The path on the container to mount the host volume at.

        • readOnly (boolean) --

          If this value is true , the container has read-only access to the volume. If this value is false , then the container can write to the volume. The default value is false .

    • volumesFrom (list) --

      Data volumes to mount from another container. This parameter maps to VolumesFrom in the Create a container section of the Docker Remote API and the --volumes-from option to docker run .

      • (dict) --

        Details on a data volume from another container in the same task definition.

        • sourceContainer (string) --

          The name of another container within the same task definition to mount volumes from.

        • readOnly (boolean) --

          If this value is true , the container has read-only access to the volume. If this value is false , then the container can write to the volume. The default value is false .

    • linuxParameters (dict) --

      Linux-specific modifications that are applied to the container, such as Linux kernel capabilities. For more information see KernelCapabilities .

      Note

      This parameter is not supported for Windows containers.

      • capabilities (dict) --

        The Linux capabilities for the container that are added to or dropped from the default configuration provided by Docker.

        Note

        For tasks that use the Fargate launch type, capabilities is supported for all platform versions but the add parameter is only supported if using platform version 1.4.0 or later.

        • add (list) --

          The Linux capabilities for the container that have been added to the default configuration provided by Docker. This parameter maps to CapAdd in the Create a container section of the Docker Remote API and the --cap-add option to docker run .

          Note

          Tasks launched on Fargate only support adding the SYS_PTRACE kernel capability.

          Valid values: "ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" | "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" | "FOWNER" | "FSETID" | "IPC_LOCK" | "IPC_OWNER" | "KILL" | "LEASE" | "LINUX_IMMUTABLE" | "MAC_ADMIN" | "MAC_OVERRIDE" | "MKNOD" | "NET_ADMIN" | "NET_BIND_SERVICE" | "NET_BROADCAST" | "NET_RAW" | "SETFCAP" | "SETGID" | "SETPCAP" | "SETUID" | "SYS_ADMIN" | "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT" | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" | "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"

          • (string) --

        • drop (list) --

          The Linux capabilities for the container that have been removed from the default configuration provided by Docker. This parameter maps to CapDrop in the Create a container section of the Docker Remote API and the --cap-drop option to docker run .

          Valid values: "ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" | "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" | "FOWNER" | "FSETID" | "IPC_LOCK" | "IPC_OWNER" | "KILL" | "LEASE" | "LINUX_IMMUTABLE" | "MAC_ADMIN" | "MAC_OVERRIDE" | "MKNOD" | "NET_ADMIN" | "NET_BIND_SERVICE" | "NET_BROADCAST" | "NET_RAW" | "SETFCAP" | "SETGID" | "SETPCAP" | "SETUID" | "SYS_ADMIN" | "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT" | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" | "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"

          • (string) --

      • devices (list) --

        Any host devices to expose to the container. This parameter maps to Devices in the Create a container section of the Docker Remote API and the --device option to docker run .

        Note

        If you're using tasks that use the Fargate launch type, the devices parameter isn't supported.

        • (dict) --

          An object representing a container instance host device.

          • hostPath (string) -- [REQUIRED]

            The path for the device on the host container instance.

          • containerPath (string) --

            The path inside the container at which to expose the host device.

          • permissions (list) --

            The explicit permissions to provide to the container for the device. By default, the container has permissions for read , write , and mknod for the device.

            • (string) --

      • initProcessEnabled (boolean) --

        Run an init process inside the container that forwards signals and reaps processes. This parameter maps to the --init option to docker run . This parameter requires version 1.25 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

      • sharedMemorySize (integer) --

        The value for the size (in MiB) of the /dev/shm volume. This parameter maps to the --shm-size option to docker run .

        Note

        If you are using tasks that use the Fargate launch type, the sharedMemorySize parameter is not supported.

      • tmpfs (list) --

        The container path, mount options, and size (in MiB) of the tmpfs mount. This parameter maps to the --tmpfs option to docker run .

        Note

        If you're using tasks that use the Fargate launch type, the tmpfs parameter isn't supported.

        • (dict) --

          The container path, mount options, and size of the tmpfs mount.

          • containerPath (string) -- [REQUIRED]

            The absolute file path where the tmpfs volume is to be mounted.

          • size (integer) -- [REQUIRED]

            The maximum size (in MiB) of the tmpfs volume.

          • mountOptions (list) --

            The list of tmpfs volume mount options.

            Valid values: "defaults" | "ro" | "rw" | "suid" | "nosuid" | "dev" | "nodev" | "exec" | "noexec" | "sync" | "async" | "dirsync" | "remount" | "mand" | "nomand" | "atime" | "noatime" | "diratime" | "nodiratime" | "bind" | "rbind" | "unbindable" | "runbindable" | "private" | "rprivate" | "shared" | "rshared" | "slave" | "rslave" | "relatime" | "norelatime" | "strictatime" | "nostrictatime" | "mode" | "uid" | "gid" | "nr_inodes" | "nr_blocks" | "mpol"

            • (string) --

      • maxSwap (integer) --

        The total amount of swap memory (in MiB) a container can use. This parameter will be translated to the --memory-swap option to docker run where the value would be the sum of the container memory plus the maxSwap value.

        If a maxSwap value of 0 is specified, the container will not use swap. Accepted values are 0 or any positive integer. If the maxSwap parameter is omitted, the container will use the swap configuration for the container instance it is running on. A maxSwap value must be set for the swappiness parameter to be used.

        Note

        If you're using tasks that use the Fargate launch type, the maxSwap parameter isn't supported.

      • swappiness (integer) --

        This allows you to tune a container's memory swappiness behavior. A swappiness value of 0 will cause swapping to not happen unless absolutely necessary. A swappiness value of 100 will cause pages to be swapped very aggressively. Accepted values are whole numbers between 0 and 100 . If the swappiness parameter is not specified, a default value of 60 is used. If a value is not specified for maxSwap then this parameter is ignored. This parameter maps to the --memory-swappiness option to docker run .

        Note

        If you're using tasks that use the Fargate launch type, the swappiness parameter isn't supported.

    • secrets (list) --

      The secrets to pass to the container. For more information, see Specifying Sensitive Data in the Amazon Elastic Container Service Developer Guide .

      • (dict) --

        An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

        • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

        • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

        For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

        • name (string) -- [REQUIRED]

          The name of the secret.

        • valueFrom (string) -- [REQUIRED]

          The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

          For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

          Note

          If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

    • dependsOn (list) --

      The dependencies defined for container startup and shutdown. A container can contain multiple dependencies on other containers in a task definition. When a dependency is defined for container startup, for container shutdown it is reversed.

      For tasks using the EC2 launch type, the container instances require at least version 1.26.0 of the container agent to turn on container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

      For tasks using the Fargate launch type, the task or service requires the following platforms:

      • Linux platform version 1.3.0 or later.

      • Windows platform version 1.0.0 or later.

      • (dict) --

        The dependencies defined for container startup and shutdown. A container can contain multiple dependencies. When a dependency is defined for container startup, for container shutdown it is reversed.

        Your Amazon ECS container instances require at least version 1.26.0 of the container agent to use container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

        Note

        For tasks that use the Fargate launch type, the task or service requires the following platforms:

        • Linux platform version 1.3.0 or later.

        • Windows platform version 1.0.0 or later.

        • containerName (string) -- [REQUIRED]

          The name of a container.

        • condition (string) -- [REQUIRED]

          The dependency condition of the container. The following are the available conditions and their behavior:

          • START - This condition emulates the behavior of links and volumes today. It validates that a dependent container is started before permitting other containers to start.

          • COMPLETE - This condition validates that a dependent container runs to completion (exits) before permitting other containers to start. This can be useful for nonessential containers that run a script and then exit. This condition can't be set on an essential container.

          • SUCCESS - This condition is the same as COMPLETE , but it also requires that the container exits with a zero status. This condition can't be set on an essential container.

          • HEALTHY - This condition validates that the dependent container passes its Docker health check before permitting other containers to start. This requires that the dependent container has health checks configured. This condition is confirmed only at task startup.

    • startTimeout (integer) --

      Time duration (in seconds) to wait before giving up on resolving dependencies for a container. For example, you specify two containers in a task definition with containerA having a dependency on containerB reaching a COMPLETE , SUCCESS , or HEALTHY status. If a startTimeout value is specified for containerB and it doesn't reach the desired status within that time then containerA gives up and not start. This results in the task transitioning to a STOPPED state.

      Note

      When the ECS_CONTAINER_START_TIMEOUT container agent configuration variable is used, it's enforced independently from this start timeout value.

      For tasks using the Fargate launch type, the task or service requires the following platforms:

      • Linux platform version 1.3.0 or later.

      • Windows platform version 1.0.0 or later.

      For tasks using the EC2 launch type, your container instances require at least version 1.26.0 of the container agent to use a container start timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

    • stopTimeout (integer) --

      Time duration (in seconds) to wait before the container is forcefully killed if it doesn't exit normally on its own.

      For tasks using the Fargate launch type, the task or service requires the following platforms:

      • Linux platform version 1.3.0 or later.

      • Windows platform version 1.0.0 or later.

      The max stop timeout value is 120 seconds and if the parameter is not specified, the default value of 30 seconds is used.

      For tasks that use the EC2 launch type, if the stopTimeout parameter isn't specified, the value set for the Amazon ECS container agent configuration variable ECS_CONTAINER_STOP_TIMEOUT is used. If neither the stopTimeout parameter or the ECS_CONTAINER_STOP_TIMEOUT agent configuration variable are set, then the default values of 30 seconds for Linux containers and 30 seconds on Windows containers are used. Your container instances require at least version 1.26.0 of the container agent to use a container stop timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

    • hostname (string) --

      The hostname to use for your container. This parameter maps to Hostname in the Create a container section of the Docker Remote API and the --hostname option to docker run .

      Note

      The hostname parameter is not supported if you're using the awsvpc network mode.

    • user (string) --

      The user to use inside the container. This parameter maps to User in the Create a container section of the Docker Remote API and the --user option to docker run .

      Warning

      When running tasks using the host network mode, don't run containers using the root user (UID 0). We recommend using a non-root user for better security.

      You can specify the user using the following formats. If specifying a UID or GID, you must specify it as a positive integer.

      • user

      • user:group

      • uid

      • uid:gid

      • user:gid

      • uid:group

      Note

      This parameter is not supported for Windows containers.

    • workingDirectory (string) --

      The working directory to run commands inside the container in. This parameter maps to WorkingDir in the Create a container section of the Docker Remote API and the --workdir option to docker run .

    • disableNetworking (boolean) --

      When this parameter is true, networking is disabled within the container. This parameter maps to NetworkDisabled in the Create a container section of the Docker Remote API .

      Note

      This parameter is not supported for Windows containers.

    • privileged (boolean) --

      When this parameter is true, the container is given elevated privileges on the host container instance (similar to the root user). This parameter maps to Privileged in the Create a container section of the Docker Remote API and the --privileged option to docker run .

      Note

      This parameter is not supported for Windows containers or tasks run on Fargate.

    • readonlyRootFilesystem (boolean) --

      When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs in the Create a container section of the Docker Remote API and the --read-only option to docker run .

      Note

      This parameter is not supported for Windows containers.

    • dnsServers (list) --

      A list of DNS servers that are presented to the container. This parameter maps to Dns in the Create a container section of the Docker Remote API and the --dns option to docker run .

      Note

      This parameter is not supported for Windows containers.

      • (string) --

    • dnsSearchDomains (list) --

      A list of DNS search domains that are presented to the container. This parameter maps to DnsSearch in the Create a container section of the Docker Remote API and the --dns-search option to docker run .

      Note

      This parameter is not supported for Windows containers.

      • (string) --

    • extraHosts (list) --

      A list of hostnames and IP address mappings to append to the /etc/hosts file on the container. This parameter maps to ExtraHosts in the Create a container section of the Docker Remote API and the --add-host option to docker run .

      Note

      This parameter isn't supported for Windows containers or tasks that use the awsvpc network mode.

      • (dict) --

        Hostnames and IP address entries that are added to the /etc/hosts file of a container via the extraHosts parameter of its ContainerDefinition .

        • hostname (string) -- [REQUIRED]

          The hostname to use in the /etc/hosts entry.

        • ipAddress (string) -- [REQUIRED]

          The IP address to use in the /etc/hosts entry.

    • dockerSecurityOptions (list) --

      A list of strings to provide custom labels for SELinux and AppArmor multi-level security systems. This field isn't valid for containers in tasks using the Fargate launch type.

      With Windows containers, this parameter can be used to reference a credential spec file when configuring a container for Active Directory authentication. For more information, see Using gMSAs for Windows Containers in the Amazon Elastic Container Service Developer Guide .

      This parameter maps to SecurityOpt in the Create a container section of the Docker Remote API and the --security-opt option to docker run .

      Note

      The Amazon ECS container agent running on a container instance must register with the ECS_SELINUX_CAPABLE=true or ECS_APPARMOR_CAPABLE=true environment variables before containers placed on that instance can use these security options. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide .

      For more information about valid values, see Docker Run Security Configuration .

      Valid values: "no-new-privileges" | "apparmor:PROFILE" | "label:value" | "credentialspec:CredentialSpecFilePath"

      • (string) --

    • interactive (boolean) --

      When this parameter is true , you can deploy containerized applications that require stdin or a tty to be allocated. This parameter maps to OpenStdin in the Create a container section of the Docker Remote API and the --interactive option to docker run .

    • pseudoTerminal (boolean) --

      When this parameter is true , a TTY is allocated. This parameter maps to Tty in the Create a container section of the Docker Remote API and the --tty option to docker run .

    • dockerLabels (dict) --

      A key/value map of labels to add to the container. This parameter maps to Labels in the Create a container section of the Docker Remote API and the --label option to docker run . This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

      • (string) --

        • (string) --

    • ulimits (list) --

      A list of ulimits to set in the container. If a ulimit value is specified in a task definition, it overrides the default values set by Docker. This parameter maps to Ulimits in the Create a container section of the Docker Remote API and the --ulimit option to docker run . Valid naming values are displayed in the Ulimit data type.

      Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and hard limit is 4096 .

      This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

      Note

      This parameter is not supported for Windows containers.

      • (dict) --

        The ulimit settings to pass to the container.

        Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and hard limit is 4096 .

        • name (string) -- [REQUIRED]

          The type of the ulimit .

        • softLimit (integer) -- [REQUIRED]

          The soft limit for the ulimit type.

        • hardLimit (integer) -- [REQUIRED]

          The hard limit for the ulimit type.

    • logConfiguration (dict) --

      The log configuration specification for the container.

      This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to docker run . By default, containers use the same logging driver that the Docker daemon uses. However the container can use a different logging driver than the Docker daemon by specifying a log driver with this parameter in the container definition. To use a different logging driver for a container, the log system must be configured properly on the container instance (or on a different log server for remote logging options). For more information about the options for different supported log drivers, see Configure logging drivers in the Docker documentation.

      Note

      Amazon ECS currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type). Additional log drivers may be available in future releases of the Amazon ECS container agent.

      This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

      Note

      The Amazon ECS container agent running on a container instance must register the logging drivers available on that instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide .

      • logDriver (string) -- [REQUIRED]

        The log driver to use for the container.

        For tasks on Fargate, the supported log drivers are awslogs , splunk , and awsfirelens .

        For tasks hosted on Amazon EC2 instances, the supported log drivers are awslogs , fluentd , gelf , json-file , journald , logentries ,``syslog`` , splunk , and awsfirelens .

        For more information about using the awslogs log driver, see Using the awslogs log driver in the Amazon Elastic Container Service Developer Guide .

        For more information about using the awsfirelens log driver, see Custom log routing in the Amazon Elastic Container Service Developer Guide .

        Note

        If you have a custom driver that isn't listed, you can fork the Amazon ECS container agent project that's available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you would like to have included. However, we don't currently provide support for running modified copies of this software.

      • options (dict) --

        The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

        • (string) --

          • (string) --

      • secretOptions (list) --

        The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

        • (dict) --

          An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

          • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

          • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

          For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

          • name (string) -- [REQUIRED]

            The name of the secret.

          • valueFrom (string) -- [REQUIRED]

            The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

            For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

            Note

            If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

    • healthCheck (dict) --

      The container health check command and associated configuration parameters for the container. This parameter maps to HealthCheck in the Create a container section of the Docker Remote API and the HEALTHCHECK parameter of docker run .

      • command (list) -- [REQUIRED]

        A string array representing the command that the container runs to determine if it is healthy. The string array must start with CMD to run the command arguments directly, or CMD-SHELL to run the command with the container's default shell.

        When you use the Amazon Web Services Management Console JSON panel, the Command Line Interface, or the APIs, enclose the list of commands in brackets.

        [ "CMD-SHELL", "curl -f http://localhost/ || exit 1" ]

        You don't need to include the brackets when you use the Amazon Web Services Management Console.

        "CMD-SHELL", "curl -f http://localhost/ || exit 1"

        An exit code of 0 indicates success, and non-zero exit code indicates failure. For more information, see HealthCheck in the Create a container section of the Docker Remote API .

        • (string) --

      • interval (integer) --

        The time period in seconds between each health check execution. You may specify between 5 and 300 seconds. The default value is 30 seconds.

      • timeout (integer) --

        The time period in seconds to wait for a health check to succeed before it is considered a failure. You may specify between 2 and 60 seconds. The default value is 5.

      • retries (integer) --

        The number of times to retry a failed health check before the container is considered unhealthy. You may specify between 1 and 10 retries. The default value is 3.

      • startPeriod (integer) --

        The optional grace period to provide containers time to bootstrap before failed health checks count towards the maximum number of retries. You can specify between 0 and 300 seconds. By default, the startPeriod is disabled.

        Note

        If a health check succeeds within the startPeriod , then the container is considered healthy and any subsequent failures count toward the maximum number of retries.

    • systemControls (list) --

      A list of namespaced kernel parameters to set in the container. This parameter maps to Sysctls in the Create a container section of the Docker Remote API and the --sysctl option to docker run .

      Note

      We don't recommended that you specify network-related systemControls parameters for multiple containers in a single task that also uses either the awsvpc or host network modes. For tasks that use the awsvpc network mode, the container that's started last determines which systemControls parameters take effect. For tasks that use the host network mode, it changes the container instance's namespaced kernel parameters as well as the containers.

      • (dict) --

        A list of namespaced kernel parameters to set in the container. This parameter maps to Sysctls in the Create a container section of the Docker Remote API and the --sysctl option to docker run .

        We don't recommend that you specify network-related systemControls parameters for multiple containers in a single task. This task also uses either the awsvpc or host network mode. It does it for the following reasons.

        • For tasks that use the awsvpc network mode, if you set systemControls for any container, it applies to all containers in the task. If you set different systemControls for multiple containers in a single task, the container that's started last determines which systemControls take effect.

        • For tasks that use the host network mode, the systemControls parameter applies to the container instance's kernel parameter and that of all containers of any tasks running on that container instance.

        • namespace (string) --

          The namespaced kernel parameter to set a value for.

        • value (string) --

          The value for the namespaced kernel parameter that's specified in namespace .

    • resourceRequirements (list) --

      The type and amount of a resource to assign to a container. The only supported resource is a GPU.

      • (dict) --

        The type and amount of a resource to assign to a container. The supported resource types are GPUs and Elastic Inference accelerators. For more information, see Working with GPUs on Amazon ECS or Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide

        • value (string) -- [REQUIRED]

          The value for the specified resource type.

          If the GPU type is used, the value is the number of physical GPUs the Amazon ECS container agent reserves for the container. The number of GPUs that's reserved for all containers in a task can't exceed the number of available GPUs on the container instance that the task is launched on.

          If the InferenceAccelerator type is used, the value matches the deviceName for an InferenceAccelerator specified in a task definition.

        • type (string) -- [REQUIRED]

          The type of resource to assign to a container. The supported values are GPU or InferenceAccelerator .

    • firelensConfiguration (dict) --

      The FireLens configuration for the container. This is used to specify and configure a log router for container logs. For more information, see Custom Log Routing in the Amazon Elastic Container Service Developer Guide .

      • type (string) -- [REQUIRED]

        The log router to use. The valid values are fluentd or fluentbit .

      • options (dict) --

        The options to use when configuring the log router. This field is optional and can be used to specify a custom configuration file or to add additional metadata, such as the task, task definition, cluster, and container instance details to the log event. If specified, the syntax to use is "options":{"enable-ecs-log-metadata":"true|false","config-file-type:"s3|file","config-file-value":"arn:aws:s3:::mybucket/fluent.conf|filepath"} . For more information, see Creating a task definition that uses a FireLens configuration in the Amazon Elastic Container Service Developer Guide .

        Note

        Tasks hosted on Fargate only support the file configuration file type.

        • (string) --

          • (string) --

type volumes

list

param volumes

A list of volume definitions in JSON format that containers in your task might use.

  • (dict) --

    A data volume that's used in a task definition. For tasks that use the Amazon Elastic File System (Amazon EFS), specify an efsVolumeConfiguration . For Windows tasks that use Amazon FSx for Windows File Server file system, specify a fsxWindowsFileServerVolumeConfiguration . For tasks that use a Docker volume, specify a DockerVolumeConfiguration . For tasks that use a bind mount host volume, specify a host and optional sourcePath . For more information, see Using Data Volumes in Tasks .

    • name (string) --

      The name of the volume. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This name is referenced in the sourceVolume parameter of container definition mountPoints .

    • host (dict) --

      This parameter is specified when you use bind mount host volumes. The contents of the host parameter determine whether your bind mount host volume persists on the host container instance and where it's stored. If the host parameter is empty, then the Docker daemon assigns a host path for your data volume. However, the data isn't guaranteed to persist after the containers that are associated with it stop running.

      Windows containers can mount whole directories on the same drive as $env:ProgramData . Windows containers can't mount directories on a different drive, and mount point can't be across drives. For example, you can mount C:\my\path:C:\my\path and D:\:D:\ , but not D:\my\path:C:\my\path or D:\:C:\my\path .

      • sourcePath (string) --

        When the host parameter is used, specify a sourcePath to declare the path on the host container instance that's presented to the container. If this parameter is empty, then the Docker daemon has assigned a host path for you. If the host parameter contains a sourcePath file location, then the data volume persists at the specified location on the host container instance until you delete it manually. If the sourcePath value doesn't exist on the host container instance, the Docker daemon creates it. If the location does exist, the contents of the source path folder are exported.

        If you're using the Fargate launch type, the sourcePath parameter is not supported.

    • dockerVolumeConfiguration (dict) --

      This parameter is specified when you use Docker volumes.

      Windows containers only support the use of the local driver. To use bind mounts, specify the host parameter instead.

      Note

      Docker volumes aren't supported by tasks run on Fargate.

      • scope (string) --

        The scope for the Docker volume that determines its lifecycle. Docker volumes that are scoped to a task are automatically provisioned when the task starts and destroyed when the task stops. Docker volumes that are scoped as shared persist after the task stops.

      • autoprovision (boolean) --

        If this value is true , the Docker volume is created if it doesn't already exist.

        Note

        This field is only used if the scope is shared .

      • driver (string) --

        The Docker volume driver to use. The driver value must match the driver name provided by Docker because it is used for task placement. If the driver was installed using the Docker plugin CLI, use docker plugin ls to retrieve the driver name from your container instance. If the driver was installed using another method, use Docker plugin discovery to retrieve the driver name. For more information, see Docker plugin discovery . This parameter maps to Driver in the Create a volume section of the Docker Remote API and the xxdriver option to docker volume create .

      • driverOpts (dict) --

        A map of Docker driver-specific options passed through. This parameter maps to DriverOpts in the Create a volume section of the Docker Remote API and the xxopt option to docker volume create .

        • (string) --

          • (string) --

      • labels (dict) --

        Custom metadata to add to your Docker volume. This parameter maps to Labels in the Create a volume section of the Docker Remote API and the xxlabel option to docker volume create .

        • (string) --

          • (string) --

    • efsVolumeConfiguration (dict) --

      This parameter is specified when you use an Amazon Elastic File System file system for task storage.

      • fileSystemId (string) -- [REQUIRED]

        The Amazon EFS file system ID to use.

      • rootDirectory (string) --

        The directory within the Amazon EFS file system to mount as the root directory inside the host. If this parameter is omitted, the root of the Amazon EFS volume will be used. Specifying / will have the same effect as omitting this parameter.

        Warning

        If an EFS access point is specified in the authorizationConfig , the root directory parameter must either be omitted or set to / which will enforce the path set on the EFS access point.

      • transitEncryption (string) --

        Determines whether to use encryption for Amazon EFS data in transit between the Amazon ECS host and the Amazon EFS server. Transit encryption must be enabled if Amazon EFS IAM authorization is used. If this parameter is omitted, the default value of DISABLED is used. For more information, see Encrypting data in transit in the Amazon Elastic File System User Guide .

      • transitEncryptionPort (integer) --

        The port to use when sending encrypted data between the Amazon ECS host and the Amazon EFS server. If you do not specify a transit encryption port, it will use the port selection strategy that the Amazon EFS mount helper uses. For more information, see EFS mount helper in the Amazon Elastic File System User Guide .

      • authorizationConfig (dict) --

        The authorization configuration details for the Amazon EFS file system.

        • accessPointId (string) --

          The Amazon EFS access point ID to use. If an access point is specified, the root directory value specified in the EFSVolumeConfiguration must either be omitted or set to / which will enforce the path set on the EFS access point. If an access point is used, transit encryption must be enabled in the EFSVolumeConfiguration . For more information, see Working with Amazon EFS access points in the Amazon Elastic File System User Guide .

        • iam (string) --

          Determines whether to use the Amazon ECS task IAM role defined in a task definition when mounting the Amazon EFS file system. If enabled, transit encryption must be enabled in the EFSVolumeConfiguration . If this parameter is omitted, the default value of DISABLED is used. For more information, see Using Amazon EFS access points in the Amazon Elastic Container Service Developer Guide .

    • fsxWindowsFileServerVolumeConfiguration (dict) --

      This parameter is specified when you use Amazon FSx for Windows File Server file system for task storage.

      • fileSystemId (string) -- [REQUIRED]

        The Amazon FSx for Windows File Server file system ID to use.

      • rootDirectory (string) -- [REQUIRED]

        The directory within the Amazon FSx for Windows File Server file system to mount as the root directory inside the host.

      • authorizationConfig (dict) -- [REQUIRED]

        The authorization configuration details for the Amazon FSx for Windows File Server file system.

        • credentialsParameter (string) -- [REQUIRED]

          The authorization credential option to use. The authorization credential options can be provided using either the Amazon Resource Name (ARN) of an Secrets Manager secret or SSM Parameter Store parameter. The ARN refers to the stored credentials.

        • domain (string) -- [REQUIRED]

          A fully qualified domain name hosted by an Directory Service Managed Microsoft AD (Active Directory) or self-hosted AD on Amazon EC2.

type placementConstraints

list

param placementConstraints

An array of placement constraint objects to use for the task. You can specify a maximum of 10 constraints for each task. This limit includes constraints in the task definition and those specified at runtime.

  • (dict) --

    An object representing a constraint on task placement in the task definition. For more information, see Task placement constraints in the Amazon Elastic Container Service Developer Guide .

    Note

    Task placement constraints aren't supported for tasks run on Fargate.

    • type (string) --

      The type of constraint. The MemberOf constraint restricts selection to be from a group of valid candidates.

    • expression (string) --

      A cluster query language expression to apply to the constraint. For more information, see Cluster query language in the Amazon Elastic Container Service Developer Guide .

type requiresCompatibilities

list

param requiresCompatibilities

The task launch type that Amazon ECS validates the task definition against. A client exception is returned if the task definition doesn't validate against the compatibilities specified. If no value is specified, the parameter is omitted from the response.

  • (string) --

type cpu

string

param cpu

The number of CPU units used by the task. It can be expressed as an integer using CPU units (for example, 1024 ) or as a string using vCPUs (for example, 1 vCPU or 1 vcpu ) in a task definition. String values are converted to an integer indicating the CPU units when the task definition is registered.

Note

Task-level CPU and memory parameters are ignored for Windows containers. We recommend specifying container-level resources for Windows containers.

If you're using the EC2 launch type, this field is optional. Supported values are between 128 CPU units (0.125 vCPUs) and 10240 CPU units (10 vCPUs). If you do not specify a value, the parameter is ignored.

If you're using the Fargate launch type, this field is required and you must use one of the following values, which determines your range of supported values for the memory parameter:

The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.

  • 256 (.25 vCPU) - Available memory values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)

  • 512 (.5 vCPU) - Available memory values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)

  • 1024 (1 vCPU) - Available memory values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)

  • 2048 (2 vCPU) - Available memory values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)

  • 4096 (4 vCPU) - Available memory values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)

  • 8192 (8 vCPU) - Available memory values: 16 GB and 60 GB in 4 GB increments This option requires Linux platform 1.4.0 or later.

  • 16384 (16vCPU) - Available memory values: 32GB and 120 GB in 8 GB increments This option requires Linux platform 1.4.0 or later.

type memory

string

param memory

The amount of memory (in MiB) used by the task. It can be expressed as an integer using MiB (for example ,``1024`` ) or as a string using GB (for example, 1GB or 1 GB ) in a task definition. String values are converted to an integer indicating the MiB when the task definition is registered.

Note

Task-level CPU and memory parameters are ignored for Windows containers. We recommend specifying container-level resources for Windows containers.

If using the EC2 launch type, this field is optional.

If using the Fargate launch type, this field is required and you must use one of the following values. This determines your range of supported values for the cpu parameter.

The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.

  • 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB) - Available cpu values: 256 (.25 vCPU)

  • 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB) - Available cpu values: 512 (.5 vCPU)

  • 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB) - Available cpu values: 1024 (1 vCPU)

  • Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB) - Available cpu values: 2048 (2 vCPU)

  • Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB) - Available cpu values: 4096 (4 vCPU)

  • Between 16 GB and 60 GB in 4 GB increments - Available cpu values: 8192 (8 vCPU) This option requires Linux platform 1.4.0 or later.

  • Between 32GB and 120 GB in 8 GB increments - Available cpu values: 16384 (16 vCPU) This option requires Linux platform 1.4.0 or later.

type tags

list

param tags

The metadata that you apply to the task definition to help you categorize and organize them. Each tag consists of a key and an optional value. You define both of them.

The following basic restrictions apply to tags:

  • Maximum number of tags per resource - 50

  • For each resource, each tag key must be unique, and each tag key can have only one value.

  • Maximum key length - 128 Unicode characters in UTF-8

  • Maximum value length - 256 Unicode characters in UTF-8

  • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

  • Tag keys and values are case-sensitive.

  • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

  • (dict) --

    The metadata that you apply to a resource to help you categorize and organize them. Each tag consists of a key and an optional value. You define them.

    The following basic restrictions apply to tags:

    • Maximum number of tags per resource - 50

    • For each resource, each tag key must be unique, and each tag key can have only one value.

    • Maximum key length - 128 Unicode characters in UTF-8

    • Maximum value length - 256 Unicode characters in UTF-8

    • If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.

    • Tag keys and values are case-sensitive.

    • Do not use aws: , AWS: , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for Amazon Web Services use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.

    • key (string) --

      One part of a key-value pair that make up a tag. A key is a general label that acts like a category for more specific tag values.

    • value (string) --

      The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).

type pidMode

string

param pidMode

The process namespace to use for the containers in the task. The valid values are host or task . If host is specified, then all containers within the tasks that specified the host PID mode on the same container instance share the same process namespace with the host Amazon EC2 instance. If task is specified, all containers within the specified task share the same process namespace. If no value is specified, the default is a private namespace. For more information, see PID settings in the Docker run reference .

If the host PID mode is used, be aware that there is a heightened risk of undesired process namespace expose. For more information, see Docker security .

Note

This parameter is not supported for Windows containers or tasks run on Fargate.

type ipcMode

string

param ipcMode

The IPC resource namespace to use for the containers in the task. The valid values are host , task , or none . If host is specified, then all containers within the tasks that specified the host IPC mode on the same container instance share the same IPC resources with the host Amazon EC2 instance. If task is specified, all containers within the specified task share the same IPC resources. If none is specified, then IPC resources within the containers of a task are private and not shared with other containers in a task or on the container instance. If no value is specified, then the IPC resource namespace sharing depends on the Docker daemon setting on the container instance. For more information, see IPC settings in the Docker run reference .

If the host IPC mode is used, be aware that there is a heightened risk of undesired IPC namespace expose. For more information, see Docker security .

If you are setting namespaced kernel parameters using systemControls for the containers in the task, the following will apply to your IPC resource namespace. For more information, see System Controls in the Amazon Elastic Container Service Developer Guide .

  • For tasks that use the host IPC mode, IPC namespace related systemControls are not supported.

  • For tasks that use the task IPC mode, IPC namespace related systemControls will apply to all containers within a task.

Note

This parameter is not supported for Windows containers or tasks run on Fargate.

type proxyConfiguration

dict

param proxyConfiguration

The configuration details for the App Mesh proxy.

For tasks hosted on Amazon EC2 instances, the container instances require at least version 1.26.0 of the container agent and at least version 1.26.0-1 of the ecs-init package to use a proxy configuration. If your container instances are launched from the Amazon ECS-optimized AMI version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized AMI versions in the Amazon Elastic Container Service Developer Guide .

  • type (string) --

    The proxy type. The only supported value is APPMESH .

  • containerName (string) -- [REQUIRED]

    The name of the container that will serve as the App Mesh proxy.

  • properties (list) --

    The set of network configuration parameters to provide the Container Network Interface (CNI) plugin, specified as key-value pairs.

    • IgnoredUID - (Required) The user ID (UID) of the proxy container as defined by the user parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If IgnoredGID is specified, this field can be empty.

    • IgnoredGID - (Required) The group ID (GID) of the proxy container as defined by the user parameter in a container definition. This is used to ensure the proxy ignores its own traffic. If IgnoredUID is specified, this field can be empty.

    • AppPorts - (Required) The list of ports that the application uses. Network traffic to these ports is forwarded to the ProxyIngressPort and ProxyEgressPort .

    • ProxyIngressPort - (Required) Specifies the port that incoming traffic to the AppPorts is directed to.

    • ProxyEgressPort - (Required) Specifies the port that outgoing traffic from the AppPorts is directed to.

    • EgressIgnoredPorts - (Required) The egress traffic going to the specified ports is ignored and not redirected to the ProxyEgressPort . It can be an empty list.

    • EgressIgnoredIPs - (Required) The egress traffic going to the specified IP addresses is ignored and not redirected to the ProxyEgressPort . It can be an empty list.

    • (dict) --

      A key-value pair object.

      • name (string) --

        The name of the key-value pair. For environment variables, this is the name of the environment variable.

      • value (string) --

        The value of the key-value pair. For environment variables, this is the value of the environment variable.

type inferenceAccelerators

list

param inferenceAccelerators

The Elastic Inference accelerators to use for the containers in the task.

  • (dict) --

    Details on an Elastic Inference accelerator. For more information, see Working with Amazon Elastic Inference on Amazon ECS in the Amazon Elastic Container Service Developer Guide .

    • deviceName (string) -- [REQUIRED]

      The Elastic Inference accelerator device name. The deviceName must also be referenced in a container definition as a ResourceRequirement .

    • deviceType (string) -- [REQUIRED]

      The Elastic Inference accelerator type to use.

type ephemeralStorage

dict

param ephemeralStorage

The amount of ephemeral storage to allocate for the task. This parameter is used to expand the total amount of ephemeral storage available, beyond the default amount, for tasks hosted on Fargate. For more information, see Fargate task storage in the Amazon ECS User Guide for Fargate .

Note

This parameter is only supported for tasks hosted on Fargate using the following platform versions:

  • Linux platform version 1.4.0 or later.

  • sizeInGiB (integer) -- [REQUIRED]

    The total amount, in GiB, of ephemeral storage to set for the task. The minimum supported value is 21 GiB and the maximum supported value is 200 GiB.

type runtimePlatform

dict

param runtimePlatform

The operating system that your tasks definitions run on. A platform family is specified only for tasks using the Fargate launch type.

When you specify a task definition in a service, this value must match the runtimePlatform value of the service.

  • cpuArchitecture (string) --

    The CPU architecture.

    You can run your Linux tasks on an ARM-based platform by setting the value to ARM64 . This option is available for tasks that run on Linux Amazon EC2 instance or Linux containers on Fargate.

  • operatingSystemFamily (string) --

    The operating system.

rtype

dict

returns

Response Syntax

{
    'taskDefinition': {
        'taskDefinitionArn': 'string',
        'containerDefinitions': [
            {
                'name': 'string',
                'image': 'string',
                'repositoryCredentials': {
                    'credentialsParameter': 'string'
                },
                'cpu': 123,
                'memory': 123,
                'memoryReservation': 123,
                'links': [
                    'string',
                ],
                'portMappings': [
                    {
                        'containerPort': 123,
                        'hostPort': 123,
                        'protocol': 'tcp'|'udp',
                        'name': 'string',
                        'appProtocol': 'http'|'http2'|'grpc'
                    },
                ],
                'essential': True|False,
                'entryPoint': [
                    'string',
                ],
                'command': [
                    'string',
                ],
                'environment': [
                    {
                        'name': 'string',
                        'value': 'string'
                    },
                ],
                'environmentFiles': [
                    {
                        'value': 'string',
                        'type': 's3'
                    },
                ],
                'mountPoints': [
                    {
                        'sourceVolume': 'string',
                        'containerPath': 'string',
                        'readOnly': True|False
                    },
                ],
                'volumesFrom': [
                    {
                        'sourceContainer': 'string',
                        'readOnly': True|False
                    },
                ],
                'linuxParameters': {
                    'capabilities': {
                        'add': [
                            'string',
                        ],
                        'drop': [
                            'string',
                        ]
                    },
                    'devices': [
                        {
                            'hostPath': 'string',
                            'containerPath': 'string',
                            'permissions': [
                                'read'|'write'|'mknod',
                            ]
                        },
                    ],
                    'initProcessEnabled': True|False,
                    'sharedMemorySize': 123,
                    'tmpfs': [
                        {
                            'containerPath': 'string',
                            'size': 123,
                            'mountOptions': [
                                'string',
                            ]
                        },
                    ],
                    'maxSwap': 123,
                    'swappiness': 123
                },
                'secrets': [
                    {
                        'name': 'string',
                        'valueFrom': 'string'
                    },
                ],
                'dependsOn': [
                    {
                        'containerName': 'string',
                        'condition': 'START'|'COMPLETE'|'SUCCESS'|'HEALTHY'
                    },
                ],
                'startTimeout': 123,
                'stopTimeout': 123,
                'hostname': 'string',
                'user': 'string',
                'workingDirectory': 'string',
                'disableNetworking': True|False,
                'privileged': True|False,
                'readonlyRootFilesystem': True|False,
                'dnsServers': [
                    'string',
                ],
                'dnsSearchDomains': [
                    'string',
                ],
                'extraHosts': [
                    {
                        'hostname': 'string',
                        'ipAddress': 'string'
                    },
                ],
                'dockerSecurityOptions': [
                    'string',
                ],
                'interactive': True|False,
                'pseudoTerminal': True|False,
                'dockerLabels': {
                    'string': 'string'
                },
                'ulimits': [
                    {
                        'name': 'core'|'cpu'|'data'|'fsize'|'locks'|'memlock'|'msgqueue'|'nice'|'nofile'|'nproc'|'rss'|'rtprio'|'rttime'|'sigpending'|'stack',
                        'softLimit': 123,
                        'hardLimit': 123
                    },
                ],
                'logConfiguration': {
                    'logDriver': 'json-file'|'syslog'|'journald'|'gelf'|'fluentd'|'awslogs'|'splunk'|'awsfirelens',
                    'options': {
                        'string': 'string'
                    },
                    'secretOptions': [
                        {
                            'name': 'string',
                            'valueFrom': 'string'
                        },
                    ]
                },
                'healthCheck': {
                    'command': [
                        'string',
                    ],
                    'interval': 123,
                    'timeout': 123,
                    'retries': 123,
                    'startPeriod': 123
                },
                'systemControls': [
                    {
                        'namespace': 'string',
                        'value': 'string'
                    },
                ],
                'resourceRequirements': [
                    {
                        'value': 'string',
                        'type': 'GPU'|'InferenceAccelerator'
                    },
                ],
                'firelensConfiguration': {
                    'type': 'fluentd'|'fluentbit',
                    'options': {
                        'string': 'string'
                    }
                }
            },
        ],
        'family': 'string',
        'taskRoleArn': 'string',
        'executionRoleArn': 'string',
        'networkMode': 'bridge'|'host'|'awsvpc'|'none',
        'revision': 123,
        'volumes': [
            {
                'name': 'string',
                'host': {
                    'sourcePath': 'string'
                },
                'dockerVolumeConfiguration': {
                    'scope': 'task'|'shared',
                    'autoprovision': True|False,
                    'driver': 'string',
                    'driverOpts': {
                        'string': 'string'
                    },
                    'labels': {
                        'string': 'string'
                    }
                },
                'efsVolumeConfiguration': {
                    'fileSystemId': 'string',
                    'rootDirectory': 'string',
                    'transitEncryption': 'ENABLED'|'DISABLED',
                    'transitEncryptionPort': 123,
                    'authorizationConfig': {
                        'accessPointId': 'string',
                        'iam': 'ENABLED'|'DISABLED'
                    }
                },
                'fsxWindowsFileServerVolumeConfiguration': {
                    'fileSystemId': 'string',
                    'rootDirectory': 'string',
                    'authorizationConfig': {
                        'credentialsParameter': 'string',
                        'domain': 'string'
                    }
                }
            },
        ],
        'status': 'ACTIVE'|'INACTIVE',
        'requiresAttributes': [
            {
                'name': 'string',
                'value': 'string',
                'targetType': 'container-instance',
                'targetId': 'string'
            },
        ],
        'placementConstraints': [
            {
                'type': 'memberOf',
                'expression': 'string'
            },
        ],
        'compatibilities': [
            'EC2'|'FARGATE'|'EXTERNAL',
        ],
        'runtimePlatform': {
            'cpuArchitecture': 'X86_64'|'ARM64',
            'operatingSystemFamily': 'WINDOWS_SERVER_2019_FULL'|'WINDOWS_SERVER_2019_CORE'|'WINDOWS_SERVER_2016_FULL'|'WINDOWS_SERVER_2004_CORE'|'WINDOWS_SERVER_2022_CORE'|'WINDOWS_SERVER_2022_FULL'|'WINDOWS_SERVER_20H2_CORE'|'LINUX'
        },
        'requiresCompatibilities': [
            'EC2'|'FARGATE'|'EXTERNAL',
        ],
        'cpu': 'string',
        'memory': 'string',
        'inferenceAccelerators': [
            {
                'deviceName': 'string',
                'deviceType': 'string'
            },
        ],
        'pidMode': 'host'|'task',
        'ipcMode': 'host'|'task'|'none',
        'proxyConfiguration': {
            'type': 'APPMESH',
            'containerName': 'string',
            'properties': [
                {
                    'name': 'string',
                    'value': 'string'
                },
            ]
        },
        'registeredAt': datetime(2015, 1, 1),
        'deregisteredAt': datetime(2015, 1, 1),
        'registeredBy': 'string',
        'ephemeralStorage': {
            'sizeInGiB': 123
        }
    },
    'tags': [
        {
            'key': 'string',
            'value': 'string'
        },
    ]
}

Response Structure

  • (dict) --

    • taskDefinition (dict) --

      The full description of the registered task definition.

      • taskDefinitionArn (string) --

        The full Amazon Resource Name (ARN) of the task definition.

      • containerDefinitions (list) --

        A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see Amazon ECS Task Definitions in the Amazon Elastic Container Service Developer Guide .

        • (dict) --

          Container definitions are used in task definitions to describe the different containers that are launched as part of a task.

          • name (string) --

            The name of a container. If you're linking multiple containers together in a task definition, the name of one container can be entered in the links of another container to connect the containers. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. This parameter maps to name in the Create a container section of the Docker Remote API and the --name option to docker run .

          • image (string) --

            The image used to start a container. This string is passed directly to the Docker daemon. By default, images in the Docker Hub registry are available. Other repositories are specified with either `` repository-url /image :tag `` or `` repository-url /image @*digest* `` . Up to 255 letters (uppercase and lowercase), numbers, hyphens, underscores, colons, periods, forward slashes, and number signs are allowed. This parameter maps to Image in the Create a container section of the Docker Remote API and the IMAGE parameter of docker run .

            • When a new task starts, the Amazon ECS container agent pulls the latest version of the specified image and tag for the container to use. However, subsequent updates to a repository image aren't propagated to already running tasks.

            • Images in Amazon ECR repositories can be specified by either using the full registry/repository:tag or registry/repository@digest . For example, 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>:latest or 012345678910.dkr.ecr.<region-name>.amazonaws.com/<repository-name>@sha256:94afd1f2e64d908bc90dbca0035a5b567EXAMPLE .

            • Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo ).

            • Images in other repositories on Docker Hub are qualified with an organization name (for example, amazon/amazon-ecs-agent ).

            • Images in other online repositories are qualified further by a domain name (for example, quay.io/assemblyline/ubuntu ).

          • repositoryCredentials (dict) --

            The private repository authentication credentials to use.

            • credentialsParameter (string) --

              The Amazon Resource Name (ARN) of the secret containing the private repository credentials.

              Note

              When you use the Amazon ECS API, CLI, or Amazon Web Services SDK, if the secret exists in the same Region as the task that you're launching then you can use either the full ARN or the name of the secret. When you use the Amazon Web Services Management Console, you must specify the full ARN of the secret.

          • cpu (integer) --

            The number of cpu units reserved for the container. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run .

            This field is optional for tasks using the Fargate launch type, and the only requirement is that the total amount of CPU reserved for all containers within a task be lower than the task-level cpu value.

            Note

            You can determine the number of CPU units that are available per EC2 instance type by multiplying the vCPUs listed for that instance type on the Amazon EC2 Instances detail page by 1,024.

            Linux containers share unallocated CPU units with other containers on the container instance with the same ratio as their allocated amount. For example, if you run a single-container task on a single-core instance type with 512 CPU units specified for that container, and that's the only task running on the container instance, that container could use the full 1,024 CPU unit share at any given time. However, if you launched another copy of the same task on that container instance, each task is guaranteed a minimum of 512 CPU units when needed. Moreover, each container could float to higher CPU usage if the other container was not using it. If both tasks were 100% active all of the time, they would be limited to 512 CPU units.

            On Linux container instances, the Docker daemon on the container instance uses the CPU value to calculate the relative CPU share ratios for running containers. For more information, see CPU share constraint in the Docker documentation. The minimum valid CPU share value that the Linux kernel allows is 2. However, the CPU parameter isn't required, and you can use CPU values below 2 in your container definitions. For CPU values below 2 (including null), the behavior varies based on your Amazon ECS container agent version:

            • Agent versions less than or equal to 1.1.0: Null and zero CPU values are passed to Docker as 0, which Docker then converts to 1,024 CPU shares. CPU values of 1 are passed to Docker as 1, which the Linux kernel converts to two CPU shares.

            • Agent versions greater than or equal to 1.2.0: Null, zero, and CPU values of 1 are passed to Docker as 2.

            On Windows container instances, the CPU limit is enforced as an absolute limit, or a quota. Windows containers only have access to the specified amount of CPU that's described in the task definition. A null or zero CPU value is passed to Docker as 0 , which Windows interprets as 1% of one CPU.

          • memory (integer) --

            The amount (in MiB) of memory to present to the container. If your container attempts to exceed the memory specified here, the container is killed. The total amount of memory reserved for all containers within a task must be lower than the task memory value, if one is specified. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run .

            If using the Fargate launch type, this parameter is optional.

            If using the EC2 launch type, you must specify either a task-level memory value or a container-level memory value. If you specify both a container-level memory and memoryReservation value, memory must be greater than memoryReservation . If you specify memoryReservation , then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used.

            The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers.

            The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers.

          • memoryReservation (integer) --

            The soft limit (in MiB) of memory to reserve for the container. When system memory is under heavy contention, Docker attempts to keep the container memory to this soft limit. However, your container can consume more memory when it needs to, up to either the hard limit specified with the memory parameter (if applicable), or all of the available memory on the container instance, whichever comes first. This parameter maps to MemoryReservation in the Create a container section of the Docker Remote API and the --memory-reservation option to docker run .

            If a task-level memory value is not specified, you must specify a non-zero integer for one or both of memory or memoryReservation in a container definition. If you specify both, memory must be greater than memoryReservation . If you specify memoryReservation , then that value is subtracted from the available memory resources for the container instance where the container is placed. Otherwise, the value of memory is used.

            For example, if your container normally uses 128 MiB of memory, but occasionally bursts to 256 MiB of memory for short periods of time, you can set a memoryReservation of 128 MiB, and a memory hard limit of 300 MiB. This configuration would allow the container to only reserve 128 MiB of memory from the remaining resources on the container instance, but also allow the container to consume more memory resources when needed.

            The Docker 20.10.0 or later daemon reserves a minimum of 6 MiB of memory for a container. So, don't specify less than 6 MiB of memory for your containers.

            The Docker 19.03.13-ce or earlier daemon reserves a minimum of 4 MiB of memory for a container. So, don't specify less than 4 MiB of memory for your containers.

          • links (list) --

            The links parameter allows containers to communicate with each other without the need for port mappings. This parameter is only supported if the network mode of a task definition is bridge . The name:internalName construct is analogous to name:alias in Docker links. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. For more information about linking Docker containers, go to Legacy container links in the Docker documentation. This parameter maps to Links in the Create a container section of the Docker Remote API and the --link option to docker run .

            Note

            This parameter is not supported for Windows containers.

            Warning

            Containers that are collocated on a single container instance may be able to communicate with each other without requiring links or host port mappings. Network isolation is achieved on the container instance using security groups and VPC settings.

            • (string) --

          • portMappings (list) --

            The list of port mappings for the container. Port mappings allow containers to access ports on the host container instance to send or receive traffic.

            For task definitions that use the awsvpc network mode, only specify the containerPort . The hostPort can be left blank or it must be the same value as the containerPort .

            Port mappings on Windows use the NetNAT gateway address rather than localhost . There's no loopback for port mappings on Windows, so you can't access a container's mapped port from the host itself.

            This parameter maps to PortBindings in the Create a container section of the Docker Remote API and the --publish option to docker run . If the network mode of a task definition is set to none , then you can't specify port mappings. If the network mode of a task definition is set to host , then host ports must either be undefined or they must match the container port in the port mapping.

            Note

            After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the Network Bindings section of a container description for a selected task in the Amazon ECS console. The assignments are also visible in the networkBindings section DescribeTasks responses.

            • (dict) --

              Port mappings allow containers to access ports on the host container instance to send or receive traffic. Port mappings are specified as part of the container definition.

              If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort . The hostPort can be left blank or it must be the same value as the containerPort .

              Note

              You can't expose the same container port for multiple protocols. If you attempt this, an error is returned.

              After a task reaches the RUNNING status, manual and automatic host and container port assignments are visible in the networkBindings section of DescribeTasks API responses.

              • containerPort (integer) --

                The port number on the container that's bound to the user-specified or automatically assigned host port.

                If you use containers in a task with the awsvpc or host network mode, specify the exposed ports using containerPort .

                If you use containers in a task with the bridge network mode and you specify a container port and not a host port, your container automatically receives a host port in the ephemeral port range. For more information, see hostPort . Port mappings that are automatically assigned in this way do not count toward the 100 reserved ports limit of a container instance.

              • hostPort (integer) --

                The port number on the container instance to reserve for your container.

                If you use containers in a task with the awsvpc or host network mode, the hostPort can either be left blank or set to the same value as the containerPort .

                If you use containers in a task with the bridge network mode, you can specify a non-reserved host port for your container port mapping, or you can omit the hostPort (or set it to 0 ) while specifying a containerPort and your container automatically receives a port in the ephemeral port range for your container instance operating system and Docker version.

                The default ephemeral port range for Docker version 1.6.0 and later is listed on the instance under /proc/sys/net/ipv4/ip_local_port_range . If this kernel parameter is unavailable, the default ephemeral port range from 49153 through 65535 is used. Do not attempt to specify a host port in the ephemeral port range as these are reserved for automatic assignment. In general, ports below 32768 are outside of the ephemeral port range.

                The default reserved ports are 22 for SSH, the Docker ports 2375 and 2376, and the Amazon ECS container agent ports 51678-51680. Any host port that was previously specified in a running task is also reserved while the task is running. That is, after a task stops, the host port is released. The current reserved ports are displayed in the remainingResources of DescribeContainerInstances output. A container instance can have up to 100 reserved ports at a time. This number includes the default reserved ports. Automatically assigned ports aren't included in the 100 reserved ports quota.

              • protocol (string) --

                The protocol used for the port mapping. Valid values are tcp and udp . The default is tcp .

              • name (string) --

                The name that's used for the port mapping. This parameter only applies to Service Connect. This parameter is the name that you use in the serviceConnectConfiguration of a service. Up to 64 characters are allowed. The characters can include lowercase letters, numbers, underscores (_), and hyphens (-). A hyphen can't be the first character.

                For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide .

              • appProtocol (string) --

                The application protocol that's used for the port mapping. This parameter only applies to Service Connect. We recommend that you set this parameter to be consistent with the protocol that your application uses. If you set this parameter, Amazon ECS adds protocol-specific connection handling to the Service Connect proxy. If you set this parameter, Amazon ECS adds protocol-specific telemetry in the Amazon ECS console and CloudWatch.

                If you don't set a value for this parameter, then TCP is used. However, Amazon ECS doesn't add protocol-specific telemetry for TCP.

                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 .

          • essential (boolean) --

            If the essential parameter of a container is marked as true , and that container fails or stops for any reason, all other containers that are part of the task are stopped. If the essential parameter of a container is marked as false , its failure doesn't affect the rest of the containers in a task. If this parameter is omitted, a container is assumed to be essential.

            All tasks must have at least one essential container. If you have an application that's composed of multiple containers, group containers that are used for a common purpose into components, and separate the different components into multiple task definitions. For more information, see Application Architecture in the Amazon Elastic Container Service Developer Guide .

          • entryPoint (list) --

            Warning

            Early versions of the Amazon ECS container agent don't properly handle entryPoint parameters. If you have problems using entryPoint , update your container agent or enter your commands and arguments as command array items instead.

            The entry point that's passed to the container. This parameter maps to Entrypoint in the Create a container section of the Docker Remote API and the --entrypoint option to docker run . For more information, see https://docs.docker.com/engine/reference/builder/#entrypoint .

            • (string) --

          • command (list) --

            The command that's passed to the container. This parameter maps to Cmd in the Create a container section of the Docker Remote API and the COMMAND parameter to docker run . For more information, see https://docs.docker.com/engine/reference/builder/#cmd . If there are multiple arguments, each argument is a separated string in the array.

            • (string) --

          • environment (list) --

            The environment variables to pass to a container. This parameter maps to Env in the Create a container section of the Docker Remote API and the --env option to docker run .

            Warning

            We don't recommend that you use plaintext environment variables for sensitive information, such as credential data.

            • (dict) --

              A key-value pair object.

              • name (string) --

                The name of the key-value pair. For environment variables, this is the name of the environment variable.

              • value (string) --

                The value of the key-value pair. For environment variables, this is the value of the environment variable.

          • environmentFiles (list) --

            A list of files containing the environment variables to pass to a container. This parameter maps to the --env-file option to docker run .

            You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file contains an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

            If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying Environment Variables in the Amazon Elastic Container Service Developer Guide .

            • (dict) --

              A list of files containing the environment variables to pass to a container. You can specify up to ten environment files. The file must have a .env file extension. Each line in an environment file should contain an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information about the environment variable file syntax, see Declare default environment variables in file .

              If there are environment variables specified using the environment parameter in a container definition, they take precedence over the variables contained within an environment file. If multiple environment files are specified that contain the same variable, they're processed from the top down. We recommend that you use unique variable names. For more information, see Specifying environment variables in the Amazon Elastic Container Service Developer Guide .

              This parameter is only supported for tasks hosted on Fargate using the following platform versions:

              • Linux platform version 1.4.0 or later.

              • Windows platform version 1.0.0 or later.

              • value (string) --

                The Amazon Resource Name (ARN) of the Amazon S3 object containing the environment variable file.

              • type (string) --

                The file type to use. The only supported value is s3 .

          • mountPoints (list) --

            The mount points for data volumes in your container.

            This parameter maps to Volumes in the Create a container section of the Docker Remote API and the --volume option to docker run .

            Windows containers can mount whole directories on the same drive as $env:ProgramData . Windows containers can't mount directories on a different drive, and mount point can't be across drives.

            • (dict) --

              Details for a volume mount point that's used in a container definition.

              • sourceVolume (string) --

                The name of the volume to mount. Must be a volume name referenced in the name parameter of task definition volume .

              • containerPath (string) --

                The path on the container to mount the host volume at.

              • readOnly (boolean) --

                If this value is true , the container has read-only access to the volume. If this value is false , then the container can write to the volume. The default value is false .

          • volumesFrom (list) --

            Data volumes to mount from another container. This parameter maps to VolumesFrom in the Create a container section of the Docker Remote API and the --volumes-from option to docker run .

            • (dict) --

              Details on a data volume from another container in the same task definition.

              • sourceContainer (string) --

                The name of another container within the same task definition to mount volumes from.

              • readOnly (boolean) --

                If this value is true , the container has read-only access to the volume. If this value is false , then the container can write to the volume. The default value is false .

          • linuxParameters (dict) --

            Linux-specific modifications that are applied to the container, such as Linux kernel capabilities. For more information see KernelCapabilities .

            Note

            This parameter is not supported for Windows containers.

            • capabilities (dict) --

              The Linux capabilities for the container that are added to or dropped from the default configuration provided by Docker.

              Note

              For tasks that use the Fargate launch type, capabilities is supported for all platform versions but the add parameter is only supported if using platform version 1.4.0 or later.

              • add (list) --

                The Linux capabilities for the container that have been added to the default configuration provided by Docker. This parameter maps to CapAdd in the Create a container section of the Docker Remote API and the --cap-add option to docker run .

                Note

                Tasks launched on Fargate only support adding the SYS_PTRACE kernel capability.

                Valid values: "ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" | "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" | "FOWNER" | "FSETID" | "IPC_LOCK" | "IPC_OWNER" | "KILL" | "LEASE" | "LINUX_IMMUTABLE" | "MAC_ADMIN" | "MAC_OVERRIDE" | "MKNOD" | "NET_ADMIN" | "NET_BIND_SERVICE" | "NET_BROADCAST" | "NET_RAW" | "SETFCAP" | "SETGID" | "SETPCAP" | "SETUID" | "SYS_ADMIN" | "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT" | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" | "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"

                • (string) --

              • drop (list) --

                The Linux capabilities for the container that have been removed from the default configuration provided by Docker. This parameter maps to CapDrop in the Create a container section of the Docker Remote API and the --cap-drop option to docker run .

                Valid values: "ALL" | "AUDIT_CONTROL" | "AUDIT_WRITE" | "BLOCK_SUSPEND" | "CHOWN" | "DAC_OVERRIDE" | "DAC_READ_SEARCH" | "FOWNER" | "FSETID" | "IPC_LOCK" | "IPC_OWNER" | "KILL" | "LEASE" | "LINUX_IMMUTABLE" | "MAC_ADMIN" | "MAC_OVERRIDE" | "MKNOD" | "NET_ADMIN" | "NET_BIND_SERVICE" | "NET_BROADCAST" | "NET_RAW" | "SETFCAP" | "SETGID" | "SETPCAP" | "SETUID" | "SYS_ADMIN" | "SYS_BOOT" | "SYS_CHROOT" | "SYS_MODULE" | "SYS_NICE" | "SYS_PACCT" | "SYS_PTRACE" | "SYS_RAWIO" | "SYS_RESOURCE" | "SYS_TIME" | "SYS_TTY_CONFIG" | "SYSLOG" | "WAKE_ALARM"

                • (string) --

            • devices (list) --

              Any host devices to expose to the container. This parameter maps to Devices in the Create a container section of the Docker Remote API and the --device option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the devices parameter isn't supported.

              • (dict) --

                An object representing a container instance host device.

                • hostPath (string) --

                  The path for the device on the host container instance.

                • containerPath (string) --

                  The path inside the container at which to expose the host device.

                • permissions (list) --

                  The explicit permissions to provide to the container for the device. By default, the container has permissions for read , write , and mknod for the device.

                  • (string) --

            • initProcessEnabled (boolean) --

              Run an init process inside the container that forwards signals and reaps processes. This parameter maps to the --init option to docker run . This parameter requires version 1.25 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

            • sharedMemorySize (integer) --

              The value for the size (in MiB) of the /dev/shm volume. This parameter maps to the --shm-size option to docker run .

              Note

              If you are using tasks that use the Fargate launch type, the sharedMemorySize parameter is not supported.

            • tmpfs (list) --

              The container path, mount options, and size (in MiB) of the tmpfs mount. This parameter maps to the --tmpfs option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the tmpfs parameter isn't supported.

              • (dict) --

                The container path, mount options, and size of the tmpfs mount.

                • containerPath (string) --

                  The absolute file path where the tmpfs volume is to be mounted.

                • size (integer) --

                  The maximum size (in MiB) of the tmpfs volume.

                • mountOptions (list) --

                  The list of tmpfs volume mount options.

                  Valid values: "defaults" | "ro" | "rw" | "suid" | "nosuid" | "dev" | "nodev" | "exec" | "noexec" | "sync" | "async" | "dirsync" | "remount" | "mand" | "nomand" | "atime" | "noatime" | "diratime" | "nodiratime" | "bind" | "rbind" | "unbindable" | "runbindable" | "private" | "rprivate" | "shared" | "rshared" | "slave" | "rslave" | "relatime" | "norelatime" | "strictatime" | "nostrictatime" | "mode" | "uid" | "gid" | "nr_inodes" | "nr_blocks" | "mpol"

                  • (string) --

            • maxSwap (integer) --

              The total amount of swap memory (in MiB) a container can use. This parameter will be translated to the --memory-swap option to docker run where the value would be the sum of the container memory plus the maxSwap value.

              If a maxSwap value of 0 is specified, the container will not use swap. Accepted values are 0 or any positive integer. If the maxSwap parameter is omitted, the container will use the swap configuration for the container instance it is running on. A maxSwap value must be set for the swappiness parameter to be used.

              Note

              If you're using tasks that use the Fargate launch type, the maxSwap parameter isn't supported.

            • swappiness (integer) --

              This allows you to tune a container's memory swappiness behavior. A swappiness value of 0 will cause swapping to not happen unless absolutely necessary. A swappiness value of 100 will cause pages to be swapped very aggressively. Accepted values are whole numbers between 0 and 100 . If the swappiness parameter is not specified, a default value of 60 is used. If a value is not specified for maxSwap then this parameter is ignored. This parameter maps to the --memory-swappiness option to docker run .

              Note

              If you're using tasks that use the Fargate launch type, the swappiness parameter isn't supported.

          • secrets (list) --

            The secrets to pass to the container. For more information, see Specifying Sensitive Data in the Amazon Elastic Container Service Developer Guide .

            • (dict) --

              An object representing the secret to expose to your container. Secrets can be exposed to a container in the following ways:

              • To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

              • To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

              For more information, see Specifying sensitive data in the Amazon Elastic Container Service Developer Guide .

              • name (string) --

                The name of the secret.

              • valueFrom (string) --

                The secret to expose to the container. The supported values are either the full ARN of the Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.

                For information about the require Identity and Access Management permissions, see Required IAM permissions for Amazon ECS secrets (for Secrets Manager) or Required IAM permissions for Amazon ECS secrets (for Systems Manager Parameter store) in the Amazon Elastic Container Service Developer Guide .

                Note

                If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.

          • dependsOn (list) --

            The dependencies defined for container startup and shutdown. A container can contain multiple dependencies on other containers in a task definition. When a dependency is defined for container startup, for container shutdown it is reversed.

            For tasks using the EC2 launch type, the container instances require at least version 1.26.0 of the container agent to turn on container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            • (dict) --

              The dependencies defined for container startup and shutdown. A container can contain multiple dependencies. When a dependency is defined for container startup, for container shutdown it is reversed.

              Your Amazon ECS container instances require at least version 1.26.0 of the container agent to use container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

              Note

              For tasks that use the Fargate launch type, the task or service requires the following platforms:

              • Linux platform version 1.3.0 or later.

              • Windows platform version 1.0.0 or later.

              • containerName (string) --

                The name of a container.

              • condition (string) --

                The dependency condition of the container. The following are the available conditions and their behavior:

                • START - This condition emulates the behavior of links and volumes today. It validates that a dependent container is started before permitting other containers to start.

                • COMPLETE - This condition validates that a dependent container runs to completion (exits) before permitting other containers to start. This can be useful for nonessential containers that run a script and then exit. This condition can't be set on an essential container.

                • SUCCESS - This condition is the same as COMPLETE , but it also requires that the container exits with a zero status. This condition can't be set on an essential container.

                • HEALTHY - This condition validates that the dependent container passes its Docker health check before permitting other containers to start. This requires that the dependent container has health checks configured. This condition is confirmed only at task startup.

          • startTimeout (integer) --

            Time duration (in seconds) to wait before giving up on resolving dependencies for a container. For example, you specify two containers in a task definition with containerA having a dependency on containerB reaching a COMPLETE , SUCCESS , or HEALTHY status. If a startTimeout value is specified for containerB and it doesn't reach the desired status within that time then containerA gives up and not start. This results in the task transitioning to a STOPPED state.

            Note

            When the ECS_CONTAINER_START_TIMEOUT container agent configuration variable is used, it's enforced independently from this start timeout value.

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            For tasks using the EC2 launch type, your container instances require at least version 1.26.0 of the container agent to use a container start timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

          • stopTimeout (integer) --

            Time duration (in seconds) to wait before the container is forcefully killed if it doesn't exit normally on its own.

            For tasks using the Fargate launch type, the task or service requires the following platforms:

            • Linux platform version 1.3.0 or later.

            • Windows platform version 1.0.0 or later.

            The max stop timeout value is 120 seconds and if the parameter is not specified, the default value of 30 seconds is used.

            For tasks that use the EC2 launch type, if the stopTimeout parameter isn't specified, the value set for the Amazon ECS container agent configuration variable ECS_CONTAINER_STOP_TIMEOUT is used. If neither the stopTimeout parameter or the ECS_CONTAINER_STOP_TIMEOUT agent configuration variable are set, then the default values of 30 seconds for Linux containers and 30 seconds on Windows containers are used. Your container instances require at least version 1.26.0 of the container agent to use a container stop timeout value. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide . If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init . For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide .

          • hostname (string) --

            The hostname to use for your container. This parameter maps to Hostname in the Create a container section of the Docker Remote API and the --hostname option to docker run .

            Note

            The hostname parameter is not supported if you're using the awsvpc network mode.

          • user (string) --

            The user to use inside the container. This parameter maps to User in the Create a container section of the Docker Remote API and the --user option to docker run .

            Warning

            When running tasks using the host network mode, don't run containers using the root user (UID 0). We recommend using a non-root user for better security.

            You can specify the user using the following formats. If specifying a UID or GID, you must specify it as a positive integer.

            • user

            • user:group

            • uid

            • uid:gid

            • user:gid

            • uid:group

            Note

            This parameter is not supported for Windows containers.

          • workingDirectory (string) --

            The working directory to run commands inside the container in. This parameter maps to WorkingDir in the Create a container section of the Docker Remote API and the --workdir option to docker run .

          • disableNetworking (boolean) --

            When this parameter is true, networking is disabled within the container. This parameter maps to NetworkDisabled in the Create a container section of the Docker Remote API .

            Note

            This parameter is not supported for Windows containers.

          • privileged (boolean) --

            When this parameter is true, the container is given elevated privileges on the host container instance (similar to the root user). This parameter maps to Privileged in the Create a container section of the Docker Remote API and the --privileged option to docker run .

            Note

            This parameter is not supported for Windows containers or tasks run on Fargate.

          • readonlyRootFilesystem (boolean) --

            When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs in the Create a container section of the Docker Remote API and the --read-only option to