Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws-batch: Batch notification configurations not implemented in CDK #28657

Closed
2 tasks
kmendler opened this issue Jan 10, 2024 · 2 comments
Closed
2 tasks

aws-batch: Batch notification configurations not implemented in CDK #28657

kmendler opened this issue Jan 10, 2024 · 2 comments
Labels
@aws-cdk/aws-batch Related to AWS Batch closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/large Large work item – several weeks of effort feature-request A feature should be added or improved. p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@kmendler
Copy link

Describe the feature

I would like to programmatically generate a Stack that lets me receive notifications in Slack via an AWS Chatbot whenever a AWS Batch Job changes status. All the pieces are there except for the notification rule that makes the link between AWS Batch and the Slack delivery channel.

Use Case

I'd like to be able to programmatically set up and tear down the Chatbot piece of my cloud app's infrastructure.

Proposed Solution

No response

Other Information

I noticed that notification rules for some of the AWS Code* services are implemented in the aws_codestarnotifications package - maybe it can be expanded to include AWS Batch? The missing pieces are the INotificationRuleSource (aws.batch in this case) and DetailType (Batch Job State Change in my case).

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

CDK version used

2.118.0

Environment details (OS name and version, etc.)

Mac OS 13.5.2

@kmendler kmendler added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Jan 10, 2024
@github-actions github-actions bot added the @aws-cdk/aws-batch Related to AWS Batch label Jan 10, 2024
@tim-finnigan tim-finnigan self-assigned this Jan 11, 2024
@tim-finnigan
Copy link

Thanks for the feature request. I think what you're requesting is something that the Batch service team would need to directly add API support for. However your use case should be addressable by the workflow documented here: https://docs.aws.amazon.com/batch/latest/userguide/batch_sns_tutorial.html.

You can use the aws_sns and aws_events modules to create the topic/rule, and then subscribe the SNS topic to AWS Chatbot.

@tim-finnigan tim-finnigan added p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. effort/large Large work item – several weeks of effort and removed needs-triage This issue or PR still needs to be triaged. labels Jan 11, 2024
@tim-finnigan tim-finnigan removed their assignment Jan 11, 2024
Copy link

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-batch Related to AWS Batch closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/large Large work item – several weeks of effort feature-request A feature should be added or improved. p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

2 participants