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

Cannot create a new CloudFormation stack alongside an existing DTH stack #60

Open
tomclukies opened this issue Sep 13, 2021 · 5 comments

Comments

@tomclukies
Copy link

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.

@JoeShi
Copy link
Contributor

JoeShi commented Sep 16, 2021

Taking a look.

@kaplanan
Copy link

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.

@evalzy
Copy link

evalzy commented Feb 23, 2024

hi @kaplanan, we are looking for this, will back to you soon.

@YikaiHu
Copy link
Collaborator

YikaiHu commented Feb 26, 2024

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.

image

@evalzy
Copy link

evalzy commented Feb 26, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants