ECS#
Client#
- class ECS.Client#
A low-level client representing Amazon EC2 Container Service (ECS)
Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service. It makes it easy to run, stop, and manage Docker containers. You can host your cluster on a serverless infrastructure that’s managed by Amazon ECS by launching your services or tasks on Fargate. For more control, you can host your tasks on a cluster of Amazon Elastic Compute Cloud (Amazon EC2) or External (on-premises) instances that you manage.
Amazon ECS makes it easy to launch and stop container-based applications with simple API calls. This makes it easy to get the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features.
You can use Amazon ECS to schedule the placement of containers across your cluster based on your resource needs, isolation policies, and availability requirements. With Amazon ECS, you don’t need to operate your own cluster management and configuration management systems. You also don’t need to worry about scaling your management infrastructure.
client = session.create_client('ecs')
These are the available methods:
- can_paginate
- close
- create_capacity_provider
- create_cluster
- create_service
- create_task_set
- delete_account_setting
- delete_attributes
- delete_capacity_provider
- delete_cluster
- delete_service
- delete_task_definitions
- delete_task_set
- deregister_container_instance
- deregister_task_definition
- describe_capacity_providers
- describe_clusters
- describe_container_instances
- describe_service_deployments
- describe_service_revisions
- describe_services
- describe_task_definition
- describe_task_sets
- describe_tasks
- discover_poll_endpoint
- execute_command
- get_paginator
- get_task_protection
- get_waiter
- list_account_settings
- list_attributes
- list_clusters
- list_container_instances
- list_service_deployments
- list_services
- list_services_by_namespace
- list_tags_for_resource
- list_task_definition_families
- list_task_definitions
- list_tasks
- put_account_setting
- put_account_setting_default
- put_attributes
- put_cluster_capacity_providers
- register_container_instance
- register_task_definition
- run_task
- start_task
- stop_task
- submit_attachment_state_changes
- submit_container_state_change
- submit_task_state_change
- tag_resource
- untag_resource
- update_capacity_provider
- update_cluster
- update_cluster_settings
- update_container_agent
- update_container_instances_state
- update_service
- update_service_primary_task_set
- update_task_protection
- update_task_set
Client Exceptions#
Client exceptions are available on a client instance via the exceptions property. For more detailed instructions and examples on the exact usage of client exceptions, see the error handling user guide.
The available client exceptions are:
- AccessDeniedException
- AttributeLimitExceededException
- BlockedException
- ClientException
- ClusterContainsContainerInstancesException
- ClusterContainsServicesException
- ClusterContainsTasksException
- ClusterNotFoundException
- ConflictException
- InvalidParameterException
- LimitExceededException
- MissingVersionException
- NamespaceNotFoundException
- NoUpdateAvailableException
- PlatformTaskDefinitionIncompatibilityException
- PlatformUnknownException
- ResourceInUseException
- ResourceNotFoundException
- ServerException
- ServiceNotActiveException
- ServiceNotFoundException
- TargetNotConnectedException
- TargetNotFoundException
- TaskSetNotFoundException
- UnsupportedFeatureException
- UpdateInProgressException
Paginators#
Paginators are available on a client instance via the get_paginator method. For more detailed instructions and examples on the usage of paginators, see the paginators user guide.
The available paginators are:
Waiters#
Waiters are available on a client instance via the get_waiter method. For more detailed instructions and examples on the usage or waiters, see the waiters user guide.
The available waiters are: