AWS mwaa documentation change
Summary
Updated wording from 'see' to 'refer to' in multiple documentation links for consistency
Security assessment
The changes are purely stylistic/editorial improvements to documentation phrasing without altering security configurations, access controls, or vulnerability guidance. No security-related content was added or modified beyond link reference wording.
Diff
diff --git a/mwaa/latest/userguide/mwaa-faqs.md b/mwaa/latest/userguide/mwaa-faqs.md index 6ef83dc3d..ede0a82ce 100644 --- a//mwaa/latest/userguide/mwaa-faqs.md +++ b//mwaa/latest/userguide/mwaa-faqs.md @@ -84 +84 @@ This page describes common questions you may encounter when using Amazon Managed -To learn what Amazon MWAA supports, see [Apache Airflow versions on Amazon Managed Workflows for Apache Airflow](./airflow-versions.html). +To learn what Amazon MWAA supports, refer to [Apache Airflow versions on Amazon Managed Workflows for Apache Airflow](./airflow-versions.html). @@ -136 +136 @@ Yes. With an Amazon SageMaker Unified Studio workflow, you can set up and run a -The task storage is limited to 20 GB, and is specified by [Amazon ECS Fargate 1.4](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-task-storage.html#fargate-task-storage-linux-pv). The amount of RAM is determined by the environment class you specify. For more information about environment classes, see [Configuring the Amazon MWAA environment class](./environment-class.html). +The task storage is limited to 20 GB, and is specified by [Amazon ECS Fargate 1.4](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-task-storage.html#fargate-task-storage-linux-pv). The amount of RAM is determined by the environment class you specify. For more information about environment classes, refer to [Configuring the Amazon MWAA environment class](./environment-class.html). @@ -158 +158 @@ To be able to use a custom domain for your Amazon MWAA hostname, do one of the f - * For Amazon MWAA deployments with public web server access, you can use Amazon CloudFront with Lambda@Edge to direct traffic to your environment, and map a custom domain name to CloudFront. For more information and an example of setting up a custom domain for a public environment, see the [Amazon MWAA custom domain for public web server](https://github.com/aws-samples/amazon-mwaa-examples/tree/main/usecases/mwaa-public-webserver-custom-domain) sample in the Amazon MWAA examples GitHub repository. + * For Amazon MWAA deployments with public web server access, you can use Amazon CloudFront with Lambda@Edge to direct traffic to your environment, and map a custom domain name to CloudFront. For more information and an example of setting up a custom domain for a public environment, refer to the [Amazon MWAA custom domain for public web server](https://github.com/aws-samples/amazon-mwaa-examples/tree/main/usecases/mwaa-public-webserver-custom-domain) sample in the Amazon MWAA examples GitHub repository. @@ -160 +160 @@ To be able to use a custom domain for your Amazon MWAA hostname, do one of the f - * For Amazon MWAA deployments with private web server access, see [Setting up a custom domain for the Apache Airflow web server](./configuring-custom-domain.html). + * For Amazon MWAA deployments with private web server access, refer to [Setting up a custom domain for the Apache Airflow web server](./configuring-custom-domain.html). @@ -186 +186 @@ To trigger the DAG in the Apache Airflow UI, use: -By creating a self-referencing rule, you're restricting the source to the same security group in the VPC, and it's not open to all networks. To learn more, see [Security in your VPC on Amazon MWAA](./vpc-security.html). +By creating a self-referencing rule, you're restricting the source to the same security group in the VPC, and it's not open to all networks. To learn more, refer to [Security in your VPC on Amazon MWAA](./vpc-security.html). @@ -202 +202 @@ Total task storage is limited to 20 GB, according to [Amazon ECS Fargate 1.4](ht -Yes. Although you can specify up to 25 Apache Airflow workers on the Amazon MWAA console, you can configure up to 50 on an environment by requesting a quota increase. For more information, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html). +Yes. Although you can specify up to 25 Apache Airflow workers on the Amazon MWAA console, you can configure up to 50 on an environment by requesting a quota increase. For more information, refer to [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html). @@ -206 +206 @@ Yes. Although you can specify up to 25 Apache Airflow workers on the Amazon MWAA -Amazon MWAA does not support shared Amazon VPCs or shared subnets. The Amazon VPC you select when you create an environment should be owned by the account that is attempting to create the environment. However, you can route traffic from an Amazon VPC in the Amazon MWAA account to a shared VPC. For more information, and to see an example of routing traffic to a shared Amazon VPC, see [Centralized outbound routing to the internet](https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-nat-igw.html) in the _Amazon VPC Transit Gateways Guide_. +Amazon MWAA does not support shared Amazon VPCs or shared subnets. The Amazon VPC you select when you create an environment should be owned by the account that is attempting to create the environment. However, you can route traffic from an Amazon VPC in the Amazon MWAA account to a shared VPC. For more information and an example of routing traffic to a shared Amazon VPC, refer to [Centralized outbound routing to the internet](https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-nat-igw.html) in the _Amazon VPC Transit Gateways Guide_. @@ -216 +216 @@ No, you cannot create, modify, or use custom Amazon SQS queues within Amazon MWA -Amazon MWAA monitors the **QueuedTasks** and **RunningTasks** in CloudWatch to determine whether to scale Apache Airflow _Workers_ on your environment. To learn more, see [Monitoring and metrics for Amazon Managed Workflows for Apache Airflow](./cw-metrics.html). +Amazon MWAA monitors the **QueuedTasks** and **RunningTasks** in CloudWatch to determine whether to scale Apache Airflow _Workers_ on your environment. To learn more, refer to [Monitoring and metrics for Amazon Managed Workflows for Apache Airflow](./cw-metrics.html). @@ -220 +220 @@ Amazon MWAA monitors the **QueuedTasks** and **RunningTasks** in CloudWatch to d -Not on the CloudWatch console. However, you can create a DAG that writes custom metrics in CloudWatch. For more information, see [Using a DAG to write custom metrics in CloudWatch](./samples-custom-metrics.html). +Not on the CloudWatch console. However, you can create a DAG that writes custom metrics in CloudWatch. For more information, refer to [Using a DAG to write custom metrics in CloudWatch](./samples-custom-metrics.html). @@ -226 +226 @@ Not on the CloudWatch console. However, you can create a DAG that writes custom -The `PythonVirtualenvOperator` is not explicitly supported on Amazon MWAA, but you can create a custom plugin that uses the `PythonVirtualenvOperator`. For sample code, see [Creating a custom plugin for Apache Airflow PythonVirtualenvOperator](./samples-virtualenv.html). +The `PythonVirtualenvOperator` is not explicitly supported on Amazon MWAA, but you can create a custom plugin that uses the `PythonVirtualenvOperator`. For sample code, refer to [Creating a custom plugin for Apache Airflow PythonVirtualenvOperator](./samples-virtualenv.html). @@ -238 +238 @@ The following are possible solutions for this issue: - 1. Check that your execution role has sufficient permissions to your Amazon S3 bucket. To learn more, see [Amazon MWAA execution role](./mwaa-create-role.html). + 1. Check that your execution role has sufficient permissions to your Amazon S3 bucket. To learn more, refer to [Amazon MWAA execution role](./mwaa-create-role.html). @@ -240 +240 @@ The following are possible solutions for this issue: - 2. Check that the Amazon S3 bucket has _Block Public Access_ configured, and _Versioning_ enabled. To learn more, see [Create an Amazon S3 bucket for Amazon MWAA](./mwaa-s3-bucket.html). + 2. Check that the Amazon S3 bucket has _Block Public Access_ configured, and _Versioning_ enabled. To learn more, refer to [Create an Amazon S3 bucket for Amazon MWAA](./mwaa-s3-bucket.html). @@ -249 +249 @@ The following are possible solutions for this issue: -Currently, there is no way to remove a plugins.zip or requirements.txt from an environment once they’ve been added, but we're working on the issue. In the interim, a workaround is to point to an empty text or zip file, respectively. To learn more, see [Deleting files on Amazon S3](./working-dags-delete.html). +Currently, there is no way to remove a plugins.zip or requirements.txt from an environment once they’ve been added, but we're working on the issue. In the interim, a workaround is to point to an empty text or zip file, respectively. To learn more, refer to [Deleting files on Amazon S3](./working-dags-delete.html).