AWS mwaa documentation change
Summary
Replaced 'see' with 'refer to' in multiple documentation links and clarified target group guidance
Security assessment
Textual improvements to documentation references without introducing new security concepts or addressing vulnerabilities. The target group availability recommendation is operational guidance, not security-specific.
Diff
diff --git a/mwaa/latest/userguide/vpc-vpe-access.md b/mwaa/latest/userguide/vpc-vpe-access.md index 0651514f7..7ad3d858c 100644 --- a//mwaa/latest/userguide/vpc-vpe-access.md +++ b//mwaa/latest/userguide/vpc-vpe-access.md @@ -75 +75 @@ If you chose the **Private network** access mode for your Apache Airflow _Web se -The interface endpoints use the execution role for your environment in AWS Identity and Access Management (IAM) to manage permission to AWS resources used by your environment. As more AWS services are enabled for an environment, each service will require you to configure permission using your environment's execution role. To add permissions, see [Amazon MWAA execution role](./mwaa-create-role.html). +The interface endpoints use the execution role for your environment in AWS Identity and Access Management (IAM) to manage permission to AWS resources used by your environment. As more AWS services are enabled for an environment, each service will require you to configure permission using your environment's execution role. To add permissions, refer to [Amazon MWAA execution role](./mwaa-create-role.html). @@ -77 +77 @@ The interface endpoints use the execution role for your environment in AWS Ident -If you've chosen the **Private network** access mode for your Apache Airflow _Web server_ , you must also allow permission in the VPC endpoint policy for each endpoint. To learn more, see [VPC endpoint policies (private routing only)](./vpc-security.html#vpc-external-vpce-policies). +If you've chosen the **Private network** access mode for your Apache Airflow _Web server_ , you must also allow permission in the VPC endpoint policy for each endpoint. To learn more, refer to [VPC endpoint policies (private routing only)](./vpc-security.html#vpc-external-vpce-policies). @@ -98 +98 @@ The following section shows the steps to view the VPC endpoint(s) created by Ama -To learn more about the VPC service endpoints that are required for an Amazon VPC with _private routing_ , see [Creating the required VPC service endpoints in an Amazon VPC with private routing](./vpc-vpe-create-access.html). +To learn more about the VPC service endpoints that are required for an Amazon VPC with _private routing_ , refer to [Creating the required VPC service endpoints in an Amazon VPC with private routing](./vpc-vpe-create-access.html). @@ -160 +160 @@ The following section shows the configurations you'll need to apply to an [Appli - 1. **Target groups**. You'll need to use target groups that point to the private IP addresses for your Apache Airflow _Web server_ , and its VPC interface endpoint. We recommend specifying both private IP addresses as your registered targets, as using only one can reduce availability. For more information on how to identify the private IP addresses, see Identifying the private IP addresses of your Apache Airflow Web server and its VPC endpoint. + 1. **Target groups**. You'll need to use target groups that point to the private IP addresses for your Apache Airflow _Web server_ , and its VPC interface endpoint. We recommend specifying both private IP addresses as your registered targets, as using only one can reduce availability. For more information on how to identify the private IP addresses, refer to Identifying the private IP addresses of your Apache Airflow Web server and its VPC endpoint.