Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

Commit

Permalink
Periodic update June 2019
Browse files Browse the repository at this point in the history
  • Loading branch information
@Reneehi
Reneehi committed Jun 29, 2019
1 parent 6c29514 commit 3a8910c
Show file tree
Hide file tree
Showing 55 changed files with 1,188 additions and 679 deletions.
30 changes: 15 additions & 15 deletions doc_source/ASGettingNotifications.md
View file
Expand Up @@ -45,7 +45,7 @@ RequestId: 4e6156f4-a9e2-4bda-a7fd-33f2ae528958
Event: autoscaling:EC2_INSTANCE_LAUNCH
AccountId: 123456789012
AutoScalingGroupName: my-asg
AutoScalingGroupARN: arn:aws:autoscaling:us-west-2:123456789012:autoScalingGroup...
AutoScalingGroupARN: arn:aws:autoscaling:region:123456789012:autoScalingGroup...
ActivityId: 4e6156f4-a9e2-4bda-a7fd-33f2ae528958
Description: Launching a new EC2 instance: i-0598c7d356eba48d7
Cause: At 2016-09-30T18:59:38Z a user request update of AutoScalingGroup constraints to ...
Expand All @@ -55,7 +55,7 @@ StatusCode: InProgress
StatusMessage:
Progress: 50
EC2InstanceId: i-0598c7d356eba48d7
Details: {"Subnet ID":"subnet-c9663da0","Availability Zone":"us-west-2b"}
Details: {"Subnet ID":"subnet-id","Availability Zone":"zone"}
```

## Configure Amazon SNS<a name="as-configure-sns"></a>
Expand Down Expand Up @@ -86,7 +86,7 @@ You will receive an acknowledgement message from AWS\. Amazon SNS is now configu

You can configure your Auto Scaling group to send notifications to Amazon SNS when a scaling event, such as launching instances or terminating instances, takes place\. Amazon SNS sends a notification with information about the instances to the email address that you specified\.

**To configure Amazon SNS notifications for your Auto Scaling group using the console**
**To configure Amazon SNS notifications for your Auto Scaling group \(console\)**

1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.

Expand All @@ -105,8 +105,8 @@ You can configure your Auto Scaling group to send notifications to Amazon SNS wh
1. Choose **Save**\.
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/autoscaling/ec2/userguide/images/as-add-notification.png)

**To configure Amazon SNS notifications for your Auto Scaling group using the AWS CLI**
Use the following [https://docs.aws.amazon.com/cli/latest/reference/autoscaling/put-notification-configuration.html](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/put-notification-configuration.html) command:
**To configure Amazon SNS notifications for your Auto Scaling group \(AWS CLI\)**
Use the following [https://docs.aws.amazon.com/cli/latest/reference/autoscaling/put-notification-configuration.html](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/put-notification-configuration.html) command\.

```
aws autoscaling put-notification-configuration --auto-scaling-group-name my-asg --topic-arn arn --notification-types "autoscaling:EC2_INSTANCE_LAUNCH" "autoscaling:EC2_INSTANCE_TERMINATE"
Expand All @@ -116,7 +116,7 @@ aws autoscaling put-notification-configuration --auto-scaling-group-name my-asg

To generate a notification for a launch event, update the Auto Scaling group by increasing the desired capacity of the Auto Scaling group by 1\. Amazon EC2 Auto Scaling launches the EC2 instance, and you receive an email notification within a few minutes\.

**To change the desired capacity using the console**
**To change the desired capacity \(console\)**

1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.

Expand All @@ -132,8 +132,8 @@ To generate a notification for a launch event, update the Auto Scaling group by

1. After a few minutes, you'll receive a notification email for the launch event\. If you do not need the additional instance that you launched for this test, you can decrease **Desired** by 1\. After a few minutes, you'll receive a notification email for the terminate event\.

