AWS AmazonS3 documentation change
Summary
Fixed apostrophe typo in Signature Version 4 authentication documentation
Security assessment
Change is purely typographical (curly apostrophe to straight apostrophe) without altering security content. No vulnerabilities or security enhancements are addressed.
Diff
diff --git a/AmazonS3/latest/developerguide/sig-v4-header-based-auth.md b/AmazonS3/latest/developerguide/sig-v4-header-based-auth.md index 4975fe668..f05e4ac7a 100644 --- a//AmazonS3/latest/developerguide/sig-v4-header-based-auth.md +++ b//AmazonS3/latest/developerguide/sig-v4-header-based-auth.md @@ -244 +244 @@ For a list of Region strings, see [Regions and Endpoints](https://docs.aws.amazo -Using a signing key enables you to keep your AWS credentials in one safe place. For example, if you have multiple servers that communicate with Amazon S3, you share the signing key with those servers; you don’t have to keep a copy of your secret access key on each server. Signing key is valid for up to seven days. So each time you calculate signing key you will need to share the signing key with your servers. For more information, see [Authenticating Requests (AWS Signature Version 4)](./sig-v4-authenticating-requests.html). +Using a signing key enables you to keep your AWS credentials in one safe place. For example, if you have multiple servers that communicate with Amazon S3, you share the signing key with those servers; you don't have to keep a copy of your secret access key on each server. Signing key is valid for up to seven days. So each time you calculate signing key you will need to share the signing key with your servers. For more information, see [Authenticating Requests (AWS Signature Version 4)](./sig-v4-authenticating-requests.html).