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

Multi-region support with StackSets #134

Open
tj opened this Issue Jul 25, 2017 · 12 comments

Comments

Projects
None yet
5 participants
@tj
Member

tj commented Jul 25, 2017

Support for multiple regions with Stack Sets.

@tj tj added the Refactor label Jul 25, 2017

@tj tj added this to the 0.1.0-beta milestone Jul 25, 2017

@tj tj modified the milestones: 0.2.0, 0.3.0 Aug 7, 2017

@stephenmathieson

This comment has been minimized.

Show comment
Hide comment
@stephenmathieson

stephenmathieson Oct 11, 2017

Contributor

Any progress here? Getting this in will be a huge win.

Contributor

stephenmathieson commented Oct 11, 2017

Any progress here? Getting this in will be a huge win.

@tj

This comment has been minimized.

Show comment
Hide comment
@tj

tj Oct 13, 2017

Member

@stephenmathieson nope not yet

Member

tj commented Oct 13, 2017

@stephenmathieson nope not yet

@tj tj removed this from the 0.3.0 milestone Oct 13, 2017

@tj tj changed the title from Utilize StackSets for multi-region provisioning to Multi-region support with StackSets Nov 10, 2017

@tj tj referenced this issue Nov 10, 2017

Closed

Multi-region service only prints 1 URL #407

2 of 3 tasks complete
@lukeed

This comment has been minimized.

Show comment
Hide comment
@lukeed

lukeed Dec 8, 2017

Poking in to ask if anything from re:Invent made this possible?

lukeed commented Dec 8, 2017

Poking in to ask if anything from re:Invent made this possible?

@tj

This comment has been minimized.

Show comment
Hide comment
@tj

tj Dec 8, 2017

Member

yep, still pretty low priority TBH, but at least now with Dynamo's replication there's more db options. In most a lot of cases one region + CDN is enough I think

Member

tj commented Dec 8, 2017

yep, still pretty low priority TBH, but at least now with Dynamo's replication there's more db options. In most a lot of cases one region + CDN is enough I think

@tj

This comment has been minimized.

Show comment
Hide comment
@tj

tj Dec 13, 2017

Member

note to self: list of hosted zone ids are here http://docs.aws.amazon.com/general/latest/gr/rande.html

Member

tj commented Dec 13, 2017

note to self: list of hosted zone ids are here http://docs.aws.amazon.com/general/latest/gr/rande.html

@sudhirj

This comment has been minimized.

Show comment
Hide comment
@sudhirj

sudhirj Dec 22, 2017

Notes to @tj

  • API Gateway recently added support for regional endpoints (earlier API-GW endpoints already had an AWS managed CloudFront distribution in front of them).

    • This should allow deploying API-GWs multi region, and then setting them up on Route53 with Latency routing so the users are always sent to the closest region. Or create a CloudFront distro that will internally route to the nearest region.
  • Environment variables need to be region specific - different regions use different DB/DynamoDB

  • Might be nice to have automatic subdomains on all configured domains - like us-east-1.app.domain.com including the main app.domain.com configured using Route53 above.

sudhirj commented Dec 22, 2017

Notes to @tj

  • API Gateway recently added support for regional endpoints (earlier API-GW endpoints already had an AWS managed CloudFront distribution in front of them).

    • This should allow deploying API-GWs multi region, and then setting them up on Route53 with Latency routing so the users are always sent to the closest region. Or create a CloudFront distro that will internally route to the nearest region.
  • Environment variables need to be region specific - different regions use different DB/DynamoDB

  • Might be nice to have automatic subdomains on all configured domains - like us-east-1.app.domain.com including the main app.domain.com configured using Route53 above.

@sudhirj

This comment has been minimized.

Show comment
Hide comment
@sudhirj

sudhirj Dec 22, 2017

Also, ACM certs will have to be requested once for each region, might make sense to just do wildcards in every region.

sudhirj commented Dec 22, 2017

Also, ACM certs will have to be requested once for each region, might make sense to just do wildcards in every region.

@tj

This comment has been minimized.

Show comment
Hide comment
@tj

tj Dec 22, 2017

Member

Yeah :( that part will be annoying (#452) they have support for DNS verification as well now at least too

Member

tj commented Dec 22, 2017

Yeah :( that part will be annoying (#452) they have support for DNS verification as well now at least too

@francocorreasosa

This comment has been minimized.

Show comment
Hide comment
@francocorreasosa

francocorreasosa Apr 12, 2018

Hello 👋 Is there any progress on this? Thanks!

francocorreasosa commented Apr 12, 2018

Hello 👋 Is there any progress on this? Thanks!

@tj

This comment has been minimized.

Show comment
Hide comment
@tj

tj Apr 12, 2018

Member

For me the ACM verifications are the biggest blocker, it would be awful UX to receive like 150 emails, and dig through which ones are for which region you still need to verify. The DNS alternative isn't much better there either :'(. I'll see if maybe I can grab one from a region and replicate it to the others, that would unblock this I think.

Keep in mind your data has to be replicated too otherwise it's not really going to be much of an improvement over the default CloudFront -> API Gateway setup we have now.

Member

tj commented Apr 12, 2018

For me the ACM verifications are the biggest blocker, it would be awful UX to receive like 150 emails, and dig through which ones are for which region you still need to verify. The DNS alternative isn't much better there either :'(. I'll see if maybe I can grab one from a region and replicate it to the others, that would unblock this I think.

Keep in mind your data has to be replicated too otherwise it's not really going to be much of an improvement over the default CloudFront -> API Gateway setup we have now.

@tj

This comment has been minimized.

Show comment
Hide comment
@tj

tj Apr 12, 2018

Member

Ohh I misread the docs actually, the DNS verification should work across regions unlike email. That's not too bad. I'll try to get on this soonish!

Member

tj commented Apr 12, 2018

Ohh I misread the docs actually, the DNS verification should work across regions unlike email. That's not too bad. I'll try to get on this soonish!

@francocorreasosa

This comment has been minimized.

Show comment
Hide comment
@francocorreasosa

francocorreasosa Apr 13, 2018

Awesome! Thanks @tj 🎉

francocorreasosa commented Apr 13, 2018

Awesome! Thanks @tj 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment