1  import {Request} from '../lib/request';
   2  import {Response} from '../lib/response';
   3  import {AWSError} from '../lib/error';
   4  import {Service} from '../lib/service';
   5  import {WaiterConfiguration} from '../lib/service';
   6  import {ServiceConfigurationOptions} from '../lib/service';
   7  import {ConfigBase as Config} from '../lib/config-base';
   8  interface Blob {}
   9  declare class ECS extends Service {
  10    /**
  11     * Constructs a service object. This object has one method for each API operation.
  12     */
  13    constructor(options?: ECS.Types.ClientConfiguration)
  14    config: Config & ECS.Types.ClientConfiguration;
  15    /**
  16     * Creates a new capacity provider. Capacity providers are associated with an Amazon ECS cluster and are used in capacity provider strategies to facilitate cluster auto scaling. Only capacity providers using an Auto Scaling group can be created. Amazon ECS tasks on Fargate use the FARGATE and FARGATE_SPOT capacity providers which are already created and available to all accounts in Regions supported by Fargate.
  17     */
  18    createCapacityProvider(params: ECS.Types.CreateCapacityProviderRequest, callback?: (err: AWSError, data: ECS.Types.CreateCapacityProviderResponse) => void): Request<ECS.Types.CreateCapacityProviderResponse, AWSError>;
  19    /**
  20     * Creates a new capacity provider. Capacity providers are associated with an Amazon ECS cluster and are used in capacity provider strategies to facilitate cluster auto scaling. Only capacity providers using an Auto Scaling group can be created. Amazon ECS tasks on Fargate use the FARGATE and FARGATE_SPOT capacity providers which are already created and available to all accounts in Regions supported by Fargate.
  21     */
  22    createCapacityProvider(callback?: (err: AWSError, data: ECS.Types.CreateCapacityProviderResponse) => void): Request<ECS.Types.CreateCapacityProviderResponse, AWSError>;
  23    /**
  24     * 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.  When you call the CreateCluster API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for your account so that required resources in other Amazon Web Services services can be managed on your behalf. However, if the IAM user that makes the call does not have permissions to create the service-linked role, it is not created. For more information, see Using Service-Linked Roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. 
  25     */
  26    createCluster(params: ECS.Types.CreateClusterRequest, callback?: (err: AWSError, data: ECS.Types.CreateClusterResponse) => void): Request<ECS.Types.CreateClusterResponse, AWSError>;
  27    /**
  28     * 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.  When you call the CreateCluster API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for your account so that required resources in other Amazon Web Services services can be managed on your behalf. However, if the IAM user that makes the call does not have permissions to create the service-linked role, it is not created. For more information, see Using Service-Linked Roles for Amazon ECS in the Amazon Elastic Container Service Developer Guide. 
  29     */
  30    createCluster(callback?: (err: AWSError, data: ECS.Types.CreateClusterResponse) => void): Request<ECS.Types.CreateClusterResponse, AWSError>;
  31    /**
  32     * Runs and maintains a 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 do not use a load balancer are considered healthy if they're in the RUNNING state. Tasks for services that do use a load balancer are considered healthy if they're in the RUNNING state and the container instance that they're hosted on is reported as healthy by the load balancer. 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. 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 and will stop tasks that do not 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 triggered by changing properties, such as the task definition or the desired count of a service, 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 is using 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, as a percentage of the desired number of tasks (rounded up to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a 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. Tasks for services that do not use a load balancer are considered healthy if they're in the RUNNING state. Tasks for services that do use a load balancer are considered healthy if they're in the RUNNING state and they're reported as healthy by the load balancer. The default value for minimum healthy percent is 100%. If a service is using 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, as a percentage of the desired number of tasks (rounded down to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to 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 is using 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 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, although 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 in your cluster using the following logic:   Determine which of the container instances in your cluster can support your service's task definition (for example, they have the required CPU, memory, ports, and container instance attributes).   By default, the service scheduler attempts to balance tasks across Availability Zones in this manner (although you can choose a different placement strategy) with the placementStrategy parameter):   Sort the valid container instances, giving priority to instances that have the fewest number of running tasks for this service in their respective Availability Zone. For example, if zone A has one running service task and zones B and C each have zero, valid container instances in either zone B or C are considered optimal for placement.   Place the new service task on a valid container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the fewest number of running tasks for this service.    
  33     */
  34    createService(params: ECS.Types.CreateServiceRequest, callback?: (err: AWSError, data: ECS.Types.CreateServiceResponse) => void): Request<ECS.Types.CreateServiceResponse, AWSError>;
  35    /**
  36     * Runs and maintains a 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 do not use a load balancer are considered healthy if they're in the RUNNING state. Tasks for services that do use a load balancer are considered healthy if they're in the RUNNING state and the container instance that they're hosted on is reported as healthy by the load balancer. 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. 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 and will stop tasks that do not 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 triggered by changing properties, such as the task definition or the desired count of a service, 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 is using 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, as a percentage of the desired number of tasks (rounded up to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a 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. Tasks for services that do not use a load balancer are considered healthy if they're in the RUNNING state. Tasks for services that do use a load balancer are considered healthy if they're in the RUNNING state and they're reported as healthy by the load balancer. The default value for minimum healthy percent is 100%. If a service is using 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, as a percentage of the desired number of tasks (rounded down to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to 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 is using 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 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, although 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 in your cluster using the following logic:   Determine which of the container instances in your cluster can support your service's task definition (for example, they have the required CPU, memory, ports, and container instance attributes).   By default, the service scheduler attempts to balance tasks across Availability Zones in this manner (although you can choose a different placement strategy) with the placementStrategy parameter):   Sort the valid container instances, giving priority to instances that have the fewest number of running tasks for this service in their respective Availability Zone. For example, if zone A has one running service task and zones B and C each have zero, valid container instances in either zone B or C are considered optimal for placement.   Place the new service task on a valid container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the fewest number of running tasks for this service.    
  37     */
  38    createService(callback?: (err: AWSError, data: ECS.Types.CreateServiceResponse) => void): Request<ECS.Types.CreateServiceResponse, AWSError>;
  39    /**
  40     * Create a task set in the specified cluster and service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
  41     */
  42    createTaskSet(params: ECS.Types.CreateTaskSetRequest, callback?: (err: AWSError, data: ECS.Types.CreateTaskSetResponse) => void): Request<ECS.Types.CreateTaskSetResponse, AWSError>;
  43    /**
  44     * Create a task set in the specified cluster and service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
  45     */
  46    createTaskSet(callback?: (err: AWSError, data: ECS.Types.CreateTaskSetResponse) => void): Request<ECS.Types.CreateTaskSetResponse, AWSError>;
  47    /**
  48     * Disables an account setting for a specified IAM user, IAM role, or the root user for an account.
  49     */
  50    deleteAccountSetting(params: ECS.Types.DeleteAccountSettingRequest, callback?: (err: AWSError, data: ECS.Types.DeleteAccountSettingResponse) => void): Request<ECS.Types.DeleteAccountSettingResponse, AWSError>;
  51    /**
  52     * Disables an account setting for a specified IAM user, IAM role, or the root user for an account.
  53     */
  54    deleteAccountSetting(callback?: (err: AWSError, data: ECS.Types.DeleteAccountSettingResponse) => void): Request<ECS.Types.DeleteAccountSettingResponse, AWSError>;
  55    /**
  56     * Deletes one or more custom attributes from an Amazon ECS resource.
  57     */
  58    deleteAttributes(params: ECS.Types.DeleteAttributesRequest, callback?: (err: AWSError, data: ECS.Types.DeleteAttributesResponse) => void): Request<ECS.Types.DeleteAttributesResponse, AWSError>;
  59    /**
  60     * Deletes one or more custom attributes from an Amazon ECS resource.
  61     */
  62    deleteAttributes(callback?: (err: AWSError, data: ECS.Types.DeleteAttributesResponse) => void): Request<ECS.Types.DeleteAttributesResponse, AWSError>;
  63    /**
  64     * Deletes the specified capacity provider.  The FARGATE and FARGATE_SPOT capacity providers are reserved and cannot be deleted. You can disassociate them from a cluster using either the PutClusterCapacityProviders API or by deleting the cluster.  Prior to a capacity provider being deleted, the capacity provider must be removed from the capacity provider strategy from all services. The UpdateService API can be used to remove a capacity provider from a service's capacity provider strategy. When updating a service, the forceNewDeployment option can be used to ensure that any tasks using the Amazon EC2 instance capacity provided by the capacity provider are transitioned to use the capacity from the remaining capacity providers. Only capacity providers that are not associated with a cluster can be deleted. To remove a capacity provider from a cluster, you can either use PutClusterCapacityProviders or delete the cluster.
  65     */
  66    deleteCapacityProvider(params: ECS.Types.DeleteCapacityProviderRequest, callback?: (err: AWSError, data: ECS.Types.DeleteCapacityProviderResponse) => void): Request<ECS.Types.DeleteCapacityProviderResponse, AWSError>;
  67    /**
  68     * Deletes the specified capacity provider.  The FARGATE and FARGATE_SPOT capacity providers are reserved and cannot be deleted. You can disassociate them from a cluster using either the PutClusterCapacityProviders API or by deleting the cluster.  Prior to a capacity provider being deleted, the capacity provider must be removed from the capacity provider strategy from all services. The UpdateService API can be used to remove a capacity provider from a service's capacity provider strategy. When updating a service, the forceNewDeployment option can be used to ensure that any tasks using the Amazon EC2 instance capacity provided by the capacity provider are transitioned to use the capacity from the remaining capacity providers. Only capacity providers that are not associated with a cluster can be deleted. To remove a capacity provider from a cluster, you can either use PutClusterCapacityProviders or delete the cluster.
  69     */
  70    deleteCapacityProvider(callback?: (err: AWSError, data: ECS.Types.DeleteCapacityProviderResponse) => void): Request<ECS.Types.DeleteCapacityProviderResponse, AWSError>;
  71    /**
  72     * Deletes the specified cluster. The cluster will transition to the INACTIVE state. 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, so you should not 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.
  73     */
  74    deleteCluster(params: ECS.Types.DeleteClusterRequest, callback?: (err: AWSError, data: ECS.Types.DeleteClusterResponse) => void): Request<ECS.Types.DeleteClusterResponse, AWSError>;
  75    /**
  76     * Deletes the specified cluster. The cluster will transition to the INACTIVE state. 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, so you should not 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.
  77     */
  78    deleteCluster(callback?: (err: AWSError, data: ECS.Types.DeleteClusterResponse) => void): Request<ECS.Types.DeleteClusterResponse, AWSError>;
  79    /**
  80     * 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 cannot delete it, and you must update the service to a desired task count of zero. For more information, see UpdateService.  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.   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. 
  81     */
  82    deleteService(params: ECS.Types.DeleteServiceRequest, callback?: (err: AWSError, data: ECS.Types.DeleteServiceResponse) => void): Request<ECS.Types.DeleteServiceResponse, AWSError>;
  83    /**
  84     * 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 cannot delete it, and you must update the service to a desired task count of zero. For more information, see UpdateService.  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.   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. 
  85     */
  86    deleteService(callback?: (err: AWSError, data: ECS.Types.DeleteServiceResponse) => void): Request<ECS.Types.DeleteServiceResponse, AWSError>;
  87    /**
  88     * Deletes a specified task set within a service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
  89     */
  90    deleteTaskSet(params: ECS.Types.DeleteTaskSetRequest, callback?: (err: AWSError, data: ECS.Types.DeleteTaskSetResponse) => void): Request<ECS.Types.DeleteTaskSetResponse, AWSError>;
  91    /**
  92     * Deletes a specified task set within a service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
  93     */
  94    deleteTaskSet(callback?: (err: AWSError, data: ECS.Types.DeleteTaskSetResponse) => void): Request<ECS.Types.DeleteTaskSetResponse, AWSError>;
  95    /**
  96     * Deregisters an Amazon ECS container instance from the specified cluster. This instance is no longer available to run tasks. If you intend to use the container instance for some other purpose after deregistration, you should stop all of the tasks running on the container instance before deregistration. That prevents any orphaned tasks from consuming resources. Deregistering a container instance removes the instance from a cluster, but it does not terminate the EC2 instance. If you are finished using the instance, be sure to terminate it in the Amazon EC2 console to stop billing.  If you terminate a running container instance, Amazon ECS automatically deregisters the instance from your cluster (stopped container instances or instances with disconnected agents are not automatically deregistered when terminated). 
  97     */
  98    deregisterContainerInstance(params: ECS.Types.DeregisterContainerInstanceRequest, callback?: (err: AWSError, data: ECS.Types.DeregisterContainerInstanceResponse) => void): Request<ECS.Types.DeregisterContainerInstanceResponse, AWSError>;
  99    /**
 100     * Deregisters an Amazon ECS container instance from the specified cluster. This instance is no longer available to run tasks. If you intend to use the container instance for some other purpose after deregistration, you should stop all of the tasks running on the container instance before deregistration. That prevents any orphaned tasks from consuming resources. Deregistering a container instance removes the instance from a cluster, but it does not terminate the EC2 instance. If you are finished using the instance, be sure to terminate it in the Amazon EC2 console to stop billing.  If you terminate a running container instance, Amazon ECS automatically deregisters the instance from your cluster (stopped container instances or instances with disconnected agents are not automatically deregistered when terminated). 
 101     */
 102    deregisterContainerInstance(callback?: (err: AWSError, data: ECS.Types.DeregisterContainerInstanceResponse) => void): Request<ECS.Types.DeregisterContainerInstanceResponse, AWSError>;
 103    /**
 104     * 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 cannot use an INACTIVE task definition to run new tasks or create new services, and you cannot 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.  At this time, INACTIVE task definitions remain discoverable in your account indefinitely. However, this behavior is subject to change in the future, so you should not rely on INACTIVE task definitions persisting beyond the lifecycle of any associated tasks and services. 
 105     */
 106    deregisterTaskDefinition(params: ECS.Types.DeregisterTaskDefinitionRequest, callback?: (err: AWSError, data: ECS.Types.DeregisterTaskDefinitionResponse) => void): Request<ECS.Types.DeregisterTaskDefinitionResponse, AWSError>;
 107    /**
 108     * 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 cannot use an INACTIVE task definition to run new tasks or create new services, and you cannot 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.  At this time, INACTIVE task definitions remain discoverable in your account indefinitely. However, this behavior is subject to change in the future, so you should not rely on INACTIVE task definitions persisting beyond the lifecycle of any associated tasks and services. 
 109     */
 110    deregisterTaskDefinition(callback?: (err: AWSError, data: ECS.Types.DeregisterTaskDefinitionResponse) => void): Request<ECS.Types.DeregisterTaskDefinitionResponse, AWSError>;
 111    /**
 112     * Describes one or more of your capacity providers.
 113     */
 114    describeCapacityProviders(params: ECS.Types.DescribeCapacityProvidersRequest, callback?: (err: AWSError, data: ECS.Types.DescribeCapacityProvidersResponse) => void): Request<ECS.Types.DescribeCapacityProvidersResponse, AWSError>;
 115    /**
 116     * Describes one or more of your capacity providers.
 117     */
 118    describeCapacityProviders(callback?: (err: AWSError, data: ECS.Types.DescribeCapacityProvidersResponse) => void): Request<ECS.Types.DescribeCapacityProvidersResponse, AWSError>;
 119    /**
 120     * Describes one or more of your clusters.
 121     */
 122    describeClusters(params: ECS.Types.DescribeClustersRequest, callback?: (err: AWSError, data: ECS.Types.DescribeClustersResponse) => void): Request<ECS.Types.DescribeClustersResponse, AWSError>;
 123    /**
 124     * Describes one or more of your clusters.
 125     */
 126    describeClusters(callback?: (err: AWSError, data: ECS.Types.DescribeClustersResponse) => void): Request<ECS.Types.DescribeClustersResponse, AWSError>;
 127    /**
 128     * Describes one or more container instances. Returns metadata about each container instance requested.
 129     */
 130    describeContainerInstances(params: ECS.Types.DescribeContainerInstancesRequest, callback?: (err: AWSError, data: ECS.Types.DescribeContainerInstancesResponse) => void): Request<ECS.Types.DescribeContainerInstancesResponse, AWSError>;
 131    /**
 132     * Describes one or more container instances. Returns metadata about each container instance requested.
 133     */
 134    describeContainerInstances(callback?: (err: AWSError, data: ECS.Types.DescribeContainerInstancesResponse) => void): Request<ECS.Types.DescribeContainerInstancesResponse, AWSError>;
 135    /**
 136     * Describes the specified services running in your cluster.
 137     */
 138    describeServices(params: ECS.Types.DescribeServicesRequest, callback?: (err: AWSError, data: ECS.Types.DescribeServicesResponse) => void): Request<ECS.Types.DescribeServicesResponse, AWSError>;
 139    /**
 140     * Describes the specified services running in your cluster.
 141     */
 142    describeServices(callback?: (err: AWSError, data: ECS.Types.DescribeServicesResponse) => void): Request<ECS.Types.DescribeServicesResponse, AWSError>;
 143    /**
 144     * 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.  You can only describe INACTIVE task definitions while an active task or service references them. 
 145     */
 146    describeTaskDefinition(params: ECS.Types.DescribeTaskDefinitionRequest, callback?: (err: AWSError, data: ECS.Types.DescribeTaskDefinitionResponse) => void): Request<ECS.Types.DescribeTaskDefinitionResponse, AWSError>;
 147    /**
 148     * 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.  You can only describe INACTIVE task definitions while an active task or service references them. 
 149     */
 150    describeTaskDefinition(callback?: (err: AWSError, data: ECS.Types.DescribeTaskDefinitionResponse) => void): Request<ECS.Types.DescribeTaskDefinitionResponse, AWSError>;
 151    /**
 152     * Describes the task sets in the specified cluster and service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
 153     */
 154    describeTaskSets(params: ECS.Types.DescribeTaskSetsRequest, callback?: (err: AWSError, data: ECS.Types.DescribeTaskSetsResponse) => void): Request<ECS.Types.DescribeTaskSetsResponse, AWSError>;
 155    /**
 156     * Describes the task sets in the specified cluster and service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
 157     */
 158    describeTaskSets(callback?: (err: AWSError, data: ECS.Types.DescribeTaskSetsResponse) => void): Request<ECS.Types.DescribeTaskSetsResponse, AWSError>;
 159    /**
 160     * Describes a specified task or tasks.
 161     */
 162    describeTasks(params: ECS.Types.DescribeTasksRequest, callback?: (err: AWSError, data: ECS.Types.DescribeTasksResponse) => void): Request<ECS.Types.DescribeTasksResponse, AWSError>;
 163    /**
 164     * Describes a specified task or tasks.
 165     */
 166    describeTasks(callback?: (err: AWSError, data: ECS.Types.DescribeTasksResponse) => void): Request<ECS.Types.DescribeTasksResponse, AWSError>;
 167    /**
 168     *  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.
 169     */
 170    discoverPollEndpoint(params: ECS.Types.DiscoverPollEndpointRequest, callback?: (err: AWSError, data: ECS.Types.DiscoverPollEndpointResponse) => void): Request<ECS.Types.DiscoverPollEndpointResponse, AWSError>;
 171    /**
 172     *  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.
 173     */
 174    discoverPollEndpoint(callback?: (err: AWSError, data: ECS.Types.DiscoverPollEndpointResponse) => void): Request<ECS.Types.DiscoverPollEndpointResponse, AWSError>;
 175    /**
 176     * Runs a command remotely on a container within a task.
 177     */
 178    executeCommand(params: ECS.Types.ExecuteCommandRequest, callback?: (err: AWSError, data: ECS.Types.ExecuteCommandResponse) => void): Request<ECS.Types.ExecuteCommandResponse, AWSError>;
 179    /**
 180     * Runs a command remotely on a container within a task.
 181     */
 182    executeCommand(callback?: (err: AWSError, data: ECS.Types.ExecuteCommandResponse) => void): Request<ECS.Types.ExecuteCommandResponse, AWSError>;
 183    /**
 184     * Lists the account settings for a specified principal.
 185     */
 186    listAccountSettings(params: ECS.Types.ListAccountSettingsRequest, callback?: (err: AWSError, data: ECS.Types.ListAccountSettingsResponse) => void): Request<ECS.Types.ListAccountSettingsResponse, AWSError>;
 187    /**
 188     * Lists the account settings for a specified principal.
 189     */
 190    listAccountSettings(callback?: (err: AWSError, data: ECS.Types.ListAccountSettingsResponse) => void): Request<ECS.Types.ListAccountSettingsResponse, AWSError>;
 191    /**
 192     * Lists the attributes for Amazon ECS resources within a specified target type and cluster. When you specify a target type and cluster, ListAttributes returns a list of attribute objects, one for each attribute on each resource. You can filter the list of results to a single attribute name to only return results that have that name. You can also filter the results by attribute name and value, for example, to see which container instances in a cluster are running a Linux AMI (ecs.os-type=linux). 
 193     */
 194    listAttributes(params: ECS.Types.ListAttributesRequest, callback?: (err: AWSError, data: ECS.Types.ListAttributesResponse) => void): Request<ECS.Types.ListAttributesResponse, AWSError>;
 195    /**
 196     * Lists the attributes for Amazon ECS resources within a specified target type and cluster. When you specify a target type and cluster, ListAttributes returns a list of attribute objects, one for each attribute on each resource. You can filter the list of results to a single attribute name to only return results that have that name. You can also filter the results by attribute name and value, for example, to see which container instances in a cluster are running a Linux AMI (ecs.os-type=linux). 
 197     */
 198    listAttributes(callback?: (err: AWSError, data: ECS.Types.ListAttributesResponse) => void): Request<ECS.Types.ListAttributesResponse, AWSError>;
 199    /**
 200     * Returns a list of existing clusters.
 201     */
 202    listClusters(params: ECS.Types.ListClustersRequest, callback?: (err: AWSError, data: ECS.Types.ListClustersResponse) => void): Request<ECS.Types.ListClustersResponse, AWSError>;
 203    /**
 204     * Returns a list of existing clusters.
 205     */
 206    listClusters(callback?: (err: AWSError, data: ECS.Types.ListClustersResponse) => void): Request<ECS.Types.ListClustersResponse, AWSError>;
 207    /**
 208     * Returns a list of container instances in a specified cluster. You can filter the results of a ListContainerInstances operation with cluster query language statements inside the filter parameter. For more information, see Cluster Query Language in the Amazon Elastic Container Service Developer Guide.
 209     */
 210    listContainerInstances(params: ECS.Types.ListContainerInstancesRequest, callback?: (err: AWSError, data: ECS.Types.ListContainerInstancesResponse) => void): Request<ECS.Types.ListContainerInstancesResponse, AWSError>;
 211    /**
 212     * Returns a list of container instances in a specified cluster. You can filter the results of a ListContainerInstances operation with cluster query language statements inside the filter parameter. For more information, see Cluster Query Language in the Amazon Elastic Container Service Developer Guide.
 213     */
 214    listContainerInstances(callback?: (err: AWSError, data: ECS.Types.ListContainerInstancesResponse) => void): Request<ECS.Types.ListContainerInstancesResponse, AWSError>;
 215    /**
 216     * Returns a list of services. You can filter the results by cluster, launch type, and scheduling strategy.
 217     */
 218    listServices(params: ECS.Types.ListServicesRequest, callback?: (err: AWSError, data: ECS.Types.ListServicesResponse) => void): Request<ECS.Types.ListServicesResponse, AWSError>;
 219    /**
 220     * Returns a list of services. You can filter the results by cluster, launch type, and scheduling strategy.
 221     */
 222    listServices(callback?: (err: AWSError, data: ECS.Types.ListServicesResponse) => void): Request<ECS.Types.ListServicesResponse, AWSError>;
 223    /**
 224     * List the tags for an Amazon ECS resource.
 225     */
 226    listTagsForResource(params: ECS.Types.ListTagsForResourceRequest, callback?: (err: AWSError, data: ECS.Types.ListTagsForResourceResponse) => void): Request<ECS.Types.ListTagsForResourceResponse, AWSError>;
 227    /**
 228     * List the tags for an Amazon ECS resource.
 229     */
 230    listTagsForResource(callback?: (err: AWSError, data: ECS.Types.ListTagsForResourceResponse) => void): Request<ECS.Types.ListTagsForResourceResponse, AWSError>;
 231    /**
 232     * Returns a list of task definition families that are registered to your account (which may include task definition families that no longer have any ACTIVE task definition revisions). You can filter out task definition families that do not contain any ACTIVE task definition revisions by setting the status parameter to ACTIVE. You can also filter the results with the familyPrefix parameter.
 233     */
 234    listTaskDefinitionFamilies(params: ECS.Types.ListTaskDefinitionFamiliesRequest, callback?: (err: AWSError, data: ECS.Types.ListTaskDefinitionFamiliesResponse) => void): Request<ECS.Types.ListTaskDefinitionFamiliesResponse, AWSError>;
 235    /**
 236     * Returns a list of task definition families that are registered to your account (which may include task definition families that no longer have any ACTIVE task definition revisions). You can filter out task definition families that do not contain any ACTIVE task definition revisions by setting the status parameter to ACTIVE. You can also filter the results with the familyPrefix parameter.
 237     */
 238    listTaskDefinitionFamilies(callback?: (err: AWSError, data: ECS.Types.ListTaskDefinitionFamiliesResponse) => void): Request<ECS.Types.ListTaskDefinitionFamiliesResponse, AWSError>;
 239    /**
 240     * Returns a list of task definitions that are registered to your account. You can filter the results by family name with the familyPrefix parameter or by status with the status parameter.
 241     */
 242    listTaskDefinitions(params: ECS.Types.ListTaskDefinitionsRequest, callback?: (err: AWSError, data: ECS.Types.ListTaskDefinitionsResponse) => void): Request<ECS.Types.ListTaskDefinitionsResponse, AWSError>;
 243    /**
 244     * Returns a list of task definitions that are registered to your account. You can filter the results by family name with the familyPrefix parameter or by status with the status parameter.
 245     */
 246    listTaskDefinitions(callback?: (err: AWSError, data: ECS.Types.ListTaskDefinitionsResponse) => void): Request<ECS.Types.ListTaskDefinitionsResponse, AWSError>;
 247    /**
 248     * Returns a list of tasks. You can filter the results by cluster, task definition family, container instance, launch type, what IAM principal started the task, or by the desired status of the task. Recently stopped tasks might appear in the returned results. Currently, stopped tasks appear in the returned results for at least one hour.
 249     */
 250    listTasks(params: ECS.Types.ListTasksRequest, callback?: (err: AWSError, data: ECS.Types.ListTasksResponse) => void): Request<ECS.Types.ListTasksResponse, AWSError>;
 251    /**
 252     * Returns a list of tasks. You can filter the results by cluster, task definition family, container instance, launch type, what IAM principal started the task, or by the desired status of the task. Recently stopped tasks might appear in the returned results. Currently, stopped tasks appear in the returned results for at least one hour.
 253     */
 254    listTasks(callback?: (err: AWSError, data: ECS.Types.ListTasksResponse) => void): Request<ECS.Types.ListTasksResponse, AWSError>;
 255    /**
 256     * Modifies an account setting. Account settings are set on a per-Region basis. If you change the account setting for the root user, the default settings for all of the IAM users and roles for which no individual account setting has been specified are reset. For more information, see Account Settings in the Amazon Elastic Container Service Developer Guide. When serviceLongArnFormat, taskLongArnFormat, or containerInstanceLongArnFormat are specified, the Amazon Resource Name (ARN) and resource ID format of the resource type for a specified IAM user, IAM role, or the root user for an account is affected. The opt-in and opt-out account setting must be set for each Amazon ECS resource separately. The ARN and resource ID format of a resource will be defined by the opt-in status of the IAM user or role that created the resource. You must enable this setting to use Amazon ECS features such as resource tagging. When awsvpcTrunking is specified, the elastic network interface (ENI) limit for any new container instances that support the feature is changed. If awsvpcTrunking is enabled, any new container instances that support the feature are launched have the increased ENI limits available to them. For more information, see Elastic Network Interface Trunking in the Amazon Elastic Container Service Developer Guide. When containerInsights is specified, the default setting indicating whether CloudWatch Container Insights is enabled for your clusters is changed. If containerInsights is enabled, any new clusters that are created will have Container Insights enabled unless you disable it during cluster creation. For more information, see CloudWatch Container Insights in the Amazon Elastic Container Service Developer Guide.
 257     */
 258    putAccountSetting(params: ECS.Types.PutAccountSettingRequest, callback?: (err: AWSError, data: ECS.Types.PutAccountSettingResponse) => void): Request<ECS.Types.PutAccountSettingResponse, AWSError>;
 259    /**
 260     * Modifies an account setting. Account settings are set on a per-Region basis. If you change the account setting for the root user, the default settings for all of the IAM users and roles for which no individual account setting has been specified are reset. For more information, see Account Settings in the Amazon Elastic Container Service Developer Guide. When serviceLongArnFormat, taskLongArnFormat, or containerInstanceLongArnFormat are specified, the Amazon Resource Name (ARN) and resource ID format of the resource type for a specified IAM user, IAM role, or the root user for an account is affected. The opt-in and opt-out account setting must be set for each Amazon ECS resource separately. The ARN and resource ID format of a resource will be defined by the opt-in status of the IAM user or role that created the resource. You must enable this setting to use Amazon ECS features such as resource tagging. When awsvpcTrunking is specified, the elastic network interface (ENI) limit for any new container instances that support the feature is changed. If awsvpcTrunking is enabled, any new container instances that support the feature are launched have the increased ENI limits available to them. For more information, see Elastic Network Interface Trunking in the Amazon Elastic Container Service Developer Guide. When containerInsights is specified, the default setting indicating whether CloudWatch Container Insights is enabled for your clusters is changed. If containerInsights is enabled, any new clusters that are created will have Container Insights enabled unless you disable it during cluster creation. For more information, see CloudWatch Container Insights in the Amazon Elastic Container Service Developer Guide.
 261     */
 262    putAccountSetting(callback?: (err: AWSError, data: ECS.Types.PutAccountSettingResponse) => void): Request<ECS.Types.PutAccountSettingResponse, AWSError>;
 263    /**
 264     * Modifies an account setting for all IAM users on an account for whom no individual account setting has been specified. Account settings are set on a per-Region basis.
 265     */
 266    putAccountSettingDefault(params: ECS.Types.PutAccountSettingDefaultRequest, callback?: (err: AWSError, data: ECS.Types.PutAccountSettingDefaultResponse) => void): Request<ECS.Types.PutAccountSettingDefaultResponse, AWSError>;
 267    /**
 268     * Modifies an account setting for all IAM users on an account for whom no individual account setting has been specified. Account settings are set on a per-Region basis.
 269     */
 270    putAccountSettingDefault(callback?: (err: AWSError, data: ECS.Types.PutAccountSettingDefaultResponse) => void): Request<ECS.Types.PutAccountSettingDefaultResponse, AWSError>;
 271    /**
 272     * Create or update an attribute on an Amazon ECS resource. If the attribute does not exist, it is created. If the attribute exists, its value is replaced with the specified value. To delete an attribute, use DeleteAttributes. For more information, see Attributes in the Amazon Elastic Container Service Developer Guide.
 273     */
 274    putAttributes(params: ECS.Types.PutAttributesRequest, callback?: (err: AWSError, data: ECS.Types.PutAttributesResponse) => void): Request<ECS.Types.PutAttributesResponse, AWSError>;
 275    /**
 276     * Create or update an attribute on an Amazon ECS resource. If the attribute does not exist, it is created. If the attribute exists, its value is replaced with the specified value. To delete an attribute, use DeleteAttributes. For more information, see Attributes in the Amazon Elastic Container Service Developer Guide.
 277     */
 278    putAttributes(callback?: (err: AWSError, data: ECS.Types.PutAttributesResponse) => void): Request<ECS.Types.PutAttributesResponse, AWSError>;
 279    /**
 280     * 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 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. It is recommended to define a default capacity provider strategy for your cluster, however you may specify an empty array ([]) to bypass defining a default strategy.
 281     */
 282    putClusterCapacityProviders(params: ECS.Types.PutClusterCapacityProvidersRequest, callback?: (err: AWSError, data: ECS.Types.PutClusterCapacityProvidersResponse) => void): Request<ECS.Types.PutClusterCapacityProvidersResponse, AWSError>;
 283    /**
 284     * 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 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. It is recommended to define a default capacity provider strategy for your cluster, however you may specify an empty array ([]) to bypass defining a default strategy.
 285     */
 286    putClusterCapacityProviders(callback?: (err: AWSError, data: ECS.Types.PutClusterCapacityProvidersResponse) => void): Request<ECS.Types.PutClusterCapacityProvidersResponse, AWSError>;
 287    /**
 288     *  This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.  Registers an EC2 instance into the specified cluster. This instance becomes available to place containers on.
 289     */
 290    registerContainerInstance(params: ECS.Types.RegisterContainerInstanceRequest, callback?: (err: AWSError, data: ECS.Types.RegisterContainerInstanceResponse) => void): Request<ECS.Types.RegisterContainerInstanceResponse, AWSError>;
 291    /**
 292     *  This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.  Registers an EC2 instance into the specified cluster. This instance becomes available to place containers on.
 293     */
 294    registerContainerInstance(callback?: (err: AWSError, data: ECS.Types.RegisterContainerInstanceResponse) => void): Request<ECS.Types.RegisterContainerInstanceResponse, AWSError>;
 295    /**
 296     * 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 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.
 297     */
 298    registerTaskDefinition(params: ECS.Types.RegisterTaskDefinitionRequest, callback?: (err: AWSError, data: ECS.Types.RegisterTaskDefinitionResponse) => void): Request<ECS.Types.RegisterTaskDefinitionResponse, AWSError>;
 299    /**
 300     * 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 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.
 301     */
 302    registerTaskDefinition(callback?: (err: AWSError, data: ECS.Types.RegisterTaskDefinitionResponse) => void): Request<ECS.Types.RegisterTaskDefinitionResponse, AWSError>;
 303    /**
 304     * Starts a new task using the specified task definition. You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places tasks using placement constraints and placement strategies. For more information, see Scheduling Tasks in the Amazon Elastic Container Service Developer Guide. Alternatively, you can use StartTask to use your own scheduler or place tasks manually on specific container instances. The Amazon ECS API follows an eventual consistency model, due to the distributed nature of the system supporting the API. This means that the result of an API command you run that affects your Amazon ECS resources might not be immediately visible to all subsequent commands you run. Keep this in mind when you carry out an API command that immediately follows a previous API command. To manage eventual consistency, you can do the following:   Confirm the state of the resource before you run a command to modify it. Run the DescribeTasks command using an exponential backoff algorithm to ensure that you allow enough time for the previous command to propagate through the system. To do this, run the DescribeTasks command repeatedly, starting with a couple of seconds of wait time and increasing gradually up to five minutes of wait time.   Add wait time between subsequent commands, even if the DescribeTasks command returns an accurate response. Apply an exponential backoff algorithm starting with a couple of seconds of wait time, and increase gradually up to about five minutes of wait time.  
 305     */
 306    runTask(params: ECS.Types.RunTaskRequest, callback?: (err: AWSError, data: ECS.Types.RunTaskResponse) => void): Request<ECS.Types.RunTaskResponse, AWSError>;
 307    /**
 308     * Starts a new task using the specified task definition. You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places tasks using placement constraints and placement strategies. For more information, see Scheduling Tasks in the Amazon Elastic Container Service Developer Guide. Alternatively, you can use StartTask to use your own scheduler or place tasks manually on specific container instances. The Amazon ECS API follows an eventual consistency model, due to the distributed nature of the system supporting the API. This means that the result of an API command you run that affects your Amazon ECS resources might not be immediately visible to all subsequent commands you run. Keep this in mind when you carry out an API command that immediately follows a previous API command. To manage eventual consistency, you can do the following:   Confirm the state of the resource before you run a command to modify it. Run the DescribeTasks command using an exponential backoff algorithm to ensure that you allow enough time for the previous command to propagate through the system. To do this, run the DescribeTasks command repeatedly, starting with a couple of seconds of wait time and increasing gradually up to five minutes of wait time.   Add wait time between subsequent commands, even if the DescribeTasks command returns an accurate response. Apply an exponential backoff algorithm starting with a couple of seconds of wait time, and increase gradually up to about five minutes of wait time.  
 309     */
 310    runTask(callback?: (err: AWSError, data: ECS.Types.RunTaskResponse) => void): Request<ECS.Types.RunTaskResponse, AWSError>;
 311    /**
 312     * Starts a new task from the specified task definition on the specified container instance or instances. Alternatively, you can use RunTask to place tasks for you. For more information, see Scheduling Tasks in the Amazon Elastic Container Service Developer Guide.
 313     */
 314    startTask(params: ECS.Types.StartTaskRequest, callback?: (err: AWSError, data: ECS.Types.StartTaskResponse) => void): Request<ECS.Types.StartTaskResponse, AWSError>;
 315    /**
 316     * Starts a new task from the specified task definition on the specified container instance or instances. Alternatively, you can use RunTask to place tasks for you. For more information, see Scheduling Tasks in the Amazon Elastic Container Service Developer Guide.
 317     */
 318    startTask(callback?: (err: AWSError, data: ECS.Types.StartTaskResponse) => void): Request<ECS.Types.StartTaskResponse, AWSError>;
 319    /**
 320     * Stops a running task. Any tags associated with the task will be deleted. When StopTask is called on a task, the equivalent of docker stop is issued to the containers running in the task. This results in a SIGTERM value and a default 30-second timeout, after which the SIGKILL value is sent and the containers are forcibly stopped. If the container handles the SIGTERM value gracefully and exits within 30 seconds from receiving it, no SIGKILL value is sent.  The default 30-second timeout can be configured on the Amazon ECS container agent with the ECS_CONTAINER_STOP_TIMEOUT variable. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide. 
 321     */
 322    stopTask(params: ECS.Types.StopTaskRequest, callback?: (err: AWSError, data: ECS.Types.StopTaskResponse) => void): Request<ECS.Types.StopTaskResponse, AWSError>;
 323    /**
 324     * Stops a running task. Any tags associated with the task will be deleted. When StopTask is called on a task, the equivalent of docker stop is issued to the containers running in the task. This results in a SIGTERM value and a default 30-second timeout, after which the SIGKILL value is sent and the containers are forcibly stopped. If the container handles the SIGTERM value gracefully and exits within 30 seconds from receiving it, no SIGKILL value is sent.  The default 30-second timeout can be configured on the Amazon ECS container agent with the ECS_CONTAINER_STOP_TIMEOUT variable. For more information, see Amazon ECS Container Agent Configuration in the Amazon Elastic Container Service Developer Guide. 
 325     */
 326    stopTask(callback?: (err: AWSError, data: ECS.Types.StopTaskResponse) => void): Request<ECS.Types.StopTaskResponse, AWSError>;
 327    /**
 328     *  This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.  Sent to acknowledge that an attachment changed states.
 329     */
 330    submitAttachmentStateChanges(params: ECS.Types.SubmitAttachmentStateChangesRequest, callback?: (err: AWSError, data: ECS.Types.SubmitAttachmentStateChangesResponse) => void): Request<ECS.Types.SubmitAttachmentStateChangesResponse, AWSError>;
 331    /**
 332     *  This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.  Sent to acknowledge that an attachment changed states.
 333     */
 334    submitAttachmentStateChanges(callback?: (err: AWSError, data: ECS.Types.SubmitAttachmentStateChangesResponse) => void): Request<ECS.Types.SubmitAttachmentStateChangesResponse, AWSError>;
 335    /**
 336     *  This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.  Sent to acknowledge that a container changed states.
 337     */
 338    submitContainerStateChange(params: ECS.Types.SubmitContainerStateChangeRequest, callback?: (err: AWSError, data: ECS.Types.SubmitContainerStateChangeResponse) => void): Request<ECS.Types.SubmitContainerStateChangeResponse, AWSError>;
 339    /**
 340     *  This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.  Sent to acknowledge that a container changed states.
 341     */
 342    submitContainerStateChange(callback?: (err: AWSError, data: ECS.Types.SubmitContainerStateChangeResponse) => void): Request<ECS.Types.SubmitContainerStateChangeResponse, AWSError>;
 343    /**
 344     *  This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.  Sent to acknowledge that a task changed states.
 345     */
 346    submitTaskStateChange(params: ECS.Types.SubmitTaskStateChangeRequest, callback?: (err: AWSError, data: ECS.Types.SubmitTaskStateChangeResponse) => void): Request<ECS.Types.SubmitTaskStateChangeResponse, AWSError>;
 347    /**
 348     *  This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.  Sent to acknowledge that a task changed states.
 349     */
 350    submitTaskStateChange(callback?: (err: AWSError, data: ECS.Types.SubmitTaskStateChangeResponse) => void): Request<ECS.Types.SubmitTaskStateChangeResponse, AWSError>;
 351    /**
 352     * Associates the specified tags to a resource with the specified resourceArn. If existing tags on a resource are not specified in the request parameters, they are not changed. When a resource is deleted, the tags associated with that resource are deleted as well.
 353     */
 354    tagResource(params: ECS.Types.TagResourceRequest, callback?: (err: AWSError, data: ECS.Types.TagResourceResponse) => void): Request<ECS.Types.TagResourceResponse, AWSError>;
 355    /**
 356     * Associates the specified tags to a resource with the specified resourceArn. If existing tags on a resource are not specified in the request parameters, they are not changed. When a resource is deleted, the tags associated with that resource are deleted as well.
 357     */
 358    tagResource(callback?: (err: AWSError, data: ECS.Types.TagResourceResponse) => void): Request<ECS.Types.TagResourceResponse, AWSError>;
 359    /**
 360     * Deletes specified tags from a resource.
 361     */
 362    untagResource(params: ECS.Types.UntagResourceRequest, callback?: (err: AWSError, data: ECS.Types.UntagResourceResponse) => void): Request<ECS.Types.UntagResourceResponse, AWSError>;
 363    /**
 364     * Deletes specified tags from a resource.
 365     */
 366    untagResource(callback?: (err: AWSError, data: ECS.Types.UntagResourceResponse) => void): Request<ECS.Types.UntagResourceResponse, AWSError>;
 367    /**
 368     * Modifies the parameters for a capacity provider.
 369     */
 370    updateCapacityProvider(params: ECS.Types.UpdateCapacityProviderRequest, callback?: (err: AWSError, data: ECS.Types.UpdateCapacityProviderResponse) => void): Request<ECS.Types.UpdateCapacityProviderResponse, AWSError>;
 371    /**
 372     * Modifies the parameters for a capacity provider.
 373     */
 374    updateCapacityProvider(callback?: (err: AWSError, data: ECS.Types.UpdateCapacityProviderResponse) => void): Request<ECS.Types.UpdateCapacityProviderResponse, AWSError>;
 375    /**
 376     * Updates the cluster.
 377     */
 378    updateCluster(params: ECS.Types.UpdateClusterRequest, callback?: (err: AWSError, data: ECS.Types.UpdateClusterResponse) => void): Request<ECS.Types.UpdateClusterResponse, AWSError>;
 379    /**
 380     * Updates the cluster.
 381     */
 382    updateCluster(callback?: (err: AWSError, data: ECS.Types.UpdateClusterResponse) => void): Request<ECS.Types.UpdateClusterResponse, AWSError>;
 383    /**
 384     * Modifies the settings to use for a cluster.
 385     */
 386    updateClusterSettings(params: ECS.Types.UpdateClusterSettingsRequest, callback?: (err: AWSError, data: ECS.Types.UpdateClusterSettingsResponse) => void): Request<ECS.Types.UpdateClusterSettingsResponse, AWSError>;
 387    /**
 388     * Modifies the settings to use for a cluster.
 389     */
 390    updateClusterSettings(callback?: (err: AWSError, data: ECS.Types.UpdateClusterSettingsResponse) => void): Request<ECS.Types.UpdateClusterSettingsResponse, AWSError>;
 391    /**
 392     * Updates the Amazon ECS container agent on a specified container instance. Updating the Amazon ECS container agent does not interrupt running tasks or services on the container instance. The process for updating the agent differs depending on whether your container instance was launched with the Amazon ECS-optimized AMI or another operating system.  The UpdateContainerAgent API isn't supported for container instances using the Amazon ECS-optimized Amazon Linux 2 (arm64) AMI. To update the container agent, you can update the ecs-init package which will update the agent. For more information, see Updating the Amazon ECS container agent in the Amazon Elastic Container Service Developer Guide.  The UpdateContainerAgent API requires an Amazon ECS-optimized AMI or Amazon Linux AMI with the ecs-init service installed and running. For help updating the Amazon ECS container agent on other operating systems, see Manually updating the Amazon ECS container agent in the Amazon Elastic Container Service Developer Guide.
 393     */
 394    updateContainerAgent(params: ECS.Types.UpdateContainerAgentRequest, callback?: (err: AWSError, data: ECS.Types.UpdateContainerAgentResponse) => void): Request<ECS.Types.UpdateContainerAgentResponse, AWSError>;
 395    /**
 396     * Updates the Amazon ECS container agent on a specified container instance. Updating the Amazon ECS container agent does not interrupt running tasks or services on the container instance. The process for updating the agent differs depending on whether your container instance was launched with the Amazon ECS-optimized AMI or another operating system.  The UpdateContainerAgent API isn't supported for container instances using the Amazon ECS-optimized Amazon Linux 2 (arm64) AMI. To update the container agent, you can update the ecs-init package which will update the agent. For more information, see Updating the Amazon ECS container agent in the Amazon Elastic Container Service Developer Guide.  The UpdateContainerAgent API requires an Amazon ECS-optimized AMI or Amazon Linux AMI with the ecs-init service installed and running. For help updating the Amazon ECS container agent on other operating systems, see Manually updating the Amazon ECS container agent in the Amazon Elastic Container Service Developer Guide.
 397     */
 398    updateContainerAgent(callback?: (err: AWSError, data: ECS.Types.UpdateContainerAgentResponse) => void): Request<ECS.Types.UpdateContainerAgentResponse, AWSError>;
 399    /**
 400     * Modifies the status of an Amazon ECS container instance. Once a container instance has reached an ACTIVE state, you can change the status of a container instance to DRAINING to manually remove an instance from a cluster, for example to perform system updates, update the Docker daemon, or scale down the cluster size.  A container instance cannot be changed to DRAINING until it has reached an ACTIVE status. If the instance is in any other status, an error will be received.  When you set a container instance to DRAINING, Amazon ECS prevents new tasks from being scheduled for placement on the container instance and replacement service tasks are started on other container instances in the cluster if the resources are available. Service tasks on the container instance that are in the PENDING state are stopped immediately. Service tasks on the container instance that are in the RUNNING state are stopped and replaced according to the service's deployment configuration parameters, minimumHealthyPercent and maximumPercent. You can change the deployment configuration of your service using UpdateService.   If minimumHealthyPercent is below 100%, the scheduler can ignore desiredCount temporarily during task replacement. For example, desiredCount is four tasks, a minimum of 50% allows the scheduler to stop two existing tasks before starting two new tasks. If the minimum is 100%, the service scheduler can't remove existing tasks until the replacement tasks are considered healthy. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state. Tasks for services that use a load balancer are considered healthy if they are in the RUNNING state and the container instance they are hosted on is reported as healthy by the load balancer.   The maximumPercent parameter represents an upper limit on the number of running tasks during task replacement, which enables you to define the replacement batch size. For example, if desiredCount is four tasks, a maximum of 200% starts four new tasks before stopping the four tasks to be drained, provided that the cluster resources required to do this are available. If the maximum is 100%, then replacement tasks can't start until the draining tasks have stopped.   Any PENDING or RUNNING tasks that do not belong to a service are not affected. You must wait for them to finish or stop them manually. A container instance has completed draining when it has no more RUNNING tasks. You can verify this using ListTasks. When a container instance has been drained, you can set a container instance to ACTIVE status and once it has reached that status the Amazon ECS scheduler can begin scheduling tasks on the instance again.
 401     */
 402    updateContainerInstancesState(params: ECS.Types.UpdateContainerInstancesStateRequest, callback?: (err: AWSError, data: ECS.Types.UpdateContainerInstancesStateResponse) => void): Request<ECS.Types.UpdateContainerInstancesStateResponse, AWSError>;
 403    /**
 404     * Modifies the status of an Amazon ECS container instance. Once a container instance has reached an ACTIVE state, you can change the status of a container instance to DRAINING to manually remove an instance from a cluster, for example to perform system updates, update the Docker daemon, or scale down the cluster size.  A container instance cannot be changed to DRAINING until it has reached an ACTIVE status. If the instance is in any other status, an error will be received.  When you set a container instance to DRAINING, Amazon ECS prevents new tasks from being scheduled for placement on the container instance and replacement service tasks are started on other container instances in the cluster if the resources are available. Service tasks on the container instance that are in the PENDING state are stopped immediately. Service tasks on the container instance that are in the RUNNING state are stopped and replaced according to the service's deployment configuration parameters, minimumHealthyPercent and maximumPercent. You can change the deployment configuration of your service using UpdateService.   If minimumHealthyPercent is below 100%, the scheduler can ignore desiredCount temporarily during task replacement. For example, desiredCount is four tasks, a minimum of 50% allows the scheduler to stop two existing tasks before starting two new tasks. If the minimum is 100%, the service scheduler can't remove existing tasks until the replacement tasks are considered healthy. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state. Tasks for services that use a load balancer are considered healthy if they are in the RUNNING state and the container instance they are hosted on is reported as healthy by the load balancer.   The maximumPercent parameter represents an upper limit on the number of running tasks during task replacement, which enables you to define the replacement batch size. For example, if desiredCount is four tasks, a maximum of 200% starts four new tasks before stopping the four tasks to be drained, provided that the cluster resources required to do this are available. If the maximum is 100%, then replacement tasks can't start until the draining tasks have stopped.   Any PENDING or RUNNING tasks that do not belong to a service are not affected. You must wait for them to finish or stop them manually. A container instance has completed draining when it has no more RUNNING tasks. You can verify this using ListTasks. When a container instance has been drained, you can set a container instance to ACTIVE status and once it has reached that status the Amazon ECS scheduler can begin scheduling tasks on the instance again.
 405     */
 406    updateContainerInstancesState(callback?: (err: AWSError, data: ECS.Types.UpdateContainerInstancesStateResponse) => void): Request<ECS.Types.UpdateContainerInstancesStateResponse, AWSError>;
 407    /**
 408     *  Updating the task placement strategies and constraints on an Amazon ECS service remains in preview and is a Beta Service as defined by and subject to the Beta Service Participation Service Terms located at https://aws.amazon.com/service-terms ("Beta Terms"). These Beta Terms apply to your participation in this preview.  Modifies the parameters of a service. For services using the rolling update (ECS) deployment controller, the desired count, deployment configuration, network configuration, task placement constraints and strategies, or task definition used can be updated. For services using the blue/green (CODE_DEPLOY) deployment controller, only the desired count, deployment configuration, task placement constraints and strategies, and health check grace period can be updated using this API. If the network configuration, platform version, or task definition need to be updated, a new CodeDeploy deployment should be created. For more information, see CreateDeployment in the CodeDeploy API Reference. For services using an external deployment controller, you can update only the desired count, task placement constraints and strategies, and health check grace period using this API. If the launch type, load balancer, network configuration, platform version, or task definition need to be updated, you should create a new task set. For more information, see CreateTaskSet. You can add to or subtract from the number of instantiations of a task definition in a service by specifying the cluster that the service is running in and a new desiredCount parameter. If you have updated the Docker image of your application, you can create a new task definition with that image and deploy it to your service. The service scheduler uses the minimum healthy percent and maximum percent parameters (in the service's deployment configuration) to determine the deployment strategy.  If your updated Docker image uses the same tag as what is in the existing task definition for your service (for example, my_image:latest), you do not need to create a new revision of your task definition. You can update the service using the forceNewDeployment option. The new tasks launched by the deployment pull the current image/tag combination from your repository when they start.  You can also update the deployment configuration of a service. When a deployment is triggered by updating the task definition of a service, the service scheduler uses the deployment configuration parameters, minimumHealthyPercent and maximumPercent, to determine the deployment strategy.   If minimumHealthyPercent is below 100%, the scheduler can ignore desiredCount temporarily during a deployment. For example, if desiredCount is four tasks, a minimum of 50% allows the scheduler to stop two existing tasks before starting two new tasks. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state. Tasks for services that use a load balancer are considered healthy if they are in the RUNNING state and the container instance they are hosted on is reported as healthy by the load balancer.   The maximumPercent parameter represents an upper limit on the number of running tasks during a deployment, which enables you to define the deployment batch size. For example, if desiredCount is four tasks, a maximum of 200% starts four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available).   When UpdateService stops a task during a deployment, the equivalent of docker stop is issued to the containers running in the task. This results in a SIGTERM and a 30-second timeout, after which SIGKILL is sent and the containers are forcibly stopped. If the container handles the SIGTERM gracefully and exits within 30 seconds from receiving it, no SIGKILL is sent. When the service scheduler launches new tasks, it determines task placement in your cluster with the following logic:   Determine which of the container instances in your cluster can support your service's task definition (for example, they have the required CPU, memory, ports, and container instance attributes).   By default, the service scheduler attempts to balance tasks across Availability Zones in this manner (although you can choose a different placement strategy):   Sort the valid container instances by the fewest number of running tasks for this service in the same Availability Zone as the instance. For example, if zone A has one running service task and zones B and C each have zero, valid container instances in either zone B or C are considered optimal for placement.   Place the new service task on a valid container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the fewest number of running tasks for this service.     When the service scheduler stops running tasks, it attempts to maintain balance across the Availability Zones in your cluster using the following logic:    Sort the container instances by the largest number of running tasks for this service in the same Availability Zone as the instance. For example, if zone A has one running service task and zones B and C each have two, container instances in either zone B or C are considered optimal for termination.   Stop the task on a container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the largest number of running tasks for this service.  
 409     */
 410    updateService(params: ECS.Types.UpdateServiceRequest, callback?: (err: AWSError, data: ECS.Types.UpdateServiceResponse) => void): Request<ECS.Types.UpdateServiceResponse, AWSError>;
 411    /**
 412     *  Updating the task placement strategies and constraints on an Amazon ECS service remains in preview and is a Beta Service as defined by and subject to the Beta Service Participation Service Terms located at https://aws.amazon.com/service-terms ("Beta Terms"). These Beta Terms apply to your participation in this preview.  Modifies the parameters of a service. For services using the rolling update (ECS) deployment controller, the desired count, deployment configuration, network configuration, task placement constraints and strategies, or task definition used can be updated. For services using the blue/green (CODE_DEPLOY) deployment controller, only the desired count, deployment configuration, task placement constraints and strategies, and health check grace period can be updated using this API. If the network configuration, platform version, or task definition need to be updated, a new CodeDeploy deployment should be created. For more information, see CreateDeployment in the CodeDeploy API Reference. For services using an external deployment controller, you can update only the desired count, task placement constraints and strategies, and health check grace period using this API. If the launch type, load balancer, network configuration, platform version, or task definition need to be updated, you should create a new task set. For more information, see CreateTaskSet. You can add to or subtract from the number of instantiations of a task definition in a service by specifying the cluster that the service is running in and a new desiredCount parameter. If you have updated the Docker image of your application, you can create a new task definition with that image and deploy it to your service. The service scheduler uses the minimum healthy percent and maximum percent parameters (in the service's deployment configuration) to determine the deployment strategy.  If your updated Docker image uses the same tag as what is in the existing task definition for your service (for example, my_image:latest), you do not need to create a new revision of your task definition. You can update the service using the forceNewDeployment option. The new tasks launched by the deployment pull the current image/tag combination from your repository when they start.  You can also update the deployment configuration of a service. When a deployment is triggered by updating the task definition of a service, the service scheduler uses the deployment configuration parameters, minimumHealthyPercent and maximumPercent, to determine the deployment strategy.   If minimumHealthyPercent is below 100%, the scheduler can ignore desiredCount temporarily during a deployment. For example, if desiredCount is four tasks, a minimum of 50% allows the scheduler to stop two existing tasks before starting two new tasks. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state. Tasks for services that use a load balancer are considered healthy if they are in the RUNNING state and the container instance they are hosted on is reported as healthy by the load balancer.   The maximumPercent parameter represents an upper limit on the number of running tasks during a deployment, which enables you to define the deployment batch size. For example, if desiredCount is four tasks, a maximum of 200% starts four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available).   When UpdateService stops a task during a deployment, the equivalent of docker stop is issued to the containers running in the task. This results in a SIGTERM and a 30-second timeout, after which SIGKILL is sent and the containers are forcibly stopped. If the container handles the SIGTERM gracefully and exits within 30 seconds from receiving it, no SIGKILL is sent. When the service scheduler launches new tasks, it determines task placement in your cluster with the following logic:   Determine which of the container instances in your cluster can support your service's task definition (for example, they have the required CPU, memory, ports, and container instance attributes).   By default, the service scheduler attempts to balance tasks across Availability Zones in this manner (although you can choose a different placement strategy):   Sort the valid container instances by the fewest number of running tasks for this service in the same Availability Zone as the instance. For example, if zone A has one running service task and zones B and C each have zero, valid container instances in either zone B or C are considered optimal for placement.   Place the new service task on a valid container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the fewest number of running tasks for this service.     When the service scheduler stops running tasks, it attempts to maintain balance across the Availability Zones in your cluster using the following logic:    Sort the container instances by the largest number of running tasks for this service in the same Availability Zone as the instance. For example, if zone A has one running service task and zones B and C each have two, container instances in either zone B or C are considered optimal for termination.   Stop the task on a container instance in an optimal Availability Zone (based on the previous steps), favoring container instances with the largest number of running tasks for this service.  
 413     */
 414    updateService(callback?: (err: AWSError, data: ECS.Types.UpdateServiceResponse) => void): Request<ECS.Types.UpdateServiceResponse, AWSError>;
 415    /**
 416     * Modifies which task set in a service is the primary task set. Any parameters that are updated on the primary task set in a service will transition to the service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
 417     */
 418    updateServicePrimaryTaskSet(params: ECS.Types.UpdateServicePrimaryTaskSetRequest, callback?: (err: AWSError, data: ECS.Types.UpdateServicePrimaryTaskSetResponse) => void): Request<ECS.Types.UpdateServicePrimaryTaskSetResponse, AWSError>;
 419    /**
 420     * Modifies which task set in a service is the primary task set. Any parameters that are updated on the primary task set in a service will transition to the service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
 421     */
 422    updateServicePrimaryTaskSet(callback?: (err: AWSError, data: ECS.Types.UpdateServicePrimaryTaskSetResponse) => void): Request<ECS.Types.UpdateServicePrimaryTaskSetResponse, AWSError>;
 423    /**
 424     * Modifies a task set. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
 425     */
 426    updateTaskSet(params: ECS.Types.UpdateTaskSetRequest, callback?: (err: AWSError, data: ECS.Types.UpdateTaskSetResponse) => void): Request<ECS.Types.UpdateTaskSetResponse, AWSError>;
 427    /**
 428     * Modifies a task set. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS Deployment Types in the Amazon Elastic Container Service Developer Guide.
 429     */
 430    updateTaskSet(callback?: (err: AWSError, data: ECS.Types.UpdateTaskSetResponse) => void): Request<ECS.Types.UpdateTaskSetResponse, AWSError>;
 431    /**
 432     * Waits for the tasksRunning state by periodically calling the underlying ECS.describeTasksoperation every 6 seconds (at most 100 times).
 433     */
 434    waitFor(state: "tasksRunning", params: ECS.Types.DescribeTasksRequest & {$waiter?: WaiterConfiguration}, callback?: (err: AWSError, data: ECS.Types.DescribeTasksResponse) => void): Request<ECS.Types.DescribeTasksResponse, AWSError>;
 435    /**
 436     * Waits for the tasksRunning state by periodically calling the underlying ECS.describeTasksoperation every 6 seconds (at most 100 times).
 437     */
 438    waitFor(state: "tasksRunning", callback?: (err: AWSError, data: ECS.Types.DescribeTasksResponse) => void): Request<ECS.Types.DescribeTasksResponse, AWSError>;
 439    /**
 440     * Waits for the tasksStopped state by periodically calling the underlying ECS.describeTasksoperation every 6 seconds (at most 100 times).
 441     */
 442    waitFor(state: "tasksStopped", params: ECS.Types.DescribeTasksRequest & {$waiter?: WaiterConfiguration}, callback?: (err: AWSError, data: ECS.Types.DescribeTasksResponse) => void): Request<ECS.Types.DescribeTasksResponse, AWSError>;
 443    /**
 444     * Waits for the tasksStopped state by periodically calling the underlying ECS.describeTasksoperation every 6 seconds (at most 100 times).
 445     */
 446    waitFor(state: "tasksStopped", callback?: (err: AWSError, data: ECS.Types.DescribeTasksResponse) => void): Request<ECS.Types.DescribeTasksResponse, AWSError>;
 447    /**
 448     * Waits for the servicesStable state by periodically calling the underlying ECS.describeServicesoperation every 15 seconds (at most 40 times).
 449     */
 450    waitFor(state: "servicesStable", params: ECS.Types.DescribeServicesRequest & {$waiter?: WaiterConfiguration}, callback?: (err: AWSError, data: ECS.Types.DescribeServicesResponse) => void): Request<ECS.Types.DescribeServicesResponse, AWSError>;
 451    /**
 452     * Waits for the servicesStable state by periodically calling the underlying ECS.describeServicesoperation every 15 seconds (at most 40 times).
 453     */
 454    waitFor(state: "servicesStable", callback?: (err: AWSError, data: ECS.Types.DescribeServicesResponse) => void): Request<ECS.Types.DescribeServicesResponse, AWSError>;
 455    /**
 456     * Waits for the servicesInactive state by periodically calling the underlying ECS.describeServicesoperation every 15 seconds (at most 40 times).
 457     */
 458    waitFor(state: "servicesInactive", params: ECS.Types.DescribeServicesRequest & {$waiter?: WaiterConfiguration}, callback?: (err: AWSError, data: ECS.Types.DescribeServicesResponse) => void): Request<ECS.Types.DescribeServicesResponse, AWSError>;
 459    /**
 460     * Waits for the servicesInactive state by periodically calling the underlying ECS.describeServicesoperation every 15 seconds (at most 40 times).
 461     */
 462    waitFor(state: "servicesInactive", callback?: (err: AWSError, data: ECS.Types.DescribeServicesResponse) => void): Request<ECS.Types.DescribeServicesResponse, AWSError>;
 463  }
 464  declare namespace ECS {
 465    export type AgentUpdateStatus = "PENDING"|"STAGING"|"STAGED"|"UPDATING"|"UPDATED"|"FAILED"|string;
 466    export type AssignPublicIp = "ENABLED"|"DISABLED"|string;
 467    export interface Attachment {
 468      /**
 469       * The unique identifier for the attachment.
 470       */
 471      id?: String;
 472      /**
 473       * The type of the attachment, such as ElasticNetworkInterface.
 474       */
 475      type?: String;
 476      /**
 477       *  The status of the attachment. Valid values are PRECREATED, CREATED, ATTACHING, ATTACHED, DETACHING, DETACHED, and DELETED.
 478       */
 479      status?: String;
 480      /**
 481       * 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.
 482       */
 483      details?: AttachmentDetails;
 484    }
 485    export type AttachmentDetails = KeyValuePair[];
 486    export interface AttachmentStateChange {
 487      /**
 488       * The Amazon Resource Name (ARN) of the attachment.
 489       */
 490      attachmentArn: String;
 491      /**
 492       * The status of the attachment.
 493       */
 494      status: String;
 495    }
 496    export type AttachmentStateChanges = AttachmentStateChange[];
 497    export type Attachments = Attachment[];
 498    export interface Attribute {
 499      /**
 500       * The name of the attribute. The name must contain between 1 and 128 characters and name may contain letters (uppercase and lowercase), numbers, hyphens, underscores, forward slashes, back slashes, or periods.
 501       */
 502      name: String;
 503      /**
 504       * The value of the attribute. The value must contain between 1 and 128 characters and may contain letters (uppercase and lowercase), numbers, hyphens, underscores, periods, at signs (@), forward slashes, back slashes, colons, or spaces. The value cannot contain any leading or trailing whitespace.
 505       */
 506      value?: String;
 507      /**
 508       * The type of the target with which to attach the attribute. This parameter is required if you use the short form ID for a resource instead of the full ARN.
 509       */
 510      targetType?: TargetType;
 511      /**
 512       * The ID of the target. You can specify the short form ID for a resource or the full Amazon Resource Name (ARN).
 513       */
 514      targetId?: String;
 515    }
 516    export type Attributes = Attribute[];
 517    export interface AutoScalingGroupProvider {
 518      /**
 519       * The Amazon Resource Name (ARN) that identifies the Auto Scaling group.
 520       */
 521      autoScalingGroupArn: String;
 522      /**
 523       * The managed scaling settings for the Auto Scaling group capacity provider.
 524       */
 525      managedScaling?: ManagedScaling;
 526      /**
 527       * The managed termination protection setting to use for the Auto Scaling group capacity provider. This determines whether the Auto Scaling group has managed termination protection.  When using managed termination protection, managed scaling must also be used otherwise managed termination protection will not work.  When managed termination protection is enabled, Amazon ECS prevents the Amazon EC2 instances in an Auto Scaling group that contain tasks from being terminated during a scale-in action. The Auto Scaling group and each instance in the Auto Scaling group must have instance protection from scale-in actions enabled as well. For more information, see Instance Protection in the Auto Scaling User Guide. When managed termination protection is disabled, your Amazon EC2 instances are not protected from termination when the Auto Scaling group scales in.
 528       */
 529      managedTerminationProtection?: ManagedTerminationProtection;
 530    }
 531    export interface AutoScalingGroupProviderUpdate {
 532      /**
 533       * The managed scaling settings for the Auto Scaling group capacity provider.
 534       */
 535      managedScaling?: ManagedScaling;
 536      /**
 537       * The managed termination protection setting to use for the Auto Scaling group capacity provider. This determines whether the Auto Scaling group has managed termination protection.  When using managed termination protection, managed scaling must also be used otherwise managed termination protection will not work.  When managed termination protection is enabled, Amazon ECS prevents the Amazon EC2 instances in an Auto Scaling group that contain tasks from being terminated during a scale-in action. The Auto Scaling group and each instance in the Auto Scaling group must have instance protection from scale-in actions enabled as well. For more information, see Instance Protection in the Auto Scaling User Guide. When managed termination protection is disabled, your Amazon EC2 instances are not protected from termination when the Auto Scaling group scales in.
 538       */
 539      managedTerminationProtection?: ManagedTerminationProtection;
 540    }
 541    export interface AwsVpcConfiguration {
 542      /**
 543       * The IDs of the subnets associated with the task or service. There is a limit of 16 subnets that can be specified per AwsVpcConfiguration.  All specified subnets must be from the same VPC. 
 544       */
 545      subnets: StringList;
 546      /**
 547       * The IDs of the security groups associated with the task or service. If you do not specify a security group, the default security group for the VPC is used. There is a limit of 5 security groups that can be specified per AwsVpcConfiguration.  All specified security groups must be from the same VPC. 
 548       */
 549      securityGroups?: StringList;
 550      /**
 551       * Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.
 552       */
 553      assignPublicIp?: AssignPublicIp;
 554    }
 555    export type Boolean = boolean;
 556    export type BoxedBoolean = boolean;
 557    export type BoxedInteger = number;
 558    export interface CapacityProvider {
 559      /**
 560       * The Amazon Resource Name (ARN) that identifies the capacity provider.
 561       */
 562      capacityProviderArn?: String;
 563      /**
 564       * The name of the capacity provider.
 565       */
 566      name?: String;
 567      /**
 568       * The current status of the capacity provider. Only capacity providers in an ACTIVE state can be used in a cluster. When a capacity provider is successfully deleted, it will have an INACTIVE status.
 569       */
 570      status?: CapacityProviderStatus;
 571      /**
 572       * The Auto Scaling group settings for the capacity provider.
 573       */
 574      autoScalingGroupProvider?: AutoScalingGroupProvider;
 575      /**
 576       * The update status of the capacity provider. The following are the possible states that will be returned.  DELETE_IN_PROGRESS  The capacity provider is in the process of being deleted.  DELETE_COMPLETE  The capacity provider has been successfully deleted and will have an INACTIVE status.  DELETE_FAILED  The capacity provider was unable to be deleted. The update status reason will provide further details about why the delete failed.  
 577       */
 578      updateStatus?: CapacityProviderUpdateStatus;
 579      /**
 580       * The update status reason. This provides further details about the update status for the capacity provider.
 581       */
 582      updateStatusReason?: String;
 583      /**
 584       * The metadata that you apply to the capacity provider to help you categorize and organize it. Each tag consists of a key and an optional value, both of which you define. 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.  
 585       */
 586      tags?: Tags;
 587    }
 588    export type CapacityProviderField = "TAGS"|string;
 589    export type CapacityProviderFieldList = CapacityProviderField[];
 590    export type CapacityProviderStatus = "ACTIVE"|"INACTIVE"|string;
 591    export type CapacityProviderStrategy = CapacityProviderStrategyItem[];
 592    export interface CapacityProviderStrategyItem {
 593      /**
 594       * The short name of the capacity provider.
 595       */
 596      capacityProvider: String;
 597      /**
 598       * 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 will not 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 is run using capacityProviderA, four tasks would use capacityProviderB.
 599       */
 600      weight?: CapacityProviderStrategyItemWeight;
 601      /**
 602       * 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.
 603       */
 604      base?: CapacityProviderStrategyItemBase;
 605    }
 606    export type CapacityProviderStrategyItemBase = number;
 607    export type CapacityProviderStrategyItemWeight = number;
 608    export type CapacityProviderUpdateStatus = "DELETE_IN_PROGRESS"|"DELETE_COMPLETE"|"DELETE_FAILED"|"UPDATE_IN_PROGRESS"|"UPDATE_COMPLETE"|"UPDATE_FAILED"|string;
 609    export type CapacityProviders = CapacityProvider[];
 610    export interface Cluster {
 611      /**
 612       * The Amazon Resource Name (ARN) that identifies the cluster. The ARN contains the arn:aws:ecs namespace, followed by the Region of the cluster, the Amazon Web Services account ID of the cluster owner, the cluster namespace, and then the cluster name. For example, arn:aws:ecs:region:012345678910:cluster/test.
 613       */
 614      clusterArn?: String;
 615      /**
 616       * A user-generated string that you use to identify your cluster.
 617       */
 618      clusterName?: String;
 619      /**
 620       * The execute command configuration for the cluster.
 621       */
 622      configuration?: ClusterConfiguration;
 623      /**
 624       * The status of the cluster. The following are the possible states that will be 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 associated with it and the resources needed for the capacity provider are being created.  DEPROVISIONING  The cluster has capacity providers associated with it and the resources needed for the capacity provider are being deleted.  FAILED  The cluster has capacity providers 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, so you should not rely on INACTIVE clusters persisting.  
 625       */
 626      status?: String;
 627      /**
 628       * The number of container instances registered into the cluster. This includes container instances in both ACTIVE and DRAINING status.
 629       */
 630      registeredContainerInstancesCount?: Integer;
 631      /**
 632       * The number of tasks in the cluster that are in the RUNNING state.
 633       */
 634      runningTasksCount?: Integer;
 635      /**
 636       * The number of tasks in the cluster that are in the PENDING state.
 637       */
 638      pendingTasksCount?: Integer;
 639      /**
 640       * The number of services that are running on the cluster in an ACTIVE state. You can view these services with ListServices.
 641       */
 642      activeServicesCount?: Integer;
 643      /**
 644       * Additional information about your clusters that are separated by launch type, including:   runningEC2TasksCount   RunningFargateTasksCount   pendingEC2TasksCount   pendingFargateTasksCount   activeEC2ServiceCount   activeFargateServiceCount   drainingEC2ServiceCount   drainingFargateServiceCount  
 645       */
 646      statistics?: Statistics;
 647      /**
 648       * 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, both of which you define. 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.  
 649       */
 650      tags?: Tags;
 651      /**
 652       * The settings for the cluster. This parameter indicates whether CloudWatch Container Insights is enabled or disabled for a cluster.
 653       */
 654      settings?: ClusterSettings;
 655      /**
 656       * The capacity providers associated with the cluster.
 657       */
 658      capacityProviders?: StringList;
 659      /**
 660       * 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.
 661       */
 662      defaultCapacityProviderStrategy?: CapacityProviderStrategy;
 663      /**
 664       * The resources attached to a cluster. When using a capacity provider with a cluster, the Auto Scaling plan that is created will be returned as a cluster attachment.
 665       */
 666      attachments?: Attachments;
 667      /**
 668       * The status of the capacity providers associated with the cluster. The following are the states that will be returned:  UPDATE_IN_PROGRESS  The available capacity providers for the cluster are updating. This occurs when the Auto Scaling plan is provisioning or deprovisioning.  UPDATE_COMPLETE  The capacity providers have successfully updated.  UPDATE_FAILED  The capacity provider updates failed.  
 669       */
 670      attachmentsStatus?: String;
 671    }
 672    export interface ClusterConfiguration {
 673      /**
 674       * The details of the execute command configuration.
 675       */
 676      executeCommandConfiguration?: ExecuteCommandConfiguration;
 677    }
 678    export type ClusterField = "ATTACHMENTS"|"CONFIGURATIONS"|"SETTINGS"|"STATISTICS"|"TAGS"|string;
 679    export type ClusterFieldList = ClusterField[];
 680    export interface ClusterSetting {
 681      /**
 682       * The name of the cluster setting. The only supported value is containerInsights.
 683       */
 684      name?: ClusterSettingName;
 685      /**
 686       * 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.
 687       */
 688      value?: String;
 689    }
 690    export type ClusterSettingName = "containerInsights"|string;
 691    export type ClusterSettings = ClusterSetting[];
 692    export type Clusters = Cluster[];
 693    export type Compatibility = "EC2"|"FARGATE"|"EXTERNAL"|string;
 694    export type CompatibilityList = Compatibility[];
 695    export type Connectivity = "CONNECTED"|"DISCONNECTED"|string;
 696    export interface Container {
 697      /**
 698       * The Amazon Resource Name (ARN) of the container.
 699       */
 700      containerArn?: String;
 701      /**
 702       * The ARN of the task.
 703       */
 704      taskArn?: String;
 705      /**
 706       * The name of the container.
 707       */
 708      name?: String;
 709      /**
 710       * The image used for the container.
 711       */
 712      image?: String;
 713      /**
 714       * The container image manifest digest.  The imageDigest is only returned if the container is using an image hosted in Amazon ECR, otherwise it is omitted. 
 715       */
 716      imageDigest?: String;
 717      /**
 718       * The ID of the Docker container.
 719       */
 720      runtimeId?: String;
 721      /**
 722       * The last known status of the container.
 723       */
 724      lastStatus?: String;
 725      /**
 726       * The exit code returned from the container.
 727       */
 728      exitCode?: BoxedInteger;
 729      /**
 730       * A short (255 max characters) human-readable string to provide additional details about a running or stopped container.
 731       */
 732      reason?: String;
 733      /**
 734       * The network bindings associated with the container.
 735       */
 736      networkBindings?: NetworkBindings;
 737      /**
 738       * The network interfaces associated with the container.
 739       */
 740      networkInterfaces?: NetworkInterfaces;
 741      /**
 742       * The health status of the container. If health checks are not configured for this container in its task definition, then it reports the health status as UNKNOWN.
 743       */
 744      healthStatus?: HealthStatus;
 745      /**
 746       * The details of any Amazon ECS managed agents associated with the container.
 747       */
 748      managedAgents?: ManagedAgents;
 749      /**
 750       * The number of CPU units set for the container. The value will be 0 if no value was specified in the container definition when the task definition was registered.
 751       */
 752      cpu?: String;
 753      /**
 754       * The hard limit (in MiB) of memory set for the container.
 755       */
 756      memory?: String;
 757      /**
 758       * The soft limit (in MiB) of memory set for the container.
 759       */
 760      memoryReservation?: String;
 761      /**
 762       * The IDs of each GPU assigned to the container.
 763       */
 764      gpuIds?: GpuIds;
 765    }
 766    export type ContainerCondition = "START"|"COMPLETE"|"SUCCESS"|"HEALTHY"|string;
 767    export interface ContainerDefinition {
 768      /**
 769       * The name of a container. If you are 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. 
 770       */
 771      name?: String;
 772      /**
 773       * The image used to start a container. This string is passed directly to the Docker daemon. Images in the Docker Hub registry are available by default. 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 are not 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.&lt;region-name&gt;.amazonaws.com/&lt;repository-name&gt;:latest or 012345678910.dkr.ecr.&lt;region-name&gt;.amazonaws.com/&lt;repository-name&gt;@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).  
 774       */
 775      image?: String;
 776      /**
 777       * The private repository authentication credentials to use.
 778       */
 779      repositoryCredentials?: RepositoryCredentials;
 780      /**
 781       * 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.  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 is 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 would be guaranteed a minimum of 512 CPU units when needed, and each container could float to higher CPU usage if the other container was not using it, but 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 is not 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 is 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.
 782       */
 783      cpu?: Integer;
 784      /**
 785       * 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 on which the container is placed. Otherwise, the value of memory is used. The Docker daemon reserves a minimum of 4 MiB of memory for a container, so you should not specify fewer than 4 MiB of memory for your containers.
 786       */
 787      memory?: BoxedInteger;
 788      /**
 789       * 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 on which 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 daemon reserves a minimum of 4 MiB of memory for a container, so you should not specify fewer than 4 MiB of memory for your containers. 
 790       */
 791      memoryReservation?: BoxedInteger;
 792      /**
 793       * 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.  This parameter is not supported for Windows containers.   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. 
 794       */
 795      links?: StringList;
 796      /**
 797       * 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, you should 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 is no loopback for port mappings on Windows, so you cannot 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.  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. 
 798       */
 799      portMappings?: PortMappingList;
 800      /**
 801       * 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, then its failure does not 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 is composed of multiple containers, you should 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.
 802       */
 803      essential?: BoxedBoolean;
 804      /**
 805       *  Early versions of the Amazon ECS container agent do not 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 is 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.
 806       */
 807      entryPoint?: StringList;
 808      /**
 809       * The command that is 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 should be a separated string in the array.
 810       */
 811      command?: StringList;
 812      /**
 813       * 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.  We do not recommend using plaintext environment variables for sensitive information, such as credential data. 
 814       */
 815      environment?: EnvironmentVariables;
 816      /**
 817       * 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 should contain an environment variable in VARIABLE=VALUE format. Lines beginning with # are treated as comments and are ignored. For more information on 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 are processed from the top down. It is recommended to use unique variable names. For more information, see Specifying Environment Variables in the Amazon Elastic Container Service Developer Guide.
 818       */
 819      environmentFiles?: EnvironmentFiles;
 820      /**
 821       * 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 cannot mount directories on a different drive, and mount point cannot be across drives.
 822       */
 823      mountPoints?: MountPointList;
 824      /**
 825       * 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.
 826       */
 827      volumesFrom?: VolumeFromList;
 828      /**
 829       * Linux-specific modifications that are applied to the container, such as Linux kernel capabilities. For more information see KernelCapabilities.  This parameter is not supported for Windows containers. 
 830       */
 831      linuxParameters?: LinuxParameters;
 832      /**
 833       * The secrets to pass to the container. For more information, see Specifying Sensitive Data in the Amazon Elastic Container Service Developer Guide.
 834       */
 835      secrets?: SecretList;
 836      /**
 837       * 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. For tasks using the EC2 launch type, the container instances require at least version 1.26.0 of the container agent to enable 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 are 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 platform version 1.3.0 or later.
 838       */
 839      dependsOn?: ContainerDependencies;
 840      /**
 841       * 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 does not reach the desired status within that time then containerA will give up and not start. This results in the task transitioning to a STOPPED state.  When the ECS_CONTAINER_START_TIMEOUT container agent configuration variable is used, it is enforced indendently from this start timeout value.  For tasks using the Fargate launch type, this parameter requires that the task or service uses platform version 1.3.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 enable 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 are 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.
 842       */
 843      startTimeout?: BoxedInteger;
 844      /**
 845       * 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 platform version 1.3.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 using the EC2 launch type, if the stopTimeout parameter is not specified, the value set for the Amazon ECS container agent configuration variable ECS_CONTAINER_STOP_TIMEOUT is used by default. 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 enable 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 are 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.
 846       */
 847      stopTimeout?: BoxedInteger;
 848      /**
 849       * 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.  The hostname parameter is not supported if you are using the awsvpc network mode. 
 850       */
 851      hostname?: String;
 852      /**
 853       * 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.  When running tasks 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.  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     This parameter is not supported for Windows containers. 
 854       */
 855      user?: String;
 856      /**
 857       * The working directory in which to run commands inside the container. This parameter maps to WorkingDir in the Create a container section of the Docker Remote API and the --workdir option to docker run.
 858       */
 859      workingDirectory?: String;
 860      /**
 861       * 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.  This parameter is not supported for Windows containers. 
 862       */
 863      disableNetworking?: BoxedBoolean;
 864      /**
 865       * 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.  This parameter is not supported for Windows containers or tasks run on Fargate. 
 866       */
 867      privileged?: BoxedBoolean;
 868      /**
 869       * 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.  This parameter is not supported for Windows containers. 
 870       */
 871      readonlyRootFilesystem?: BoxedBoolean;
 872      /**
 873       * 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.  This parameter is not supported for Windows containers. 
 874       */
 875      dnsServers?: StringList;
 876      /**
 877       * 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.  This parameter is not supported for Windows containers. 
 878       */
 879      dnsSearchDomains?: StringList;
 880      /**
 881       * 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.  This parameter is not supported for Windows containers or tasks that use the awsvpc network mode. 
 882       */
 883      extraHosts?: HostEntryList;
 884      /**
 885       * A list of strings to provide custom labels for SELinux and AppArmor multi-level security systems. This field is not 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.  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"
 886       */
 887      dockerSecurityOptions?: StringList;
 888      /**
 889       * When this parameter is true, this allows you to 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.
 890       */
 891      interactive?: BoxedBoolean;
 892      /**
 893       * 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.
 894       */
 895      pseudoTerminal?: BoxedBoolean;
 896      /**
 897       * 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}}' 
 898       */
 899      dockerLabels?: DockerLabelsMap;
 900      /**
 901       * A list of ulimits to set in the container. If a ulimit value is specified in a task definition, it will override 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}}'   This parameter is not supported for Windows containers. 
 902       */
 903      ulimits?: UlimitList;
 904      /**
 905       * 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 may 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 on the options for different supported log drivers, see Configure logging drivers in the Docker documentation.  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}}'   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. 
 906       */
 907      logConfiguration?: LogConfiguration;
 908      /**
 909       * 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.
 910       */
 911      healthCheck?: HealthCheck;
 912      /**
 913       * 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.  It is not 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 is 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. 
 914       */
 915      systemControls?: SystemControls;
 916      /**
 917       * The type and amount of a resource to assign to a container. The only supported resource is a GPU.
 918       */
 919      resourceRequirements?: ResourceRequirements;
 920      /**
 921       * 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.
 922       */
 923      firelensConfiguration?: FirelensConfiguration;
 924    }
 925    export type ContainerDefinitions = ContainerDefinition[];
 926    export type ContainerDependencies = ContainerDependency[];
 927    export interface ContainerDependency {
 928      /**
 929       * The name of a container.
 930       */
 931      containerName: String;
 932      /**
 933       * 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 cannot 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 cannot 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.  
 934       */
 935      condition: ContainerCondition;
 936    }
 937    export interface ContainerInstance {
 938      /**
 939       * The Amazon Resource Name (ARN) of the container instance. The ARN contains the arn:aws:ecs namespace, followed by the Region of the container instance, the Amazon Web Services account ID of the container instance owner, the container-instance namespace, and then the container instance ID. For example, arn:aws:ecs:region:aws_account_id:container-instance/container_instance_ID.
 940       */
 941      containerInstanceArn?: String;
 942      /**
 943       * The ID of the container instance. For Amazon EC2 instances, this value is the Amazon EC2 instance ID. For external instances, this value is the Amazon Web Services Systems Manager managed instance ID.
 944       */
 945      ec2InstanceId?: String;
 946      /**
 947       * The capacity provider associated with the container instance.
 948       */
 949      capacityProviderName?: String;
 950      /**
 951       * The version counter for the container instance. Every time a container instance experiences a change that triggers a CloudWatch event, the version counter is incremented. If you are replicating your Amazon ECS container instance state with CloudWatch Events, you can compare the version of a container instance reported by the Amazon ECS APIs with the version reported in CloudWatch Events for the container instance (inside the detail object) to verify that the version in your event stream is current.
 952       */
 953      version?: Long;
 954      /**
 955       * The version information for the Amazon ECS container agent and Docker daemon running on the container instance.
 956       */
 957      versionInfo?: VersionInfo;
 958      /**
 959       * For CPU and memory resource types, this parameter describes the remaining CPU and memory that has not already been allocated to tasks and is therefore available for new tasks. For port resource types, this parameter describes the ports that were reserved by the Amazon ECS container agent (at instance registration time) and any task containers that have reserved port mappings on the host (with the host or bridge network mode). Any port that is not specified here is available for new tasks.
 960       */
 961      remainingResources?: Resources;
 962      /**
 963       * For CPU and memory resource types, this parameter describes the amount of each resource that was available on the container instance when the container agent registered it with Amazon ECS. This value represents the total amount of CPU and memory that can be allocated on this container instance to tasks. For port resource types, this parameter describes the ports that were reserved by the Amazon ECS container agent when it registered the container instance with Amazon ECS.
 964       */
 965      registeredResources?: Resources;
 966      /**
 967       * The status of the container instance. The valid values are REGISTERING, REGISTRATION_FAILED, ACTIVE, INACTIVE, DEREGISTERING, or DRAINING. If your account has opted in to the awsvpcTrunking account setting, then any newly registered container instance will transition to a REGISTERING status while the trunk elastic network interface is provisioned for the instance. If the registration fails, the instance will transition to a REGISTRATION_FAILED status. You can describe the container instance and see the reason for failure in the statusReason parameter. Once the container instance is terminated, the instance transitions to a DEREGISTERING status while the trunk elastic network interface is deprovisioned. The instance then transitions to an INACTIVE status. The ACTIVE status indicates that the container instance can accept tasks. The DRAINING indicates that new tasks are not placed on the container instance and any service tasks running on the container instance are removed if possible. For more information, see Container Instance Draining in the Amazon Elastic Container Service Developer Guide.
 968       */
 969      status?: String;
 970      /**
 971       * The reason that the container instance reached its current status.
 972       */
 973      statusReason?: String;
 974      /**
 975       * This parameter returns true if the agent is connected to Amazon ECS. Registered instances with an agent that may be unhealthy or stopped return false. Only instances connected to an agent can accept placement requests.
 976       */
 977      agentConnected?: Boolean;
 978      /**
 979       * The number of tasks on the container instance that are in the RUNNING status.
 980       */
 981      runningTasksCount?: Integer;
 982      /**
 983       * The number of tasks on the container instance that are in the PENDING status.
 984       */
 985      pendingTasksCount?: Integer;
 986      /**
 987       * The status of the most recent agent update. If an update has never been requested, this value is NULL.
 988       */
 989      agentUpdateStatus?: AgentUpdateStatus;
 990      /**
 991       * The attributes set for the container instance, either by the Amazon ECS container agent at instance registration or manually with the PutAttributes operation.
 992       */
 993      attributes?: Attributes;
 994      /**
 995       * The Unix timestamp for when the container instance was registered.
 996       */
 997      registeredAt?: Timestamp;
 998      /**
 999       * The resources attached to a container instance, such as elastic network interfaces.
1000       */
1001      attachments?: Attachments;
1002      /**
1003       * The metadata that you apply to the container instance to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. 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.  
1004       */
1005      tags?: Tags;
1006    }
1007    export type ContainerInstanceField = "TAGS"|string;
1008    export type ContainerInstanceFieldList = ContainerInstanceField[];
1009    export type ContainerInstanceStatus = "ACTIVE"|"DRAINING"|"REGISTERING"|"DEREGISTERING"|"REGISTRATION_FAILED"|string;
1010    export type ContainerInstances = ContainerInstance[];
1011    export interface ContainerOverride {
1012      /**
1013       * The name of the container that receives the override. This parameter is required if any override is specified.
1014       */
1015      name?: String;
1016      /**
1017       * 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.
1018       */
1019      command?: StringList;
1020      /**
1021       * 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.
1022       */
1023      environment?: EnvironmentVariables;
1024      /**
1025       * A list of files containing the environment variables to pass to a container, instead of the value from the container definition.
1026       */
1027      environmentFiles?: EnvironmentFiles;
1028      /**
1029       * 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.
1030       */
1031      cpu?: BoxedInteger;
1032      /**
1033       * 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.
1034       */
1035      memory?: BoxedInteger;
1036      /**
1037       * 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.
1038       */
1039      memoryReservation?: BoxedInteger;
1040      /**
1041       * 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.
1042       */
1043      resourceRequirements?: ResourceRequirements;
1044    }
1045    export type ContainerOverrides = ContainerOverride[];
1046    export interface ContainerStateChange {
1047      /**
1048       * The name of the container.
1049       */
1050      containerName?: String;
1051      /**
1052       * The container image SHA 256 digest.
1053       */
1054      imageDigest?: String;
1055      /**
1056       * The ID of the Docker container.
1057       */
1058      runtimeId?: String;
1059      /**
1060       * The exit code for the container, if the state change is a result of the container exiting.
1061       */
1062      exitCode?: BoxedInteger;
1063      /**
1064       * Any network bindings associated with the container.
1065       */
1066      networkBindings?: NetworkBindings;
1067      /**
1068       * The reason for the state change.
1069       */
1070      reason?: String;
1071      /**
1072       * The status of the container.
1073       */
1074      status?: String;
1075    }
1076    export type ContainerStateChanges = ContainerStateChange[];
1077    export type Containers = Container[];
1078    export interface CreateCapacityProviderRequest {
1079      /**
1080       * The name of the capacity provider. Up to 255 characters are allowed, including letters (upper and lowercase), numbers, underscores, and hyphens. The name cannot be prefixed with "aws", "ecs", or "fargate".
1081       */
1082      name: String;
1083      /**
1084       * The details of the Auto Scaling group for the capacity provider.
1085       */
1086      autoScalingGroupProvider: AutoScalingGroupProvider;
1087      /**
1088       * The metadata that you apply to the capacity provider to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. 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.  
1089       */
1090      tags?: Tags;
1091    }
1092    export interface CreateCapacityProviderResponse {
1093      /**
1094       * The full description of the new capacity provider.
1095       */
1096      capacityProvider?: CapacityProvider;
1097    }
1098    export interface CreateClusterRequest {
1099      /**
1100       * The name of your cluster. If you do not specify a name for your cluster, you create a cluster named default. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed. 
1101       */
1102      clusterName?: String;
1103      /**
1104       * 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, both of which you define. 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.  
1105       */
1106      tags?: Tags;
1107      /**
1108       * The setting to use when creating a cluster. This parameter is used to enable CloudWatch Container Insights for a cluster. If this value is specified, it will override the containerInsights value set with PutAccountSetting or PutAccountSettingDefault.
1109       */
1110      settings?: ClusterSettings;
1111      /**
1112       * The execute command configuration for the cluster.
1113       */
1114      configuration?: ClusterConfiguration;
1115      /**
1116       * 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 already be created and not already 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.
1117       */
1118      capacityProviders?: StringList;
1119      /**
1120       * The capacity provider strategy to set as the default for the cluster. When a default capacity provider strategy is set for a cluster, when calling 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 is not defined for a cluster during creation, it can be defined later with the PutClusterCapacityProviders API operation.
1121       */
1122      defaultCapacityProviderStrategy?: CapacityProviderStrategy;
1123    }
1124    export interface CreateClusterResponse {
1125      /**
1126       * The full description of your new cluster.
1127       */
1128      cluster?: Cluster;
1129    }
1130    export interface CreateServiceRequest {
1131      /**
1132       * The short name or full Amazon Resource Name (ARN) of the cluster on which to run your service. If you do not specify a cluster, the default cluster is assumed.
1133       */
1134      cluster?: String;
1135      /**
1136       * 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.
1137       */
1138      serviceName: String;
1139      /**
1140       * The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision is not specified, the latest ACTIVE revision is used. A task definition must be specified if the service is using either the ECS or CODE_DEPLOY deployment controllers.
1141       */
1142      taskDefinition?: String;
1143      /**
1144       * 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 is using 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 make use of 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 is using 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 associates one target group with it, and then 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 allows you perform validation tests with Lambda functions before routing production traffic to it. After you create a service using the ECS deployment controller, the load balancer name or target group ARN, container name, and container port specified in the service definition are immutable. If you are using 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 (as it appears in a container definition), and the container port to access from the load balancer. 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 specified here. For Classic Load Balancers, this object must contain the load balancer name, the container name (as it appears in a container definition), and the container port to access from the load balancer. 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 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 are not supported. Also, when you create any target groups for these services, you must choose ip as the target type, not instance, because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance.
1145       */
1146      loadBalancers?: LoadBalancers;
1147      /**
1148       * The details of the service discovery registry to associate with this service. For more information, see Service discovery.  Each service may be associated with one service registry. Multiple service registries per service isn't supported. 
1149       */
1150      serviceRegistries?: ServiceRegistries;
1151      /**
1152       * 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 is not specified. If schedulingStrategy is DAEMON then this is not required.
1153       */
1154      desiredCount?: BoxedInteger;
1155      /**
1156       * Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. Up to 32 ASCII characters are allowed.
1157       */
1158      clientToken?: String;
1159      /**
1160       * The infrastructure on which to run your service. 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.  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-premise 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.
1161       */
1162      launchType?: LaunchType;
1163      /**
1164       * 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.
1165       */
1166      capacityProviderStrategy?: CapacityProviderStrategy;
1167      /**
1168       * 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 by default. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide.
1169       */
1170      platformVersion?: String;
1171      /**
1172       * 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 does not use the awsvpc network mode. If you specify the role parameter, you must also specify a load balancer object with the loadBalancers parameter.  If your account has already created the Amazon ECS service-linked role, that role is used by default 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 should not 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.
1173       */
1174      role?: String;
1175      /**
1176       * Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
1177       */
1178      deploymentConfiguration?: DeploymentConfiguration;
1179      /**
1180       * An array of placement constraint objects to use for tasks in your service. You can specify a maximum of 10 constraints per task (this limit includes constraints in the task definition and those specified at runtime).
1181       */
1182      placementConstraints?: PlacementConstraints;
1183      /**
1184       * The placement strategy objects to use for tasks in your service. You can specify a maximum of 5 strategy rules per service.
1185       */
1186      placementStrategy?: PlacementStrategies;
1187      /**
1188       * 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 is not supported for other network modes. For more information, see Task networking in the Amazon Elastic Container Service Developer Guide.
1189       */
1190      networkConfiguration?: NetworkConfiguration;
1191      /**
1192       * The period of time, in seconds, that the Amazon ECS service scheduler should ignore 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 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. 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.
1193       */
1194      healthCheckGracePeriodSeconds?: BoxedInteger;
1195      /**
1196       * 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 is using 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 do not 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.  Tasks using the Fargate launch type or the CODE_DEPLOY or EXTERNAL deployment controller types don't support the DAEMON scheduling strategy.   
1197       */
1198      schedulingStrategy?: SchedulingStrategy;
1199      /**
1200       * The deployment controller to use for the service. If no deployment controller is specified, the default value of ECS is used.
1201       */
1202      deploymentController?: DeploymentController;
1203      /**
1204       * 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.  
1205       */
1206      tags?: Tags;
1207      /**
1208       * Specifies whether to enable 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.
1209       */
1210      enableECSManagedTags?: Boolean;
1211      /**
1212       * Specifies whether to propagate the tags from the task definition or the service to the tasks in the service. If no value is specified, the tags are not propagated. Tags can only be propagated to the tasks within the service during service creation. To add tags to a task after service creation, use the TagResource API action.
1213       */
1214      propagateTags?: PropagateTags;
1215      /**
1216       * Whether or not the execute command functionality is enabled for the service. If true, this enables execute command functionality on all containers in the service tasks.
1217       */
1218      enableExecuteCommand?: Boolean;
1219    }
1220    export interface CreateServiceResponse {
1221      /**
1222       * The full description of your service following the create call. A service will return either a capacityProviderStrategy or launchType parameter, but not both, depending on which one was specified during creation. If a service is using the ECS deployment controller, the deploymentController and taskSets parameters will not be returned. If the service is using the CODE_DEPLOY deployment controller, the deploymentController, taskSets and deployments parameters will be returned, however the deployments parameter will be an empty list.
1223       */
1224      service?: Service;
1225    }
1226    export interface CreateTaskSetRequest {
1227      /**
1228       * The short name or full Amazon Resource Name (ARN) of the service to create the task set in.
1229       */
1230      service: String;
1231      /**
1232       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service to create the task set in.
1233       */
1234      cluster: String;
1235      /**
1236       * An optional non-unique tag that identifies this task set in external systems. If the task set is associated with a service discovery registry, the tasks in this task set will have the ECS_TASK_SET_EXTERNAL_ID Cloud Map attribute set to the provided value.
1237       */
1238      externalId?: String;
1239      /**
1240       * The task definition for the tasks in the task set to use.
1241       */
1242      taskDefinition: String;
1243      /**
1244       * An object representing the network configuration for a task set.
1245       */
1246      networkConfiguration?: NetworkConfiguration;
1247      /**
1248       * A load balancer object representing the load balancer to use with the task set. The supported load balancer types are either an Application Load Balancer or a Network Load Balancer.
1249       */
1250      loadBalancers?: LoadBalancers;
1251      /**
1252       * The details of the service discovery registries to assign to this task set. For more information, see Service Discovery.
1253       */
1254      serviceRegistries?: ServiceRegistries;
1255      /**
1256       * The launch type that new tasks in the task set will use. For more information, see Amazon ECS Launch Types in the Amazon Elastic Container Service Developer Guide. If a launchType is specified, the capacityProviderStrategy parameter must be omitted.
1257       */
1258      launchType?: LaunchType;
1259      /**
1260       * The capacity provider strategy to use for the task set. 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 a capacityProviderStrategy is specified, the launchType parameter must be omitted. If no capacityProviderStrategy or launchType is specified, the defaultCapacityProviderStrategy for the cluster is 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. The PutClusterCapacityProviders API operation is used to update the list of available capacity providers for a cluster after the cluster is created.
1261       */
1262      capacityProviderStrategy?: CapacityProviderStrategy;
1263      /**
1264       * The platform version that the tasks in the task set should use. A platform version is specified only for tasks using the Fargate launch type. If one isn't specified, the LATEST platform version is used by default.
1265       */
1266      platformVersion?: String;
1267      /**
1268       * A floating-point percentage of the desired number of tasks to place and keep running in the task set.
1269       */
1270      scale?: Scale;
1271      /**
1272       * Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. Up to 32 ASCII characters are allowed.
1273       */
1274      clientToken?: String;
1275      /**
1276       * 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, 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.  
1277       */
1278      tags?: Tags;
1279    }
1280    export interface CreateTaskSetResponse {
1281      /**
1282       * Information about a set of Amazon ECS tasks in either an CodeDeploy or an EXTERNAL deployment. A task set includes details such as the desired number of tasks, how many tasks are running, and whether the task set serves production traffic.
1283       */
1284      taskSet?: TaskSet;
1285    }
1286    export interface DeleteAccountSettingRequest {
1287      /**
1288       * The resource name for which to disable the account setting. If serviceLongArnFormat is specified, the ARN for your Amazon ECS services is affected. If taskLongArnFormat is specified, the ARN and resource ID for your Amazon ECS tasks is affected. If containerInstanceLongArnFormat is specified, the ARN and resource ID for your Amazon ECS container instances is affected. If awsvpcTrunking is specified, the ENI limit for your Amazon ECS container instances is affected.
1289       */
1290      name: SettingName;
1291      /**
1292       * The ARN of the principal, which can be an IAM user, IAM role, or the root user. If you specify the root user, it disables the account setting for all IAM users, IAM roles, and the root user of the account unless an IAM user or role explicitly overrides these settings. If this field is omitted, the setting is changed only for the authenticated user.
1293       */
1294      principalArn?: String;
1295    }
1296    export interface DeleteAccountSettingResponse {
1297      /**
1298       * The account setting for the specified principal ARN.
1299       */
1300      setting?: Setting;
1301    }
1302    export interface DeleteAttributesRequest {
1303      /**
1304       * The short name or full Amazon Resource Name (ARN) of the cluster that contains the resource to delete attributes. If you do not specify a cluster, the default cluster is assumed.
1305       */
1306      cluster?: String;
1307      /**
1308       * The attributes to delete from your resource. You can specify up to 10 attributes per request. For custom attributes, specify the attribute name and target ID, but do not specify the value. If you specify the target ID using the short form, you must also specify the target type.
1309       */
1310      attributes: Attributes;
1311    }
1312    export interface DeleteAttributesResponse {
1313      /**
1314       * A list of attribute objects that were successfully deleted from your resource.
1315       */
1316      attributes?: Attributes;
1317    }
1318    export interface DeleteCapacityProviderRequest {
1319      /**
1320       * The short name or full Amazon Resource Name (ARN) of the capacity provider to delete.
1321       */
1322      capacityProvider: String;
1323    }
1324    export interface DeleteCapacityProviderResponse {
1325      /**
1326       * The details of the capacity provider.
1327       */
1328      capacityProvider?: CapacityProvider;
1329    }
1330    export interface DeleteClusterRequest {
1331      /**
1332       * The short name or full Amazon Resource Name (ARN) of the cluster to delete.
1333       */
1334      cluster: String;
1335    }
1336    export interface DeleteClusterResponse {
1337      /**
1338       * The full description of the deleted cluster.
1339       */
1340      cluster?: Cluster;
1341    }
1342    export interface DeleteServiceRequest {
1343      /**
1344       * 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.
1345       */
1346      cluster?: String;
1347      /**
1348       * The name of the service to delete.
1349       */
1350      service: String;
1351      /**
1352       * If true, allows you to delete a service even if it has not been scaled down to zero tasks. It is only necessary to use this if the service is using the REPLICA scheduling strategy.
1353       */
1354      force?: BoxedBoolean;
1355    }
1356    export interface DeleteServiceResponse {
1357      /**
1358       * The full description of the deleted service.
1359       */
1360      service?: Service;
1361    }
1362    export interface DeleteTaskSetRequest {
1363      /**
1364       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task set exists in to delete.
1365       */
1366      cluster: String;
1367      /**
1368       * The short name or full Amazon Resource Name (ARN) of the service that hosts the task set to delete.
1369       */
1370      service: String;
1371      /**
1372       * The task set ID or full Amazon Resource Name (ARN) of the task set to delete.
1373       */
1374      taskSet: String;
1375      /**
1376       * If true, this allows you to delete a task set even if it hasn't been scaled down to zero.
1377       */
1378      force?: BoxedBoolean;
1379    }
1380    export interface DeleteTaskSetResponse {
1381      /**
1382       * Details about the task set.
1383       */
1384      taskSet?: TaskSet;
1385    }
1386    export interface Deployment {
1387      /**
1388       * The ID of the deployment.
1389       */
1390      id?: String;
1391      /**
1392       * 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.  
1393       */
1394      status?: String;
1395      /**
1396       * The most recent task definition that was specified for the tasks in the service to use.
1397       */
1398      taskDefinition?: String;
1399      /**
1400       * The most recent desired count of tasks that was specified for the service to deploy or maintain.
1401       */
1402      desiredCount?: Integer;
1403      /**
1404       * The number of tasks in the deployment that are in the PENDING status.
1405       */
1406      pendingCount?: Integer;
1407      /**
1408       * The number of tasks in the deployment that are in the RUNNING status.
1409       */
1410      runningCount?: Integer;
1411      /**
1412       * 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.  Once a service deployment has one or more successfully running tasks, the failed task count resets to zero and stops being evaluated. 
1413       */
1414      failedTasks?: Integer;
1415      /**
1416       * The Unix timestamp for when the service deployment was created.
1417       */
1418      createdAt?: Timestamp;
1419      /**
1420       * The Unix timestamp for when the service deployment was last updated.
1421       */
1422      updatedAt?: Timestamp;
1423      /**
1424       * The capacity provider strategy that the deployment is using.
1425       */
1426      capacityProviderStrategy?: CapacityProviderStrategy;
1427      /**
1428       * 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.
1429       */
1430      launchType?: LaunchType;
1431      /**
1432       * The platform version on which your tasks in the service are running. A platform version is only specified for tasks using the Fargate launch type. If one is not specified, the LATEST platform version is used by default. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.
1433       */
1434      platformVersion?: String;
1435      /**
1436       * The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.
1437       */
1438      networkConfiguration?: NetworkConfiguration;
1439      /**
1440       *  The rolloutState of a service is only returned for services that use the rolling update (ECS) deployment type that are not 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 will transition to a COMPLETED state. If the service fails to reach a steady state and circuit breaker is enabled, the deployment will transition to a FAILED state. A deployment in FAILED state will launch no new tasks. For more information, see DeploymentCircuitBreaker.
1441       */
1442      rolloutState?: DeploymentRolloutState;
1443      /**
1444       * A description of the rollout state of a deployment.
1445       */
1446      rolloutStateReason?: String;
1447    }
1448    export interface DeploymentCircuitBreaker {
1449      /**
1450       * Whether to enable the deployment circuit breaker logic for the service.
1451       */
1452      enable: Boolean;
1453      /**
1454       * Whether to enable 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.
1455       */
1456      rollback: Boolean;
1457    }
1458    export interface DeploymentConfiguration {
1459      /**
1460       *  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.
1461       */
1462      deploymentCircuitBreaker?: DeploymentCircuitBreaker;
1463      /**
1464       * If a service is using the rolling update (ECS) deployment type, 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, as a percentage of the desired number of tasks (rounded down to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to 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 is using 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.
1465       */
1466      maximumPercent?: BoxedInteger;
1467      /**
1468       * If a service is using the rolling update (ECS) deployment type, 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, as a percentage of the desired number of tasks (rounded up to the nearest integer), and while any container instances are in the DRAINING state if the service contains tasks using the EC2 launch type. This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desired number of four tasks and a minimum healthy percent of 50%, the scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks. Tasks for services that do not use a load balancer are considered healthy if they are in the RUNNING state; tasks for services that do use a load balancer are considered healthy if they are in the RUNNING state and they are reported as healthy by the load balancer. The default value for minimum healthy percent is 100%. If a service is using the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and 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 the tasks in the service use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.
1469       */
1470      minimumHealthyPercent?: BoxedInteger;
1471    }
1472    export interface DeploymentController {
1473      /**
1474       * 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.  
1475       */
1476      type: DeploymentControllerType;
1477    }
1478    export type DeploymentControllerType = "ECS"|"CODE_DEPLOY"|"EXTERNAL"|string;
1479    export type DeploymentRolloutState = "COMPLETED"|"FAILED"|"IN_PROGRESS"|string;
1480    export type Deployments = Deployment[];
1481    export interface DeregisterContainerInstanceRequest {
1482      /**
1483       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the container instance to deregister. If you do not specify a cluster, the default cluster is assumed.
1484       */
1485      cluster?: String;
1486      /**
1487       * The container instance ID or full ARN of the container instance to deregister. The ARN contains the arn:aws:ecs namespace, followed by the Region of the container instance, the Amazon Web Services account ID of the container instance owner, the container-instance namespace, and then the container instance ID. For example, arn:aws:ecs:region:aws_account_id:container-instance/container_instance_ID.
1488       */
1489      containerInstance: String;
1490      /**
1491       * Forces the deregistration of the container instance. If you have tasks running on the container instance when you deregister it with the force option, these tasks remain running until you terminate the instance or the tasks stop through some other means, but they are orphaned (no longer monitored or accounted for by Amazon ECS). If an orphaned task on your container instance is part of an Amazon ECS service, then the service scheduler starts another copy of that task, on a different container instance if possible.  Any containers in orphaned service tasks that are registered with a Classic Load Balancer or an Application Load Balancer target group are deregistered. They begin connection draining according to the settings on the load balancer or target group.
1492       */
1493      force?: BoxedBoolean;
1494    }
1495    export interface DeregisterContainerInstanceResponse {
1496      /**
1497       * The container instance that was deregistered.
1498       */
1499      containerInstance?: ContainerInstance;
1500    }
1501    export interface DeregisterTaskDefinitionRequest {
1502      /**
1503       * The family and revision (family:revision) or full Amazon Resource Name (ARN) of the task definition to deregister. You must specify a revision.
1504       */
1505      taskDefinition: String;
1506    }
1507    export interface DeregisterTaskDefinitionResponse {
1508      /**
1509       * The full description of the deregistered task.
1510       */
1511      taskDefinition?: TaskDefinition;
1512    }
1513    export interface DescribeCapacityProvidersRequest {
1514      /**
1515       * The short name or full Amazon Resource Name (ARN) of one or more capacity providers. Up to 100 capacity providers can be described in an action.
1516       */
1517      capacityProviders?: StringList;
1518      /**
1519       * Specifies whether or not you want to see the resource tags for the capacity provider. If TAGS is specified, the tags are included in the response. If this field is omitted, tags are not included in the response.
1520       */
1521      include?: CapacityProviderFieldList;
1522      /**
1523       * The maximum number of account setting results returned by DescribeCapacityProviders in paginated output. When this parameter is used, DescribeCapacityProviders 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 DescribeCapacityProviders request with the returned nextToken value. This value can be between 1 and 10. If this parameter is not used, then DescribeCapacityProviders returns up to 10 results and a nextToken value if applicable.
1524       */
1525      maxResults?: BoxedInteger;
1526      /**
1527       * The nextToken value returned from a previous paginated DescribeCapacityProviders request where maxResults was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the nextToken value.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
1528       */
1529      nextToken?: String;
1530    }
1531    export interface DescribeCapacityProvidersResponse {
1532      /**
1533       * The list of capacity providers.
1534       */
1535      capacityProviders?: CapacityProviders;
1536      /**
1537       * Any failures associated with the call.
1538       */
1539      failures?: Failures;
1540      /**
1541       * The nextToken value to include in a future DescribeCapacityProviders request. When the results of a DescribeCapacityProviders request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
1542       */
1543      nextToken?: String;
1544    }
1545    export interface DescribeClustersRequest {
1546      /**
1547       * 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.
1548       */
1549      clusters?: StringList;
1550      /**
1551       * 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. 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.
1552       */
1553      include?: ClusterFieldList;
1554    }
1555    export interface DescribeClustersResponse {
1556      /**
1557       * The list of clusters.
1558       */
1559      clusters?: Clusters;
1560      /**
1561       * Any failures associated with the call.
1562       */
1563      failures?: Failures;
1564    }
1565    export interface DescribeContainerInstancesRequest {
1566      /**
1567       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the container instances to describe. If you do not specify a cluster, the default cluster is assumed. This parameter is required if the container instance or container instances you are describing were launched in any cluster other than the default cluster.
1568       */
1569      cluster?: String;
1570      /**
1571       * A list of up to 100 container instance IDs or full Amazon Resource Name (ARN) entries.
1572       */
1573      containerInstances: StringList;
1574      /**
1575       * Specifies whether you want to see the resource tags for the container instance. If TAGS is specified, the tags are included in the response. If this field is omitted, tags are not included in the response.
1576       */
1577      include?: ContainerInstanceFieldList;
1578    }
1579    export interface DescribeContainerInstancesResponse {
1580      /**
1581       * The list of container instances.
1582       */
1583      containerInstances?: ContainerInstances;
1584      /**
1585       * Any failures associated with the call.
1586       */
1587      failures?: Failures;
1588    }
1589    export interface DescribeServicesRequest {
1590      /**
1591       * 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.
1592       */
1593      cluster?: String;
1594      /**
1595       * A list of services to describe. You may specify up to 10 services to describe in a single operation.
1596       */
1597      services: StringList;
1598      /**
1599       * Specifies 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 are not included in the response.
1600       */
1601      include?: ServiceFieldList;
1602    }
1603    export interface DescribeServicesResponse {
1604      /**
1605       * The list of services described.
1606       */
1607      services?: Services;
1608      /**
1609       * Any failures associated with the call.
1610       */
1611      failures?: Failures;
1612    }
1613    export interface DescribeTaskDefinitionRequest {
1614      /**
1615       * 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.
1616       */
1617      taskDefinition: String;
1618      /**
1619       * Specifies 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 are not included in the response.
1620       */
1621      include?: TaskDefinitionFieldList;
1622    }
1623    export interface DescribeTaskDefinitionResponse {
1624      /**
1625       * The full task definition description.
1626       */
1627      taskDefinition?: TaskDefinition;
1628      /**
1629       * The metadata that is applied to the task definition to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. 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.  
1630       */
1631      tags?: Tags;
1632    }
1633    export interface DescribeTaskSetsRequest {
1634      /**
1635       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task sets exist in.
1636       */
1637      cluster: String;
1638      /**
1639       * The short name or full Amazon Resource Name (ARN) of the service that the task sets exist in.
1640       */
1641      service: String;
1642      /**
1643       * The ID or full Amazon Resource Name (ARN) of task sets to describe.
1644       */
1645      taskSets?: StringList;
1646      /**
1647       * Specifies whether to see the resource tags for the task set. If TAGS is specified, the tags are included in the response. If this field is omitted, tags are not included in the response.
1648       */
1649      include?: TaskSetFieldList;
1650    }
1651    export interface DescribeTaskSetsResponse {
1652      /**
1653       * The list of task sets described.
1654       */
1655      taskSets?: TaskSets;
1656      /**
1657       * Any failures associated with the call.
1658       */
1659      failures?: Failures;
1660    }
1661    export interface DescribeTasksRequest {
1662      /**
1663       * 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.
1664       */
1665      cluster?: String;
1666      /**
1667       * A list of up to 100 task IDs or full ARN entries.
1668       */
1669      tasks: StringList;
1670      /**
1671       * 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 are not included in the response.
1672       */
1673      include?: TaskFieldList;
1674    }
1675    export interface DescribeTasksResponse {
1676      /**
1677       * The list of tasks.
1678       */
1679      tasks?: Tasks;
1680      /**
1681       * Any failures associated with the call.
1682       */
1683      failures?: Failures;
1684    }
1685    export type DesiredStatus = "RUNNING"|"PENDING"|"STOPPED"|string;
1686    export interface Device {
1687      /**
1688       * The path for the device on the host container instance.
1689       */
1690      hostPath: String;
1691      /**
1692       * The path inside the container at which to expose the host device.
1693       */
1694      containerPath?: String;
1695      /**
1696       * 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.
1697       */
1698      permissions?: DeviceCgroupPermissions;
1699    }
1700    export type DeviceCgroupPermission = "read"|"write"|"mknod"|string;
1701    export type DeviceCgroupPermissions = DeviceCgroupPermission[];
1702    export type DevicesList = Device[];
1703    export interface DiscoverPollEndpointRequest {
1704      /**
1705       * The container instance ID or full ARN of the container instance. The ARN contains the arn:aws:ecs namespace, followed by the Region of the container instance, the Amazon Web Services account ID of the container instance owner, the container-instance namespace, and then the container instance ID. For example, arn:aws:ecs:region:aws_account_id:container-instance/container_instance_ID.
1706       */
1707      containerInstance?: String;
1708      /**
1709       * The short name or full Amazon Resource Name (ARN) of the cluster to which the container instance belongs.
1710       */
1711      cluster?: String;
1712    }
1713    export interface DiscoverPollEndpointResponse {
1714      /**
1715       * The endpoint for the Amazon ECS agent to poll.
1716       */
1717      endpoint?: String;
1718      /**
1719       * The telemetry endpoint for the Amazon ECS agent.
1720       */
1721      telemetryEndpoint?: String;
1722    }
1723    export type DockerLabelsMap = {[key: string]: String};
1724    export interface DockerVolumeConfiguration {
1725      /**
1726       * 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.
1727       */
1728      scope?: Scope;
1729      /**
1730       * If this value is true, the Docker volume is created if it does not already exist.  This field is only used if the scope is shared. 
1731       */
1732      autoprovision?: BoxedBoolean;
1733      /**
1734       * 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.
1735       */
1736      driver?: String;
1737      /**
1738       * 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.
1739       */
1740      driverOpts?: StringMap;
1741      /**
1742       * 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.
1743       */
1744      labels?: StringMap;
1745    }
1746    export type Double = number;
1747    export interface EFSAuthorizationConfig {
1748      /**
1749       * 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.
1750       */
1751      accessPointId?: String;
1752      /**
1753       * Whether or not 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.
1754       */
1755      iam?: EFSAuthorizationConfigIAM;
1756    }
1757    export type EFSAuthorizationConfigIAM = "ENABLED"|"DISABLED"|string;
1758    export type EFSTransitEncryption = "ENABLED"|"DISABLED"|string;
1759    export interface EFSVolumeConfiguration {
1760      /**
1761       * The Amazon EFS file system ID to use.
1762       */
1763      fileSystemId: String;
1764      /**
1765       * 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.  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. 
1766       */
1767      rootDirectory?: String;
1768      /**
1769       * Whether or not to enable 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.
1770       */
1771      transitEncryption?: EFSTransitEncryption;
1772      /**
1773       * 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.
1774       */
1775      transitEncryptionPort?: BoxedInteger;
1776      /**
1777       * The authorization configuration details for the Amazon EFS file system.
1778       */
1779      authorizationConfig?: EFSAuthorizationConfig;
1780    }
1781    export interface EnvironmentFile {
1782      /**
1783       * The Amazon Resource Name (ARN) of the Amazon S3 object containing the environment variable file.
1784       */
1785      value: String;
1786      /**
1787       * The file type to use. The only supported value is s3.
1788       */
1789      type: EnvironmentFileType;
1790    }
1791    export type EnvironmentFileType = "s3"|string;
1792    export type EnvironmentFiles = EnvironmentFile[];
1793    export type EnvironmentVariables = KeyValuePair[];
1794    export interface EphemeralStorage {
1795      /**
1796       * 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.
1797       */
1798      sizeInGiB: Integer;
1799    }
1800    export interface ExecuteCommandConfiguration {
1801      /**
1802       * Specify an Key Management Service key ID to encrypt the data between the local client and the container.
1803       */
1804      kmsKeyId?: String;
1805      /**
1806       * 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.  
1807       */
1808      logging?: ExecuteCommandLogging;
1809      /**
1810       * 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.
1811       */
1812      logConfiguration?: ExecuteCommandLogConfiguration;
1813    }
1814    export interface ExecuteCommandLogConfiguration {
1815      /**
1816       * The name of the CloudWatch log group to send logs to.  The CloudWatch log group must already be created. 
1817       */
1818      cloudWatchLogGroupName?: String;
1819      /**
1820       * Whether or not to enable encryption on the CloudWatch logs. If not specified, encryption will be disabled.
1821       */
1822      cloudWatchEncryptionEnabled?: Boolean;
1823      /**
1824       * The name of the S3 bucket to send logs to.  The S3 bucket must already be created. 
1825       */
1826      s3BucketName?: String;
1827      /**
1828       * Whether or not to enable encryption on the CloudWatch logs. If not specified, encryption will be disabled.
1829       */
1830      s3EncryptionEnabled?: Boolean;
1831      /**
1832       * An optional folder in the S3 bucket to place logs in.
1833       */
1834      s3KeyPrefix?: String;
1835    }
1836    export type ExecuteCommandLogging = "NONE"|"DEFAULT"|"OVERRIDE"|string;
1837    export interface ExecuteCommandRequest {
1838      /**
1839       * The Amazon Resource Name (ARN) or short name of the cluster the task is running in. If you do not specify a cluster, the default cluster is assumed.
1840       */
1841      cluster?: String;
1842      /**
1843       * The name of the container to execute the command on. A container name only needs to be specified for tasks containing multiple containers.
1844       */
1845      container?: String;
1846      /**
1847       * The command to run on the container.
1848       */
1849      command: String;
1850      /**
1851       * Use this flag to run your command in interactive mode.
1852       */
1853      interactive: Boolean;
1854      /**
1855       * The Amazon Resource Name (ARN) or ID of the task the container is part of.
1856       */
1857      task: String;
1858    }
1859    export interface ExecuteCommandResponse {
1860      /**
1861       * The Amazon Resource Name (ARN) of the cluster.
1862       */
1863      clusterArn?: String;
1864      /**
1865       * The Amazon Resource Name (ARN) of the container.
1866       */
1867      containerArn?: String;
1868      /**
1869       * The name of the container.
1870       */
1871      containerName?: String;
1872      /**
1873       * Whether or not the execute command session is running in interactive mode. Amazon ECS only supports initiating interactive sessions, so you must specify true for this value.
1874       */
1875      interactive?: Boolean;
1876      /**
1877       * The details of the SSM session that was created for this instance of execute-command.
1878       */
1879      session?: Session;
1880      /**
1881       * The Amazon Resource Name (ARN) of the task.
1882       */
1883      taskArn?: String;
1884    }
1885    export interface FSxWindowsFileServerAuthorizationConfig {
1886      /**
1887       * 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 ARNs refer to the stored credentials.
1888       */
1889      credentialsParameter: String;
1890      /**
1891       * A fully qualified domain name hosted by an Directory Service Managed Microsoft AD (Active Directory) or self-hosted AD on Amazon EC2.
1892       */
1893      domain: String;
1894    }
1895    export interface FSxWindowsFileServerVolumeConfiguration {
1896      /**
1897       * The Amazon FSx for Windows File Server file system ID to use.
1898       */
1899      fileSystemId: String;
1900      /**
1901       * The directory within the Amazon FSx for Windows File Server file system to mount as the root directory inside the host.
1902       */
1903      rootDirectory: String;
1904      /**
1905       * The authorization configuration details for the Amazon FSx for Windows File Server file system.
1906       */
1907      authorizationConfig: FSxWindowsFileServerAuthorizationConfig;
1908    }
1909    export interface Failure {
1910      /**
1911       * The Amazon Resource Name (ARN) of the failed resource.
1912       */
1913      arn?: String;
1914      /**
1915       * The reason for the failure.
1916       */
1917      reason?: String;
1918      /**
1919       * The details of the failure.
1920       */
1921      detail?: String;
1922    }
1923    export type Failures = Failure[];
1924    export interface FirelensConfiguration {
1925      /**
1926       * The log router to use. The valid values are fluentd or fluentbit.
1927       */
1928      type: FirelensConfigurationType;
1929      /**
1930       * 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.  Tasks hosted on Fargate only support the file configuration file type. 
1931       */
1932      options?: FirelensConfigurationOptionsMap;
1933    }
1934    export type FirelensConfigurationOptionsMap = {[key: string]: String};
1935    export type FirelensConfigurationType = "fluentd"|"fluentbit"|string;
1936    export type GpuIds = String[];
1937    export interface HealthCheck {
1938      /**
1939       * A string array representing the command that the container runs to determine if it is healthy. The string array must start with CMD to execute 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, you should enclose the list of commands in brackets, as shown below.  [ "CMD-SHELL", "curl -f http://localhost/ || exit 1" ]  You do not need to include the brackets when you use the Amazon Web Services Management Consoleas shown below.   "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.
1940       */
1941      command: StringList;
1942      /**
1943       * The time period in seconds between each health check execution. You may specify between 5 and 300 seconds. The default value is 30 seconds.
1944       */
1945      interval?: BoxedInteger;
1946      /**
1947       * 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.
1948       */
1949      timeout?: BoxedInteger;
1950      /**
1951       * 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.
1952       */
1953      retries?: BoxedInteger;
1954      /**
1955       * The optional grace period within which to provide containers time to bootstrap before failed health checks count towards the maximum number of retries. You may specify between 0 and 300 seconds. The startPeriod is disabled by default.  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. 
1956       */
1957      startPeriod?: BoxedInteger;
1958    }
1959    export type HealthStatus = "HEALTHY"|"UNHEALTHY"|"UNKNOWN"|string;
1960    export interface HostEntry {
1961      /**
1962       * The hostname to use in the /etc/hosts entry.
1963       */
1964      hostname: String;
1965      /**
1966       * The IP address to use in the /etc/hosts entry.
1967       */
1968      ipAddress: String;
1969    }
1970    export type HostEntryList = HostEntry[];
1971    export interface HostVolumeProperties {
1972      /**
1973       * When the host parameter is used, specify a sourcePath to declare the path on the host container instance that is 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 does not 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 are using the Fargate launch type, the sourcePath parameter is not supported.
1974       */
1975      sourcePath?: String;
1976    }
1977    export interface InferenceAccelerator {
1978      /**
1979       * The Elastic Inference accelerator device name. The deviceName must also be referenced in a container definition as a ResourceRequirement.
1980       */
1981      deviceName: String;
1982      /**
1983       * The Elastic Inference accelerator type to use.
1984       */
1985      deviceType: String;
1986    }
1987    export interface InferenceAcceleratorOverride {
1988      /**
1989       * The Elastic Inference accelerator device name to override for the task. This parameter must match a deviceName specified in the task definition.
1990       */
1991      deviceName?: String;
1992      /**
1993       * The Elastic Inference accelerator type to use.
1994       */
1995      deviceType?: String;
1996    }
1997    export type InferenceAcceleratorOverrides = InferenceAcceleratorOverride[];
1998    export type InferenceAccelerators = InferenceAccelerator[];
1999    export type Integer = number;
2000    export type IpcMode = "host"|"task"|"none"|string;
2001    export interface KernelCapabilities {
2002      /**
2003       * 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.  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" 
2004       */
2005      add?: StringList;
2006      /**
2007       * 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" 
2008       */
2009      drop?: StringList;
2010    }
2011    export interface KeyValuePair {
2012      /**
2013       * The name of the key-value pair. For environment variables, this is the name of the environment variable.
2014       */
2015      name?: String;
2016      /**
2017       * The value of the key-value pair. For environment variables, this is the value of the environment variable.
2018       */
2019      value?: String;
2020    }
2021    export type LaunchType = "EC2"|"FARGATE"|"EXTERNAL"|string;
2022    export interface LinuxParameters {
2023      /**
2024       * The Linux capabilities for the container that are added to or dropped from the default configuration provided by Docker.  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. 
2025       */
2026      capabilities?: KernelCapabilities;
2027      /**
2028       * 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.  If you are using tasks that use the Fargate launch type, the devices parameter is not supported. 
2029       */
2030      devices?: DevicesList;
2031      /**
2032       * 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}}' 
2033       */
2034      initProcessEnabled?: BoxedBoolean;
2035      /**
2036       * The value for the size (in MiB) of the /dev/shm volume. This parameter maps to the --shm-size option to docker run.  If you are using tasks that use the Fargate launch type, the sharedMemorySize parameter is not supported. 
2037       */
2038      sharedMemorySize?: BoxedInteger;
2039      /**
2040       * The container path, mount options, and size (in MiB) of the tmpfs mount. This parameter maps to the --tmpfs option to docker run.  If you are using tasks that use the Fargate launch type, the tmpfs parameter is not supported. 
2041       */
2042      tmpfs?: TmpfsList;
2043      /**
2044       * 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.  If you are using tasks that use the Fargate launch type, the maxSwap parameter is not supported. 
2045       */
2046      maxSwap?: BoxedInteger;
2047      /**
2048       * 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.  If you are using tasks that use the Fargate launch type, the swappiness parameter is not supported. 
2049       */
2050      swappiness?: BoxedInteger;
2051    }
2052    export interface ListAccountSettingsRequest {
2053      /**
2054       * The name of the account setting you want to list the settings for.
2055       */
2056      name?: SettingName;
2057      /**
2058       * The value of the account settings with which to filter results. You must also specify an account setting name to use this parameter.
2059       */
2060      value?: String;
2061      /**
2062       * The ARN of the principal, which can be an IAM user, IAM role, or the root user. If this field is omitted, the account settings are listed only for the authenticated user.  Federated users assume the account setting of the root user and can't have explicit account settings set for them. 
2063       */
2064      principalArn?: String;
2065      /**
2066       * Specifies whether to return the effective settings. If true, the account settings for the root user or the default setting for the principalArn are returned. If false, the account settings for the principalArn are returned if they are set. Otherwise, no account settings are returned.
2067       */
2068      effectiveSettings?: Boolean;
2069      /**
2070       * The nextToken value returned from a ListAccountSettings request indicating that more results are available to fulfill the request and further calls will be needed. If maxResults was provided, it is possible the number of results to be fewer than maxResults.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
2071       */
2072      nextToken?: String;
2073      /**
2074       * The maximum number of account setting results returned by ListAccountSettings in paginated output. When this parameter is used, ListAccountSettings 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 ListAccountSettings request with the returned nextToken value. This value can be between 1 and 10. If this parameter is not used, then ListAccountSettings returns up to 10 results and a nextToken value if applicable.
2075       */
2076      maxResults?: Integer;
2077    }
2078    export interface ListAccountSettingsResponse {
2079      /**
2080       * The account settings for the resource.
2081       */
2082      settings?: Settings;
2083      /**
2084       * The nextToken value to include in a future ListAccountSettings request. When the results of a ListAccountSettings request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
2085       */
2086      nextToken?: String;
2087    }
2088    export interface ListAttributesRequest {
2089      /**
2090       * The short name or full Amazon Resource Name (ARN) of the cluster to list attributes. If you do not specify a cluster, the default cluster is assumed.
2091       */
2092      cluster?: String;
2093      /**
2094       * The type of the target with which to list attributes.
2095       */
2096      targetType: TargetType;
2097      /**
2098       * The name of the attribute with which to filter the results. 
2099       */
2100      attributeName?: String;
2101      /**
2102       * The value of the attribute with which to filter results. You must also specify an attribute name to use this parameter.
2103       */
2104      attributeValue?: String;
2105      /**
2106       * The nextToken value returned from a ListAttributes request indicating that more results are available to fulfill the request and further calls will be needed. If maxResults was provided, it is possible the number of results to be fewer than maxResults.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
2107       */
2108      nextToken?: String;
2109      /**
2110       * The maximum number of cluster results returned by ListAttributes in paginated output. When this parameter is used, ListAttributes 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 ListAttributes request with the returned nextToken value. This value can be between 1 and 100. If this parameter is not used, then ListAttributes returns up to 100 results and a nextToken value if applicable.
2111       */
2112      maxResults?: BoxedInteger;
2113    }
2114    export interface ListAttributesResponse {
2115      /**
2116       * A list of attribute objects that meet the criteria of the request.
2117       */
2118      attributes?: Attributes;
2119      /**
2120       * The nextToken value to include in a future ListAttributes request. When the results of a ListAttributes request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
2121       */
2122      nextToken?: String;
2123    }
2124    export interface ListClustersRequest {
2125      /**
2126       * The nextToken value returned from a ListClusters request indicating that more results are available to fulfill the request and further calls will be needed. If maxResults was provided, it is possible the number of results to be fewer than maxResults.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
2127       */
2128      nextToken?: String;
2129      /**
2130       * The maximum number of cluster results returned by ListClusters in paginated output. When this parameter is used, ListClusters 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 ListClusters request with the returned nextToken value. This value can be between 1 and 100. If this parameter is not used, then ListClusters returns up to 100 results and a nextToken value if applicable.
2131       */
2132      maxResults?: BoxedInteger;
2133    }
2134    export interface ListClustersResponse {
2135      /**
2136       * The list of full Amazon Resource Name (ARN) entries for each cluster associated with your account.
2137       */
2138      clusterArns?: StringList;
2139      /**
2140       * The nextToken value to include in a future ListClusters request. When the results of a ListClusters request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
2141       */
2142      nextToken?: String;
2143    }
2144    export interface ListContainerInstancesRequest {
2145      /**
2146       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the container instances to list. If you do not specify a cluster, the default cluster is assumed.
2147       */
2148      cluster?: String;
2149      /**
2150       * You can filter the results of a ListContainerInstances operation with cluster query language statements. For more information, see Cluster Query Language in the Amazon Elastic Container Service Developer Guide.
2151       */
2152      filter?: String;
2153      /**
2154       * The nextToken value returned from a ListContainerInstances request indicating that more results are available to fulfill the request and further calls will be needed. If maxResults was provided, it is possible the number of results to be fewer than maxResults.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
2155       */
2156      nextToken?: String;
2157      /**
2158       * The maximum number of container instance results returned by ListContainerInstances in paginated output. When this parameter is used, ListContainerInstances 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 ListContainerInstances request with the returned nextToken value. This value can be between 1 and 100. If this parameter is not used, then ListContainerInstances returns up to 100 results and a nextToken value if applicable.
2159       */
2160      maxResults?: BoxedInteger;
2161      /**
2162       * Filters the container instances by status. For example, if you specify the DRAINING status, the results include only container instances that have been set to DRAINING using UpdateContainerInstancesState. If you do not specify this parameter, the default is to include container instances set to all states other than INACTIVE.
2163       */
2164      status?: ContainerInstanceStatus;
2165    }
2166    export interface ListContainerInstancesResponse {
2167      /**
2168       * The list of container instances with full ARN entries for each container instance associated with the specified cluster.
2169       */
2170      containerInstanceArns?: StringList;
2171      /**
2172       * The nextToken value to include in a future ListContainerInstances request. When the results of a ListContainerInstances request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
2173       */
2174      nextToken?: String;
2175    }
2176    export interface ListServicesRequest {
2177      /**
2178       * The short name or full Amazon Resource Name (ARN) of the cluster to use when filtering the ListServices results. If you do not specify a cluster, the default cluster is assumed.
2179       */
2180      cluster?: String;
2181      /**
2182       * The nextToken value returned from a ListServices request indicating that more results are available to fulfill the request and further calls will be needed. If maxResults was provided, it is possible the number of results to be fewer than maxResults.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
2183       */
2184      nextToken?: String;
2185      /**
2186       * The maximum number of service results returned by ListServices in paginated output. When this parameter is used, ListServices 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 ListServices request with the returned nextToken value. This value can be between 1 and 100. If this parameter is not used, then ListServices returns up to 10 results and a nextToken value if applicable.
2187       */
2188      maxResults?: BoxedInteger;
2189      /**
2190       * The launch type to use when filtering the ListServices results.
2191       */
2192      launchType?: LaunchType;
2193      /**
2194       * The scheduling strategy to use when filtering the ListServices results.
2195       */
2196      schedulingStrategy?: SchedulingStrategy;
2197    }
2198    export interface ListServicesResponse {
2199      /**
2200       * The list of full ARN entries for each service associated with the specified cluster.
2201       */
2202      serviceArns?: StringList;
2203      /**
2204       * The nextToken value to include in a future ListServices request. When the results of a ListServices request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
2205       */
2206      nextToken?: String;
2207    }
2208    export interface ListTagsForResourceRequest {
2209      /**
2210       * The Amazon Resource Name (ARN) that identifies the resource for which to list the tags. Currently, the supported resources are Amazon ECS tasks, services, task definitions, clusters, and container instances.
2211       */
2212      resourceArn: String;
2213    }
2214    export interface ListTagsForResourceResponse {
2215      /**
2216       * The tags for the resource.
2217       */
2218      tags?: Tags;
2219    }
2220    export interface ListTaskDefinitionFamiliesRequest {
2221      /**
2222       * The familyPrefix is a string that is used to filter the results of ListTaskDefinitionFamilies. If you specify a familyPrefix, only task definition family names that begin with the familyPrefix string are returned.
2223       */
2224      familyPrefix?: String;
2225      /**
2226       * The task definition family status with which to filter the ListTaskDefinitionFamilies results. By default, both ACTIVE and INACTIVE task definition families are listed. If this parameter is set to ACTIVE, only task definition families that have an ACTIVE task definition revision are returned. If this parameter is set to INACTIVE, only task definition families that do not have any ACTIVE task definition revisions are returned. If you paginate the resulting output, be sure to keep the status value constant in each subsequent request.
2227       */
2228      status?: TaskDefinitionFamilyStatus;
2229      /**
2230       * The nextToken value returned from a ListTaskDefinitionFamilies request indicating that more results are available to fulfill the request and further calls will be needed. If maxResults was provided, it is possible the number of results to be fewer than maxResults.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
2231       */
2232      nextToken?: String;
2233      /**
2234       * The maximum number of task definition family results returned by ListTaskDefinitionFamilies in paginated output. When this parameter is used, ListTaskDefinitions 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 ListTaskDefinitionFamilies request with the returned nextToken value. This value can be between 1 and 100. If this parameter is not used, then ListTaskDefinitionFamilies returns up to 100 results and a nextToken value if applicable.
2235       */
2236      maxResults?: BoxedInteger;
2237    }
2238    export interface ListTaskDefinitionFamiliesResponse {
2239      /**
2240       * The list of task definition family names that match the ListTaskDefinitionFamilies request.
2241       */
2242      families?: StringList;
2243      /**
2244       * The nextToken value to include in a future ListTaskDefinitionFamilies request. When the results of a ListTaskDefinitionFamilies request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
2245       */
2246      nextToken?: String;
2247    }
2248    export interface ListTaskDefinitionsRequest {
2249      /**
2250       * The full family name with which to filter the ListTaskDefinitions results. Specifying a familyPrefix limits the listed task definitions to task definition revisions that belong to that family.
2251       */
2252      familyPrefix?: String;
2253      /**
2254       * The task definition status with which to filter the ListTaskDefinitions results. By default, only ACTIVE task definitions are listed. By setting this parameter to INACTIVE, you can view task definitions that are INACTIVE as long as an active task or service still references them. If you paginate the resulting output, be sure to keep the status value constant in each subsequent request.
2255       */
2256      status?: TaskDefinitionStatus;
2257      /**
2258       * The order in which to sort the results. Valid values are ASC and DESC. By default (ASC), task definitions are listed lexicographically by family name and in ascending numerical order by revision so that the newest task definitions in a family are listed last. Setting this parameter to DESC reverses the sort order on family name and revision so that the newest task definitions in a family are listed first.
2259       */
2260      sort?: SortOrder;
2261      /**
2262       * The nextToken value returned from a ListTaskDefinitions request indicating that more results are available to fulfill the request and further calls will be needed. If maxResults was provided, it is possible the number of results to be fewer than maxResults.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
2263       */
2264      nextToken?: String;
2265      /**
2266       * The maximum number of task definition results returned by ListTaskDefinitions in paginated output. When this parameter is used, ListTaskDefinitions 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 ListTaskDefinitions request with the returned nextToken value. This value can be between 1 and 100. If this parameter is not used, then ListTaskDefinitions returns up to 100 results and a nextToken value if applicable.
2267       */
2268      maxResults?: BoxedInteger;
2269    }
2270    export interface ListTaskDefinitionsResponse {
2271      /**
2272       * The list of task definition Amazon Resource Name (ARN) entries for the ListTaskDefinitions request.
2273       */
2274      taskDefinitionArns?: StringList;
2275      /**
2276       * The nextToken value to include in a future ListTaskDefinitions request. When the results of a ListTaskDefinitions request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
2277       */
2278      nextToken?: String;
2279    }
2280    export interface ListTasksRequest {
2281      /**
2282       * The short name or full Amazon Resource Name (ARN) of the cluster to use when filtering the ListTasks results. If you do not specify a cluster, the default cluster is assumed.
2283       */
2284      cluster?: String;
2285      /**
2286       * The container instance ID or full ARN of the container instance to use when filtering the ListTasks results. Specifying a containerInstance limits the results to tasks that belong to that container instance.
2287       */
2288      containerInstance?: String;
2289      /**
2290       * The name of the task definition family to use when filtering the ListTasks results. Specifying a family limits the results to tasks that belong to that family.
2291       */
2292      family?: String;
2293      /**
2294       * The nextToken value returned from a ListTasks request indicating that more results are available to fulfill the request and further calls will be needed. If maxResults was provided, it is possible the number of results to be fewer than maxResults.  This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes. 
2295       */
2296      nextToken?: String;
2297      /**
2298       * The maximum number of task results returned by ListTasks in paginated output. When this parameter is used, ListTasks 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 ListTasks request with the returned nextToken value. This value can be between 1 and 100. If this parameter is not used, then ListTasks returns up to 100 results and a nextToken value if applicable.
2299       */
2300      maxResults?: BoxedInteger;
2301      /**
2302       * The startedBy value with which to filter the task results. Specifying a startedBy value limits the results to tasks that were started with that value.
2303       */
2304      startedBy?: String;
2305      /**
2306       * The name of the service to use when filtering the ListTasks results. Specifying a serviceName limits the results to tasks that belong to that service.
2307       */
2308      serviceName?: String;
2309      /**
2310       * The task desired status to use when filtering the ListTasks results. Specifying a desiredStatus of STOPPED limits the results to tasks that Amazon ECS has set the desired status to STOPPED. This can be useful for debugging tasks that are not starting properly or have died or finished. The default status filter is RUNNING, which shows tasks that Amazon ECS has set the desired status to RUNNING.  Although you can filter results based on a desired status of PENDING, this does not return any results. Amazon ECS never sets the desired status of a task to that value (only a task's lastStatus may have a value of PENDING). 
2311       */
2312      desiredStatus?: DesiredStatus;
2313      /**
2314       * The launch type to use when filtering the ListTasks results.
2315       */
2316      launchType?: LaunchType;
2317    }
2318    export interface ListTasksResponse {
2319      /**
2320       * The list of task ARN entries for the ListTasks request.
2321       */
2322      taskArns?: StringList;
2323      /**
2324       * The nextToken value to include in a future ListTasks request. When the results of a ListTasks request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
2325       */
2326      nextToken?: String;
2327    }
2328    export interface LoadBalancer {
2329      /**
2330       * 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 are using a Classic Load Balancer the target group ARN should be omitted. 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 are 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.  If your service's task definition uses the awsvpc network mode (which is required for the Fargate launch type), you must choose ip as the target type, not instance, 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. 
2331       */
2332      targetGroupArn?: String;
2333      /**
2334       * 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.
2335       */
2336      loadBalancerName?: String;
2337      /**
2338       * The name of the container (as it appears in a container definition) to associate with the load balancer.
2339       */
2340      containerName?: String;
2341      /**
2342       * 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 are launched on must allow ingress traffic on the hostPort of the port mapping.
2343       */
2344      containerPort?: BoxedInteger;
2345    }
2346    export type LoadBalancers = LoadBalancer[];
2347    export interface LogConfiguration {
2348      /**
2349       * 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.  If you have a custom driver that is not listed, you can fork the Amazon ECS container agent project that is 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 do not currently provide support for running modified copies of this software. 
2350       */
2351      logDriver: LogDriver;
2352      /**
2353       * 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}}' 
2354       */
2355      options?: LogConfigurationOptionsMap;
2356      /**
2357       * The secrets to pass to the log configuration. For more information, see Specifying Sensitive Data in the Amazon Elastic Container Service Developer Guide.
2358       */
2359      secretOptions?: SecretList;
2360    }
2361    export type LogConfigurationOptionsMap = {[key: string]: String};
2362    export type LogDriver = "json-file"|"syslog"|"journald"|"gelf"|"fluentd"|"awslogs"|"splunk"|"awsfirelens"|string;
2363    export type Long = number;
2364    export interface ManagedAgent {
2365      /**
2366       * The Unix timestamp for when the managed agent was last started.
2367       */
2368      lastStartedAt?: Timestamp;
2369      /**
2370       * The name of the managed agent. When the execute command feature is enabled, the managed agent name is ExecuteCommandAgent.
2371       */
2372      name?: ManagedAgentName;
2373      /**
2374       * The reason for why the managed agent is in the state it is in.
2375       */
2376      reason?: String;
2377      /**
2378       * The last known status of the managed agent.
2379       */
2380      lastStatus?: String;
2381    }
2382    export type ManagedAgentName = "ExecuteCommandAgent"|string;
2383    export interface ManagedAgentStateChange {
2384      /**
2385       * The name of the container associated with the managed agent.
2386       */
2387      containerName: String;
2388      /**
2389       * The name of the managed agent.
2390       */
2391      managedAgentName: ManagedAgentName;
2392      /**
2393       * The status of the managed agent.
2394       */
2395      status: String;
2396      /**
2397       * The reason for the status of the managed agent.
2398       */
2399      reason?: String;
2400    }
2401    export type ManagedAgentStateChanges = ManagedAgentStateChange[];
2402    export type ManagedAgents = ManagedAgent[];
2403    export interface ManagedScaling {
2404      /**
2405       * Whether or not to enable managed scaling for the capacity provider.
2406       */
2407      status?: ManagedScalingStatus;
2408      /**
2409       * The target capacity value for the capacity provider. The specified value must be greater than 0 and less than or equal to 100. A value of 100 will result in the Amazon EC2 instances in your Auto Scaling group being completely utilized.
2410       */
2411      targetCapacity?: ManagedScalingTargetCapacity;
2412      /**
2413       * The minimum number of container instances that Amazon ECS will scale in or scale out at one time. If this parameter is omitted, the default value of 1 is used.
2414       */
2415      minimumScalingStepSize?: ManagedScalingStepSize;
2416      /**
2417       * The maximum number of container instances that Amazon ECS will scale in or scale out at one time. If this parameter is omitted, the default value of 10000 is used.
2418       */
2419      maximumScalingStepSize?: ManagedScalingStepSize;
2420      /**
2421       * The period of time, in seconds, after a newly launched Amazon EC2 instance can contribute to CloudWatch metrics for Auto Scaling group. If this parameter is omitted, the default value of 300 seconds is used.
2422       */
2423      instanceWarmupPeriod?: ManagedScalingInstanceWarmupPeriod;
2424    }
2425    export type ManagedScalingInstanceWarmupPeriod = number;
2426    export type ManagedScalingStatus = "ENABLED"|"DISABLED"|string;
2427    export type ManagedScalingStepSize = number;
2428    export type ManagedScalingTargetCapacity = number;
2429    export type ManagedTerminationProtection = "ENABLED"|"DISABLED"|string;
2430    export interface MountPoint {
2431      /**
2432       * The name of the volume to mount. Must be a volume name referenced in the name parameter of task definition volume.
2433       */
2434      sourceVolume?: String;
2435      /**
2436       * The path on the container to mount the host volume at.
2437       */
2438      containerPath?: String;
2439      /**
2440       * 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.
2441       */
2442      readOnly?: BoxedBoolean;
2443    }
2444    export type MountPointList = MountPoint[];
2445    export interface NetworkBinding {
2446      /**
2447       * The IP address that the container is bound to on the container instance.
2448       */
2449      bindIP?: String;
2450      /**
2451       * The port number on the container that is used with the network binding.
2452       */
2453      containerPort?: BoxedInteger;
2454      /**
2455       * The port number on the host that is used with the network binding.
2456       */
2457      hostPort?: BoxedInteger;
2458      /**
2459       * The protocol used for the network binding.
2460       */
2461      protocol?: TransportProtocol;
2462    }
2463    export type NetworkBindings = NetworkBinding[];
2464    export interface NetworkConfiguration {
2465      /**
2466       * The VPC subnets and security groups associated with a task.  All specified subnets and security groups must be from the same VPC. 
2467       */
2468      awsvpcConfiguration?: AwsVpcConfiguration;
2469    }
2470    export interface NetworkInterface {
2471      /**
2472       * The attachment ID for the network interface.
2473       */
2474      attachmentId?: String;
2475      /**
2476       * The private IPv4 address for the network interface.
2477       */
2478      privateIpv4Address?: String;
2479      /**
2480       * The private IPv6 address for the network interface.
2481       */
2482      ipv6Address?: String;
2483    }
2484    export type NetworkInterfaces = NetworkInterface[];
2485    export type NetworkMode = "bridge"|"host"|"awsvpc"|"none"|string;
2486    export type PidMode = "host"|"task"|string;
2487    export interface PlacementConstraint {
2488      /**
2489       * 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.
2490       */
2491      type?: PlacementConstraintType;
2492      /**
2493       * 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.
2494       */
2495      expression?: String;
2496    }
2497    export type PlacementConstraintType = "distinctInstance"|"memberOf"|string;
2498    export type PlacementConstraints = PlacementConstraint[];
2499    export type PlacementStrategies = PlacementStrategy[];
2500    export interface PlacementStrategy {
2501      /**
2502       * 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 is 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).
2503       */
2504      type?: PlacementStrategyType;
2505      /**
2506       * 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 is 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.
2507       */
2508      field?: String;
2509    }
2510    export type PlacementStrategyType = "random"|"spread"|"binpack"|string;
2511    export interface PlatformDevice {
2512      /**
2513       * The ID for the GPU(s) on the container instance. The available GPU IDs can also be obtained on the container instance in the /var/lib/ecs/gpu/nvidia_gpu_info.json file.
2514       */
2515      id: String;
2516      /**
2517       * The type of device that is available on the container instance. The only supported value is GPU.
2518       */
2519      type: PlatformDeviceType;
2520    }
2521    export type PlatformDeviceType = "GPU"|string;
2522    export type PlatformDevices = PlatformDevice[];
2523    export interface PortMapping {
2524      /**
2525       * The port number on the container that is bound to the user-specified or automatically assigned host port. If you are using containers in a task with the awsvpc or host network mode, exposed ports should be specified using containerPort. If you are using 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.
2526       */
2527      containerPort?: BoxedInteger;
2528      /**
2529       * The port number on the container instance to reserve for your container. If you are using 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 are using 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 ephemeral port range from 49153 through 65535 is always used for Docker versions before 1.6.0.  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 (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, including the default reserved ports. Automatically assigned ports don't count toward the 100 reserved ports limit.
2530       */
2531      hostPort?: BoxedInteger;
2532      /**
2533       * The protocol used for the port mapping. Valid values are tcp and udp. The default is tcp.
2534       */
2535      protocol?: TransportProtocol;
2536    }
2537    export type PortMappingList = PortMapping[];
2538    export type PropagateTags = "TASK_DEFINITION"|"SERVICE"|string;
2539    export interface ProxyConfiguration {
2540      /**
2541       * The proxy type. The only supported value is APPMESH.
2542       */
2543      type?: ProxyConfigurationType;
2544      /**
2545       * The name of the container that will serve as the App Mesh proxy.
2546       */
2547      containerName: String;
2548      /**
2549       * 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.  
2550       */
2551      properties?: ProxyConfigurationProperties;
2552    }
2553    export type ProxyConfigurationProperties = KeyValuePair[];
2554    export type ProxyConfigurationType = "APPMESH"|string;
2555    export interface PutAccountSettingDefaultRequest {
2556      /**
2557       * The resource name for which to modify the account setting. If serviceLongArnFormat is specified, the ARN for your Amazon ECS services is affected. If taskLongArnFormat is specified, the ARN and resource ID for your Amazon ECS tasks is affected. If containerInstanceLongArnFormat is specified, the ARN and resource ID for your Amazon ECS container instances is affected. If awsvpcTrunking is specified, the ENI limit for your Amazon ECS container instances is affected. If containerInsights is specified, the default setting for CloudWatch Container Insights for your clusters is affected.
2558       */
2559      name: SettingName;
2560      /**
2561       * The account setting value for the specified principal ARN. Accepted values are enabled and disabled.
2562       */
2563      value: String;
2564    }
2565    export interface PutAccountSettingDefaultResponse {
2566      /**
2567       * The current setting for a resource.
2568       */
2569      setting?: Setting;
2570    }
2571    export interface PutAccountSettingRequest {
2572      /**
2573       * The Amazon ECS resource name for which to modify the account setting. If serviceLongArnFormat is specified, the ARN for your Amazon ECS services is affected. If taskLongArnFormat is specified, the ARN and resource ID for your Amazon ECS tasks is affected. If containerInstanceLongArnFormat is specified, the ARN and resource ID for your Amazon ECS container instances is affected. If awsvpcTrunking is specified, the elastic network interface (ENI) limit for your Amazon ECS container instances is affected. If containerInsights is specified, the default setting for CloudWatch Container Insights for your clusters is affected.
2574       */
2575      name: SettingName;
2576      /**
2577       * The account setting value for the specified principal ARN. Accepted values are enabled and disabled.
2578       */
2579      value: String;
2580      /**
2581       * The ARN of the principal, which can be an IAM user, IAM role, or the root user. If you specify the root user, it modifies the account setting for all IAM users, IAM roles, and the root user of the account unless an IAM user or role explicitly overrides these settings. If this field is omitted, the setting is changed only for the authenticated user.  Federated users assume the account setting of the root user and can't have explicit account settings set for them. 
2582       */
2583      principalArn?: String;
2584    }
2585    export interface PutAccountSettingResponse {
2586      /**
2587       * The current account setting for a resource.
2588       */
2589      setting?: Setting;
2590    }
2591    export interface PutAttributesRequest {
2592      /**
2593       * The short name or full Amazon Resource Name (ARN) of the cluster that contains the resource to apply attributes. If you do not specify a cluster, the default cluster is assumed.
2594       */
2595      cluster?: String;
2596      /**
2597       * The attributes to apply to your resource. You can specify up to 10 custom attributes per resource. You can specify up to 10 attributes in a single call.
2598       */
2599      attributes: Attributes;
2600    }
2601    export interface PutAttributesResponse {
2602      /**
2603       * The attributes applied to your resource.
2604       */
2605      attributes?: Attributes;
2606    }
2607    export interface PutClusterCapacityProvidersRequest {
2608      /**
2609       * The short name or full Amazon Resource Name (ARN) of the cluster to modify the capacity provider settings for. If you do not specify a cluster, the default cluster is assumed.
2610       */
2611      cluster: String;
2612      /**
2613       * 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.
2614       */
2615      capacityProviders: StringList;
2616      /**
2617       * 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.
2618       */
2619      defaultCapacityProviderStrategy: CapacityProviderStrategy;
2620    }
2621    export interface PutClusterCapacityProvidersResponse {
2622      /**
2623       * Details about the cluster.
2624       */
2625      cluster?: Cluster;
2626    }
2627    export interface RegisterContainerInstanceRequest {
2628      /**
2629       * The short name or full Amazon Resource Name (ARN) of the cluster with which to register your container instance. If you do not specify a cluster, the default cluster is assumed.
2630       */
2631      cluster?: String;
2632      /**
2633       * The instance identity document for the EC2 instance to register. This document can be found by running the following command from the instance: curl http://169.254.169.254/latest/dynamic/instance-identity/document/ 
2634       */
2635      instanceIdentityDocument?: String;
2636      /**
2637       * The instance identity document signature for the EC2 instance to register. This signature can be found by running the following command from the instance: curl http://169.254.169.254/latest/dynamic/instance-identity/signature/ 
2638       */
2639      instanceIdentityDocumentSignature?: String;
2640      /**
2641       * The resources available on the instance.
2642       */
2643      totalResources?: Resources;
2644      /**
2645       * The version information for the Amazon ECS container agent and Docker daemon running on the container instance.
2646       */
2647      versionInfo?: VersionInfo;
2648      /**
2649       * The ARN of the container instance (if it was previously registered).
2650       */
2651      containerInstanceArn?: String;
2652      /**
2653       * The container instance attributes that this container instance supports.
2654       */
2655      attributes?: Attributes;
2656      /**
2657       * The devices that are available on the container instance. The only supported device type is a GPU.
2658       */
2659      platformDevices?: PlatformDevices;
2660      /**
2661       * The metadata that you apply to the container instance to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. 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.  
2662       */
2663      tags?: Tags;
2664    }
2665    export interface RegisterContainerInstanceResponse {
2666      /**
2667       * The container instance that was registered.
2668       */
2669      containerInstance?: ContainerInstance;
2670    }
2671    export interface RegisterTaskDefinitionRequest {
2672      /**
2673       * You must specify a family for a task definition, which allows you to 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.
2674       */
2675      family: String;
2676      /**
2677       * 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.
2678       */
2679      taskRoleArn?: String;
2680      /**
2681       * 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.
2682       */
2683      executionRoleArn?: String;
2684      /**
2685       * 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, &lt;default&gt; 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.   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.
2686       */
2687      networkMode?: NetworkMode;
2688      /**
2689       * A list of container definitions in JSON format that describe the different containers that make up your task.
2690       */
2691      containerDefinitions: ContainerDefinitions;
2692      /**
2693       * A list of volume definitions in JSON format that containers in your task may use.
2694       */
2695      volumes?: VolumeList;
2696      /**
2697       * An array of placement constraint objects to use for the task. You can specify a maximum of 10 constraints per task (this limit includes constraints in the task definition and those specified at runtime).
2698       */
2699      placementConstraints?: TaskDefinitionPlacementConstraints;
2700      /**
2701       * The task launch type that Amazon ECS should validate 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.
2702       */
2703      requiresCompatibilities?: CompatibilityList;
2704      /**
2705       * 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.  Task-level CPU and memory parameters are ignored for Windows containers. We recommend specifying container-level resources for Windows containers.  If you are 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 are 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:   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: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)   4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)  
2706       */
2707      cpu?: String;
2708      /**
2709       * 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.  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, which determines your 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)  
2710       */
2711      memory?: String;
2712      /**
2713       * 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, both of which you define. 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.  
2714       */
2715      tags?: Tags;
2716      /**
2717       * 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.  This parameter is not supported for Windows containers or tasks run on Fargate. 
2718       */
2719      pidMode?: PidMode;
2720      /**
2721       * 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.    This parameter is not supported for Windows containers or tasks run on Fargate. 
2722       */
2723      ipcMode?: IpcMode;
2724      /**
2725       * 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 enable 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.
2726       */
2727      proxyConfiguration?: ProxyConfiguration;
2728      /**
2729       * The Elastic Inference accelerators to use for the containers in the task.
2730       */
2731      inferenceAccelerators?: InferenceAccelerators;
2732      /**
2733       * 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.  This parameter is only supported for tasks hosted on Fargate using platform version 1.4.0 or later. 
2734       */
2735      ephemeralStorage?: EphemeralStorage;
2736    }
2737    export interface RegisterTaskDefinitionResponse {
2738      /**
2739       * The full description of the registered task definition.
2740       */
2741      taskDefinition?: TaskDefinition;
2742      /**
2743       * The list of tags associated with the task definition.
2744       */
2745      tags?: Tags;
2746    }
2747    export interface RepositoryCredentials {
2748      /**
2749       * The Amazon Resource Name (ARN) of the secret containing the private repository credentials.  When you are using the Amazon ECS API, CLI, or Amazon Web Services SDK, if the secret exists in the same Region as the task that you are launching then you can use either the full ARN or the name of the secret. When you are using the Amazon Web Services Management Console, you must specify the full ARN of the secret. 
2750       */
2751      credentialsParameter: String;
2752    }
2753    export type RequiresAttributes = Attribute[];
2754    export interface Resource {
2755      /**
2756       * The name of the resource, such as CPU, MEMORY, PORTS, PORTS_UDP, or a user-defined resource.
2757       */
2758      name?: String;
2759      /**
2760       * The type of the resource, such as INTEGER, DOUBLE, LONG, or STRINGSET.
2761       */
2762      type?: String;
2763      /**
2764       * When the doubleValue type is set, the value of the resource must be a double precision floating-point type.
2765       */
2766      doubleValue?: Double;
2767      /**
2768       * When the longValue type is set, the value of the resource must be an extended precision floating-point type.
2769       */
2770      longValue?: Long;
2771      /**
2772       * When the integerValue type is set, the value of the resource must be an integer.
2773       */
2774      integerValue?: Integer;
2775      /**
2776       * When the stringSetValue type is set, the value of the resource must be a string type.
2777       */
2778      stringSetValue?: StringList;
2779    }
2780    export interface ResourceRequirement {
2781      /**
2782       * 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 will reserve for the container. The number of GPUs reserved for all containers in a task should not exceed the number of available GPUs on the container instance the task is launched on. If the InferenceAccelerator type is used, the value should match the deviceName for an InferenceAccelerator specified in a task definition.
2783       */
2784      value: String;
2785      /**
2786       * The type of resource to assign to a container. The supported values are GPU or InferenceAccelerator.
2787       */
2788      type: ResourceType;
2789    }
2790    export type ResourceRequirements = ResourceRequirement[];
2791    export type ResourceType = "GPU"|"InferenceAccelerator"|string;
2792    export type Resources = Resource[];
2793    export interface RunTaskRequest {
2794      /**
2795       * The capacity provider strategy to use for the task. 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. When you use cluster auto scaling, you must specify capacityProviderStrategy and not launchType.  A capacity provider strategy may contain a maximum of 6 capacity providers.
2796       */
2797      capacityProviderStrategy?: CapacityProviderStrategy;
2798      /**
2799       * The short name or full Amazon Resource Name (ARN) of the cluster on which to run your task. If you do not specify a cluster, the default cluster is assumed.
2800       */
2801      cluster?: String;
2802      /**
2803       * The number of instantiations of the specified task to place on your cluster. You can specify up to 10 tasks per call.
2804       */
2805      count?: BoxedInteger;
2806      /**
2807       * Specifies whether to enable Amazon ECS managed tags for the task. For more information, see Tagging Your Amazon ECS Resources in the Amazon Elastic Container Service Developer Guide.
2808       */
2809      enableECSManagedTags?: Boolean;
2810      /**
2811       * Whether or not to enable the execute command functionality for the containers in this task. If true, this enables execute command functionality on all containers in the task.
2812       */
2813      enableExecuteCommand?: Boolean;
2814      /**
2815       * The name of the task group to associate with the task. The default value is the family name of the task definition (for example, family:my-family-name).
2816       */
2817      group?: String;
2818      /**
2819       * The infrastructure on which to run your standalone task. 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.  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-premise server or virtual machine (VM) capacity registered to your cluster. A task can use either a launch type or a capacity provider strategy. If a launchType is specified, the capacityProviderStrategy parameter must be omitted. When you use cluster auto scaling, you must specify capacityProviderStrategy and not launchType. 
2820       */
2821      launchType?: LaunchType;
2822      /**
2823       * The network configuration for the task. This parameter is required for task definitions that use the awsvpc network mode to receive their own elastic network interface, and it is not supported for other network modes. For more information, see Task networking in the Amazon Elastic Container Service Developer Guide.
2824       */
2825      networkConfiguration?: NetworkConfiguration;
2826      /**
2827       * A list of container overrides in JSON format that specify the name of a container in the specified task definition and the overrides it should receive. You can override the default command for a container (that is specified in the task definition or Docker image) with a command override. You can also override existing environment variables (that are specified in the task definition or Docker image) on a container or add new environment variables to it with an environment override. A total of 8192 characters are allowed for overrides. This limit includes the JSON formatting characters of the override structure.
2828       */
2829      overrides?: TaskOverride;
2830      /**
2831       * An array of placement constraint objects to use for the task. You can specify up to 10 constraints per task (including constraints in the task definition and those specified at runtime).
2832       */
2833      placementConstraints?: PlacementConstraints;
2834      /**
2835       * The placement strategy objects to use for the task. You can specify a maximum of 5 strategy rules per task.
2836       */
2837      placementStrategy?: PlacementStrategies;
2838      /**
2839       * The platform version the task should use. A platform version is only specified for tasks hosted on Fargate. If one is not specified, the LATEST platform version is used by default. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide.
2840       */
2841      platformVersion?: String;
2842      /**
2843       * Specifies whether to propagate the tags from the task definition to the task. If no value is specified, the tags are not 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.  An error will be received if you specify the SERVICE option when running a task. 
2844       */
2845      propagateTags?: PropagateTags;
2846      /**
2847       * The reference ID to use for the task. The reference ID can have a maximum length of 1024 characters.
2848       */
2849      referenceId?: String;
2850      /**
2851       * An optional tag specified when a task is started. For example, if you automatically trigger a task to run a batch process job, you could apply a unique identifier for that job to your task with the startedBy parameter. You can then identify which tasks belong to that job by filtering the results of a ListTasks call with the startedBy value. Up to 36 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed. If a task is started by an Amazon ECS service, then the startedBy parameter contains the deployment ID of the service that starts it.
2852       */
2853      startedBy?: String;
2854      /**
2855       * The metadata that you apply to the task to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. 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.  
2856       */
2857      tags?: Tags;
2858      /**
2859       * The family and revision (family:revision) or full ARN of the task definition to run. If a revision is not specified, the latest ACTIVE revision is used.
2860       */
2861      taskDefinition: String;
2862    }
2863    export interface RunTaskResponse {
2864      /**
2865       * A full description of the tasks that were run. The tasks that were successfully placed on your cluster are described here.
2866       */
2867      tasks?: Tasks;
2868      /**
2869       * Any failures associated with the call.
2870       */
2871      failures?: Failures;
2872    }
2873    export interface Scale {
2874      /**
2875       * 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.
2876       */
2877      value?: Double;
2878      /**
2879       * The unit of measure for the scale value.
2880       */
2881      unit?: ScaleUnit;
2882    }
2883    export type ScaleUnit = "PERCENT"|string;
2884    export type SchedulingStrategy = "REPLICA"|"DAEMON"|string;
2885    export type Scope = "task"|"shared"|string;
2886    export interface Secret {
2887      /**
2888       * The name of the secret.
2889       */
2890      name: String;
2891      /**
2892       * 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.  If the SSM Parameter Store parameter exists in the same Region as the task you are 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. 
2893       */
2894      valueFrom: String;
2895    }
2896    export type SecretList = Secret[];
2897    export type SensitiveString = string;
2898    export interface Service {
2899      /**
2900       * The ARN that identifies the service. The ARN contains the arn:aws:ecs namespace, followed by the Region of the service, the Amazon Web Services account ID of the service owner, the service namespace, and then the service name. For example, arn:aws:ecs:region:012345678910:service/my-service.
2901       */
2902      serviceArn?: String;
2903      /**
2904       * 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.
2905       */
2906      serviceName?: String;
2907      /**
2908       * The Amazon Resource Name (ARN) of the cluster that hosts the service.
2909       */
2910      clusterArn?: String;
2911      /**
2912       * A list of Elastic Load Balancing load balancer objects, containing the load balancer name, the container name (as it appears in a container definition), and the container port to access from the load balancer.
2913       */
2914      loadBalancers?: LoadBalancers;
2915      /**
2916       * The details of the service discovery registries to assign to this service. For more information, see Service Discovery.
2917       */
2918      serviceRegistries?: ServiceRegistries;
2919      /**
2920       * The status of the service. The valid values are ACTIVE, DRAINING, or INACTIVE.
2921       */
2922      status?: String;
2923      /**
2924       * 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.
2925       */
2926      desiredCount?: Integer;
2927      /**
2928       * The number of tasks in the cluster that are in the RUNNING state.
2929       */
2930      runningCount?: Integer;
2931      /**
2932       * The number of tasks in the cluster that are in the PENDING state.
2933       */
2934      pendingCount?: Integer;
2935      /**
2936       * 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.
2937       */
2938      launchType?: LaunchType;
2939      /**
2940       * The capacity provider strategy the service is using. When using the DescribeServices API, this field is omitted if the service was created using a launch type.
2941       */
2942      capacityProviderStrategy?: CapacityProviderStrategy;
2943      /**
2944       * The platform version on which to run your service. A platform version is only specified for tasks hosted on Fargate. If one is not specified, the LATEST platform version is used by default. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.
2945       */
2946      platformVersion?: String;
2947      /**
2948       * 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.
2949       */
2950      taskDefinition?: String;
2951      /**
2952       * Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
2953       */
2954      deploymentConfiguration?: DeploymentConfiguration;
2955      /**
2956       * 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.
2957       */
2958      taskSets?: TaskSets;
2959      /**
2960       * The current state of deployments for the service.
2961       */
2962      deployments?: Deployments;
2963      /**
2964       * The ARN of the IAM role associated with the service that allows the Amazon ECS container agent to register container instances with an Elastic Load Balancing load balancer.
2965       */
2966      roleArn?: String;
2967      /**
2968       * The event stream for your service. A maximum of 100 of the latest events are displayed.
2969       */
2970      events?: ServiceEvents;
2971      /**
2972       * The Unix timestamp for when the service was created.
2973       */
2974      createdAt?: Timestamp;
2975      /**
2976       * The placement constraints for the tasks in the service.
2977       */
2978      placementConstraints?: PlacementConstraints;
2979      /**
2980       * The placement strategy that determines how tasks for the service are placed.
2981       */
2982      placementStrategy?: PlacementStrategies;
2983      /**
2984       * The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.
2985       */
2986      networkConfiguration?: NetworkConfiguration;
2987      /**
2988       * 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.
2989       */
2990      healthCheckGracePeriodSeconds?: BoxedInteger;
2991      /**
2992       * 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 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 do not meet the placement constraints.  Fargate tasks do not support the DAEMON scheduling strategy.   
2993       */
2994      schedulingStrategy?: SchedulingStrategy;
2995      /**
2996       * The deployment controller type the service is using. When using the DescribeServices API, this field is omitted if the service is using the ECS deployment controller type.
2997       */
2998      deploymentController?: DeploymentController;
2999      /**
3000       * 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. 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.  
3001       */
3002      tags?: Tags;
3003      /**
3004       * The principal that created the service.
3005       */
3006      createdBy?: String;
3007      /**
3008       * Specifies whether to enable 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.
3009       */
3010      enableECSManagedTags?: Boolean;
3011      /**
3012       * Specifies whether to propagate the tags from the task definition or the service to the task. If no value is specified, the tags are not propagated.
3013       */
3014      propagateTags?: PropagateTags;
3015      /**
3016       * Whether or not 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.
3017       */
3018      enableExecuteCommand?: Boolean;
3019    }
3020    export interface ServiceEvent {
3021      /**
3022       * The ID string of the event.
3023       */
3024      id?: String;
3025      /**
3026       * The Unix timestamp for when the event was triggered.
3027       */
3028      createdAt?: Timestamp;
3029      /**
3030       * The event message.
3031       */
3032      message?: String;
3033    }
3034    export type ServiceEvents = ServiceEvent[];
3035    export type ServiceField = "TAGS"|string;
3036    export type ServiceFieldList = ServiceField[];
3037    export type ServiceRegistries = ServiceRegistry[];
3038    export interface ServiceRegistry {
3039      /**
3040       * The Amazon Resource Name (ARN) of the service registry. The currently supported service registry is Cloud Map. For more information, see CreateService.
3041       */
3042      registryArn?: String;
3043      /**
3044       * The port value used if your service discovery service specified an SRV record. This field may be used if both the awsvpc network mode and SRV records are used.
3045       */
3046      port?: BoxedInteger;
3047      /**
3048       * The container name value, already specified in the task definition, to be used for your service discovery service. 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, but not both.
3049       */
3050      containerName?: String;
3051      /**
3052       * The port value, already specified in the task definition, to be used for your service discovery service. 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, but not both.
3053       */
3054      containerPort?: BoxedInteger;
3055    }
3056    export type Services = Service[];
3057    export interface Session {
3058      /**
3059       * The ID of the execute command session.
3060       */
3061      sessionId?: String;
3062      /**
3063       * A URL back to managed agent on the container that the SSM Session Manager client uses to send commands and receive output from the container.
3064       */
3065      streamUrl?: String;
3066      /**
3067       * An encrypted token value containing session and caller information. Used to authenticate the connection to the container.
3068       */
3069      tokenValue?: SensitiveString;
3070    }
3071    export interface Setting {
3072      /**
3073       * The Amazon ECS resource name.
3074       */
3075      name?: SettingName;
3076      /**
3077       * Whether the account setting is enabled or disabled for the specified resource.
3078       */
3079      value?: String;
3080      /**
3081       * The ARN of the principal, which can be an IAM user, IAM role, or the root user. If this field is omitted, the authenticated user is assumed.
3082       */
3083      principalArn?: String;
3084    }
3085    export type SettingName = "serviceLongArnFormat"|"taskLongArnFormat"|"containerInstanceLongArnFormat"|"awsvpcTrunking"|"containerInsights"|string;
3086    export type Settings = Setting[];
3087    export type SortOrder = "ASC"|"DESC"|string;
3088    export type StabilityStatus = "STEADY_STATE"|"STABILIZING"|string;
3089    export interface StartTaskRequest {
3090      /**
3091       * The short name or full Amazon Resource Name (ARN) of the cluster on which to start your task. If you do not specify a cluster, the default cluster is assumed.
3092       */
3093      cluster?: String;
3094      /**
3095       * The container instance IDs or full ARN entries for the container instances on which you would like to place your task. You can specify up to 10 container instances.
3096       */
3097      containerInstances: StringList;
3098      /**
3099       * Specifies whether to enable Amazon ECS managed tags for the task. For more information, see Tagging Your Amazon ECS Resources in the Amazon Elastic Container Service Developer Guide.
3100       */
3101      enableECSManagedTags?: Boolean;
3102      /**
3103       * Whether or not the execute command functionality is enabled for the task. If true, this enables execute command functionality on all containers in the task.
3104       */
3105      enableExecuteCommand?: Boolean;
3106      /**
3107       * The name of the task group to associate with the task. The default value is the family name of the task definition (for example, family:my-family-name).
3108       */
3109      group?: String;
3110      /**
3111       * The VPC subnet and security group configuration for tasks that receive their own elastic network interface by using the awsvpc networking mode.
3112       */
3113      networkConfiguration?: NetworkConfiguration;
3114      /**
3115       * A list of container overrides in JSON format that specify the name of a container in the specified task definition and the overrides it should receive. You can override the default command for a container (that is specified in the task definition or Docker image) with a command override. You can also override existing environment variables (that are specified in the task definition or Docker image) on a container or add new environment variables to it with an environment override.  A total of 8192 characters are allowed for overrides. This limit includes the JSON formatting characters of the override structure. 
3116       */
3117      overrides?: TaskOverride;
3118      /**
3119       * Specifies whether to propagate the tags from the task definition or the service to the task. If no value is specified, the tags are not propagated.
3120       */
3121      propagateTags?: PropagateTags;
3122      /**
3123       * The reference ID to use for the task.
3124       */
3125      referenceId?: String;
3126      /**
3127       * An optional tag specified when a task is started. For example, if you automatically trigger a task to run a batch process job, you could apply a unique identifier for that job to your task with the startedBy parameter. You can then identify which tasks belong to that job by filtering the results of a ListTasks call with the startedBy value. Up to 36 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed. If a task is started by an Amazon ECS service, then the startedBy parameter contains the deployment ID of the service that starts it.
3128       */
3129      startedBy?: String;
3130      /**
3131       * The metadata that you apply to the task to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. 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.  
3132       */
3133      tags?: Tags;
3134      /**
3135       * The family and revision (family:revision) or full ARN of the task definition to start. If a revision is not specified, the latest ACTIVE revision is used.
3136       */
3137      taskDefinition: String;
3138    }
3139    export interface StartTaskResponse {
3140      /**
3141       * A full description of the tasks that were started. Each task that was successfully placed on your container instances is described.
3142       */
3143      tasks?: Tasks;
3144      /**
3145       * Any failures associated with the call.
3146       */
3147      failures?: Failures;
3148    }
3149    export type Statistics = KeyValuePair[];
3150    export interface StopTaskRequest {
3151      /**
3152       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the task to stop. If you do not specify a cluster, the default cluster is assumed.
3153       */
3154      cluster?: String;
3155      /**
3156       * The task ID or full Amazon Resource Name (ARN) of the task to stop.
3157       */
3158      task: String;
3159      /**
3160       * An optional message specified when a task is stopped. For example, if you are using a custom scheduler, you can use this parameter to specify the reason for stopping the task here, and the message appears in subsequent DescribeTasks API operations on this task. Up to 255 characters are allowed in this message.
3161       */
3162      reason?: String;
3163    }
3164    export interface StopTaskResponse {
3165      /**
3166       * The task that was stopped.
3167       */
3168      task?: Task;
3169    }
3170    export type String = string;
3171    export type StringList = String[];
3172    export type StringMap = {[key: string]: String};
3173    export interface SubmitAttachmentStateChangesRequest {
3174      /**
3175       * The short name or full ARN of the cluster that hosts the container instance the attachment belongs to.
3176       */
3177      cluster?: String;
3178      /**
3179       * Any attachments associated with the state change request.
3180       */
3181      attachments: AttachmentStateChanges;
3182    }
3183    export interface SubmitAttachmentStateChangesResponse {
3184      /**
3185       * Acknowledgement of the state change.
3186       */
3187      acknowledgment?: String;
3188    }
3189    export interface SubmitContainerStateChangeRequest {
3190      /**
3191       * The short name or full ARN of the cluster that hosts the container.
3192       */
3193      cluster?: String;
3194      /**
3195       * The task ID or full Amazon Resource Name (ARN) of the task that hosts the container.
3196       */
3197      task?: String;
3198      /**
3199       * The name of the container.
3200       */
3201      containerName?: String;
3202      /**
3203       * The ID of the Docker container.
3204       */
3205      runtimeId?: String;
3206      /**
3207       * The status of the state change request.
3208       */
3209      status?: String;
3210      /**
3211       * The exit code returned for the state change request.
3212       */
3213      exitCode?: BoxedInteger;
3214      /**
3215       * The reason for the state change request.
3216       */
3217      reason?: String;
3218      /**
3219       * The network bindings of the container.
3220       */
3221      networkBindings?: NetworkBindings;
3222    }
3223    export interface SubmitContainerStateChangeResponse {
3224      /**
3225       * Acknowledgement of the state change.
3226       */
3227      acknowledgment?: String;
3228    }
3229    export interface SubmitTaskStateChangeRequest {
3230      /**
3231       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the task.
3232       */
3233      cluster?: String;
3234      /**
3235       * The task ID or full ARN of the task in the state change request.
3236       */
3237      task?: String;
3238      /**
3239       * The status of the state change request.
3240       */
3241      status?: String;
3242      /**
3243       * The reason for the state change request.
3244       */
3245      reason?: String;
3246      /**
3247       * Any containers associated with the state change request.
3248       */
3249      containers?: ContainerStateChanges;
3250      /**
3251       * Any attachments associated with the state change request.
3252       */
3253      attachments?: AttachmentStateChanges;
3254      /**
3255       * The details for the managed agent associated with the task.
3256       */
3257      managedAgents?: ManagedAgentStateChanges;
3258      /**
3259       * The Unix timestamp for when the container image pull began.
3260       */
3261      pullStartedAt?: Timestamp;
3262      /**
3263       * The Unix timestamp for when the container image pull completed.
3264       */
3265      pullStoppedAt?: Timestamp;
3266      /**
3267       * The Unix timestamp for when the task execution stopped.
3268       */
3269      executionStoppedAt?: Timestamp;
3270    }
3271    export interface SubmitTaskStateChangeResponse {
3272      /**
3273       * Acknowledgement of the state change.
3274       */
3275      acknowledgment?: String;
3276    }
3277    export interface SystemControl {
3278      /**
3279       * The namespaced kernel parameter for which to set a value.
3280       */
3281      namespace?: String;
3282      /**
3283       * The value for the namespaced kernel parameter specified in namespace.
3284       */
3285      value?: String;
3286    }
3287    export type SystemControls = SystemControl[];
3288    export interface Tag {
3289      /**
3290       * 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.
3291       */
3292      key?: TagKey;
3293      /**
3294       * The optional part of a key-value pair that make up a tag. A value acts as a descriptor within a tag category (key).
3295       */
3296      value?: TagValue;
3297    }
3298    export type TagKey = string;
3299    export type TagKeys = TagKey[];
3300    export interface TagResourceRequest {
3301      /**
3302       * The Amazon Resource Name (ARN) of the resource to which to add tags. Currently, the supported resources are Amazon ECS capacity providers, tasks, services, task definitions, clusters, and container instances.
3303       */
3304      resourceArn: String;
3305      /**
3306       * The tags to add to the resource. A tag is an array of key-value pairs. 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.  
3307       */
3308      tags: Tags;
3309    }
3310    export interface TagResourceResponse {
3311    }
3312    export type TagValue = string;
3313    export type Tags = Tag[];
3314    export type TargetType = "container-instance"|string;
3315    export interface Task {
3316      /**
3317       * The Elastic Network Adapter associated with the task if the task uses the awsvpc network mode.
3318       */
3319      attachments?: Attachments;
3320      /**
3321       * The attributes of the task
3322       */
3323      attributes?: Attributes;
3324      /**
3325       * The availability zone of the task.
3326       */
3327      availabilityZone?: String;
3328      /**
3329       * The capacity provider associated with the task.
3330       */
3331      capacityProviderName?: String;
3332      /**
3333       * The ARN of the cluster that hosts the task.
3334       */
3335      clusterArn?: String;
3336      /**
3337       * The connectivity status of a task.
3338       */
3339      connectivity?: Connectivity;
3340      /**
3341       * The Unix timestamp for when the task last went into CONNECTED status.
3342       */
3343      connectivityAt?: Timestamp;
3344      /**
3345       * The ARN of the container instances that host the task.
3346       */
3347      containerInstanceArn?: String;
3348      /**
3349       * The containers associated with the task.
3350       */
3351      containers?: Containers;
3352      /**
3353       * 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 indicating the CPU units when the task definition is registered. If you are 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 are 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:   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: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)   4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)  
3354       */
3355      cpu?: String;
3356      /**
3357       * The Unix timestamp for when the task was created (the task entered the PENDING state).
3358       */
3359      createdAt?: Timestamp;
3360      /**
3361       * The desired status of the task. For more information, see Task Lifecycle.
3362       */
3363      desiredStatus?: String;
3364      /**
3365       * Whether or not execute command functionality is enabled for this task. If true, this enables execute command functionality on all containers in the task.
3366       */
3367      enableExecuteCommand?: Boolean;
3368      /**
3369       * The Unix timestamp for when the task execution stopped.
3370       */
3371      executionStoppedAt?: Timestamp;
3372      /**
3373       * The name of the task group associated with the task.
3374       */
3375      group?: String;
3376      /**
3377       * The health status for the task, which is determined by the health of the essential containers in the task. If all essential containers in the task are reporting as HEALTHY, then the task status also reports as HEALTHY. If any essential containers in the task are reporting as UNHEALTHY or UNKNOWN, then the task status also reports as UNHEALTHY or UNKNOWN, accordingly.  The Amazon ECS container agent does not monitor or report on Docker health checks that are embedded in a container image (such as those specified in a parent image or from the image's Dockerfile) and not specified in the container definition. Health check parameters that are specified in a container definition override any Docker health checks that exist in the container image. 
3378       */
3379      healthStatus?: HealthStatus;
3380      /**
3381       * The Elastic Inference accelerator associated with the task.
3382       */
3383      inferenceAccelerators?: InferenceAccelerators;
3384      /**
3385       * The last known status of the task. For more information, see Task Lifecycle.
3386       */
3387      lastStatus?: String;
3388      /**
3389       * The infrastructure on which your task is running. For more information, see Amazon ECS launch types in the Amazon Elastic Container Service Developer Guide.
3390       */
3391      launchType?: LaunchType;
3392      /**
3393       * The amount of memory (in MiB) used by the task as expressed in a task definition. It can be expressed as an integer using MiB, for example 1024. It can also be expressed as a string using GB, for example 1GB or 1 GB. String values are converted to an integer indicating the MiB when the task definition is registered. If you are using the EC2 launch type, this field is optional. If you are 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 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)  
3394       */
3395      memory?: String;
3396      /**
3397       * One or more container overrides.
3398       */
3399      overrides?: TaskOverride;
3400      /**
3401       * The platform version on which your task is running. A platform version is only specified for tasks using the Fargate launch type. If one is not specified, the LATEST platform version is used by default. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.
3402       */
3403      platformVersion?: String;
3404      /**
3405       * The Unix timestamp for when the container image pull began.
3406       */
3407      pullStartedAt?: Timestamp;
3408      /**
3409       * The Unix timestamp for when the container image pull completed.
3410       */
3411      pullStoppedAt?: Timestamp;
3412      /**
3413       * The Unix timestamp for when the task started (the task transitioned from the PENDING state to the RUNNING state).
3414       */
3415      startedAt?: Timestamp;
3416      /**
3417       * The tag specified when a task is started. If the task is started by an Amazon ECS service, then the startedBy parameter contains the deployment ID of the service that starts it.
3418       */
3419      startedBy?: String;
3420      /**
3421       * The stop code indicating why a task was stopped. The stoppedReason may contain additional details.
3422       */
3423      stopCode?: TaskStopCode;
3424      /**
3425       * The Unix timestamp for when the task was stopped (the task transitioned from the RUNNING state to the STOPPED state).
3426       */
3427      stoppedAt?: Timestamp;
3428      /**
3429       * The reason that the task was stopped.
3430       */
3431      stoppedReason?: String;
3432      /**
3433       * The Unix timestamp for when the task stops (transitions from the RUNNING state to STOPPED).
3434       */
3435      stoppingAt?: Timestamp;
3436      /**
3437       * The metadata that you apply to the task to help you categorize and organize them. Each tag consists of a key and an optional value, both of which you define. 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.  
3438       */
3439      tags?: Tags;
3440      /**
3441       * The Amazon Resource Name (ARN) of the task.
3442       */
3443      taskArn?: String;
3444      /**
3445       * The ARN of the task definition that creates the task.
3446       */
3447      taskDefinitionArn?: String;
3448      /**
3449       * The version counter for the task. Every time a task experiences a change that triggers a CloudWatch event, the version counter is incremented. If you are replicating 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.
3450       */
3451      version?: Long;
3452      /**
3453       * The ephemeral storage settings for the task.
3454       */
3455      ephemeralStorage?: EphemeralStorage;
3456    }
3457    export interface TaskDefinition {
3458      /**
3459       * The full Amazon Resource Name (ARN) of the task definition.
3460       */
3461      taskDefinitionArn?: String;
3462      /**
3463       * 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.
3464       */
3465      containerDefinitions?: ContainerDefinitions;
3466      /**
3467       * The name of a family that this task definition is registered to. Up to 255 letters (uppercase and lowercase), 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.
3468       */
3469      family?: String;
3470      /**
3471       * 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 in order to take advantage of the feature. For more information, see Windows IAM roles for tasks in the Amazon Elastic Container Service Developer Guide.
3472       */
3473      taskRoleArn?: String;
3474      /**
3475       * 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.
3476       */
3477      executionRoleArn?: String;
3478      /**
3479       * 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, &lt;default&gt; 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.   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.
3480       */
3481      networkMode?: NetworkMode;
3482      /**
3483       * 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, even if you have deregistered previous revisions in this family.
3484       */
3485      revision?: Integer;
3486      /**
3487       * 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.  The host and sourcePath parameters are not supported for tasks run on Fargate. 
3488       */
3489      volumes?: VolumeList;
3490      /**
3491       * The status of the task definition.
3492       */
3493      status?: TaskDefinitionStatus;
3494      /**
3495       * 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, specified as key-value pairs using the Amazon ECS console or the PutAttributes API. These attributes are used when considering task placement for tasks hosted on Amazon EC2 instances. For more information, see Attributes in the Amazon Elastic Container Service Developer Guide.  This parameter is not supported for tasks run on Fargate. 
3496       */
3497      requiresAttributes?: RequiresAttributes;
3498      /**
3499       * An array of placement constraint objects to use for tasks.  This parameter is not supported for tasks run on Fargate. 
3500       */
3501      placementConstraints?: TaskDefinitionPlacementConstraints;
3502      /**
3503       * 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.
3504       */
3505      compatibilities?: CompatibilityList;
3506      /**
3507       * 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.
3508       */
3509      requiresCompatibilities?: CompatibilityList;
3510      /**
3511       * The number of cpu units used by the task. If you are using the EC2 launch type, this field is optional and any value can be used. If you are using the Fargate launch type, this field is required and you must use one of the following values, which determines your range of valid values for the memory parameter:   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: Between 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)   4096 (4 vCPU) - Available memory values: Between 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)  
3512       */
3513      cpu?: String;
3514      /**
3515       * The amount (in MiB) of memory used by the task. If your tasks will be run 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 then the container-level memory value is optional. For more information regarding container-level memory and memory reservation, see ContainerDefinition. If your tasks will be run on Fargate, this field is required and you must use one of the following values, which 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)  
3516       */
3517      memory?: String;
3518      /**
3519       * The Elastic Inference accelerator associated with the task.
3520       */
3521      inferenceAccelerators?: InferenceAccelerators;
3522      /**
3523       * 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.  This parameter is not supported for Windows containers or tasks run on Fargate. 
3524       */
3525      pidMode?: PidMode;
3526      /**
3527       * 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.    This parameter is not supported for Windows containers or tasks run on Fargate. 
3528       */
3529      ipcMode?: IpcMode;
3530      /**
3531       * 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 enable 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 Linux AMI in the Amazon Elastic Container Service Developer Guide.
3532       */
3533      proxyConfiguration?: ProxyConfiguration;
3534      /**
3535       * The Unix timestamp for when the task definition was registered.
3536       */
3537      registeredAt?: Timestamp;
3538      /**
3539       * The Unix timestamp for when the task definition was deregistered.
3540       */
3541      deregisteredAt?: Timestamp;
3542      /**
3543       * The principal that registered the task definition.
3544       */
3545      registeredBy?: String;
3546      /**
3547       * The ephemeral storage settings to use for tasks run with the task definition.
3548       */
3549      ephemeralStorage?: EphemeralStorage;
3550    }
3551    export type TaskDefinitionFamilyStatus = "ACTIVE"|"INACTIVE"|"ALL"|string;
3552    export type TaskDefinitionField = "TAGS"|string;
3553    export type TaskDefinitionFieldList = TaskDefinitionField[];
3554    export interface TaskDefinitionPlacementConstraint {
3555      /**
3556       * The type of constraint. The MemberOf constraint restricts selection to be from a group of valid candidates.
3557       */
3558      type?: TaskDefinitionPlacementConstraintType;
3559      /**
3560       * 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.
3561       */
3562      expression?: String;
3563    }
3564    export type TaskDefinitionPlacementConstraintType = "memberOf"|string;
3565    export type TaskDefinitionPlacementConstraints = TaskDefinitionPlacementConstraint[];
3566    export type TaskDefinitionStatus = "ACTIVE"|"INACTIVE"|string;
3567    export type TaskField = "TAGS"|string;
3568    export type TaskFieldList = TaskField[];
3569    export interface TaskOverride {
3570      /**
3571       * One or more container overrides sent to a task.
3572       */
3573      containerOverrides?: ContainerOverrides;
3574      /**
3575       * The cpu override for the task.
3576       */
3577      cpu?: String;
3578      /**
3579       * The Elastic Inference accelerator override for the task.
3580       */
3581      inferenceAcceleratorOverrides?: InferenceAcceleratorOverrides;
3582      /**
3583       * The Amazon Resource Name (ARN) of the task execution IAM role override for the task.
3584       */
3585      executionRoleArn?: String;
3586      /**
3587       * The memory override for the task.
3588       */
3589      memory?: String;
3590      /**
3591       * 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.
3592       */
3593      taskRoleArn?: String;
3594      /**
3595       * The ephemeral storage setting override for the task.  This parameter is only supported for tasks hosted on Fargate using platform version 1.4.0 or later. 
3596       */
3597      ephemeralStorage?: EphemeralStorage;
3598    }
3599    export interface TaskSet {
3600      /**
3601       * The ID of the task set.
3602       */
3603      id?: String;
3604      /**
3605       * The Amazon Resource Name (ARN) of the task set.
3606       */
3607      taskSetArn?: String;
3608      /**
3609       * The Amazon Resource Name (ARN) of the service the task set exists in.
3610       */
3611      serviceArn?: String;
3612      /**
3613       * The Amazon Resource Name (ARN) of the cluster that the service that hosts the task set exists in.
3614       */
3615      clusterArn?: String;
3616      /**
3617       * The tag specified when a task set is started. If the task set is created by an CodeDeploy deployment, the startedBy parameter is CODE_DEPLOY. For a task set created for an external deployment, the startedBy field isn't used.
3618       */
3619      startedBy?: String;
3620      /**
3621       * The external ID associated with the task set. If a task set is created by an CodeDeploy deployment, 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.
3622       */
3623      externalId?: String;
3624      /**
3625       * The status of the task set. The following describes each state:  PRIMARY  The task set is serving production traffic.  ACTIVE  The task set is not serving production traffic.  DRAINING  The tasks in the task set are being stopped and their corresponding targets are being deregistered from their target group.  
3626       */
3627      status?: String;
3628      /**
3629       * The task definition the task set is using.
3630       */
3631      taskDefinition?: String;
3632      /**
3633       * 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.
3634       */
3635      computedDesiredCount?: Integer;
3636      /**
3637       * 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 is restarted after being in the STOPPED state.
3638       */
3639      pendingCount?: Integer;
3640      /**
3641       * 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.
3642       */
3643      runningCount?: Integer;
3644      /**
3645       * The Unix timestamp for when the task set was created.
3646       */
3647      createdAt?: Timestamp;
3648      /**
3649       * The Unix timestamp for when the task set was last updated.
3650       */
3651      updatedAt?: Timestamp;
3652      /**
3653       * 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.
3654       */
3655      launchType?: LaunchType;
3656      /**
3657       * The capacity provider strategy associated with the task set.
3658       */
3659      capacityProviderStrategy?: CapacityProviderStrategy;
3660      /**
3661       * The Fargate platform version on which 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.
3662       */
3663      platformVersion?: String;
3664      /**
3665       * The network configuration for the task set.
3666       */
3667      networkConfiguration?: NetworkConfiguration;
3668      /**
3669       * Details on a load balancer that is used with a task set.
3670       */
3671      loadBalancers?: LoadBalancers;
3672      /**
3673       * The details of the service discovery registries to assign to this task set. For more information, see Service discovery.
3674       */
3675      serviceRegistries?: ServiceRegistries;
3676      /**
3677       * A floating-point percentage of the desired number of tasks to place and keep running in the task set.
3678       */
3679      scale?: Scale;
3680      /**
3681       * The stability status, which indicates whether the task set has reached a steady state. If the following conditions are met, the task set will be in STEADY_STATE:   The task runningCount is equal to the computedDesiredCount.   The pendingCount is 0.   There are no tasks 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 are not met, the stability status returns STABILIZING.
3682       */
3683      stabilityStatus?: StabilityStatus;
3684      /**
3685       * The Unix timestamp for when the task set stability status was retrieved.
3686       */
3687      stabilityStatusAt?: Timestamp;
3688      /**
3689       * 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, both of which you define. 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.  
3690       */
3691      tags?: Tags;
3692    }
3693    export type TaskSetField = "TAGS"|string;
3694    export type TaskSetFieldList = TaskSetField[];
3695    export type TaskSets = TaskSet[];
3696    export type TaskStopCode = "TaskFailedToStart"|"EssentialContainerExited"|"UserInitiated"|string;
3697    export type Tasks = Task[];
3698    export type Timestamp = Date;
3699    export interface Tmpfs {
3700      /**
3701       * The absolute file path where the tmpfs volume is to be mounted.
3702       */
3703      containerPath: String;
3704      /**
3705       * The maximum size (in MiB) of the tmpfs volume.
3706       */
3707      size: Integer;
3708      /**
3709       * 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" 
3710       */
3711      mountOptions?: StringList;
3712    }
3713    export type TmpfsList = Tmpfs[];
3714    export type TransportProtocol = "tcp"|"udp"|string;
3715    export interface Ulimit {
3716      /**
3717       * The type of the ulimit.
3718       */
3719      name: UlimitName;
3720      /**
3721       * The soft limit for the ulimit type.
3722       */
3723      softLimit: Integer;
3724      /**
3725       * The hard limit for the ulimit type.
3726       */
3727      hardLimit: Integer;
3728    }
3729    export type UlimitList = Ulimit[];
3730    export type UlimitName = "core"|"cpu"|"data"|"fsize"|"locks"|"memlock"|"msgqueue"|"nice"|"nofile"|"nproc"|"rss"|"rtprio"|"rttime"|"sigpending"|"stack"|string;
3731    export interface UntagResourceRequest {
3732      /**
3733       * The Amazon Resource Name (ARN) of the resource from which to delete tags. Currently, the supported resources are Amazon ECS capacity providers, tasks, services, task definitions, clusters, and container instances.
3734       */
3735      resourceArn: String;
3736      /**
3737       * The keys of the tags to be removed.
3738       */
3739      tagKeys: TagKeys;
3740    }
3741    export interface UntagResourceResponse {
3742    }
3743    export interface UpdateCapacityProviderRequest {
3744      /**
3745       * The name of the capacity provider to update.
3746       */
3747      name: String;
3748      /**
3749       * An object representing the parameters to update for the Auto Scaling group capacity provider.
3750       */
3751      autoScalingGroupProvider: AutoScalingGroupProviderUpdate;
3752    }
3753    export interface UpdateCapacityProviderResponse {
3754      /**
3755       * Details about the capacity provider.
3756       */
3757      capacityProvider?: CapacityProvider;
3758    }
3759    export interface UpdateClusterRequest {
3760      /**
3761       * The name of the cluster to modify the settings for.
3762       */
3763      cluster: String;
3764      /**
3765       * The cluster settings for your cluster.
3766       */
3767      settings?: ClusterSettings;
3768      /**
3769       * The execute command configuration for the cluster.
3770       */
3771      configuration?: ClusterConfiguration;
3772    }
3773    export interface UpdateClusterResponse {
3774      /**
3775       * Details about the cluster.
3776       */
3777      cluster?: Cluster;
3778    }
3779    export interface UpdateClusterSettingsRequest {
3780      /**
3781       * The name of the cluster to modify the settings for.
3782       */
3783      cluster: String;
3784      /**
3785       * The setting to use by default for a cluster. This parameter is used to enable CloudWatch Container Insights for a cluster. If this value is specified, it will override the containerInsights value set with PutAccountSetting or PutAccountSettingDefault.
3786       */
3787      settings: ClusterSettings;
3788    }
3789    export interface UpdateClusterSettingsResponse {
3790      /**
3791       * Details about the cluster
3792       */
3793      cluster?: Cluster;
3794    }
3795    export interface UpdateContainerAgentRequest {
3796      /**
3797       * The short name or full Amazon Resource Name (ARN) of the cluster that your container instance is running on. If you do not specify a cluster, the default cluster is assumed.
3798       */
3799      cluster?: String;
3800      /**
3801       * The container instance ID or full ARN entries for the container instance on which you would like to update the Amazon ECS container agent.
3802       */
3803      containerInstance: String;
3804    }
3805    export interface UpdateContainerAgentResponse {
3806      /**
3807       * The container instance for which the container agent was updated.
3808       */
3809      containerInstance?: ContainerInstance;
3810    }
3811    export interface UpdateContainerInstancesStateRequest {
3812      /**
3813       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the container instance to update. If you do not specify a cluster, the default cluster is assumed.
3814       */
3815      cluster?: String;
3816      /**
3817       * A list of container instance IDs or full ARN entries.
3818       */
3819      containerInstances: StringList;
3820      /**
3821       * The container instance state with which to update the container instance. The only valid values for this action are ACTIVE and DRAINING. A container instance can only be updated to DRAINING status once it has reached an ACTIVE state. If a container instance is in REGISTERING, DEREGISTERING, or REGISTRATION_FAILED state you can describe the container instance but will be unable to update the container instance state.
3822       */
3823      status: ContainerInstanceStatus;
3824    }
3825    export interface UpdateContainerInstancesStateResponse {
3826      /**
3827       * The list of container instances.
3828       */
3829      containerInstances?: ContainerInstances;
3830      /**
3831       * Any failures associated with the call.
3832       */
3833      failures?: Failures;
3834    }
3835    export interface UpdateServicePrimaryTaskSetRequest {
3836      /**
3837       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task set exists in.
3838       */
3839      cluster: String;
3840      /**
3841       * The short name or full Amazon Resource Name (ARN) of the service that the task set exists in.
3842       */
3843      service: String;
3844      /**
3845       * The short name or full Amazon Resource Name (ARN) of the task set to set as the primary task set in the deployment.
3846       */
3847      primaryTaskSet: String;
3848    }
3849    export interface UpdateServicePrimaryTaskSetResponse {
3850      /**
3851       * Details about the task set.
3852       */
3853      taskSet?: TaskSet;
3854    }
3855    export interface UpdateServiceRequest {
3856      /**
3857       * The short name or full Amazon Resource Name (ARN) of the cluster that your service is running on. If you do not specify a cluster, the default cluster is assumed.
3858       */
3859      cluster?: String;
3860      /**
3861       * The name of the service to update.
3862       */
3863      service: String;
3864      /**
3865       * The number of instantiations of the task to place and keep running in your service.
3866       */
3867      desiredCount?: BoxedInteger;
3868      /**
3869       * The family and revision (family:revision) or full ARN of the task definition to run in your service. If a revision is not specified, the latest ACTIVE revision is used. If you modify the task definition with UpdateService, Amazon ECS spawns a task with the new version of the task definition and then stops an old task after the new version is running.
3870       */
3871      taskDefinition?: String;
3872      /**
3873       * The capacity provider strategy to update the service to use. If the service is using the default capacity provider strategy for the cluster, the service can be updated to use one or more capacity providers as opposed to the default capacity provider strategy. However, when a service is using a capacity provider strategy that is not the default capacity provider strategy, the service cannot be updated to use the cluster's default capacity provider strategy. 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. The PutClusterCapacityProviders API operation is used to update the list of available capacity providers for a cluster after the cluster is created. 
3874       */
3875      capacityProviderStrategy?: CapacityProviderStrategy;
3876      /**
3877       * Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks.
3878       */
3879      deploymentConfiguration?: DeploymentConfiguration;
3880      /**
3881       * An object representing the network configuration for the service.
3882       */
3883      networkConfiguration?: NetworkConfiguration;
3884      /**
3885       * An array of task placement constraint objects to update the service to use. If no value is specified, the existing placement constraints for the service will remain unchanged. If this value is specified, it will override any existing placement constraints defined for the service. To remove all existing placement constraints, specify an empty array. You can specify a maximum of 10 constraints per task (this limit includes constraints in the task definition and those specified at runtime).
3886       */
3887      placementConstraints?: PlacementConstraints;
3888      /**
3889       * The task placement strategy objects to update the service to use. If no value is specified, the existing placement strategy for the service will remain unchanged. If this value is specified, it will override the existing placement strategy defined for the service. To remove an existing placement strategy, specify an empty object. You can specify a maximum of five strategy rules per service.
3890       */
3891      placementStrategy?: PlacementStrategies;
3892      /**
3893       * The platform version on which your tasks in the service are running. A platform version is only specified for tasks using the Fargate launch type. If a platform version is not specified, the LATEST platform version is used by default. For more information, see Fargate Platform Versions in the Amazon Elastic Container Service Developer Guide.
3894       */
3895      platformVersion?: String;
3896      /**
3897       * Whether to force a new deployment of the service. Deployments are not forced by default. You can use this option to trigger a new deployment with no service definition changes. For example, you can update a service's tasks to use a newer Docker image with the same image/tag combination (my_image:latest) or to roll Fargate tasks onto a newer platform version.
3898       */
3899      forceNewDeployment?: Boolean;
3900      /**
3901       * The period of time, in seconds, that the Amazon ECS service scheduler should ignore unhealthy Elastic Load Balancing target health checks after a task has first started. This is only valid if your service is configured to use a load balancer. 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. During that time, the Amazon ECS service scheduler ignores the Elastic Load Balancing health check status. This grace period can prevent the ECS service scheduler from marking tasks as unhealthy and stopping them before they have time to come up.
3902       */
3903      healthCheckGracePeriodSeconds?: BoxedInteger;
3904      /**
3905       * If true, this enables execute command functionality on all task containers. If you do not want to override the value that was set when the service was created, you can set this to null when performing this action.
3906       */
3907      enableExecuteCommand?: BoxedBoolean;
3908    }
3909    export interface UpdateServiceResponse {
3910      /**
3911       * The full description of your service following the update call.
3912       */
3913      service?: Service;
3914    }
3915    export interface UpdateTaskSetRequest {
3916      /**
3917       * The short name or full Amazon Resource Name (ARN) of the cluster that hosts the service that the task set exists in.
3918       */
3919      cluster: String;
3920      /**
3921       * The short name or full Amazon Resource Name (ARN) of the service that the task set exists in.
3922       */
3923      service: String;
3924      /**
3925       * The short name or full Amazon Resource Name (ARN) of the task set to update.
3926       */
3927      taskSet: String;
3928      /**
3929       * A floating-point percentage of the desired number of tasks to place and keep running in the task set.
3930       */
3931      scale: Scale;
3932    }
3933    export interface UpdateTaskSetResponse {
3934      /**
3935       * Details about the task set.
3936       */
3937      taskSet?: TaskSet;
3938    }
3939    export interface VersionInfo {
3940      /**
3941       * The version number of the Amazon ECS container agent.
3942       */
3943      agentVersion?: String;
3944      /**
3945       * The Git commit hash for the Amazon ECS container agent build on the amazon-ecs-agent  GitHub repository.
3946       */
3947      agentHash?: String;
3948      /**
3949       * The Docker version running on the container instance.
3950       */
3951      dockerVersion?: String;
3952    }
3953    export interface Volume {
3954      /**
3955       * 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.
3956       */
3957      name?: String;
3958      /**
3959       * This parameter is specified when you are using 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 is stored. If the host parameter is empty, then the Docker daemon assigns a host path for your data volume. However, the data is not guaranteed to persist after the containers associated with it stop running. Windows containers can mount whole directories on the same drive as $env:ProgramData. Windows containers cannot mount directories on a different drive, and mount point cannot 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.
3960       */
3961      host?: HostVolumeProperties;
3962      /**
3963       * This parameter is specified when you are using Docker volumes. Windows containers only support the use of the local driver. To use bind mounts, specify the host parameter instead.  Docker volumes are not supported by tasks run on Fargate. 
3964       */
3965      dockerVolumeConfiguration?: DockerVolumeConfiguration;
3966      /**
3967       * This parameter is specified when you are using an Amazon Elastic File System file system for task storage.
3968       */
3969      efsVolumeConfiguration?: EFSVolumeConfiguration;
3970      /**
3971       * This parameter is specified when you are using Amazon FSx for Windows File Server file system for task storage.
3972       */
3973      fsxWindowsFileServerVolumeConfiguration?: FSxWindowsFileServerVolumeConfiguration;
3974    }
3975    export interface VolumeFrom {
3976      /**
3977       * The name of another container within the same task definition from which to mount volumes.
3978       */
3979      sourceContainer?: String;
3980      /**
3981       * 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.
3982       */
3983      readOnly?: BoxedBoolean;
3984    }
3985    export type VolumeFromList = VolumeFrom[];
3986    export type VolumeList = Volume[];
3987    /**
3988     * A string in YYYY-MM-DD format that represents the latest possible API version that can be used in this service. Specify 'latest' to use the latest possible version.
3989     */
3990    export type apiVersion = "2014-11-13"|"latest"|string;
3991    export interface ClientApiVersions {
3992      /**
3993       * A string in YYYY-MM-DD format that represents the latest possible API version that can be used in this service. Specify 'latest' to use the latest possible version.
3994       */
3995      apiVersion?: apiVersion;
3996    }
3997    export type ClientConfiguration = ServiceConfigurationOptions & ClientApiVersions;
3998    /**
3999     * Contains interfaces for use with the ECS client.
4000     */
4001    export import Types = ECS;
4002  }
4003  export = ECS;