Class: Aws::ECS::Client
- Inherits:
-
Seahorse::Client::Base
- Object
- Seahorse::Client::Base
- Aws::ECS::Client
- Includes:
- ClientStubs
- Defined in:
- lib/aws-sdk-ecs/client.rb
Overview
An API client for ECS. To construct a client, you need to configure a ‘:region` and `:credentials`.
client = Aws::ECS::Client.new(
region: region_name,
credentials: credentials,
# ...
)
For details on configuring region and credentials see the [developer guide](/sdk-for-ruby/v3/developer-guide/setup-config.html).
See #initialize for a full list of supported configuration options.
Class Attribute Summary collapse
- .identifier ⇒ Object readonly private
API Operations collapse
-
#create_capacity_provider(params = {}) ⇒ Types::CreateCapacityProviderResponse
Creates a new capacity provider.
-
#create_cluster(params = {}) ⇒ Types::CreateClusterResponse
Creates a new Amazon ECS cluster.
-
#create_service(params = {}) ⇒ Types::CreateServiceResponse
Runs and maintains your desired number of tasks from a specified task definition.
-
#create_task_set(params = {}) ⇒ Types::CreateTaskSetResponse
Create a task set in the specified cluster and service.
-
#delete_account_setting(params = {}) ⇒ Types::DeleteAccountSettingResponse
Disables an account setting for a specified user, role, or the root user for an account.
-
#delete_attributes(params = {}) ⇒ Types::DeleteAttributesResponse
Deletes one or more custom attributes from an Amazon ECS resource.
-
#delete_capacity_provider(params = {}) ⇒ Types::DeleteCapacityProviderResponse
Deletes the specified capacity provider.
-
#delete_cluster(params = {}) ⇒ Types::DeleteClusterResponse
Deletes the specified cluster.
-
#delete_service(params = {}) ⇒ Types::DeleteServiceResponse
Deletes a specified service within a cluster.
-
#delete_task_definitions(params = {}) ⇒ Types::DeleteTaskDefinitionsResponse
Deletes one or more task definitions.
-
#delete_task_set(params = {}) ⇒ Types::DeleteTaskSetResponse
Deletes a specified task set within a service.
-
#deregister_container_instance(params = {}) ⇒ Types::DeregisterContainerInstanceResponse
Deregisters an Amazon ECS container instance from the specified cluster.
-
#deregister_task_definition(params = {}) ⇒ Types::DeregisterTaskDefinitionResponse
Deregisters the specified task definition by family and revision.
-
#describe_capacity_providers(params = {}) ⇒ Types::DescribeCapacityProvidersResponse
Describes one or more of your capacity providers.
-
#describe_clusters(params = {}) ⇒ Types::DescribeClustersResponse
Describes one or more of your clusters.
-
#describe_container_instances(params = {}) ⇒ Types::DescribeContainerInstancesResponse
Describes one or more container instances.
-
#describe_services(params = {}) ⇒ Types::DescribeServicesResponse
Describes the specified services running in your cluster.
-
#describe_task_definition(params = {}) ⇒ Types::DescribeTaskDefinitionResponse
Describes a task definition.
-
#describe_task_sets(params = {}) ⇒ Types::DescribeTaskSetsResponse
Describes the task sets in the specified cluster and service.
-
#describe_tasks(params = {}) ⇒ Types::DescribeTasksResponse
Describes a specified task or tasks.
-
#discover_poll_endpoint(params = {}) ⇒ Types::DiscoverPollEndpointResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
-
#execute_command(params = {}) ⇒ Types::ExecuteCommandResponse
Runs a command remotely on a container within a task.
-
#get_task_protection(params = {}) ⇒ Types::GetTaskProtectionResponse
Retrieves the protection status of tasks in an Amazon ECS service.
-
#list_account_settings(params = {}) ⇒ Types::ListAccountSettingsResponse
Lists the account settings for a specified principal.
-
#list_attributes(params = {}) ⇒ Types::ListAttributesResponse
Lists the attributes for Amazon ECS resources within a specified target type and cluster.
-
#list_clusters(params = {}) ⇒ Types::ListClustersResponse
Returns a list of existing clusters.
-
#list_container_instances(params = {}) ⇒ Types::ListContainerInstancesResponse
Returns a list of container instances in a specified cluster.
-
#list_services(params = {}) ⇒ Types::ListServicesResponse
Returns a list of services.
-
#list_services_by_namespace(params = {}) ⇒ Types::ListServicesByNamespaceResponse
This operation lists all of the services that are associated with a Cloud Map namespace.
-
#list_tags_for_resource(params = {}) ⇒ Types::ListTagsForResourceResponse
List the tags for an Amazon ECS resource.
-
#list_task_definition_families(params = {}) ⇒ Types::ListTaskDefinitionFamiliesResponse
Returns a list of task definition families that are registered to your account.
-
#list_task_definitions(params = {}) ⇒ Types::ListTaskDefinitionsResponse
Returns a list of task definitions that are registered to your account.
-
#list_tasks(params = {}) ⇒ Types::ListTasksResponse
Returns a list of tasks.
-
#put_account_setting(params = {}) ⇒ Types::PutAccountSettingResponse
Modifies an account setting.
-
#put_account_setting_default(params = {}) ⇒ Types::PutAccountSettingDefaultResponse
Modifies an account setting for all users on an account for whom no individual account setting has been specified.
-
#put_attributes(params = {}) ⇒ Types::PutAttributesResponse
Create or update an attribute on an Amazon ECS resource.
-
#put_cluster_capacity_providers(params = {}) ⇒ Types::PutClusterCapacityProvidersResponse
Modifies the available capacity providers and the default capacity provider strategy for a cluster.
-
#register_container_instance(params = {}) ⇒ Types::RegisterContainerInstanceResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
-
#register_task_definition(params = {}) ⇒ Types::RegisterTaskDefinitionResponse
Registers a new task definition from the supplied ‘family` and `containerDefinitions`.
-
#run_task(params = {}) ⇒ Types::RunTaskResponse
Starts a new task using the specified task definition.
-
#start_task(params = {}) ⇒ Types::StartTaskResponse
Starts a new task from the specified task definition on the specified container instance or instances.
-
#stop_task(params = {}) ⇒ Types::StopTaskResponse
Stops a running task.
-
#submit_attachment_state_changes(params = {}) ⇒ Types::SubmitAttachmentStateChangesResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
-
#submit_container_state_change(params = {}) ⇒ Types::SubmitContainerStateChangeResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
-
#submit_task_state_change(params = {}) ⇒ Types::SubmitTaskStateChangeResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
-
#tag_resource(params = {}) ⇒ Struct
Associates the specified tags to a resource with the specified ‘resourceArn`.
-
#untag_resource(params = {}) ⇒ Struct
Deletes specified tags from a resource.
-
#update_capacity_provider(params = {}) ⇒ Types::UpdateCapacityProviderResponse
Modifies the parameters for a capacity provider.
-
#update_cluster(params = {}) ⇒ Types::UpdateClusterResponse
Updates the cluster.
-
#update_cluster_settings(params = {}) ⇒ Types::UpdateClusterSettingsResponse
Modifies the settings to use for a cluster.
-
#update_container_agent(params = {}) ⇒ Types::UpdateContainerAgentResponse
Updates the Amazon ECS container agent on a specified container instance.
-
#update_container_instances_state(params = {}) ⇒ Types::UpdateContainerInstancesStateResponse
Modifies the status of an Amazon ECS container instance.
-
#update_service(params = {}) ⇒ Types::UpdateServiceResponse
Modifies the parameters of a service.
-
#update_service_primary_task_set(params = {}) ⇒ Types::UpdateServicePrimaryTaskSetResponse
Modifies which task set in a service is the primary task set.
-
#update_task_protection(params = {}) ⇒ Types::UpdateTaskProtectionResponse
Updates the protection status of a task.
-
#update_task_set(params = {}) ⇒ Types::UpdateTaskSetResponse
Modifies a task set.
Class Method Summary collapse
- .errors_module ⇒ Object private
Instance Method Summary collapse
- #build_request(operation_name, params = {}) ⇒ Object private
-
#initialize(options) ⇒ Client
constructor
A new instance of Client.
-
#wait_until(waiter_name, params = {}, options = {}) {|w.waiter| ... } ⇒ Boolean
Polls an API operation until a resource enters a desired state.
- #waiter_names ⇒ Object deprecated private Deprecated.
Constructor Details
#initialize(options) ⇒ Client
Returns a new instance of Client.
441 442 443 |
# File 'lib/aws-sdk-ecs/client.rb', line 441 def initialize(*args) super end |
Class Attribute Details
.identifier ⇒ Object (readonly)
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
10574 10575 10576 |
# File 'lib/aws-sdk-ecs/client.rb', line 10574 def identifier @identifier end |
Class Method Details
.errors_module ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
10577 10578 10579 |
# File 'lib/aws-sdk-ecs/client.rb', line 10577 def errors_module Errors end |
Instance Method Details
#build_request(operation_name, params = {}) ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
10428 10429 10430 10431 10432 10433 10434 10435 10436 10437 10438 10439 10440 10441 10442 10443 10444 |
# File 'lib/aws-sdk-ecs/client.rb', line 10428 def build_request(operation_name, params = {}) handlers = @handlers.for(operation_name) tracer = config.telemetry_provider.tracer_provider.tracer( Aws::Telemetry.module_to_tracer_name('Aws::ECS') ) context = Seahorse::Client::RequestContext.new( operation_name: operation_name, operation: config.api.operation(operation_name), client: self, params: params, config: config, tracer: tracer ) context[:gem_name] = 'aws-sdk-ecs' context[:gem_version] = '1.155.0' Seahorse::Client::Request.new(handlers, context) end |
#create_capacity_provider(params = {}) ⇒ Types::CreateCapacityProviderResponse
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 that use an Auto Scaling group can be created. Amazon ECS tasks on Fargate use the ‘FARGATE` and `FARGATE_SPOT` capacity providers. These providers are available to all accounts in the Amazon Web Services Regions that Fargate supports.
546 547 548 549 |
# File 'lib/aws-sdk-ecs/client.rb', line 546 def create_capacity_provider(params = {}, = {}) req = build_request(:create_capacity_provider, params) req.send_request() end |
#create_cluster(params = {}) ⇒ Types::CreateClusterResponse
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.
<note markdown=“1”> When you call the [CreateCluster] API operation, Amazon ECS attempts to create the Amazon ECS service-linked role for your account. This is so that it can manage required resources in other Amazon Web Services services on your behalf. However, if the user that makes the call doesn’t have permissions to create the service-linked role, it isn’t created. For more information, see [Using service-linked roles for Amazon ECS] in the *Amazon Elastic Container Service Developer Guide*.
</note>
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html
807 808 809 810 |
# File 'lib/aws-sdk-ecs/client.rb', line 807 def create_cluster(params = {}, = {}) req = build_request(:create_cluster, params) req.send_request() end |
#create_service(params = {}) ⇒ Types::CreateServiceResponse
Runs and maintains your desired number of tasks from a specified task definition. If the number of tasks running in a service drops below the ‘desiredCount`, Amazon ECS runs another copy of the task in the specified cluster. To update an existing service, use [UpdateService].
<note markdown=“1”> On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.
</note>
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*.
You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or updating a service. ‘volumeConfigurations` is only supported for REPLICA service and not DAEMON service. For more infomation, see [Amazon EBS volumes] in the *Amazon Elastic Container Service Developer Guide*.
Tasks for services that don’t use a load balancer are considered healthy if they’re in the ‘RUNNING` state. Tasks for services that use a load balancer are considered healthy if they’re in the ‘RUNNING` state and are reported as healthy by the load balancer.
There are two service scheduler strategies available:
-
‘REPLICA` - The replica scheduling strategy places and maintains your desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. For more information, see [Service scheduler concepts] in the *Amazon Elastic Container Service Developer Guide*.
-
‘DAEMON` - The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks. It also stops tasks that don’t meet the placement constraints. When using this strategy, you don’t need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. For more information, see [Service scheduler concepts] in the *Amazon Elastic Container Service Developer Guide*.
You can optionally specify a deployment configuration for your service. The deployment is initiated by changing properties. For example, the deployment might be initiated by the task definition or by your desired count of a service. You can use [UpdateService]. The default value for a replica service for ‘minimumHealthyPercent` is 100%. The default value for a daemon service for `minimumHealthyPercent` is 0%.
If a service uses the ‘ECS` deployment controller, the minimum healthy percent represents a lower limit on the number of tasks in a service that must remain in the `RUNNING` state during a deployment. Specifically, it represents it as a percentage of your desired number of tasks (rounded up to the nearest integer). This happens when any of your container instances are in the `DRAINING` state if the service contains tasks using the EC2 launch type. Using this parameter, you can deploy without using additional cluster capacity. For example, if you set your service to have desired number of four tasks and a minimum healthy percent of 50%, the scheduler might stop two existing tasks to free up cluster capacity before starting two new tasks. If they’re in the ‘RUNNING` state, tasks for services that don’t use a load balancer are considered healthy . If they’re in the ‘RUNNING` state and reported as healthy by the load balancer, tasks for services that do use a load balancer are considered healthy . The default value for minimum healthy percent is 100%.
If a service uses the ‘ECS` deployment controller, the **maximum percent** parameter represents an upper limit on the number of tasks in a service that are allowed in the `RUNNING` or `PENDING` state during a deployment. Specifically, it represents it as a percentage of the desired number of tasks (rounded down to the nearest integer). This happens when any of your container instances are in the `DRAINING` state if the service contains tasks using the EC2 launch type. Using this parameter, you can define the deployment batch size. For example, if your service has a desired number of four tasks and a maximum percent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default value for maximum percent is 200%.
If a service uses either the ‘CODE_DEPLOY` or `EXTERNAL` deployment controller types and tasks that use the EC2 launch type, the **minimum healthy percent** and **maximum percent** values are used only to define the lower and upper limit on the number of the tasks in the service that remain in the `RUNNING` state. This is while the container instances are in the `DRAINING` state. If the tasks in the service use the Fargate launch type, the minimum healthy percent and maximum percent values aren’t used. This is the case even if they’re currently visible when describing your service.
When creating a service that uses the ‘EXTERNAL` deployment controller, you can specify only parameters that aren’t controlled at the task set level. The only required parameter is the service name. You control your services using the [CreateTaskSet]. For more information, see [Amazon ECS deployment types] in the *Amazon Elastic Container Service Developer Guide*.
When the service scheduler launches new tasks, it determines task placement. For information about task placement and task placement strategies, see [Amazon ECS task placement] in the *Amazon Elastic Container Service Developer Guide*
Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service.
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html [3]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types [4]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html [5]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html [6]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html [7]: docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html
1755 1756 1757 1758 |
# File 'lib/aws-sdk-ecs/client.rb', line 1755 def create_service(params = {}, = {}) req = build_request(:create_service, params) req.send_request() end |
#create_task_set(params = {}) ⇒ Types::CreateTaskSetResponse
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*.
<note markdown=“1”> On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.
</note>
For information about the maximum number of task sets and other quotas, see [Amazon ECS service quotas] in the *Amazon Elastic Container Service Developer Guide*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html
2011 2012 2013 2014 |
# File 'lib/aws-sdk-ecs/client.rb', line 2011 def create_task_set(params = {}, = {}) req = build_request(:create_task_set, params) req.send_request() end |
#delete_account_setting(params = {}) ⇒ Types::DeleteAccountSettingResponse
Disables an account setting for a specified user, role, or the root user for an account.
2096 2097 2098 2099 |
# File 'lib/aws-sdk-ecs/client.rb', line 2096 def delete_account_setting(params = {}, = {}) req = build_request(:delete_account_setting, params) req.send_request() end |
#delete_attributes(params = {}) ⇒ Types::DeleteAttributesResponse
Deletes one or more custom attributes from an Amazon ECS resource.
2145 2146 2147 2148 |
# File 'lib/aws-sdk-ecs/client.rb', line 2145 def delete_attributes(params = {}, = {}) req = build_request(:delete_attributes, params) req.send_request() end |
#delete_capacity_provider(params = {}) ⇒ Types::DeleteCapacityProviderResponse
Deletes the specified capacity provider.
<note markdown=“1”> The ‘FARGATE` and `FARGATE_SPOT` capacity providers are reserved and can’t be deleted. You can disassociate them from a cluster using either [PutCapacityProviderProviders] or by deleting the cluster.
</note>
Prior to a capacity provider being deleted, the capacity provider must be removed from the capacity provider strategy from all services. The
- UpdateService][2
-
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 aren’t associated with a cluster can be deleted. To remove a capacity provider from a cluster, you can either use [PutCapacityProviderProviders] or delete the cluster.
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutCapacityProviderProviders.html [2]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html
2212 2213 2214 2215 |
# File 'lib/aws-sdk-ecs/client.rb', line 2212 def delete_capacity_provider(params = {}, = {}) req = build_request(:delete_capacity_provider, params) req.send_request() end |
#delete_cluster(params = {}) ⇒ Types::DeleteClusterResponse
Deletes the specified cluster. The cluster transitions to the ‘INACTIVE` state. Clusters with an `INACTIVE` status might remain discoverable in your account for a period of time. However, this behavior is subject to change in the future. We don’t recommend that you rely on ‘INACTIVE` clusters persisting.
You must deregister all container instances from this cluster before you may delete it. You can list the container instances in a cluster with [ListContainerInstances] and deregister them with [DeregisterContainerInstance].
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListContainerInstances.html [2]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeregisterContainerInstance.html
2316 2317 2318 2319 |
# File 'lib/aws-sdk-ecs/client.rb', line 2316 def delete_cluster(params = {}, = {}) req = build_request(:delete_cluster, params) req.send_request() end |
#delete_service(params = {}) ⇒ Types::DeleteServiceResponse
Deletes a specified service within a cluster. You can delete a service if you have no running tasks in it and the desired task count is zero. If the service is actively maintaining tasks, you can’t delete it, and you must update the service to a desired task count of zero. For more information, see [UpdateService].
<note markdown=“1”> 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][2
-
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][3
-
calls on those services return a
‘ServiceNotFoundException` error.
</note>
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.
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html [2]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListServices.html [3]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DescribeServices.html
2566 2567 2568 2569 |
# File 'lib/aws-sdk-ecs/client.rb', line 2566 def delete_service(params = {}, = {}) req = build_request(:delete_service, params) req.send_request() end |
#delete_task_definitions(params = {}) ⇒ Types::DeleteTaskDefinitionsResponse
Deletes one or more task definitions.
You must deregister a task definition revision before you delete it. For more information, see [DeregisterTaskDefinition].
When you delete a task definition revision, it is immediately transitions from the ‘INACTIVE` to `DELETE_IN_PROGRESS`. Existing tasks and services that reference a `DELETE_IN_PROGRESS` task definition revision continue to run without disruption. Existing services that reference a `DELETE_IN_PROGRESS` task definition revision can still scale up or down by modifying the service’s desired count.
You can’t use a ‘DELETE_IN_PROGRESS` task definition revision to run new tasks or create new services. You also can’t update an existing service to reference a ‘DELETE_IN_PROGRESS` task definition revision.
A task definition revision will stay in ‘DELETE_IN_PROGRESS` status until all the associated tasks and services have been terminated.
When you delete all ‘INACTIVE` task definition revisions, the task definition name is not displayed in the console and not returned in the API. If a task definition revisions are in the `DELETE_IN_PROGRESS` state, the task definition name is displayed in the console and returned in the API. The task definition name is retained by Amazon ECS and the revision is incremented the next time you create a task definition with that name.
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeregisterTaskDefinition.html
2801 2802 2803 2804 |
# File 'lib/aws-sdk-ecs/client.rb', line 2801 def delete_task_definitions(params = {}, = {}) req = build_request(:delete_task_definitions, params) req.send_request() end |
#delete_task_set(params = {}) ⇒ Types::DeleteTaskSetResponse
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*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html
2894 2895 2896 2897 |
# File 'lib/aws-sdk-ecs/client.rb', line 2894 def delete_task_set(params = {}, = {}) req = build_request(:delete_task_set, params) req.send_request() end |
#deregister_container_instance(params = {}) ⇒ Types::DeregisterContainerInstanceResponse
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, we recommend that you 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 doesn’t terminate the EC2 instance. If you are finished using the instance, be sure to terminate it in the Amazon EC2 console to stop billing.
<note markdown=“1”> If you terminate a running container instance, Amazon ECS automatically deregisters the instance from your cluster (stopped container instances or instances with disconnected agents aren’t automatically deregistered when terminated).
</note>
3034 3035 3036 3037 |
# File 'lib/aws-sdk-ecs/client.rb', line 3034 def deregister_container_instance(params = {}, = {}) req = build_request(:deregister_container_instance, params) req.send_request() end |
#deregister_task_definition(params = {}) ⇒ Types::DeregisterTaskDefinitionResponse
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. If you want to delete a task definition revision, you must first deregister the task definition revision.
You can’t use an ‘INACTIVE` task definition to run new tasks or create new services, and you can’t update an existing service to reference an ‘INACTIVE` task definition. However, there may be up to a 10-minute window following deregistration where these restrictions have not yet taken effect.
<note markdown=“1”> At this time, ‘INACTIVE` task definitions remain discoverable in your account indefinitely. However, this behavior is subject to change in the future. We don’t recommend that you rely on ‘INACTIVE` task definitions persisting beyond the lifecycle of any associated tasks and services.
</note>
You must deregister a task definition revision before you delete it. For more information, see [DeleteTaskDefinitions].
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeleteTaskDefinitions.html
3258 3259 3260 3261 |
# File 'lib/aws-sdk-ecs/client.rb', line 3258 def deregister_task_definition(params = {}, = {}) req = build_request(:deregister_task_definition, params) req.send_request() end |
#describe_capacity_providers(params = {}) ⇒ Types::DescribeCapacityProvidersResponse
Describes one or more of your capacity providers.
3344 3345 3346 3347 |
# File 'lib/aws-sdk-ecs/client.rb', line 3344 def describe_capacity_providers(params = {}, = {}) req = build_request(:describe_capacity_providers, params) req.send_request() end |
#describe_clusters(params = {}) ⇒ Types::DescribeClustersResponse
Describes one or more of your clusters.
3464 3465 3466 3467 |
# File 'lib/aws-sdk-ecs/client.rb', line 3464 def describe_clusters(params = {}, = {}) req = build_request(:describe_clusters, params) req.send_request() end |
#describe_container_instances(params = {}) ⇒ Types::DescribeContainerInstancesResponse
Describes one or more container instances. Returns metadata about each container instance requested.
3655 3656 3657 3658 |
# File 'lib/aws-sdk-ecs/client.rb', line 3655 def describe_container_instances(params = {}, = {}) req = build_request(:describe_container_instances, params) req.send_request() end |
#describe_services(params = {}) ⇒ Types::DescribeServicesResponse
Describes the specified services running in your cluster.
The following waiters are defined for this operation (see #wait_until for detailed usage):
* services_inactive
* services_stable
3933 3934 3935 3936 |
# File 'lib/aws-sdk-ecs/client.rb', line 3933 def describe_services(params = {}, = {}) req = build_request(:describe_services, params) req.send_request() end |
#describe_task_definition(params = {}) ⇒ Types::DescribeTaskDefinitionResponse
Describes a task definition. You can specify a ‘family` and `revision` to find information about a specific task definition, or you can simply specify the family to find the latest `ACTIVE` revision in that family.
<note markdown=“1”> You can only describe ‘INACTIVE` task definitions while an active task or service references them.
</note>
4211 4212 4213 4214 |
# File 'lib/aws-sdk-ecs/client.rb', line 4211 def describe_task_definition(params = {}, = {}) req = build_request(:describe_task_definition, params) req.send_request() end |
#describe_task_sets(params = {}) ⇒ Types::DescribeTaskSetsResponse
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*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html
4310 4311 4312 4313 |
# File 'lib/aws-sdk-ecs/client.rb', line 4310 def describe_task_sets(params = {}, = {}) req = build_request(:describe_task_sets, params) req.send_request() end |
#describe_tasks(params = {}) ⇒ Types::DescribeTasksResponse
Describes a specified task or tasks.
Currently, stopped tasks appear in the returned results for at least one hour.
If you have tasks with tags, and then delete the cluster, the tagged tasks are returned in the response. If you create a new cluster with the same name as the deleted cluster, the tagged tasks are not included in the response.
The following waiters are defined for this operation (see #wait_until for detailed usage):
* tasks_running
* tasks_stopped
4527 4528 4529 4530 |
# File 'lib/aws-sdk-ecs/client.rb', line 4527 def describe_tasks(params = {}, = {}) req = build_request(:describe_tasks, params) req.send_request() end |
#discover_poll_endpoint(params = {}) ⇒ Types::DiscoverPollEndpointResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
</note>
Returns an endpoint for the Amazon ECS agent to poll for updates.
4575 4576 4577 4578 |
# File 'lib/aws-sdk-ecs/client.rb', line 4575 def discover_poll_endpoint(params = {}, = {}) req = build_request(:discover_poll_endpoint, params) req.send_request() end |
#execute_command(params = {}) ⇒ Types::ExecuteCommandResponse
Runs a command remotely on a container within a task.
If you use a condition key in your IAM policy to refine the conditions for the policy statement, for example limit the actions to a specific cluster, you receive an ‘AccessDeniedException` when there is a mismatch between the condition key value and the corresponding parameter value.
For information about required permissions and considerations, see
- Using Amazon ECS Exec for debugging][1
-
in the *Amazon ECS Developer
Guide*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.html
4649 4650 4651 4652 |
# File 'lib/aws-sdk-ecs/client.rb', line 4649 def execute_command(params = {}, = {}) req = build_request(:execute_command, params) req.send_request() end |
#get_task_protection(params = {}) ⇒ Types::GetTaskProtectionResponse
Retrieves the protection status of tasks in an Amazon ECS service.
4715 4716 4717 4718 |
# File 'lib/aws-sdk-ecs/client.rb', line 4715 def get_task_protection(params = {}, = {}) req = build_request(:get_task_protection, params) req.send_request() end |
#list_account_settings(params = {}) ⇒ Types::ListAccountSettingsResponse
Lists the account settings for a specified principal.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
4860 4861 4862 4863 |
# File 'lib/aws-sdk-ecs/client.rb', line 4860 def list_account_settings(params = {}, = {}) req = build_request(:list_account_settings, params) req.send_request() end |
#list_attributes(params = {}) ⇒ Types::ListAttributesResponse
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. You can do this, for example, to see which container instances in a cluster are running a Linux AMI (`ecs.os-type=linux`).
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
4942 4943 4944 4945 |
# File 'lib/aws-sdk-ecs/client.rb', line 4942 def list_attributes(params = {}, = {}) req = build_request(:list_attributes, params) req.send_request() end |
#list_clusters(params = {}) ⇒ Types::ListClustersResponse
Returns a list of existing clusters.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
5011 5012 5013 5014 |
# File 'lib/aws-sdk-ecs/client.rb', line 5011 def list_clusters(params = {}, = {}) req = build_request(:list_clusters, params) req.send_request() end |
#list_container_instances(params = {}) ⇒ Types::ListContainerInstancesResponse
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*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-query-language.html
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
5120 5121 5122 5123 |
# File 'lib/aws-sdk-ecs/client.rb', line 5120 def list_container_instances(params = {}, = {}) req = build_request(:list_container_instances, params) req.send_request() end |
#list_services(params = {}) ⇒ Types::ListServicesResponse
Returns a list of services. You can filter the results by cluster, launch type, and scheduling strategy.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
5204 5205 5206 5207 |
# File 'lib/aws-sdk-ecs/client.rb', line 5204 def list_services(params = {}, = {}) req = build_request(:list_services, params) req.send_request() end |
#list_services_by_namespace(params = {}) ⇒ Types::ListServicesByNamespaceResponse
This operation lists all of the services that are associated with a Cloud Map namespace. This list might include services in different clusters. In contrast, ‘ListServices` can only list services in one cluster at a time. If you need to filter the list of services in a single cluster by various parameters, use `ListServices`. For more information, see [Service Connect] in the *Amazon Elastic Container Service Developer Guide*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
5280 5281 5282 5283 |
# File 'lib/aws-sdk-ecs/client.rb', line 5280 def list_services_by_namespace(params = {}, = {}) req = build_request(:list_services_by_namespace, params) req.send_request() end |
#list_tags_for_resource(params = {}) ⇒ Types::ListTagsForResourceResponse
List the tags for an Amazon ECS resource.
5331 5332 5333 5334 |
# File 'lib/aws-sdk-ecs/client.rb', line 5331 def (params = {}, = {}) req = build_request(:list_tags_for_resource, params) req.send_request() end |
#list_task_definition_families(params = {}) ⇒ Types::ListTaskDefinitionFamiliesResponse
Returns a list of task definition families that are registered to your account. This list includes task definition families that no longer have any ‘ACTIVE` task definition revisions.
You can filter out task definition families that don’t contain any ‘ACTIVE` task definition revisions by setting the `status` parameter to `ACTIVE`. You can also filter the results with the `familyPrefix` parameter.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
5446 5447 5448 5449 |
# File 'lib/aws-sdk-ecs/client.rb', line 5446 def list_task_definition_families(params = {}, = {}) req = build_request(:list_task_definition_families, params) req.send_request() end |
#list_task_definitions(params = {}) ⇒ Types::ListTaskDefinitionsResponse
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.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
5565 5566 5567 5568 |
# File 'lib/aws-sdk-ecs/client.rb', line 5565 def list_task_definitions(params = {}, = {}) req = build_request(:list_task_definitions, params) req.send_request() end |
#list_tasks(params = {}) ⇒ Types::ListTasksResponse
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.
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
5710 5711 5712 5713 |
# File 'lib/aws-sdk-ecs/client.rb', line 5710 def list_tasks(params = {}, = {}) req = build_request(:list_tasks, params) req.send_request() end |
#put_account_setting(params = {}) ⇒ Types::PutAccountSettingResponse
Modifies an account setting. Account settings are set on a per-Region basis.
If you change the root user account setting, the default settings are reset for users and roles that do not have specified individual account settings. For more information, see [Account Settings] in the *Amazon Elastic Container Service Developer Guide*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html
5917 5918 5919 5920 |
# File 'lib/aws-sdk-ecs/client.rb', line 5917 def put_account_setting(params = {}, = {}) req = build_request(:put_account_setting, params) req.send_request() end |
#put_account_setting_default(params = {}) ⇒ Types::PutAccountSettingDefaultResponse
Modifies an account setting for all users on an account for whom no individual account setting has been specified. Account settings are set on a per-Region basis.
6079 6080 6081 6082 |
# File 'lib/aws-sdk-ecs/client.rb', line 6079 def put_account_setting_default(params = {}, = {}) req = build_request(:put_account_setting_default, params) req.send_request() end |
#put_attributes(params = {}) ⇒ Types::PutAttributesResponse
Create or update an attribute on an Amazon ECS resource. If the attribute doesn’t exist, it’s 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*.
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeleteAttributes.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html#attributes
6135 6136 6137 6138 |
# File 'lib/aws-sdk-ecs/client.rb', line 6135 def put_attributes(params = {}, = {}) req = build_request(:put_attributes, params) req.send_request() end |
#put_cluster_capacity_providers(params = {}) ⇒ Types::PutClusterCapacityProvidersResponse
Modifies the available capacity providers and the default capacity provider strategy for a cluster.
You must specify both the available capacity providers and a default capacity provider strategy for the cluster. If the specified cluster has existing capacity providers associated with it, you must specify all existing capacity providers in addition to any new ones you want to add. Any existing capacity providers that are associated with a cluster that are omitted from a [PutClusterCapacityProviders] API call will be disassociated with the cluster. You can only disassociate an existing capacity provider from a cluster if it’s not being used by any existing tasks.
When creating a service or running a task on a cluster, if no capacity provider or launch type is specified, then the cluster’s default capacity provider strategy is used. We recommend that you define a default capacity provider strategy for your cluster. However, you must specify an empty array (‘[]`) to bypass defining a default strategy.
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html
6278 6279 6280 6281 |
# File 'lib/aws-sdk-ecs/client.rb', line 6278 def put_cluster_capacity_providers(params = {}, = {}) req = build_request(:put_cluster_capacity_providers, params) req.send_request() end |
#register_container_instance(params = {}) ⇒ Types::RegisterContainerInstanceResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
</note>
Registers an EC2 instance into the specified cluster. This instance becomes available to place containers on.
6462 6463 6464 6465 |
# File 'lib/aws-sdk-ecs/client.rb', line 6462 def register_container_instance(params = {}, = {}) req = build_request(:register_container_instance, params) req.send_request() end |
#register_task_definition(params = {}) ⇒ Types::RegisterTaskDefinitionResponse
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 a role for your task with the ‘taskRoleArn` parameter. When you specify a 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 policy that’s associated with the role. For more information, see [IAM Roles for Tasks] in the *Amazon Elastic Container Service Developer Guide*.
You can specify a Docker networking mode for the containers in your task definition with the ‘networkMode` parameter. 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*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/task_defintions.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html [3]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_NetworkConfiguration.html [4]: docs.aws.amazon.com/AmazonECS/latest/developerguide/task-networking.html
7307 7308 7309 7310 |
# File 'lib/aws-sdk-ecs/client.rb', line 7307 def register_task_definition(params = {}, = {}) req = build_request(:register_task_definition, params) req.send_request() end |
#run_task(params = {}) ⇒ Types::RunTaskResponse
Starts a new task using the specified task definition.
<note markdown=“1”> On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.
</note>
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.
Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service.
You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or updating a service. For more infomation, see [Amazon EBS volumes] in the *Amazon Elastic Container Service Developer Guide*.
The Amazon ECS API follows an eventual consistency model. This is because of 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.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types
7890 7891 7892 7893 |
# File 'lib/aws-sdk-ecs/client.rb', line 7890 def run_task(params = {}, = {}) req = build_request(:run_task, params) req.send_request() end |
#start_task(params = {}) ⇒ Types::StartTaskResponse
Starts a new task from the specified task definition on the specified container instance or instances.
<note markdown=“1”> On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.
</note>
Starting April 15, 2023, Amazon Web Services will not onboard new customers to Amazon Elastic Inference (EI), and will help current customers migrate their workloads to options that offer better price and performance. After April 15, 2023, new customers will not be able to launch instances with Amazon EI accelerators in Amazon SageMaker, Amazon ECS, or Amazon EC2. However, customers who have used Amazon EI at least once during the past 30-day period are considered current customers and will be able to continue using the service.
Alternatively, you can use`RunTask` to place tasks for you. For more information, see [Scheduling Tasks] in the *Amazon Elastic Container Service Developer Guide*.
You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or updating a service. For more infomation, see [Amazon EBS volumes] in the *Amazon Elastic Container Service Developer Guide*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types
8270 8271 8272 8273 |
# File 'lib/aws-sdk-ecs/client.rb', line 8270 def start_task(params = {}, = {}) req = build_request(:start_task, params) req.send_request() end |
#stop_task(params = {}) ⇒ Types::StopTaskResponse
Stops a running task. Any tags associated with the task will be deleted.
When you call ‘StopTask` 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.
For Windows containers, POSIX signals do not work and runtime stops the container by sending a ‘CTRL_SHUTDOWN_EVENT`. For more information, see [Unable to react to graceful shutdown of (Windows) container #25982] on GitHub.
<note markdown=“1”> 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*.
</note>
[1]: github.com/moby/moby/issues/25982 [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
8445 8446 8447 8448 |
# File 'lib/aws-sdk-ecs/client.rb', line 8445 def stop_task(params = {}, = {}) req = build_request(:stop_task, params) req.send_request() end |
#submit_attachment_state_changes(params = {}) ⇒ Types::SubmitAttachmentStateChangesResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
</note>
Sent to acknowledge that an attachment changed states.
8488 8489 8490 8491 |
# File 'lib/aws-sdk-ecs/client.rb', line 8488 def (params = {}, = {}) req = build_request(:submit_attachment_state_changes, params) req.send_request() end |
#submit_container_state_change(params = {}) ⇒ Types::SubmitContainerStateChangeResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
</note>
Sent to acknowledge that a container changed states.
8559 8560 8561 8562 |
# File 'lib/aws-sdk-ecs/client.rb', line 8559 def submit_container_state_change(params = {}, = {}) req = build_request(:submit_container_state_change, params) req.send_request() end |
#submit_task_state_change(params = {}) ⇒ Types::SubmitTaskStateChangeResponse
<note markdown=“1”> This action is only used by the Amazon ECS agent, and it is not intended for use outside of the agent.
</note>
Sent to acknowledge that a task changed states.
8661 8662 8663 8664 |
# File 'lib/aws-sdk-ecs/client.rb', line 8661 def submit_task_state_change(params = {}, = {}) req = build_request(:submit_task_state_change, params) req.send_request() end |
#tag_resource(params = {}) ⇒ Struct
Associates the specified tags to a resource with the specified ‘resourceArn`. If existing tags on a resource aren’t specified in the request parameters, they aren’t changed. When a resource is deleted, the tags that are associated with that resource are deleted as well.
8741 8742 8743 8744 |
# File 'lib/aws-sdk-ecs/client.rb', line 8741 def tag_resource(params = {}, = {}) req = build_request(:tag_resource, params) req.send_request() end |
#untag_resource(params = {}) ⇒ Struct
Deletes specified tags from a resource.
8785 8786 8787 8788 |
# File 'lib/aws-sdk-ecs/client.rb', line 8785 def untag_resource(params = {}, = {}) req = build_request(:untag_resource, params) req.send_request() end |
#update_capacity_provider(params = {}) ⇒ Types::UpdateCapacityProviderResponse
Modifies the parameters for a capacity provider.
8843 8844 8845 8846 |
# File 'lib/aws-sdk-ecs/client.rb', line 8843 def update_capacity_provider(params = {}, = {}) req = build_request(:update_capacity_provider, params) req.send_request() end |
#update_cluster(params = {}) ⇒ Types::UpdateClusterResponse
Updates the cluster.
8964 8965 8966 8967 |
# File 'lib/aws-sdk-ecs/client.rb', line 8964 def update_cluster(params = {}, = {}) req = build_request(:update_cluster, params) req.send_request() end |
#update_cluster_settings(params = {}) ⇒ Types::UpdateClusterSettingsResponse
Modifies the settings to use for a cluster.
9055 9056 9057 9058 |
# File 'lib/aws-sdk-ecs/client.rb', line 9055 def update_cluster_settings(params = {}, = {}) req = build_request(:update_cluster_settings, params) req.send_request() end |
#update_container_agent(params = {}) ⇒ Types::UpdateContainerAgentResponse
Updates the Amazon ECS container agent on a specified container instance. Updating the Amazon ECS container agent doesn’t 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.
<note markdown=“1”> 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. This updates the agent. For more information, see [Updating the Amazon ECS container agent] in the *Amazon Elastic Container Service Developer Guide*.
</note>
<note markdown=“1”> Agent updates with the ‘UpdateContainerAgent` API operation do not apply to Windows container instances. We recommend that you launch new container instances to update the agent version in your Windows clusters.
</note>
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*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/agent-update-ecs-ami.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html#manually_update_agent
9173 9174 9175 9176 |
# File 'lib/aws-sdk-ecs/client.rb', line 9173 def update_container_agent(params = {}, = {}) req = build_request(:update_container_agent, params) req.send_request() end |
#update_container_instances_state(params = {}) ⇒ Types::UpdateContainerInstancesStateResponse
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 can’t 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’re in the ‘RUNNING` state. Tasks for services that use a load balancer are considered healthy if they’re in the ‘RUNNING` state and are reported as healthy by the load balancer.
-
The ‘maximumPercent` parameter represents an upper limit on the number of running tasks during task replacement. You can use this 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 aren’t 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.
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html [2]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ListTasks.html
9331 9332 9333 9334 |
# File 'lib/aws-sdk-ecs/client.rb', line 9331 def update_container_instances_state(params = {}, = {}) req = build_request(:update_container_instances_state, params) req.send_request() end |
#update_service(params = {}) ⇒ Types::UpdateServiceResponse
Modifies the parameters of a service.
<note markdown=“1”> On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.
</note>
For services using the rolling update (‘ECS`) you can update the desired count, deployment configuration, network configuration, load balancers, service registries, enable ECS managed tags option, propagate tags option, task placement constraints and strategies, and task definition. When you update any of these parameters, Amazon ECS starts new tasks with the new configuration.
You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when starting or running a task, or when creating or updating a service. For more infomation, see [Amazon EBS volumes] in the *Amazon Elastic Container Service Developer Guide*. You can update your volume configurations and trigger a new deployment. ‘volumeConfigurations` is only supported for REPLICA service and not DAEMON service. If you leave `volumeConfigurations` `null`, it doesn’t trigger a new deployment. For more infomation on volumes, see
- Amazon EBS volumes][1
-
in the *Amazon Elastic Container Service
Developer Guide*.
For services using the blue/green (‘CODE_DEPLOY`) deployment controller, only the desired count, deployment configuration, health check grace period, task placement constraints and strategies, enable ECS managed tags option, and propagate tags can be updated using this API. If the network configuration, platform version, task definition, or load balancer need to be updated, create a new CodeDeploy deployment. 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, health check grace period, enable ECS managed tags option, and propagate tags option, using this API. If the launch type, load balancer, network configuration, platform version, or task definition need to be updated, 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.
You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when starting or running a task, or when creating or updating a service. For more infomation, see [Amazon EBS volumes] in the *Amazon Elastic Container Service Developer Guide*.
If you have updated the container 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.
<note markdown=“1”> 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 don’t 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.
</note>
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 don’t use a load balancer are considered healthy if they’re in the ‘RUNNING` state. Tasks for services that use a load balancer are considered healthy if they’re in the ‘RUNNING` state and are reported as healthy by the load balancer.
-
The ‘maximumPercent` parameter represents an upper limit on the number of running tasks during a deployment. You can use it 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 this, `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 even though 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.
<note markdown=“1”> You must have a service-linked role when you update any of the following service properties:
* `loadBalancers`,
-
‘serviceRegistries`
For more information about the role see the `CreateService` request
parameter [ ‘role` ][5].
</note>
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types [2]: docs.aws.amazon.com/codedeploy/latest/APIReference/API_CreateDeployment.html [3]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateTaskSet.html [4]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_UpdateService.html [5]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateService.html#ECS-CreateService-request-role
10061 10062 10063 10064 |
# File 'lib/aws-sdk-ecs/client.rb', line 10061 def update_service(params = {}, = {}) req = build_request(:update_service, params) req.send_request() end |
#update_service_primary_task_set(params = {}) ⇒ Types::UpdateServicePrimaryTaskSetResponse
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][1
-
in the *Amazon Elastic Container
Service Developer Guide*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html
10151 10152 10153 10154 |
# File 'lib/aws-sdk-ecs/client.rb', line 10151 def update_service_primary_task_set(params = {}, = {}) req = build_request(:update_service_primary_task_set, params) req.send_request() end |
#update_task_protection(params = {}) ⇒ Types::UpdateTaskProtectionResponse
Updates the protection status of a task. You can set ‘protectionEnabled` to `true` to protect your task from termination during scale-in events from [Service Autoscaling] or [deployments].
Task-protection, by default, expires after 2 hours at which point Amazon ECS clears the ‘protectionEnabled` property making the task eligible for termination by a subsequent scale-in event.
You can specify a custom expiration period for task protection from 1 minute to up to 2,880 minutes (48 hours). To specify the custom expiration period, set the ‘expiresInMinutes` property. The `expiresInMinutes` property is always reset when you invoke this operation for a task that already has `protectionEnabled` set to `true`. You can keep extending the protection expiration period of a task by invoking this operation repeatedly.
To learn more about Amazon ECS task protection, see [Task scale-in protection] in the Amazon Elastic Container Service Developer Guide .
<note markdown=“1”> This operation is only supported for tasks belonging to an Amazon ECS service. Invoking this operation for a standalone task will result in an ‘TASK_NOT_VALID` failure. For more information, see [API failure reasons].
</note>
If you prefer to set task protection from within the container, we recommend using the [Task scale-in protection endpoint].
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/service-auto-scaling.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html [3]: docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection.html [4]: docs.aws.amazon.com/AmazonECS/latest/developerguide/api_failures_messages.html [5]: docs.aws.amazon.com/AmazonECS/latest/developerguide/task-scale-in-protection-endpoint.html
10323 10324 10325 10326 |
# File 'lib/aws-sdk-ecs/client.rb', line 10323 def update_task_protection(params = {}, = {}) req = build_request(:update_task_protection, params) req.send_request() end |
#update_task_set(params = {}) ⇒ Types::UpdateTaskSetResponse
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*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html
10419 10420 10421 10422 |
# File 'lib/aws-sdk-ecs/client.rb', line 10419 def update_task_set(params = {}, = {}) req = build_request(:update_task_set, params) req.send_request() end |
#wait_until(waiter_name, params = {}, options = {}) {|w.waiter| ... } ⇒ Boolean
Polls an API operation until a resource enters a desired state.
## Basic Usage
A waiter will call an API operation until:
-
It is successful
-
It enters a terminal state
-
It makes the maximum number of attempts
In between attempts, the waiter will sleep.
# polls in a loop, sleeping between attempts
client.wait_until(waiter_name, params)
## Configuration
You can configure the maximum number of polling attempts, and the delay (in seconds) between each polling attempt. You can pass configuration as the final arguments hash.
# poll for ~25 seconds
client.wait_until(waiter_name, params, {
max_attempts: 5,
delay: 5,
})
## Callbacks
You can be notified before each polling attempt and before each delay. If you throw ‘:success` or `:failure` from these callbacks, it will terminate the waiter.
started_at = Time.now
client.wait_until(waiter_name, params, {
# disable max attempts
max_attempts: nil,
# poll for 1 hour, instead of a number of attempts
before_wait: -> (attempts, response) do
throw :failure if Time.now - started_at > 3600
end
})
## Handling Errors
When a waiter is unsuccessful, it will raise an error. All of the failure errors extend from Waiters::Errors::WaiterFailed.
begin
client.wait_until(...)
rescue Aws::Waiters::Errors::WaiterFailed
# resource did not enter the desired state in time
end
## Valid Waiters
The following table lists the valid waiter names, the operations they call, and the default ‘:delay` and `:max_attempts` values.
| waiter_name | params | :delay | :max_attempts | | —————– | ————————– | ——– | ————- | | services_inactive | #describe_services | 15 | 40 | | services_stable | #describe_services | 15 | 40 | | tasks_running | #describe_tasks | 6 | 100 | | tasks_stopped | #describe_tasks | 6 | 100 |
10537 10538 10539 10540 10541 |
# File 'lib/aws-sdk-ecs/client.rb', line 10537 def wait_until(waiter_name, params = {}, = {}) w = waiter(waiter_name, ) yield(w.waiter) if block_given? # deprecated w.wait(params) end |
#waiter_names ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
10545 10546 10547 |
# File 'lib/aws-sdk-ecs/client.rb', line 10545 def waiter_names waiters.keys end |