-
Notifications
You must be signed in to change notification settings - Fork 22
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
Cannot create a new CloudFormation stack alongside an existing DTH stack #60
Comments
Taking a look. |
Hi @evalzy can we push this issue? It would be great if the Cloudformation resource identifiers contain a dynamically created (unique) suffix to have rolling updates enabled when upgrading DTH stacks. |
hi @kaplanan, we are looking for this, will back to you soon. |
Hi @kaplanan , here is the workaround, please using this customized template: DataTransferHub-cognito-reDeployable.json Note: the stack name must be all lowercase for this re-deployable template! I have successfully deployed two DTHs in my account. |
hi @kaplanan , May I know in which case that need install 2 main stack in same account? In solution web console, you can create multiple transfer pipelines to manage tasks. |
We are trying to upgrade to v2 of data-transfer-hub. We would like to create a new stack in parallel to the existing, and make sure its in working order before removing the existing stack.
We ran into issues with resource names overlapping. Error message:
Export with name TaskClusterName is already exported by stack DataReplicationHub. Rollback requested by user.
Resource names should be unique between Data Transfer Hub Cloudformation Stacks.
The text was updated successfully, but these errors were encountered: