Updating AWS managed permissions to a newer
version
Occasionally, AWS updates the AWS managed permissions available to attach to a resource share for a specific resource type. When AWS does this, it creates a new version of the AWS managed permission. Resource shares that include the specified resource type aren't automatically updated to use the latest version of the managed permission. You must explicitly update the managed permission for each resource share. This extra step is required so that you can evaluate the changes before you apply them to your resource shares.
Whenever the console displays a page that lists the permissions associated with a resource share, and one or more of those permissions are using a version other than the default for the permission, the console displays a banner at the top of the console page. The banner indicates that your resource share is using a version other than the default.
In addition, individual permissions can display an Update to default version button next to the current version number when that version is not the default.
Choosing that button starts the Update resource share wizard. On Step 2 of the wizard you can update the version of any non-default permissions to use their default versions.
The changes are not saved until you complete the wizard by choosing Submit on the last page of the wizard.
Note
You can attach only the default version, and you can't revert to another version.
For customer managed permissions, after you update the permissions to the default version, you can't apply another version to a resource share unless you first set that other version as the default. For example, if you updated a permission to the default version and then found an error that you wanted to roll back, you could designate the previous version as the default. Alternatively, you could create a different new version and then designate that as the default. After you performed one of those options, you would then update your resource shares to use what is now the default version.