AWS elasticbeanstalk documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in multiple troubleshooting sections
Security assessment
Terminology update with no impact on security guidance or vulnerability disclosures
Diff
diff --git a/elasticbeanstalk/latest/dg/troubleshooting.md b/elasticbeanstalk/latest/dg/troubleshooting.md index 233d79e00..76c9a39bd 100644 --- a//elasticbeanstalk/latest/dg/troubleshooting.md +++ b//elasticbeanstalk/latest/dg/troubleshooting.md @@ -59 +59 @@ You can use Systems Manager to troubleshoot your Elastic Beanstalk environments. -The document `AWSSupport-TroubleshootElasticBeanstalk` is an Automation runbook designed to help identify a number of common issues that can degrade your Elastic Beanstalk environment. To do so, it checks components of your environment, including the following: EC2 instances, the VPC, AWS CloudFormation stack, load balancers, Auto Scaling groups, and network configuration associated with security group rules, route tables, and ACLs. +The document `AWSSupport-TroubleshootElasticBeanstalk` is an Automation runbook designed to help identify a number of common issues that can degrade your Elastic Beanstalk environment. To do so, it checks components of your environment, including the following: EC2 instances, the VPC, CloudFormation stack, load balancers, Auto Scaling groups, and network configuration associated with security group rules, route tables, and ACLs. @@ -222 +222 @@ This message indicates that your Elastic Beanstalk environment may be a single i -The underlying AWS CloudFormation stack of your environment may be in a _*_FAILED_ status. This status must be remedied in order to continue Elastic Beanstalk operations on your environment. For more information, see [Recovering your Elastic Beanstalk environment from an invalid state](./environment-management-invalid-stack.html). +The underlying CloudFormation stack of your environment may be in a _*_FAILED_ status. This status must be remedied in order to continue Elastic Beanstalk operations on your environment. For more information, see [Recovering your Elastic Beanstalk environment from an invalid state](./environment-management-invalid-stack.html).