- Newest
- Most votes
- Most comments
In Amazon Redshift, when a table is restored from a snapshot, the restore process is executed by the AWS account's root user. The root user has full access to all resources in the account, including Redshift clusters and snapshots. However, after the restore is completed, the ownership of the restored table is set to the original user who executed the restore command, not the root user.
The issue you encountered with the default ACL permissions not being applied to the table after the restore could be due to the ownership change from the root user to the original user. Default ACLs are applied when a new object is created, and since the table is restored and not created from scratch, the default ACLs may not be triggered.
To overcome this issue, you can explicitly set the required permissions on the table after the restore is completed. Ensure that the necessary access control privileges are granted to the appropriate groups or users who need access to the table. You can also consider defining the required permissions in the default ACLs for the user who restores the table, as you mentioned, to ensure the permissions are applied correctly during the restore process.
I've listed a link below to documentation on altering privileges that should assist with this issue: https://docs.aws.amazon.com/redshift/latest/dg/r_ALTER_DEFAULT_PRIVILEGES.html
Relevant content
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 19 days ago
- AWS OFFICIALUpdated 3 years ago