AWS prescriptive-guidance documentation change
Summary
Updated quotation marks in documentation links to AWS blog posts.
Security assessment
Formatting change only. The referenced content about AWS PrivateLink security practices was not altered, only the quotation style.
Diff
diff --git a/prescriptive-guidance/latest/patterns/migrate-data-from-an-on-premises-hadoop-environment-to-amazon-s3-using-distcp-with-aws-privatelink-for-amazon-s3.md b/prescriptive-guidance/latest/patterns/migrate-data-from-an-on-premises-hadoop-environment-to-amazon-s3-using-distcp-with-aws-privatelink-for-amazon-s3.md index 04a7a662f..31a9c3e19 100644 --- a//prescriptive-guidance/latest/patterns/migrate-data-from-an-on-premises-hadoop-environment-to-amazon-s3-using-distcp-with-aws-privatelink-for-amazon-s3.md +++ b//prescriptive-guidance/latest/patterns/migrate-data-from-an-on-premises-hadoop-environment-to-amazon-s3-using-distcp-with-aws-privatelink-for-amazon-s3.md @@ -9 +9 @@ SummaryPrerequisites and limitationsArchitectureToolsEpics - _Created by Jason Owens (AWS), Andres Cantor (AWS), Jeff Klopfenstein (AWS), Bruno Rocha Oliveira (AWS), and Samuel Schmidt (AWS)_ + _Jason Owens, Andres Cantor, Jeff Klopfenstein, Bruno Rocha Oliveira, and Samuel Schmidt, Amazon Web Services_ @@ -138,2 +138,2 @@ Configure the name resolution.| You must configure the name resolution to allow - * Use on-premises DNS to resolve the private IP address of the endpoint. You can override behavior for all buckets or selected buckets. For more information, see “Option 2: Access Amazon S3 using Domain Name System Response Policy Zones (DNS RPZ)” in [Secure hybrid access to Amazon S3 using AWS PrivateLink](https://aws.amazon.com/blogs/networking-and-content-delivery/secure-hybrid-access-to-amazon-s3-using-aws-privatelink/) (AWS blog post). - * Configure on-premises DNS to conditionally forward traffic to the resolver inbound endpoints in the VPC. Traffic is forwarded to Route 53. For more information, see “Option 3: Forwarding DNS requests from on premises using Amazon Route 53 Resolver Inbound Endpoints” in [Secure hybrid access to Amazon S3 using AWS PrivateLink](https://aws.amazon.com/blogs/networking-and-content-delivery/secure-hybrid-access-to-amazon-s3-using-aws-privatelink/) (AWS blog post). + * Use on-premises DNS to resolve the private IP address of the endpoint. You can override behavior for all buckets or selected buckets. For more information, see "Option 2: Access Amazon S3 using Domain Name System Response Policy Zones (DNS RPZ)" in [Secure hybrid access to Amazon S3 using AWS PrivateLink](https://aws.amazon.com/blogs/networking-and-content-delivery/secure-hybrid-access-to-amazon-s3-using-aws-privatelink/) (AWS blog post). + * Configure on-premises DNS to conditionally forward traffic to the resolver inbound endpoints in the VPC. Traffic is forwarded to Route 53. For more information, see "Option 3: Forwarding DNS requests from on premises using Amazon Route 53 Resolver Inbound Endpoints" in [Secure hybrid access to Amazon S3 using AWS PrivateLink](https://aws.amazon.com/blogs/networking-and-content-delivery/secure-hybrid-access-to-amazon-s3-using-aws-privatelink/) (AWS blog post).