@aws-cdk/aws-autoscaling

The CDK Construct Library for AWS Auto-Scaling

This module is part of the AWS Cloud Development Kit project.

Fleet

Auto Scaling Group

An AutoScalingGroup represents a number of instances on which you run your code. You pick the size of the fleet, the instance type and the OS image:

import autoscaling = require('@aws-cdk/aws-autoscaling');
import ec2 = require('@aws-cdk/aws-ec2');

new autoscaling.AutoScalingGroup(stack, 'ASG', {
    vpc,
    instanceType: new ec2.InstanceTypePair(InstanceClass.Burstable2, InstanceSize.Micro),
    machineImage: new ec2.AmazonLinuxImage() // get the latest Amazon Linux image
});

NOTE: AutoScalingGroup has an property called allowAllOutbound (allowing the instances to contact the internet) which is set to true by default. Be sure to set this to false if you don't want your instances to be able to start arbitrary connections.

AMIs

AMIs control the OS that gets launched when you start your instance.

Depending on the type of AMI, you select it a different way.

The latest version of Windows images are regionally published under labels, so you can select Windows images like this:

new ec2.WindowsImage(WindowsVersion.WindowsServer2016EnglishNanoBase)

You can select the latest Amazon Linux image like this:

new ec2.AmazonLinuxImage()

Other Linux images are unfortunately not currently published this way, so you have to supply a region-to-AMI map when creating a Linux image:

machineImage: new ec2.GenericLinuxImage({
    'us-east-1': 'ami-97785bed',
    'eu-west-1': 'ami-12345678',
    // ...
})

NOTE: Selecting Linux images will change when the information is published in an automatically consumable way.

Allowing Connections

See the documentation of the aws-ec2 package for more information about allowing connections between resources backed by instances.

Changelog

0.14.0 (2018-10-26)

IMPORTANT NOTE: when upgrading to this version of the CDK framework, you must also upgrade your installation the CDK Toolkit to the matching version:

$ npm i -g aws-cdk
$ cdk --version
0.14.0 (build ...)

Bug Fixes

• remove CloudFormation property renames (#973) (3f86603), closes #852
• aws-ec2: fix retention of all egress traffic rule (#998) (b9d5b43), closes #987
• aws-s3-deployment: avoid deletion during update using physical ids (#1006) (bca99c6), closes #981 #981
• cloudformation-diff: ignore changes to DependsOn (#1005) (3605f9c), closes #274
• cloudformation-diff: track replacements (#1003) (a83ac5f), closes #1001
• docs: fix EC2 readme for "natgatway" configuration (#994) (0b1e7cc)
• docs: updates to contribution guide (#997) (b42e742)
• iam: Merge multiple principals correctly (#983) (3fc5c8c), closes #924 #916 #958

Features

• add construct library for Application AutoScaling (#933) (7861c6f), closes #856 #861 #640 #644
• add HostedZone context provider (#823) (1626c37)
• assert: haveResource lists failing properties (#1016) (7f6f3fd)
• aws-cdk: add CDK app version negotiation (#988) (db4e718), closes #891
• aws-codebuild: Introduce a CodePipeline test Action. (#873) (770f9aa)
• aws-sqs: Add grantXxx() methods (#1004) (8c90350)
• core: Pre-concatenate Fn::Join (#967) (33c32a8), closes #916 #958

BREAKING CHANGES TO EXPERIMENTAL FEATURES

• DynamoDB AutoScaling: Instead of addReadAutoScaling(), call autoScaleReadCapacity(), and similar for write scaling.
• CloudFormation resource usage: If you use L1s, you may need to change some XxxName properties back into Name. These will match the CloudFormation property names.
• You must use the matching aws-cdk toolkit when upgrading to this version, or context providers will cease to work. All existing cached context values in cdk.json will be invalidated and refreshed.