handling access denied when reading vault policy when vault has been deleted #19749
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Relates OR Closes #0000
It's a new issue we stumbled on but not reported.
In essence, if the backup vault is deleted outside of terraform, the update operation fails with
AccessDenied
error instead ofResourceNotFoundException.
The cause for that is that authors ofGetBackupVaultAccessPolicy
API decided (allegedly) to follow some no-exposure security rule that advocates not exposing resource absence to avoid discovery of valid resource names using some kind of brute force iteration.Output from acceptance testing:
TODO
@DrFaust92 any ideas how we can test this? The reproduction steps are:
resourceAwsBackupVaultPolicyRead
At this stage, the PR is not ready for merging, it's a discussion on how the issue can be tested.