AWS AmazonS3 documentation change
Summary
Fixed grammatical structure in presigned URL validity explanation (added subject 'Presigned URLs')
Security assessment
Minor grammatical correction with no security implications. Does not alter security guidance about presigned URL expiration.
Diff
diff --git a/AmazonS3/latest/userguide/using-presigned-url.md b/AmazonS3/latest/userguide/using-presigned-url.md index d5c6b1818..f573e56ec 100644 --- a//AmazonS3/latest/userguide/using-presigned-url.md +++ b//AmazonS3/latest/userguide/using-presigned-url.md @@ -144 +144 @@ The following IAM policy statement requires the principal to access AWS only fro -remain valid only while their underlying credentials are valid. A presigned URL expires at either its configured expiration time or when its associated credentials expire, whichever occurs first. For Amazon Elastic Container Service tasks or containers, role credentials typically rotate every 1-6 hours. When using AWS Security Token Service (AWS STS) AssumeRole, the presigned URL expires when the role session ends, which by default is 1 hour. For Amazon EC2 instance profiles, metadata credentials rotate periodically with a maximum validity period of approximately 6 hours. +Presigned URLs remain valid only while their underlying credentials are valid. A presigned URL expires at either its configured expiration time or when its associated credentials expire, whichever occurs first. For Amazon Elastic Container Service tasks or containers, role credentials typically rotate every 1-6 hours. When using AWS Security Token Service (AWS STS) AssumeRole, the presigned URL expires when the role session ends, which by default is 1 hour. For Amazon EC2 instance profiles, metadata credentials rotate periodically with a maximum validity period of approximately 6 hours.