AWS AmazonCloudFront medium security documentation change
Summary
Updated expiration dates in policy examples to 2026
Security assessment
Updates expiration timestamps to 2026 and aligns with 64-bit epoch time to prevent 2038-related expiration failures, ensuring continued enforcement of access controls for signed cookies.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/private-content-setting-signed-cookie-custom-policy.md b/AmazonCloudFront/latest/DeveloperGuide/private-content-setting-signed-cookie-custom-policy.md index 79bea3db9..568add0e4 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/private-content-setting-signed-cookie-custom-policy.md +++ b//AmazonCloudFront/latest/DeveloperGuide/private-content-setting-signed-cookie-custom-policy.md @@ -304 +304 @@ The following example custom policy in a signed cookie specifies that a user can - "AWS:EpochTime": 1357034400 + "AWS:EpochTime": 1767290400 @@ -325 +325 @@ The following example custom policy allows you to create signed cookies for any - "AWS:EpochTime": 1357034400 + "AWS:EpochTime": 1767290400 @@ -350 +350 @@ The following sample custom policy allows you to set signed cookies for any file - "AWS:EpochTime": 1357034400 + "AWS:EpochTime": 1767290400 @@ -353 +353 @@ The following sample custom policy allows you to set signed cookies for any file - "AWS:EpochTime": 1357120800 + "AWS:EpochTime": 1767376800