-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Feature request: Budget notifications #4548
Comments
Please support both SNS and email notification options Option 2 is better, as it matches what the underlying API can do. |
I opened a PR (#4523) a while back that's not merged yet, maybe add a 👍 over there if you are interested in this feature |
Was this ever added? |
Support for |
Thanks for adding this functionality. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
I'm using the new
aws_budgets_budget
resource, and am trying to set up notifications around it. This resource would support that use case.I'm interested in implementing this, but would love feedback first.
New or Affected Resource(s)
Potential Terraform Configuration
Disclaimers
The subscription configuration needs to be included in the
aws_budgets_notification
resource configuration because they are (strangely) required when creating notifications, even though there are API actions to add and remove them.Option 1 is presumably simpler to implement (in terms of parsing, state management, etc.), but Option 2 gives the option for supporting multiple
subscription
blocks.The account ID is required when creating a notification through the API, but it's not an option in the Console. It's unclear when that would/could be a value other than the "effective account ID".
References
The text was updated successfully, but these errors were encountered: