SNS topic for codepipeline notification events #546
Conversation
This file contains hidden or 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
1 participant
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.
This feature adds a CodePipeline notification rule to each new account customization pipeline.
Notifications are sent to a dedicated SNS topic that receives the various event notifications that codepipeline supports:
https://docs.aws.amazon.com/dtconsole/latest/userguide/concepts.html#events-ref-pipeline
This functionality addresses a gap in visibility, where we have notification topics for account creation / provisioning, but no insight into the results of customization pipeline executions.
It will enable the ability to listen and act on events of a pipeline, such as reporting the status for api-driven workflows, alerting support teams, or auditing/reporting capability.
Once this feature is implemented there will be 3 SNS topics:
This could also open the door for more granular information such as CodePipeline action or stage notifications in the future.