As stated in the README one can choose multiple regions for a StackSet:
"Select which regions in which you’d like to deploy the integration. Note that you can modify regions to monitor from the Datadog AWS configuration page after deploying the stack."
Actual Behavior
Deployment fails for all stacks except one because DatadogAPICall resource fails with the 409 conflict error. The root cause is that all stacks try to create an AWS integration for the same account with the Datadog API and only one succeeds. I haven't found a feasible way to fix this so far, because with the Datadog API it seems to be not possible to get an External ID for an integration, I may only to reset it, but it will cause failures for other parallel stacks in any case this way.
Steps to Reproduce the Problem
Just follow the instruction and choose multiple regions
Expected Behavior
As stated in the README one can choose multiple regions for a StackSet: "Select which regions in which you’d like to deploy the integration. Note that you can modify regions to monitor from the Datadog AWS configuration page after deploying the stack."
Actual Behavior
Deployment fails for all stacks except one because
DatadogAPICall
resource fails with the 409 conflict error. The root cause is that all stacks try to create an AWS integration for the same account with the Datadog API and only one succeeds. I haven't found a feasible way to fix this so far, because with the Datadog API it seems to be not possible to get an External ID for an integration, I may only to reset it, but it will cause failures for other parallel stacks in any case this way.Steps to Reproduce the Problem
Specifications
Stacktrace