**To change the desired capacity using the AWS CLI**
Use the following [https://docs.aws.amazon.com/cli/latest/reference/autoscaling/set-desired-capacity.html](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/set-desired-capacity.html) command:
**To change the desired capacity \(AWS CLI\)**
Use the following [https://docs.aws.amazon.com/cli/latest/reference/autoscaling/set-desired-capacity.html](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/set-desired-capacity.html) command\.

```
aws autoscaling set-desired-capacity --auto-scaling-group-name my-asg --desired-capacity 2
Expand All @@ -143,16 +143,16 @@ aws autoscaling set-desired-capacity --auto-scaling-group-name my-asg --desired-

Check your email for a message from Amazon SNS and open the email\. After you receive notification of a scaling event for your Auto Scaling group, you can confirm the scaling event by looking at the description of your Auto Scaling group\. You need information from the notification email, such as the ID of the instance that was launched or terminated\.

**To verify that your Auto Scaling group has launched new instance using the console**
**To verify that your Auto Scaling group has launched new instance \(console\)**

1. Select your Auto Scaling group\.

1. On the **Activity History** tab, the **Status** column shows the current status of your instance\. For example, if the notification indicates that an instance has launched, use the refresh button to verify that the status of the launch activity is **Successful**\.

1. On the **Instances** tab, you can view the current **Lifecycle** state of the instance whose ID you received in the notification email\. After a new instance starts, its lifecycle state changes to `InService`\.

**To verify that your Auto Scaling group has launched a new instance using the AWS CLI**
Use the following [https://docs.aws.amazon.com/cli/latest/reference/autoscaling/describe-auto-scaling-groups.html](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/describe-auto-scaling-groups.html) command to confirm that the size of your Auto Scaling group has changed:
**To verify that your Auto Scaling group has launched a new instance \(AWS CLI\)**
Use the following [https://docs.aws.amazon.com/cli/latest/reference/autoscaling/describe-auto-scaling-groups.html](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/describe-auto-scaling-groups.html) command to confirm that the size of your Auto Scaling group has changed\.

```
aws autoscaling describe-auto-scaling-groups --auto-scaling-group-name my-asg
Expand Down Expand Up @@ -211,7 +211,7 @@ The following example output shows that the group has two instances\. Check for

You can delete your Amazon EC2 Auto Scaling notification configuration at any time\.

**To delete Amazon EC2 Auto Scaling notification configuration using the console**
**To delete Amazon EC2 Auto Scaling notification configuration \(console\)**

1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.

Expand All @@ -221,11 +221,11 @@ You can delete your Amazon EC2 Auto Scaling notification configuration at any ti

1. On the **Notifications** tab, choose **Delete** next to the notification\.

**To delete Amazon EC2 Auto Scaling notification configuration using the AWS CLI**
Use the following delete\-notification\-configuration command:
**To delete Amazon EC2 Auto Scaling notification configuration \(AWS CLI\)**
Use the following delete\-notification\-configuration command\.

```
aws autoscaling delete-notification-configuration --auto-scaling-group-name my-asg --topic-arn arn:aws:sns:us-west-2:123456789012:my-sns-topic
aws autoscaling delete-notification-configuration --auto-scaling-group-name my-asg --topic-arn arn
```

For information about deleting the Amazon SNS topic and all subscriptions associated with your Auto Scaling group, see [Clean Up](https://docs.aws.amazon.com/sns/latest/dg/CleanUp.html) in the *Amazon Simple Notification Service Developer Guide*\.
8 changes: 4 additions & 4 deletions doc_source/AutoScalingGroup.md
View file
Expand Up @@ -2,17 +2,17 @@

An *Auto Scaling group* contains a collection of Amazon EC2 instances that are treated as a logical grouping for the purposes of automatic scaling and management\. An Auto Scaling group also enables you to use Amazon EC2 Auto Scaling features such as health check replacements and scaling policies\. Both maintaining the number of instances in an Auto Scaling group and automatic scaling are the core functionality of the Amazon EC2 Auto Scaling service\.

The size of an Auto Scaling group depends on the number of instances you set as the desired capacity\. You can adjust its size to meet demand either manually, or by using automatic scaling\.
The size of an Auto Scaling group depends on the number of instances you set as the desired capacity\. You can adjust its size to meet demand, either manually or by using automatic scaling\.

An Auto Scaling group starts by launching enough instances to meet its desired capacity\. It maintains this number of instances by performing periodic health checks on the instances in the group\. The Auto Scaling group continues to maintain a fixed number of instances even if an instance becomes unhealthy\. If an instance becomes unhealthy, the group terminates the unhealthy instance and launches another instance to replace it\. For more information, see [Health Checks for Auto Scaling Instances](healthcheck.md)\.

You can use scaling policies to increase or decrease the number of instances in your group dynamically to meet changing conditions\. When the scaling policy is in effect, the Auto Scaling group adjusts the desired capacity of the group, between the minimum and maximum capacity values that you specify, and launches or terminates the instances as needed\. You can also scale on a schedule\. For more information, see [Scaling the Size of Your Auto Scaling Group](scaling_plan.md)\.

An Auto Scaling group can launch On\-Demand Instances, Spot Instances, or both\. You can specify multiple purchase options for your Auto Scaling group only when you configure the group to use a launch template\. \(We recommend that you use launch templates instead of launch configurations to make sure that you can use the latest features of Amazon EC2\.\)

Spot Instances provide you with access to unused Amazon EC2 capacity at steep discounts relative to On\-Demand prices\. For more information, see [Amazon EC2 Spot Instances](https://aws.amazon.com/ec2/spot/pricing/)\. The key differences between Spot Instances and On\-Demand Instances are that Spot Instances might not launch immediately, the price for Spot Instances varies based on demand, and Amazon EC2 can terminate an individual Spot Instance as the availability of, or price for, Spot Instances changes\. When a Spot Instance is terminated, the Auto Scaling group attempts to launch a replacement instance to maintain the desired capacity for the group\.
Spot Instances provide you with access to unused Amazon EC2 capacity at steep discounts relative to On\-Demand prices\. For more information, see [Amazon EC2 Spot Instances](https://aws.amazon.com/ec2/spot/pricing/)\. The key differences between Spot Instances and On\-Demand Instances are that the price for Spot Instances varies based on demand, and Amazon EC2 can terminate an individual Spot Instance as the availability of, or price for, Spot Instances changes\. When a Spot Instance is terminated, the Auto Scaling group attempts to launch a replacement instance to maintain the desired capacity for the group\.

When instances are launched, if you specified multiple Availability Zones, the desired capacity is distributed across these Availability Zones\. If a scaling action occurs, Amazon EC2 Auto Scaling automatically maintains balance across all the Availability Zones that you specify\.
When instances are launched, if you specified multiple Availability Zones, the desired capacity is distributed across these Availability Zones\. If a scaling action occurs, Amazon EC2 Auto Scaling automatically maintains balance across all of the Availability Zones that you specify\.

This section provides detailed steps for creating an Auto Scaling group\. If you're new to Auto Scaling groups, start with [Getting Started with Amazon EC2 Auto Scaling](GettingStartedTutorial.md) to learn about the various building blocks that are used in Amazon EC2 Auto Scaling\.

Expand All @@ -23,7 +23,7 @@ This section provides detailed steps for creating an Auto Scaling group\. If you
+ [Creating an Auto Scaling Group Using an EC2 Instance](create-asg-from-instance.md)
+ [Creating an Auto Scaling Group Using the Amazon EC2 Launch Wizard](create-asg-ec2-wizard.md)
+ [Tagging Auto Scaling Groups and Instances](autoscaling-tagging.md)
+ [Using a Load Balancer With an Auto Scaling Group](autoscaling-load-balancer.md)
+ [Using a Load Balancer with an Auto Scaling Group](autoscaling-load-balancer.md)
+ [Launching Spot Instances in Your Auto Scaling Group](asg-launch-spot-instances.md)
+ [Merging Your Auto Scaling Groups into a Single Multi\-Zone Group](merge-auto-scaling-groups.md)
+ [Deleting Your Auto Scaling Infrastructure](as-process-shutdown.md)
2 changes: 1 addition & 1 deletion doc_source/CHAP_Troubleshooting.md
View file
Expand Up @@ -47,7 +47,7 @@ The following tables list the types of error messages and provide links to the t
| --- | --- |
| Auto Scaling group | [AutoScalingGroup <Auto Scaling group name> not found\.](ts-as-instancelaunchfailure.md#ts-as-instancelaunchfailure-4) |
| Availability Zone | [The requested Availability Zone is no longer supported\. Please retry your request\.\.\.](ts-as-instancelaunchfailure.md#ts-as-instancelaunchfailure-5) |
| AWS account | [You are not subscribed to this service\. Please see http://aws\.amazon\.com\.](ts-as-instancelaunchfailure.md#ts-as-instancelaunchfailure-7) |
| AWS account | [You are not subscribed to this service\. Please see https://aws\.amazon\.com/\.](ts-as-instancelaunchfailure.md#ts-as-instancelaunchfailure-7) |
| Block device mapping | [Invalid device name upload\. Launching EC2 instance failed\.](ts-as-instancelaunchfailure.md#ts-as-instancelaunchfailure-8) |
| Block device mapping | [Value \(<name associated with the instance storage device>\) for parameter virtualName is invalid\.\.\.](ts-as-instancelaunchfailure.md#ts-as-instancelaunchfailure-9) |
| Block device mapping | [EBS block device mappings not supported for instance\-store AMIs\.](ts-as-instancelaunchfailure.md#ts-as-instancelaunchfailure-10) |
Expand Down
4 changes: 2 additions & 2 deletions doc_source/Cooldown.md
View file
Expand Up @@ -26,7 +26,7 @@ To help ensure that the Auto Scaling group for the application tier has the appr

![\[An example of how a CloudWatch alarm works with a scaling policy\]](http://docs.aws.amazon.com/autoscaling/ec2/userguide/images/cooldowns-example-scaling-policy-diagram.png)

These instances use a configuration script to install and configure software before the instance is put into service\. As a result, it takes around two or three minutes from the time the instance launches until it comes into service\. The actual time depends on several factors, such as the size of the instance and whether there are startup scripts to complete\.
These instances use a configuration script to install and configure software before the instance is put into service\. As a result, it takes around two or three minutes from the time the instance launches until it's fully in service\. The actual time depends on several factors, such as the size of the instance and whether there are startup scripts to complete\.

Now a spike in traffic occurs, causing the CloudWatch alarm to fire\. When it does, the Auto Scaling group launches an instance to help with the increase in demand\. However, there's a problem: the instance takes a couple of minutes to launch\. During that time, the CloudWatch alarm could continue to fire, causing the Auto Scaling group to launch another instance each time the alarm fires\.

Expand Down Expand Up @@ -64,4 +64,4 @@ Lifecycle hooks can affect the impact of any cooldown periods configured for the

## Cooldowns and Spot Instances<a name="cooldowns-spot"></a>

You can create Auto Scaling groups to use [Spot Instances](asg-launch-spot-instances.md) instead of On\-Demand or Reserved Instances\. The cooldown period begins when the bid for any Spot Instance is successful\.
You can create Auto Scaling groups to use [Spot Instances](asg-launch-spot-instances.md) instead of On\-Demand or Reserved Instances\. The cooldown period begins when the bid for any Spot Instance is successful\.
4 changes: 3 additions & 1 deletion doc_source/DocumentHistory.md
View file
Expand Up @@ -4,8 +4,10 @@ The following table describes important additions to the Amazon EC2 Auto Scaling

| Change | Description | Date |
| --- |--- |--- |
| [Guide changes](#DocumentHistory) | Improved Amazon EC2 Auto Scaling documentation in the [Suspending and Resuming Scaling Processes](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html) topic\. Updated [Customer Managed Policy Examples](https://docs.aws.amazon.com/autoscaling/ec2/userguide/control-access-using-iam.html#example-policies-auto-scaling) to include an example policy that allows users to pass only specific custom service\-linked roles to Amazon EC2 Auto Scaling\. | June 13, 2019 |
| [Support for new Amazon EBS feature](#DocumentHistory) | Added support for new Amazon EBS feature in the launch template topic\. Change the encryption state of an EBS volume while restoring from a snapshot\. For more information, see [Creating a Launch Template for an Auto Scaling Group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html) in the *Amazon EC2 Auto Scaling User Guide*\. | May 13, 2019 |
| [Guide changes](#DocumentHistory) | Improved Amazon EC2 Auto Scaling documentation in the following sections: [Controlling Which Auto Scaling Instances Terminate During Scale In](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html), [Auto Scaling Groups](https://docs.aws.amazon.com/autoscaling/ec2/userguide/AutoScalingGroup.html), [Auto Scaling Groups with Multiple Instance Types and Purchase Options](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-purchase-options.html), and [Dynamic Scaling for Amazon EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scale-based-on-demand.html)\. | March 12, 2019 |
| [Support for combining instance types and purchase options](#DocumentHistory) | Provision and automatically scale instances across purchase options \(Spot, On\-Demand, and Reserved Instances\) and instance types within a single Auto Scaling group\. For more information, see [Using Multiple Instance Types and Purchase Options](https://docs.aws.amazon.com/autoscaling/ec2/userguide/AutoScalingGroup.html#asg-purchase-options) in the *Amazon EC2 Auto Scaling User Guide*\. | November 13, 2018 |
| [Support for combining instance types and purchase options](#DocumentHistory) | Provision and automatically scale instances across purchase options \(Spot, On\-Demand, and Reserved Instances\) and instance types within a single Auto Scaling group\. For more information, see [Auto Scaling Groups with Multiple Instance Types and Purchase Options](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-purchase-options.html) in the *Amazon EC2 Auto Scaling User Guide*\. | November 13, 2018 |
| [Updated topic for scaling based on Amazon SQS](#DocumentHistory) | Updated guide to explain how you can use custom metrics to scale an Auto Scaling group in response to changing demand from an Amazon SQS queue\. For more information, see [Scaling Based on Amazon SQS](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-using-sqs-queue.html) in the *Amazon EC2 Auto Scaling User Guide*\. | July 26, 2018 |

The following table describes important changes to the Amazon EC2 Auto Scaling documentation before July 2018\.
Expand Down

0 comments on commit 3a8910c

Please sign in to comment.