Skip to content

Creating 2nd CloudFormation stack, errors creating already-existing resources #2874

You must be logged in to vote

Using the same internal + link domains, I have not seen anyone successfully deploy a second deployment.

Using a different subdomain for the main domain, I have not heard anyone successfully deploying a second deployment. -- you'd be trailblazing if you did!

I'd recommend deploying a second stack with completely different domains.
The backend would stay in sync because of our HC auto-update system.
You'd iterate with the custom client by using npm run login and npm run logout to login to each stack, then deploy the same custom client to each.

Replies: 2 comments 2 replies

You must be logged in to vote
2 replies
@robinkwilson

@aidanhmiles

Answer selected by robinkwilson

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants