AWS mwaa documentation change
Summary
Updated documentation references from 'see' to 'refer to' in multiple troubleshooting sections
Security assessment
The changes are purely stylistic updates to reference wording without modifying security configurations or addressing vulnerabilities. The security-related content (e.g., VPC port 5432 configuration) remains unchanged.
Diff
diff --git a/mwaa/latest/userguide/t-apache-airflow-202.md b/mwaa/latest/userguide/t-apache-airflow-202.md index 96692121d..e4ffa2888 100644 --- a//mwaa/latest/userguide/t-apache-airflow-202.md +++ b//mwaa/latest/userguide/t-apache-airflow-202.md @@ -155 +155 @@ We recommend the following steps: - 1. Check Apache Airflow configuration options. Verify that the key-value pairs you specified as an Apache Airflow configuration option, such as AWS Secrets Manager, were configured correctly. To learn more, see [I can't connect to Secrets Manager](./t-apache-airflow-11012.html#access-secrets-manager). + 1. Check Apache Airflow configuration options. Verify that the key-value pairs you specified as an Apache Airflow configuration option, such as AWS Secrets Manager, were configured correctly. To learn more, refer to [I can't connect to Secrets Manager](./t-apache-airflow-11012.html#access-secrets-manager). @@ -170 +170 @@ We recommend the following steps: - 1. Confirm that your VPC security group allows inbound access to port `5432`. This port is needed to connect to the Amazon Aurora PostgreSQL metadata database for your environment. After this rule is added, give Amazon MWAA a few minutes, and the error should disappear. To learn more, see [Security in your VPC on Amazon MWAA](./vpc-security.html). + 1. Confirm that your VPC security group allows inbound access to port `5432`. This port is needed to connect to the Amazon Aurora PostgreSQL metadata database for your environment. After this rule is added, give Amazon MWAA a few minutes, and the error should disappear. To learn more, refer to [Security in your VPC on Amazon MWAA](./vpc-security.html). @@ -178 +178 @@ We recommend the following steps: - 2. If the scheduler is not running, it might be due to a number of factors such as [dependency installation failures](./best-practices-dependencies.html), or an [overloaded scheduler](./best-practices-tuning.html). Confirm that your DAGs, plugins, and requirements are working correctly by viewing the corresponding log groups in CloudWatch Logs. To learn more, see [Monitoring and metrics for Amazon Managed Workflows for Apache Airflow](./cw-metrics.html). + 2. If the scheduler is not running, it might be due to a number of factors such as [dependency installation failures](./best-practices-dependencies.html), or an [overloaded scheduler](./best-practices-tuning.html). Confirm that your DAGs, plugins, and requirements are working correctly by viewing the corresponding log groups in CloudWatch Logs. To learn more, refer to [Monitoring and metrics for Amazon Managed Workflows for Apache Airflow](./cw-metrics.html). @@ -195 +195 @@ If your Apache Airflow tasks are "stuck" or not completing, we recommend the fol - 2. To learn more about the best practices we recommend to tune the performance of your environment, see [Performance tuning for Apache Airflow on Amazon MWAA](./best-practices-tuning.html). + 2. To learn more about the best practices we recommend to tune the performance of your environment, refer to [Performance tuning for Apache Airflow on Amazon MWAA](./best-practices-tuning.html). @@ -209 +209 @@ If your Apache Airflow tasks are "stuck" or not completing, we recommend the fol - 5. To learn more about the best practices we recommend to tune the performance of your environment, see [Performance tuning for Apache Airflow on Amazon MWAA](./best-practices-tuning.html). + 5. To learn more about the best practices we recommend to tune the performance of your environment, refer to [Performance tuning for Apache Airflow on Amazon MWAA](./best-practices-tuning.html). @@ -259 +259 @@ The following topic describes the errors you may receive when using Operators. -We recommend the following steps if you're trying to run a shell script with the _S3Transform_ operator and you're receiving a `PermissionError: [Errno 13] Permission denied` error. The following steps assume you have an existing plugins.zip file. If you're creating a _new_ plugins.zip, see [Installing custom plugins](./configuring-dag-import-plugins.html). +We recommend the following steps if you're trying to run a shell script with the _S3Transform_ operator and you're receiving a `PermissionError: [Errno 13] Permission denied` error. The following steps assume you have an existing plugins.zip file. If you're creating a _new_ plugins.zip, refer to [Installing custom plugins](./configuring-dag-import-plugins.html).