Open OlafConijn opened 4 years ago
this probably depends on https://github.com/aws-cloudformation/aws-cloudformation-resource-schema/pull/86
Similar error while changing threshold percentage.
AWS::Budgets::Budget Budget UPDATE_FAILED (Error creating budget: budgetName - the budget already exists. (Service: AWSBudgets; Status Code: 400; Error Code: DuplicateRecordException; Request ID: caada7f6-3cf6-46d9-8d6a-643e9b5c4c66; Proxy: null))
aws-cloudformation/cloudformation-resource-schema#86 has been merged now. Any update on progress here?
Bumping for an update. Please!
Just chipping in our vote to say we would really like to see this addressed
+1
Added subscribers to a budget-alert template deployed by control tower. This error sadly still occurs.
Still waiting for a fix.
As a workaround, what seems to work for me is adding a unique string to the name, I'm using a unix timestamp (in millis) and set the time period start date to a fixed date, so that the budget doesn't "move" when you redeploy it.
Is there any update on this? or workaround (without having to create a new budgetalert?)
Workaround is simple: do not set a BudgetName
This way CF can re-create alarms as they are updated. Budget name will then be something like Budget-eu-west-1-012345678789012-J8OitO03ogC5
The first part is the CloudFormation resource name, so you have a bit of control over the eventual name. As you update your alarms, the last part of the name will be refreshed every time.
AWS::Budgets::Budget
does not handle changing attributes likeNotificationsWithSubscribers-Subscribers
well.problem: If Subscribers are added/removed from a
AWS::Budgets::Budget
resource updating the stack fails with an errorResource Budget failed because Error creating budget: my-budget - the budget already exists.
problem might apply to other attributes too.
expected behavior is for the stack not to fail.
test case create a stack with
update stack by adding/changing the
NotificationsWithSubscribers-Subscribers