AWS emr documentation change
Summary
Fixed typo in NAT Gateway dependencies explanation
Security assessment
Minor grammatical correction with no security implications.
Diff
diff --git a/emr/latest/EMR-Serverless-UserGuide/jobs-spark-streaming-connectors.md b/emr/latest/EMR-Serverless-UserGuide/jobs-spark-streaming-connectors.md index d57eb97c0..995dd1127 100644 --- a//emr/latest/EMR-Serverless-UserGuide/jobs-spark-streaming-connectors.md +++ b//emr/latest/EMR-Serverless-UserGuide/jobs-spark-streaming-connectors.md @@ -85 +85 @@ To use Amazon Managed Streaming for Apache Kafka with IAM authentication, includ -To use the Kafka connector and the IAM authentication library from Amazon MSK configure the EMR Serverless application with VPC access. Your subnets must have Internet access and use a NAT Gateway to access the the Maven dependencies. For more information, refer to [Configuring VPC access](https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/vpc-access.html). The subnets must have network connectivity to access the Kafka cluster. This is true regardless of whether your Kafka cluster is self-managed or if you use Amazon Managed Streaming for Apache Kafka. +To use the Kafka connector and the IAM authentication library from Amazon MSK configure the EMR Serverless application with VPC access. Your subnets must have Internet access and use a NAT Gateway to access the Maven dependencies. For more information, refer to [Configuring VPC access](https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/vpc-access.html). The subnets must have network connectivity to access the Kafka cluster. This is true regardless of whether your Kafka cluster is self-managed or if you use Amazon Managed Streaming for Apache Kafka.