fix: Role that the StackSet creates has backup/ as path but the Backup Policy does not reference it like that. #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
what
I was very happy to find a sample for a setup with Backup Policies in AWS, as it seemed quite complicated to set up without IaC. When I ran the Terraform Module I found that the policy created by the StackSet creates is always in the
backup/path.However the Backup Policy does not reference the IAM Role with that path. This will result in an error when the backup plan is executed.
The fix here just hardcodes the
backup/path in the Backup Policy, because it is also hardcoded in the StackSet.why