AWS Organizations - Different accounts for different environments #2479
-
Firstly, kudos to the team for pushing out v1.8.0 which I was particularly interested due to the addition of custom DNS 🎉 I have a question, though. I understand that Copilot supports different AWS accounts for keeping environments like dev, prod isolated. This is great! How should I go about using Any help will be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
Hello @afgallo! The default domain is formatted as |
Beta Was this translation helpful? Give feedback.
-
Hi @iamhopaul123 I have finally got around to start deploying my application using copilot and have come across this issue #2554, just though I'd flag this here so other may also benefit. Thanks! |
Beta Was this translation helpful? Give feedback.
Hello @afgallo! The default domain is formatted as
svc.env.app.domain
under the hood Copilot creates an app hosted zone (app.domain
) and env hosted zone per environment (env.app.domain
). So both app hosted zone and the root hosted zone (created by route53 when you purchase the domain) are shared across the whole app. You could either place the alias in the app hosted zone (e.g.,v1.app.domain
) or root hosted zone (e.g.,v1.domain
) for multi-account scenario.