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.
375 376 377 |
# File 'lib/aws-sdk-ecs/client.rb', line 375 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.
9772 9773 9774 |
# File 'lib/aws-sdk-ecs/client.rb', line 9772 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.
9775 9776 9777 |
# File 'lib/aws-sdk-ecs/client.rb', line 9775 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.
9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 |
# File 'lib/aws-sdk-ecs/client.rb', line 9631 def build_request(operation_name, params = {}) handlers = @handlers.for(operation_name) context = Seahorse::Client::RequestContext.new( operation_name: operation_name, operation: config.api.operation(operation_name), client: self, params: params, config: config) context[:gem_name] = 'aws-sdk-ecs' context[:gem_version] = '1.111.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.
478 479 480 481 |
# File 'lib/aws-sdk-ecs/client.rb', line 478 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 with the `CreateCluster` action.
<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/developerguide/using-service-linked-roles.html
727 728 729 730 |
# File 'lib/aws-sdk-ecs/client.rb', line 727 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, see the UpdateService action.
In addition to maintaining the desired count of tasks in your service, you can optionally run your service behind one or more load balancers. The load balancers distribute traffic across the tasks that are associated with the service. For more information, see [Service load balancing] in the *Amazon Elastic Container Service Developer Guide*.
Tasks for services that don't use a load balancer are considered healthy if they're in the `RUNNING` state. Tasks for services that use a load balancer are considered healthy if they're in the `RUNNING` state and are reported as healthy by the load balancer.
There are two service scheduler strategies available:
-
`REPLICA` - The replica scheduling strategy places and maintains your desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. For more information, see [Service scheduler concepts] in the *Amazon Elastic Container Service Developer Guide*.
-
`DAEMON` - The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks. It also stops tasks that don't meet the placement constraints. When using this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies. For more information, see [Service scheduler concepts] in the *Amazon Elastic Container Service Developer Guide*.
You can optionally specify a deployment configuration for your service. The deployment is initiated by changing properties. For example, the deployment might be initiated by the task definition or by your desired count of a service. This is done with an UpdateService operation. The default value for a replica service for `minimumHealthyPercent` is 100%. The default value for a daemon service for `minimumHealthyPercent` is 0%.
If a service uses the `ECS` deployment controller, the minimum healthy percent represents a lower limit on the number of tasks in a service that must remain in the `RUNNING` state during a deployment. Specifically, it represents it as a percentage of your desired number of tasks (rounded up to the nearest integer). This happens when any of your container instances are in the `DRAINING` state if the service contains tasks using the EC2 launch type. Using this parameter, you can deploy without using additional cluster capacity. For example, if you set your service to have desired number of four tasks and a minimum healthy percent of 50%, the scheduler might stop two existing tasks to free up cluster capacity before starting two new tasks. If they're in the `RUNNING` state, tasks for services that don't use a load balancer are considered healthy . If they're in the `RUNNING` state and reported as healthy by the load balancer, tasks for services that do use a load balancer are considered healthy . The default value for minimum healthy percent is 100%.
If a service uses the `ECS` deployment controller, the **maximum percent** parameter represents an upper limit on the number of tasks in a service that are allowed in the `RUNNING` or `PENDING` state during a deployment. Specifically, it represents it as a percentage of the desired number of tasks (rounded down to the nearest integer). This happens when any of your container instances are in the `DRAINING` state if the service contains tasks using the EC2 launch type. Using this parameter, you can define the deployment batch size. For example, if your service has a desired number of four tasks and a maximum percent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default value for maximum percent is 200%.
If a service uses either the `CODE_DEPLOY` or `EXTERNAL` deployment controller types and tasks that use the EC2 launch type, the **minimum healthy percent** and **maximum percent** values are used only to define the lower and upper limit on the number of the tasks in the service that remain in the `RUNNING` state. This is while the container instances are in the `DRAINING` state. If the tasks in the service use the Fargate launch type, the minimum healthy percent and maximum percent values aren't used. This is the case even if they're currently visible when describing your service.
When creating a service that uses the `EXTERNAL` deployment controller, you can specify only parameters that aren't controlled at the task set level. The only required parameter is the service name. You control your services using the CreateTaskSet operation. For more information, see [Amazon ECS deployment types] in the *Amazon Elastic Container Service Developer Guide*.
When the service scheduler launches new tasks, it determines task placement. For information about task placement and task placement strategies, see [Amazon ECS task placement] in the *Amazon Elastic Container Service Developer Guide*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html [2]: docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html [3]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html [4]: docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html
1561 1562 1563 1564 |
# File 'lib/aws-sdk-ecs/client.rb', line 1561 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*.
[1]: docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html
1798 1799 1800 1801 |
# File 'lib/aws-sdk-ecs/client.rb', line 1798 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.
1882 1883 1884 1885 |
# File 'lib/aws-sdk-ecs/client.rb', line 1882 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.
1931 1932 1933 1934 |
# File 'lib/aws-sdk-ecs/client.rb', line 1931 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 the PutClusterCapacityProviders API 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 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 PutClusterCapacityProviders or delete the cluster.
1991 1992 1993 1994 |
# File 'lib/aws-sdk-ecs/client.rb', line 1991 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.
2088 2089 2090 2091 |
# File 'lib/aws-sdk-ecs/client.rb', line 2088 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 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.
</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.
2307 2308 2309 2310 |
# File 'lib/aws-sdk-ecs/client.rb', line 2307 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.
[1]: docs.aws.amazon.com/AmazonECS/latest/APIReference/API_DeregisterTaskDefinition.html
2527 2528 2529 2530 |
# File 'lib/aws-sdk-ecs/client.rb', line 2527 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
2619 2620 2621 2622 |
# File 'lib/aws-sdk-ecs/client.rb', line 2619 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>
2759 2760 2761 2762 |
# File 'lib/aws-sdk-ecs/client.rb', line 2759 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
2976 2977 2978 2979 |
# File 'lib/aws-sdk-ecs/client.rb', line 2976 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.
3061 3062 3063 3064 |
# File 'lib/aws-sdk-ecs/client.rb', line 3061 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.
3179 3180 3181 3182 |
# File 'lib/aws-sdk-ecs/client.rb', line 3179 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.
3370 3371 3372 3373 |
# File 'lib/aws-sdk-ecs/client.rb', line 3370 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
3624 3625 3626 3627 |
# File 'lib/aws-sdk-ecs/client.rb', line 3624 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>
3895 3896 3897 3898 |
# File 'lib/aws-sdk-ecs/client.rb', line 3895 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
3993 3994 3995 3996 |
# File 'lib/aws-sdk-ecs/client.rb', line 3993 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.
The following waiters are defined for this operation (see #wait_until for detailed usage):
* tasks_running
* tasks_stopped