Creating SNS topics and updating IAM policy for instance scheduler #5679
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.
A reference to the issue / Description of it
This PR partially implements the issue 2722.
This is to allow the instance scheduler lambda function to publish to SNS topics and to create topics that the lambda is going to use as the destination config. This is also integrating with an existing pagerduty service.
How does this PR fix the problem?
This is to enable alerts when the instance scheduler fails/succeeds.
How has this been tested?
Run the tf plan locally and it works as expected for the added functionality, but it fails for a transit gateway policy saying it needs an apply. Not end-to-end tested yet, as the lambda terraform module needs updating first.
Deployment Plan / Instructions
Will this deployment impact the platform and / or services on it?
The instance scheduler IAM policy may be impacted if configured incorrectly.
SNS topics and the pagerduty integration are new resources, so it does not break the existing functionality.
Checklist (check
x
in[ ]
of list items)Additional comments (if any)
{Please write here}