AutoScaling¶
Client¶
- class AutoScaling.Client¶
A low-level client representing Auto Scaling
The DescribeAutoScalingGroups API operation might be throttled when retrieving details for an Auto Scaling group that contains many instances. By default, this operation returns details for all instances in the group. To help prevent throttling, you can set the
IncludeInstancesparameter tofalseto exclude instance details from the response.Amazon EC2 Auto Scaling is designed to automatically launch and terminate EC2 instances based on user-defined scaling policies, scheduled actions, and health checks.
For more information, see the Amazon EC2 Auto Scaling User Guide and the Amazon EC2 Auto Scaling API Reference.
import boto3 client = boto3.client('autoscaling')
These are the available methods:
- attach_instances
- attach_load_balancer_target_groups
- attach_load_balancers
- attach_traffic_sources
- batch_delete_scheduled_action
- batch_put_scheduled_update_group_action
- can_paginate
- cancel_instance_refresh
- close
- complete_lifecycle_action
- create_auto_scaling_group
- create_launch_configuration
- create_or_update_tags
- delete_auto_scaling_group
- delete_launch_configuration
- delete_lifecycle_hook
- delete_notification_configuration
- delete_policy
- delete_scheduled_action
- delete_tags
- delete_warm_pool
- describe_account_limits
- describe_adjustment_types
- describe_auto_scaling_groups
- describe_auto_scaling_instances
- describe_auto_scaling_notification_types
- describe_instance_refreshes
- describe_launch_configurations
- describe_lifecycle_hook_types
- describe_lifecycle_hooks
- describe_load_balancer_target_groups
- describe_load_balancers
- describe_metric_collection_types
- describe_notification_configurations
- describe_policies
- describe_scaling_activities
- describe_scaling_process_types
- describe_scheduled_actions
- describe_tags
- describe_termination_policy_types
- describe_traffic_sources
- describe_warm_pool
- detach_instances
- detach_load_balancer_target_groups
- detach_load_balancers
- detach_traffic_sources
- disable_metrics_collection
- enable_metrics_collection
- enter_standby
- execute_policy
- exit_standby
- get_paginator
- get_predictive_scaling_forecast
- get_waiter
- put_lifecycle_hook
- put_notification_configuration
- put_scaling_policy
- put_scheduled_update_group_action
- put_warm_pool
- record_lifecycle_action_heartbeat
- resume_processes
- rollback_instance_refresh
- set_desired_capacity
- set_instance_health
- set_instance_protection
- start_instance_refresh
- suspend_processes
- terminate_instance_in_auto_scaling_group
- update_auto_scaling_group
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: