AWS mwaa documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for consistency in terminology
Security assessment
Changes are purely branding/terminology updates (removing redundant 'AWS' prefix from CloudFormation references). No security-related content was added or modified. Bastion host setup remains unchanged in security context.
Diff
diff --git a/mwaa/latest/userguide/tutorials-private-network-bastion.md b/mwaa/latest/userguide/tutorials-private-network-bastion.md index 013a2edc4..712cc16bf 100644 --- a//mwaa/latest/userguide/tutorials-private-network-bastion.md +++ b//mwaa/latest/userguide/tutorials-private-network-bastion.md @@ -71 +71 @@ In this tutorial, you'll do the following: - 1. Create a Linux Bastion Host instance using a [AWS CloudFormation template for an existing VPC](https://fwd.aws/vWMxm). + 1. Create a Linux Bastion Host instance using a [CloudFormation template for an existing VPC](https://fwd.aws/vWMxm). @@ -86 +86 @@ In this tutorial, you'll do the following: -The following section describes the steps to create the linux bastion instance using a [AWS CloudFormation template for an existing VPC](https://fwd.aws/vWMxm) on the AWS CloudFormation console. +The following section describes the steps to create the linux bastion instance using a [CloudFormation template for an existing VPC](https://fwd.aws/vWMxm) on the CloudFormation console. @@ -90 +90 @@ The following section describes the steps to create the linux bastion instance u - 1. Open the [Deploy Quick Start](https://fwd.aws/Jwzqv) page on the AWS CloudFormation console. + 1. Open the [Deploy Quick Start](https://fwd.aws/Jwzqv) page on the CloudFormation console. @@ -110 +110 @@ The following section describes the steps to create the linux bastion instance u -The simplest way to identify a range is to use the same CIDR range as your public subnets. For example, the public subnets in the AWS CloudFormation template on the [Create the VPC network](./vpc-create.html) page are `10.192.10.0/24` and `10.192.11.0/24`. +The simplest way to identify a range is to use the same CIDR range as your public subnets. For example, the public subnets in the CloudFormation template on the [Create the VPC network](./vpc-create.html) page are `10.192.10.0/24` and `10.192.11.0/24`.