AWS prescriptive-guidance documentation change
Summary
Added 'Best practices' to section list, updated author information, and added new 'Best practices' overview section linking to security guidance.
Security assessment
Added navigation links to existing security content (foundational practices, guardrails, logging). While referencing security topics, this doesn't introduce new security information but improves discoverability of existing documentation.
Diff
diff --git a/prescriptive-guidance/latest/presigned-url-best-practices/introduction.md b/prescriptive-guidance/latest/presigned-url-best-practices/introduction.md index 791cfd979..dd933e577 100644 --- a//prescriptive-guidance/latest/presigned-url-best-practices/introduction.md +++ b//prescriptive-guidance/latest/presigned-url-best-practices/introduction.md @@ -7 +7 @@ -Intended audienceObjectivesPrerequisites +Best practicesIntended audienceObjectivesPrerequisites @@ -11,3 +11 @@ Intended audienceObjectivesPrerequisites - _Ryan Baker, Amazon Web Services (AWS)_ - -_August 2025_ ([document history](./doc-history.html)) + _Antonio Aga Rossi, Amazon Web Services_ @@ -33,0 +32,13 @@ In this guide, you will learn: +## Best practices + +The following sections of this guide discuss best practices that a security engineer should consider. The guidelines include: + + * [Foundational best practices](./foundational-best-practices.html), which are practices that every organization should follow. + + * [Additional guardrails](./additional-guardrails.html), which are practices that you should consider, but might decide to implement partially or with exceptions. These are intended to provide additional control and defense in depth, but should be balanced against overall complexity. + + * [Logging interactions](./logging-interactions.html), which might result from devices or services that are part of your or your customer's responsibility in the shared responsibility model. This section includes precautions to limit the information that is accessible through logs. + + + +