AutoScaling
Auto Scaling groups, launch configurations, scaling policies, lifecycle hooks, scheduled actions, warm pools.
Quick start
import boto3
asg = boto3.client("autoscaling", endpoint_url="http://localhost:4566",
region_name="us-east-1",
aws_access_key_id="test", aws_secret_access_key="test")
asg.create_launch_configuration(LaunchConfigurationName="lc", ImageId="ami-000",
InstanceType="t3.micro")
asg.create_auto_scaling_group(AutoScalingGroupName="g",
LaunchConfigurationName="lc", MinSize=1, MaxSize=3,
AvailabilityZones=["us-east-1a"])
Supported operations
23 operations exposed by this service as of MiniStack 1.3.14. Extracted directly from the handler dispatch in the source module.
CompleteLifecycleAction
CreateAutoScalingGroup
CreateLaunchConfiguration
CreateOrUpdateTags
DeleteAutoScalingGroup
DeleteLaunchConfiguration
DeleteLifecycleHook
DeletePolicy
DeleteScheduledAction
DeleteTags
DescribeAutoScalingGroups
DescribeAutoScalingInstances
DescribeLaunchConfigurations
DescribeLifecycleHooks
DescribePolicies
DescribeScalingActivities
DescribeScheduledActions
DescribeTags
PutLifecycleHook
PutScalingPolicy
PutScheduledUpdateGroupAction
RecordLifecycleActionHeartbeat
UpdateAutoScalingGroup
CloudFormation
The CloudFormation engine provisions these resource types via this service:
AWS::AutoScaling::AutoScalingGroup
AWS::AutoScaling::LaunchConfiguration
AWS::AutoScaling::ScalingPolicy
AWS::AutoScaling::LifecycleHook
AWS::AutoScaling::ScheduledAction
See CloudFormation engine for intrinsic support and lifecycle details.
Known limitations
- Scaling policies are stored but never triggered by CloudWatch alarms.
- Lifecycle hooks exist but the Pending:Wait / Terminating:Wait signal handling is incomplete.
Source
ministack/services/autoscaling.py:500-560
Read the source to verify the ops list above — dispatch tables and handler functions are the ground truth.