AWS prescriptive-guidance documentation change
Summary
Reformatted notes section and introduced typo ('treated' to 'streated') in metadata comparison.
Security assessment
Formatting changes and accidental typo introduction. No security implications as core concepts about headers vs query strings remain unchanged despite the typo.
Diff
diff --git a/prescriptive-guidance/latest/presigned-url-best-practices/overview.md b/prescriptive-guidance/latest/presigned-url-best-practices/overview.md index a32374d5b..17ddb5c8e 100644 --- a//prescriptive-guidance/latest/presigned-url-best-practices/overview.md +++ b//prescriptive-guidance/latest/presigned-url-best-practices/overview.md @@ -13 +13 @@ A presigned URL is a type of HTTP request that's recognized by the [AWS Identity -###### Notes +**Notes** : @@ -70 +70 @@ The only inherently secret component of a presigned request is its Signature Ver -Presigned URLs and signature-only solutions are cryptographically similar. However, signature-only solutions have practical advantages such as the ability to use an HTTP header instead of a query string parameter to transmit the signature (see the [Logging interactions and mitigations](./logging-interactions.html) section). Administrators should also consider that query strings are more commonly treated as metadata, whereas headers are less commonly treated as such. +Presigned URLs and signature-only solutions are cryptographically similar. However, signature-only solutions have practical advantages such as the ability to use an HTTP header instead of a query string parameter to transmit the signature (see the [Logging interactions and mitigations](./logging-interactions.html) section). Administrators should also consider that query strings are more commonly treated as metadata, whereas headers are less commonly streated as such.