AWS prescriptive-guidance documentation change
Summary
Updated link text to 'AWS Resource Access Manager' for clarity in cross-account resource sharing documentation
Security assessment
Change only improves hyperlink clarity without introducing or modifying security controls. AWS RAM usage for cross-account access was already documented.
Diff
diff --git a/prescriptive-guidance/latest/privacy-reference-architecture/network-account.md b/prescriptive-guidance/latest/privacy-reference-architecture/network-account.md index c7918ad15..13f23d705 100644 --- a//prescriptive-guidance/latest/privacy-reference-architecture/network-account.md +++ b//prescriptive-guidance/latest/privacy-reference-architecture/network-account.md @@ -42 +42 @@ You can also configure CloudFront to generate access logs that contain detailed -In addition to sharing VPCs and transit gateway connections, AWS RAM can be used to share resources that don't support IAM resource-based policies. For a workload hosted in the [Personal Data OU](./personal-data-account.html), you can use AWS RAM to access personal data that is located in a separate AWS account. For more information, see [](./personal-data-account.html#aws-ram-pd-account) in the _Personal Data OU – PD Application account_ section. +In addition to sharing VPCs and transit gateway connections, AWS RAM can be used to share resources that don't support IAM resource-based policies. For a workload hosted in the [Personal Data OU](./personal-data-account.html), you can use AWS RAM to access personal data that is located in a separate AWS account. For more information, see [AWS Resource Access Manager](./personal-data-account.html#aws-ram-pd-account) in the _Personal Data OU – PD Application account_ section.