AWS prescriptive-guidance documentation change
Summary
Removed 'Attachments' section and added GitHub repository link under 'Tools' section
Security assessment
Removing an attachment reference and adding a code repository improves documentation structure but doesn't address security issues or document new security features.
Diff
diff --git a/prescriptive-guidance/latest/patterns/iam-roles-anywhere-private-ca.md b/prescriptive-guidance/latest/patterns/iam-roles-anywhere-private-ca.md index 08f0f2d92..99466f34f 100644 --- a//prescriptive-guidance/latest/patterns/iam-roles-anywhere-private-ca.md +++ b//prescriptive-guidance/latest/patterns/iam-roles-anywhere-private-ca.md @@ -7 +7 @@ -SummaryPrerequisites and limitationsArchitectureToolsBest practicesEpicsTroubleshootingRelated resourcesAdditional informationAttachments +SummaryPrerequisites and limitationsArchitectureToolsBest practicesEpicsTroubleshootingRelated resourcesAdditional information @@ -149,2 +148,0 @@ This pattern includes complete automation through: -**Tools** - @@ -160,0 +159,4 @@ This pattern includes complete automation through: + _Code repository_ + +[ AWS IAM Roles Anywhere with Private Certificate Authority](https://github.com/aws-samples/sample-aws-iam-roles-anywhere-automation) + @@ -241,4 +242,0 @@ This pattern is ideal for organizations with hybrid cloud architectures, CI/CD p -## Attachments - -To access additional content that is associated with this document, unzip the following file: [attachment.zip](samples/p-attach/2600dc9f-9c1a-442e-9523-1c925aff7620/attachments/attachment.zip) -