Expand description
With Application Auto Scaling, you can configure automatic scaling for the following resources:
-
Amazon AppStream 2.0 fleets
-
Amazon Aurora Replicas
-
Amazon Comprehend document classification and entity recognizer endpoints
-
Amazon DynamoDB tables and global secondary indexes throughput capacity
-
Amazon ECS services
-
Amazon ElastiCache for Redis clusters (replication groups)
-
Amazon EMR clusters
-
Amazon Keyspaces (for Apache Cassandra) tables
-
Lambda function provisioned concurrency
-
Amazon Managed Streaming for Apache Kafka broker storage
-
Amazon Neptune clusters
-
Amazon SageMaker endpoint variants
-
Spot Fleets (Amazon EC2)
-
Custom resources provided by your own applications or services
API Summary
The Application Auto Scaling service API includes three key sets of actions:
-
Register and manage scalable targets - Register Amazon Web Services or custom resources as scalable targets (a resource that Application Auto Scaling can scale), set minimum and maximum capacity limits, and retrieve information on existing scalable targets.
-
Configure and manage automatic scaling - Define scaling policies to dynamically scale your resources in response to CloudWatch alarms, schedule one-time or recurring scaling actions, and retrieve your recent scaling activity history.
-
Suspend and resume scaling - Temporarily suspend and later resume automatic scaling by calling the RegisterScalableTarget API action for any Application Auto Scaling scalable target. You can suspend and resume (individually or in combination) scale-out activities that are triggered by a scaling policy, scale-in activities that are triggered by a scaling policy, and scheduled scaling.
To learn more about Application Auto Scaling, including information about granting IAM users required permissions for Application Auto Scaling actions, see the Application Auto Scaling User Guide.
Crate Organization
The entry point for most customers will be Client
. Client
exposes one method for each API offered
by the service.
Some APIs require complex or nested arguments. These exist in model
.
Lastly, errors that can be returned by the service are contained within error
. Error
defines a meta
error encompassing all possible errors that can be returned by the service.
The other modules within this crate are not required for normal usage.
Examples
Examples can be found here.
Re-exports
Modules
Client and fluent builders for calling the service.
Configuration for the service.
Errors that can occur when calling the service.
Input structures for operations.
Base Middleware Stack
Data structures used by operation inputs/outputs.
All operations that this crate can perform.
Output structures for operations.
Paginators for the service
Structs
App name that can be configured with an AWS SDK client to become part of the user agent string.
Binary Blob Type
Stream of binary data
AWS SDK Credentials
DateTime in time.
API Endpoint
The region to send requests to.
Retry configuration for requests.
Enums
Statics
Crate version number.