AWS verifiedpermissions documentation change
Summary
Updated Cedar version references from v4.2.3 to v4.3 and extended upgrade timeline to December 2025
Security assessment
Version number updates and timeline changes do not contain explicit security context or vulnerability references
Diff
diff --git a/verifiedpermissions/latest/userguide/cedar4-faq.md b/verifiedpermissions/latest/userguide/cedar4-faq.md index 7c9141b40..1383c2ec2 100644 --- a/verifiedpermissions/latest/userguide/cedar4-faq.md +++ b/verifiedpermissions/latest/userguide/cedar4-faq.md @@ -28 +28 @@ Amazon Verified Permissions is in the process of updating to Cedar v4. We're wor -As a first step we've upgraded the console to use Cedar v4.2.3, however the back end is still running on Cedar v2.5.0. This means that while you can now use the console to author policies using new features like the `is` operator, when you attempt to save them you will still get an error until we complete the upgrade. +As a first step we've upgraded the console to use Cedar v4.3, however the back end is still running on Cedar v2.5.0. This means that while you can now use the console to author policies using new features like the `is` operator, when you attempt to save them you will still get an error until we complete the upgrade. @@ -36 +36 @@ As a first step we've upgraded the console to use Cedar v4.2.3, however the back -**No**. Prior to upgrading we will run tests to check that your policy store works correctly with Cedar v4. There are some minor breaking changes between v2.5.0 and v4.2.3, but it’s very unlikely that your policy store will be impacted. If it is, then your policy store will not be upgraded, and will continue to authorize using Cedar v2.3.1. Should this happen, we will reach out to explain any changes you need to make before being able to upgrade. +**No**. Prior to upgrading we will run tests to check that your policy store works correctly with Cedar v4. There are some minor breaking changes between v2.5.0 and v4.3, but it’s very unlikely that your policy store will be impacted. If it is, then your policy store will not be upgraded, and will continue to authorize using Cedar v2.3.1. Should this happen, we will reach out to explain any changes you need to make before being able to upgrade. @@ -48 +48 @@ If your policy store is affected by breaking changes it won't be upgraded, and w -Our goal is to complete the upgrade by the end of Q1 2025. +Our goal is for all accounts to be upgraded by December 31, 2025.