Wondering why can’t delete snapshot in Amazon Redshift? We can help you.

At Bobcares we assist our customers with several AWS queries as part of our AWS Support Services for AWS users, and online service providers.

Today, let us discuss how to resolve this Redshift error.

Can’t delete snapshot in Amazon Redshift

Usually, error occurs if you’re trying to delete a snapshot that shares access with another AWS account.

Typical error looks as shown below:

"Cannot delete the snapshot- xxx-xxx-xxx because other accounts still have access to it."

To resolve this error message, remove the shared access from the AWS account that created the cluster snapshot in Amazon Redshift.

Then, delete your cluster snapshot.

Today, let us see the steps followed by our Support Techs to delete snapshots.

To delete a shared cluster snapshot using the Amazon Redshift console, perform the following steps:

1.Firstly, sign in to the AWS Management Console with the AWS account that created the cluster snapshot.

2.Then, open the Amazon Redshift console.

3.From Clusters, choose the snapshot that you want to delete.

4.Then, choose Actions.

5.Choose Manage Access to view the access settings for your cluster.

6.Choose Remove Account to delete the shared access of your cluster snapshot.

7.Then, delete your cluster snapshot.

Please note if you receive errors when running AWS CLI commands, make sure that you’re using the most recent AWS CLI version.

To delete a shared cluster snapshot using the AWS Command Line Interface (AWS CLI), perform the following steps:

1.Revoke the shared snapshot access using the revoke-snapshot-access command:

aws redshift revoke-snapshot-access --snapshot-id my-snapshot-id --account-with-restore-access <AWS-account-id-with-access>

2.Delete your Amazon Redshift cluster snapshot using the delete-cluster-snapshot command:

aws redshift delete-cluster-snapshot --snapshot-identifier my-snapshot-id

[Need help with the Amazon error? We’d be happy to assist]

Conclusion

In short, today we saw how our  Support Techs resolve this Redshift error.