AWS codedeploy documentation change
Summary
Updated documentation to consistently use 'Amazon EC2 Auto Scaling' instead of 'Auto Scaling' throughout the troubleshooting guide. Changes include service name standardization in error messages, CLI commands, and procedural steps.
Security assessment
The changes are purely branding/naming consistency updates (adding 'Amazon EC2' to 'Auto Scaling' references). No security vulnerabilities, permissions changes, or security features are introduced or modified. The updates focus on terminology alignment rather than addressing security concerns.
Diff
diff --git a/codedeploy/latest/userguide/troubleshooting-auto-scaling.md b/codedeploy/latest/userguide/troubleshooting-auto-scaling.md index f4d9c85aa..5a87f9022 100644 --- a//codedeploy/latest/userguide/troubleshooting-auto-scaling.md +++ b//codedeploy/latest/userguide/troubleshooting-auto-scaling.md @@ -55 +55 @@ Disassociate the Amazon EC2 Auto Scaling group from the CodeDeploy deployment gr -Deployments that use an Auto Scaling group created with a launch template require the following permissions. These are in addition to the permissions granted by the `AWSCodeDeployRole` AWS managed policy. +Deployments that use an Amazon EC2 Auto Scaling group created with a launch template require the following permissions. These are in addition to the permissions granted by the `AWSCodeDeployRole` AWS managed policy. @@ -66 +66 @@ Deployments that use an Auto Scaling group created with a launch template requir -You might received this error if you are missing these permissions. For more information, see [Tutorial: Use CodeDeploy to deploy an application to an Auto Scaling group](./tutorials-auto-scaling-group.html), [Creating a launch template for an Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html), and [Permissions](https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-templates.html#launch-templates-permissions) in the _Amazon EC2 Auto Scaling User Guide_. +You might received this error if you are missing these permissions. For more information, see [Tutorial: Use CodeDeploy to deploy an application to an Amazon EC2 Auto Scaling group](./tutorials-auto-scaling-group.html), [Creating a launch template for an Amazon EC2 Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html), and [Permissions](https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-templates.html#launch-templates-permissions) in the _Amazon EC2 Auto Scaling User Guide_. @@ -132 +132 @@ Finally, if deployment to any instance fails, Amazon EC2 Auto Scaling immediatel -For more information about Amazon EC2 Auto Scaling, see [Under the hood: CodeDeploy and Auto Scaling integration](https://aws.amazon.com/blogs/devops/under-the-hood-aws-codedeploy-and-auto-scaling-integration/). +For more information about Amazon EC2 Auto Scaling, see [Under the hood: CodeDeploy and Amazon EC2 Auto Scaling integration](https://aws.amazon.com/blogs/devops/under-the-hood-aws-codedeploy-and-auto-scaling-integration/). @@ -144 +144 @@ This message usually indicates one of the following: - * The Auto Scaling group tried to launch too many EC2 instances too quickly. The API calls to [RecordLifecycleActionHeartbeat](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_RecordLifecycleActionHeartbeat.html) or [CompleteLifecycleAction](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_CompleteLifecycleAction.html) for each new instance were throttled. + * The Amazon EC2 Auto Scaling group tried to launch too many EC2 instances too quickly. The API calls to [RecordLifecycleActionHeartbeat](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_RecordLifecycleActionHeartbeat.html) or [CompleteLifecycleAction](https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_CompleteLifecycleAction.html) for each new instance were throttled. @@ -159 +159 @@ If you receive a “Heartbeat Timeout” error message, you can determine if lef - * Call the [delete-deployment-group](https://docs.aws.amazon.com/cli/latest/reference/deploy/delete-deployment-group.html) command to delete the deployment group associated with the Auto Scaling group that is causing the heartbeat timeout. + * Call the [delete-deployment-group](https://docs.aws.amazon.com/cli/latest/reference/deploy/delete-deployment-group.html) command to delete the deployment group associated with the Amazon EC2 Auto Scaling group that is causing the heartbeat timeout. @@ -161 +161 @@ If you receive a “Heartbeat Timeout” error message, you can determine if lef - * Call the [update-deployment-group](https://docs.aws.amazon.com/cli/latest/reference/deploy/update-deployment-group.html) command with a non-null empty list of Auto Scaling group names to detach all CodeDeploy-managed Auto Scaling lifecycle hooks. + * Call the [update-deployment-group](https://docs.aws.amazon.com/cli/latest/reference/deploy/update-deployment-group.html) command with a non-null empty list of Amazon EC2 Auto Scaling group names to detach all CodeDeploy-managed Amazon EC2 Auto Scaling lifecycle hooks. @@ -175 +175 @@ Examine the output of the call. If the output contains a `hooksNotCleanedUp` str - * Amazon EC2 Auto Scaling lifecycle hook names that contain the name of the deployment group associated with the Auto Scaling group that's failing. + * Amazon EC2 Auto Scaling lifecycle hook names that contain the name of the deployment group associated with the Amazon EC2 Auto Scaling group that's failing. @@ -185 +185 @@ Only delete hooks that are causing problems, as outlined in step 2. If you delet - 4. Call either the [update-deployment-group](https://docs.aws.amazon.com/cli/latest/reference/deploy/update-deployment-group.html) or [create-deployment-group](https://docs.aws.amazon.com/cli/latest/reference/deploy/create-deployment-group.html) command with the desired Auto Scaling group names. CodeDeploy re-installs the Auto Scaling hooks with new UUIDs. + 4. Call either the [update-deployment-group](https://docs.aws.amazon.com/cli/latest/reference/deploy/update-deployment-group.html) or [create-deployment-group](https://docs.aws.amazon.com/cli/latest/reference/deploy/create-deployment-group.html) command with the desired Amazon EC2 Auto Scaling group names. CodeDeploy re-installs the Amazon EC2 Auto Scaling hooks with new UUIDs. @@ -192 +192 @@ Only delete hooks that are causing problems, as outlined in step 2. If you delet -If you detach an Auto Scaling group from a CodeDeploy deployment group, any in-progress deployments to the Auto Scaling group may fail, and new EC2 instances that are scaled out by the Auto Scaling group will not receive your application revisions from CodeDeploy. To get Auto Scaling working again with CodeDeploy, you'll need to re-attach the Auto Scaling group to the deployment group and call a new `CreateDeployment` to start a fleet-wide deployment. +If you detach an Amazon EC2 Auto Scaling group from a CodeDeploy deployment group, any in-progress deployments to the Amazon EC2 Auto Scaling group may fail, and new EC2 instances that are scaled out by the Amazon EC2 Auto Scaling group will not receive your application revisions from CodeDeploy. To get Amazon EC2 Auto Scaling working again with CodeDeploy, you'll need to re-attach the Amazon EC2 Auto Scaling group to the deployment group and call a new `CreateDeployment` to start a fleet-wide deployment. @@ -234 +234 @@ Read this section if you see the following CodeDeploy error: -`The deployment failed because no instances were found for your deployment group. Check your deployment group settings to make sure the tags for your EC2 instances or Auto Scaling groups correctly identify the instances you want to deploy to, and then try again.` +`The deployment failed because no instances were found for your deployment group. Check your deployment group settings to make sure the tags for your EC2 instances or Amazon EC2 Auto Scaling groups correctly identify the instances you want to deploy to, and then try again.` @@ -238 +238 @@ Possible causes for this error are: - 1. Your deployment group settings include tags for EC2 instances, on-premises instances, or Auto Scaling groups that are not correct. To fix this problem, check that your tags are correct, and then redeploy your application. + 1. Your deployment group settings include tags for EC2 instances, on-premises instances, or Amazon EC2 Auto Scaling groups that are not correct. To fix this problem, check that your tags are correct, and then redeploy your application. @@ -242 +242 @@ Possible causes for this error are: - 3. Your Auto Scaling group does not include any instances that are in the `InService` state. In this scenario, when you try to do a fleet-wide deployment, the deployment fails with the error message above because CodeDeploy needs at least one instance to be in the `InService` state. There are many reasons why you might have no instances in the `InService` state. A few of them include: + 3. Your Amazon EC2 Auto Scaling group does not include any instances that are in the `InService` state. In this scenario, when you try to do a fleet-wide deployment, the deployment fails with the error message above because CodeDeploy needs at least one instance to be in the `InService` state. There are many reasons why you might have no instances in the `InService` state. A few of them include: @@ -244 +244 @@ Possible causes for this error are: - * You scheduled (or manually configured) the Auto Scaling group size to be `0`. + * You scheduled (or manually configured) the Amazon EC2 Auto Scaling group size to be `0`. @@ -246 +246 @@ Possible causes for this error are: - * Auto Scaling detected bad EC2 instances (for example, the EC2 instances had hardware failures), so canceled them all, leaving none in the `InService` state. + * Amazon EC2 Auto Scaling detected bad EC2 instances (for example, the EC2 instances had hardware failures), so canceled them all, leaving none in the `InService` state. @@ -248 +248 @@ Possible causes for this error are: - * During a scale out event from `0` to `1`, CodeDeploy deployed a previously successful revision (called a _last successful revision_) that had become unhealthy since the last deployment. This caused the deployment on the scaled-out instance to fail, which in turn caused Auto Scaling to cancel the instance, leaving no instances in the `InService` state. + * During a scale out event from `0` to `1`, CodeDeploy deployed a previously successful revision (called a _last successful revision_) that had become unhealthy since the last deployment. This caused the deployment on the scaled-out instance to fail, which in turn caused Amazon EC2 Auto Scaling to cancel the instance, leaving no instances in the `InService` state. @@ -259 +259 @@ To troubleshoot the error if there are no instances in the InService state - 1. In the Amazon EC2 console, verify the **Desired Capacity** setting. If it is zero, set it to a positive number. Wait for the instance to be `InService`, which means the deployment succeeded. You have fixed the problem and can skip the remaining steps of this troubleshooting procedure. For information on setting the **Desired Capacity** setting, see [Setting capacity limits on your Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-capacity-limits.html) in the _Amazon EC2 Auto Scaling User Guide_. + 1. In the Amazon EC2 console, verify the **Desired Capacity** setting. If it is zero, set it to a positive number. Wait for the instance to be `InService`, which means the deployment succeeded. You have fixed the problem and can skip the remaining steps of this troubleshooting procedure. For information on setting the **Desired Capacity** setting, see [Setting capacity limits on your Amazon EC2 Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-capacity-limits.html) in the _Amazon EC2 Auto Scaling User Guide_. @@ -261 +261 @@ To troubleshoot the error if there are no instances in the InService state - 2. If Auto Scaling keeps attempting to launch new EC2 instances to meet the desired capacity but can never fulfill the scale out, it is usually due to a failing Auto Scaling lifecycle hook. Troubleshoot this problem as follows: + 2. If Amazon EC2 Auto Scaling keeps attempting to launch new EC2 instances to meet the desired capacity but can never fulfill the scale out, it is usually due to a failing Amazon EC2 Auto Scaling lifecycle hook. Troubleshoot this problem as follows: @@ -263 +263 @@ To troubleshoot the error if there are no instances in the InService state - 1. To check which Auto Scaling lifecycle hook event is failing, see [Verifying a scaling activity for an Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-verify-scaling-activity.html) in the Amazon EC2 Auto Scaling User Guide. + 1. To check which Amazon EC2 Auto Scaling lifecycle hook event is failing, see [Verifying a scaling activity for an Amazon EC2 Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-verify-scaling-activity.html) in the Amazon EC2 Auto Scaling User Guide. @@ -265 +265 @@ To troubleshoot the error if there are no instances in the InService state - 2. If the failing hook's name is `CodeDeploy-managed-automatic-launch-deployment-hook-`DEPLOYMENT_GROUP_NAME``, go to CodeDeploy, find the deployment group, and find the failed deployment that was started by Auto Scaling. Then investigate why the deployment failed. + 2. If the failing hook's name is `CodeDeploy-managed-automatic-launch-deployment-hook-`DEPLOYMENT_GROUP_NAME``, go to CodeDeploy, find the deployment group, and find the failed deployment that was started by Amazon EC2 Auto Scaling. Then investigate why the deployment failed. @@ -269 +269 @@ To troubleshoot the error if there are no instances in the InService state - 4. If, after investigation, you determine that CodeDeploy’s _last successful revision_ is no longer healthy, and there are zero healthy instances in your Auto Scaling group, you are in a deployment deadlock scenario. To solve this issue, you must fix the bad CodeDeploy revision by temporarily removing CodeDeploy’s lifecycle hook from the Auto Scaling group, and then reinstalling the hook and redeploying a new (good) revision. For instructions, see: + 4. If, after investigation, you determine that CodeDeploy’s _last successful revision_ is no longer healthy, and there are zero healthy instances in your Amazon EC2 Auto Scaling group, you are in a deployment deadlock scenario. To solve this issue, you must fix the bad CodeDeploy revision by temporarily removing CodeDeploy’s lifecycle hook from the Amazon EC2 Auto Scaling group, and then reinstalling the hook and redeploying a new (good) revision. For instructions, see: @@ -284 +284 @@ To fix the deployment deadlock issue (CLI) - 2. Take note of your current Auto Scaling **DesiredCapacity** setting: + 2. Take note of your current Amazon EC2 Auto Scaling **DesiredCapacity** setting: @@ -290 +290 @@ You may need to scale back to this number at the end of this procedure. - 3. Set your Auto Scaling **DesiredCapacity** setting to `1`. This is optional if your desired capacity was greater than `1` to begin with. By decreasing it to `1`, the instance will take less time to provision and deploy later, which speeds up troubleshooting. If your Auto Scaling desired capacity was originally set to `0`, you must increase it to `1`. This is mandatory. + 3. Set your Amazon EC2 Auto Scaling **DesiredCapacity** setting to `1`. This is optional if your desired capacity was greater than `1` to begin with. By decreasing it to `1`, the instance will take less time to provision and deploy later, which speeds up troubleshooting. If your Amazon EC2 Auto Scaling desired capacity was originally set to `0`, you must increase it to `1`. This is mandatory. @@ -298 +298 @@ The remaining steps of this procedure assume you have set your **DesiredCapacity -At this point, Auto Scaling attempts to scale to one instance. Then, because the hook that CodeDeploy added is still present, CodeDeploy tries to deploy; the deployment fails; Auto Scaling cancels the instance; and Auto Scaling tries to re-launch an instance to reach desired capacity of one, which again fails. You are in a cancel-relaunch loop. +At this point, Amazon EC2 Auto Scaling attempts to scale to one instance. Then, because the hook that CodeDeploy added is still present, CodeDeploy tries to deploy; the deployment fails; Amazon EC2 Auto Scaling cancels the instance; and Amazon EC2 Auto Scaling tries to re-launch an instance to reach desired capacity of one, which again fails. You are in a cancel-relaunch loop. @@ -300 +300 @@ At this point, Auto Scaling attempts to scale to one instance. Then, because the - 4. De-register the Auto Scaling group from the deployment group: + 4. De-register the Amazon EC2 Auto Scaling group from the deployment group: @@ -304 +304 @@ At this point, Auto Scaling attempts to scale to one instance. Then, because the -The following command will launch a new EC2 instance with no software on it. Before running the command, make sure that an Auto Scaling `InService` instance running no software is acceptable. For example, make sure the load balancer associated with the instance is not sending traffic to this host without software. +The following command will launch a new EC2 instance with no software on it. Before running the command, make sure that an Amazon EC2 Auto Scaling `InService` instance running no software is acceptable. For example, make sure the load balancer associated with the instance is not sending traffic to this host without software. @@ -308 +308 @@ The following command will launch a new EC2 instance with no software on it. Bef -Use the CodeDeploy command shown below to remove the hook. Do not remove the hook through the Auto Scaling service, because the removal will not be recognized by CodeDeploy. +Use the CodeDeploy command shown below to remove the hook. Do not remove the hook through the Amazon EC2 Auto Scaling service, because the removal will not be recognized by CodeDeploy. @@ -314 +314 @@ After running this command, the following occurs: - 1. CodeDeploy de-registers the Auto Scaling group from the deployment group. + 1. CodeDeploy de-registers the Amazon EC2 Auto Scaling group from the deployment group. @@ -316 +316 @@ After running this command, the following occurs: - 2. CodeDeploy removes the Auto Scaling lifecycle hook from the Auto Scaling group. + 2. CodeDeploy removes the Amazon EC2 Auto Scaling lifecycle hook from the Amazon EC2 Auto Scaling group. @@ -318 +318 @@ After running this command, the following occurs: - 3. Since the hook that was causing a failed deployment is no longer present, Auto Scaling cancels the existing EC2 instance and immediately launches a new one to scale to the desired capacity. The new instance should soon move into `InService` state. The new instance does not include software. + 3. Since the hook that was causing a failed deployment is no longer present, Amazon EC2 Auto Scaling cancels the existing EC2 instance and immediately launches a new one to scale to the desired capacity. The new instance should soon move into `InService` state. The new instance does not include software. @@ -334 +334 @@ After running this command, the following occurs: - 1. CodeDeploy re-installs the Auto Scaling lifecycle hook to the EC2 instance + 1. CodeDeploy re-installs the Amazon EC2 Auto Scaling lifecycle hook to the EC2 instance @@ -336 +336 @@ After running this command, the following occurs: - 2. CodeDeploy reregisters the Auto Scaling group with the deployment group. + 2. CodeDeploy reregisters the Amazon EC2 Auto Scaling group with the deployment group. @@ -344 +344 @@ For example, if the revision is a .zip file in an Amazon S3 bucket called `my-re -Since there is now one `InService` instance in the Auto Scaling group, this deployment should work, and you should no longer see the error _The deployment failed because no instances were found for your deployment group_. +Since there is now one `InService` instance in the Amazon EC2 Auto Scaling group, this deployment should work, and you should no longer see the error _The deployment failed because no instances were found for your deployment group_. @@ -346 +346 @@ Since there is now one `InService` instance in the Auto Scaling group, this depl - 8. After the deployment succeeds, scale your Auto Scaling group back out to the original capacity, if you previously scaled it in: + 8. After the deployment succeeds, scale your Amazon EC2 Auto Scaling group back out to the original capacity, if you previously scaled it in: @@ -359 +359 @@ To fix the deployment deadlock issue (console) - 2. Go to the Amazon EC2 console, and take note of your Auto Scaling **Desired capacity** setting. You may need to scale back to this number at the end of this procedure. For information on finding this setting, see [Setting capacity limits on your Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-capacity-limits.html). + 2. Go to the Amazon EC2 console, and take note of your Amazon EC2 Auto Scaling **Desired capacity** setting. You may need to scale back to this number at the end of this procedure. For information on finding this setting, see [Setting capacity limits on your Amazon EC2 Auto Scaling group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-capacity-limits.html). @@ -363 +363 @@ To fix the deployment deadlock issue (console) -This is optional if your desired capacity was greater than `1` to begin with. By decreasing it to `1`, the instance will take less time to provision and deploy later, which speeds up troubleshooting. If your Auto Scaling **Desired capacity** was originally set to `0`, you must increase it to `1`. This is mandatory. +This is optional if your desired capacity was greater than `1` to begin with. By decreasing it to `1`, the instance will take less time to provision and deploy later, which speeds up troubleshooting. If your Amazon EC2 Auto Scaling **Desired capacity** was originally set to `0`, you must increase it to `1`. This is mandatory. @@ -369 +369 @@ The remaining steps of this procedure assume you have set your **Desired capacit - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/), and choose **Auto Scaling Groups** from the navigation pane. + 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/), and choose **Amazon EC2 Auto Scaling Groups** from the navigation pane. @@ -373 +373 @@ The remaining steps of this procedure assume you have set your **Desired capacit - 3. Go to the problematic Auto Scaling group. + 3. Go to the problematic Amazon EC2 Auto Scaling group. @@ -381 +381 @@ The remaining steps of this procedure assume you have set your **Desired capacit - 4. De-register the Auto Scaling group from the deployment group: + 4. De-register the Amazon EC2 Auto Scaling group from the deployment group: @@ -385 +385 @@ The remaining steps of this procedure assume you have set your **Desired capacit -The following sub-steps will launch a new EC2 instance with no software on it. Before running the command, make sure that an Auto Scaling `InService` instance running no software is acceptable. For example, make sure the load balancer associated with the instance is not sending traffic to this host without software. +The following sub-steps will launch a new EC2 instance with no software on it. Before running the command, make sure that an Amazon EC2 Auto Scaling `InService` instance running no software is acceptable. For example, make sure the load balancer associated with the instance is not sending traffic to this host without software. @@ -409 +409 @@ After completing these sub-steps, the following occurs: - 1. CodeDeploy de-registers the Auto Scaling group from the deployment group. + 1. CodeDeploy de-registers the Amazon EC2 Auto Scaling group from the deployment group. @@ -411 +411 @@ After completing these sub-steps, the following occurs: - 2. CodeDeploy removes the Auto Scaling lifecycle hook from the Auto Scaling group. + 2. CodeDeploy removes the Amazon EC2 Auto Scaling lifecycle hook from the Amazon EC2 Auto Scaling group. @@ -413 +413 @@ After completing these sub-steps, the following occurs: - 3. Since the hook that was causing a failed deployment is no longer present, Auto Scaling cancels the existing EC2 instance and immediately launches a new one to scale to the desired capacity. The new instance should soon move into `InService` state. The new instance does not include software. + 3. Since the hook that was causing a failed deployment is no longer present, Amazon EC2 Auto Scaling cancels the existing EC2 instance and immediately launches a new one to scale to the desired capacity. The new instance should soon move into `InService` state. The new instance does not include software. @@ -419 +419 @@ After completing these sub-steps, the following occurs: - 2. In the navigation pane, choose **Auto Scaling Groups**. + 2. In the navigation pane, choose **Amazon EC2 Auto Scaling Groups**. @@ -421 +421 @@ After completing these sub-steps, the following occurs: - 3. Choose your Auto Scaling group. + 3. Choose your Amazon EC2 Auto Scaling group. @@ -427 +427 @@ After completing these sub-steps, the following occurs: - 6. Re-register the Auto Scaling group with the CodeDeploy deployment group using the same method you used to remove it: + 6. Re-register the Amazon EC2 Auto Scaling group with the CodeDeploy deployment group using the same method you used to remove it: @@ -441 +441 @@ After completing these sub-steps, the following occurs: - 7. In **Environment configuration** , select **Amazon EC2 Auto Scaling groups** and select your Auto Scaling group from the list. + 7. In **Environment configuration** , select **Amazon EC2 Auto Scaling groups** and select your Amazon EC2 Auto Scaling group from the list. @@ -449 +449 @@ After completing these sub-steps, the following occurs: -This configuration re-installs the lifecycle hook into the Auto Scaling group. +This configuration re-installs the lifecycle hook into the Amazon EC2 Auto Scaling group. @@ -465 +465 @@ For example, if the revision is a .zip file in an Amazon S3 bucket called `my-re -Since there is now one `InService` instance in the Auto Scaling group, this deployment should work, and you should no longer see the error _The deployment failed because no instances were found for your deployment group_. +Since there is now one `InService` instance in the Amazon EC2 Auto Scaling group, this deployment should work, and you should no longer see the error _The deployment failed because no instances were found for your deployment group_. @@ -467 +467 @@ Since there is now one `InService` instance in the Auto Scaling group, this depl - 8. After the deployment succeeds, scale your Auto Scaling group back out to the original capacity, if you previously scaled it in: + 8. After the deployment succeeds, scale your Amazon EC2 Auto Scaling group back out to the original capacity, if you previously scaled it in: @@ -469 +469 @@ Since there is now one `InService` instance in the Auto Scaling group, this depl - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/), and choose **Auto Scaling Groups** from the navigation pane. + 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/), and choose **Amazon EC2 Auto Scaling Groups** from the navigation pane. @@ -473 +473 @@ Since there is now one `InService` instance in the Auto Scaling group, this depl - 3. Go to your Auto Scaling group. + 3. Go to your Amazon EC2 Auto Scaling group.