AWS amazondynamodb: Fix Well-Architected documentation link
Summary
Corrected URL formatting in the link to AWS account separation best practices.
Security assessment
URL fix maintains existing security guidance without introducing new content.
Evidence
+If you want to separate production and test workloads to help control an event's potential "blast radius," the best practice is to create separate AWS accounts for test and production workloads. For more information, see [AWS Account Management and Separation](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/aws-account-management-and-separation.html).
Diff
diff --git a/amazondynamodb/latest/developerguide/iam-policy-separate-environments.md b/amazondynamodb/latest/developerguide/iam-policy-separate-environments.md index 36616f14a..6b611177e 100644 --- a//amazondynamodb/latest/developerguide/iam-policy-separate-environments.md +++ b//amazondynamodb/latest/developerguide/iam-policy-separate-environments.md @@ -15 +15 @@ As a result, each action in one environment reduces the number of operations ava -If you want to separate production and test workloads to help control an event's potential "blast radius," the best practice is to create separate AWS accounts for test and production workloads. For more information, see [AWS Account Management and Separation](https://docs.aws.amazon.com//wellarchitected/latest/security-pillar/aws-account-management-and-separation.html). +If you want to separate production and test workloads to help control an event's potential "blast radius," the best practice is to create separate AWS accounts for test and production workloads. For more information, see [AWS Account Management and Separation](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/aws-account-management-and-separation.html).