AWS Security ChangesHomeSearch

AWS whitepapers documentation change

Service: whitepapers · 2025-11-22 · Documentation low

File: whitepapers/latest/building-a-data-perimeter-on-aws/building-a-data-perimeter-on-aws.md

Summary

Added working hyperlink to AWS Shared Responsibility Model

Security assessment

Change only fixes a broken URL reference without altering security content. No evidence of addressing vulnerabilities or security features.

Diff

diff --git a/whitepapers/latest/building-a-data-perimeter-on-aws/building-a-data-perimeter-on-aws.md b/whitepapers/latest/building-a-data-perimeter-on-aws/building-a-data-perimeter-on-aws.md
index 56dabb892..f15f27758 100644
--- a//whitepapers/latest/building-a-data-perimeter-on-aws/building-a-data-perimeter-on-aws.md
+++ b//whitepapers/latest/building-a-data-perimeter-on-aws/building-a-data-perimeter-on-aws.md
@@ -21 +21 @@ For more expert guidance and best practices for your cloud architecture—refere
-In traditional, on-premises data center environments, a trusted network and strong authentication are the foundation of security. They establish a high-level perimeter to help prevent untrusted entities from coming in and data from going out. This perimeter provides a clear boundary of trust and ownership. When customers think about creating an AWS perimeter as part of their responsibility for security “in the cloud” in the [AWS Shared Responsibility Model](), they want to achieve the same outcomes. They want to draw a circle around their AWS resources, like Amazon Simple Storage Service (Amazon S3) buckets and Amazon Simple Queue Service (Amazon SQS) queues, that clearly separates “my AWS” from other customers. 
+In traditional, on-premises data center environments, a trusted network and strong authentication are the foundation of security. They establish a high-level perimeter to help prevent untrusted entities from coming in and data from going out. This perimeter provides a clear boundary of trust and ownership. When customers think about creating an AWS perimeter as part of their responsibility for security “in the cloud” in the [AWS Shared Responsibility Model](https://aws.amazon.com/), they want to achieve the same outcomes. They want to draw a circle around their AWS resources, like Amazon Simple Storage Service (Amazon S3) buckets and Amazon Simple Queue Service (Amazon SQS) queues, that clearly separates “my AWS” from other customers.