AWS drs: Guidance to use S3 interface endpoint with private DNS for failback
Summary
Adds a note that if the server cannot reach public Amazon S3, users should use an Amazon S3 interface endpoint with private DNS so s3.{REGION}.amazonaws.com resolves to the endpoint, linking to the S3 Private DNS docs.
Security assessment
Documents using an AWS PrivateLink interface endpoint with private DNS to keep S3 traffic on private networking rather than the public internet, a recognized network-security best practice.
Evidence
+If the server cannot reach public Amazon S3, use an Amazon S3 interface endpoint with private DNS, so that `s3.{REGION}.amazonaws.com` resolves to the endpoint. See [Private DNS](https://docs.aws.amazon.com/AmazonS3/latest/userguide/privatelink-interface-endpoints.html#private-dns) in the Amazon S3 User Guide.
Diff
diff --git a/drs/latest/userguide/failback-performing.md b/drs/latest/userguide/failback-performing.md index 6d7bbd9..4fd8f07 100644 --- a//drs/latest/userguide/failback-performing.md +++ b//drs/latest/userguide/failback-performing.md @@ -45,0 +46,2 @@ Prior to performing a failback, ensure that you meet all [replication network re +If the server cannot reach public Amazon S3, use an Amazon S3 interface endpoint with private DNS, so that `s3.{REGION}.amazonaws.com` resolves to the endpoint. See [Private DNS](https://docs.aws.amazon.com/AmazonS3/latest/userguide/privatelink-interface-endpoints.html#private-dns) in the Amazon S3 User Guide. +