AWS elasticbeanstalk documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in two security group modification instructions
Security assessment
Consistent terminology update across two instances. The BOM warning and HTTPS security configuration remain intact.
Diff
diff --git a/elasticbeanstalk/latest/dg/https-singleinstance-ruby.md b/elasticbeanstalk/latest/dg/https-singleinstance-ruby.md index fa76843e4..ebcc3ae84 100644 --- a//elasticbeanstalk/latest/dg/https-singleinstance-ruby.md +++ b//elasticbeanstalk/latest/dg/https-singleinstance-ruby.md @@ -129 +129 @@ Avoid committing a configuration file that contains your private key to source c -In a single instance environment, you must also modify the instance's security group to allow traffic on port 443. The following configuration file retrieves the security group's ID using an AWS CloudFormation [function](./ebextensions-functions.html) and adds a rule to it. +In a single instance environment, you must also modify the instance's security group to allow traffic on port 443. The following configuration file retrieves the security group's ID using an CloudFormation [function](./ebextensions-functions.html) and adds a rule to it. @@ -219 +219 @@ This JSON file must not contain a byte order mark (BOM). If it does, the Passeng -In a single instance environment, you must also modify the instance's security group to allow traffic on port 443. The following configuration file retrieves the security group's ID using an AWS CloudFormation [function](./ebextensions-functions.html) and adds a rule to it. +In a single instance environment, you must also modify the instance's security group to allow traffic on port 443. The following configuration file retrieves the security group's ID using an CloudFormation [function](./ebextensions-functions.html) and adds a rule to it.