Multi-region support with StackSets

apex / up

Deploy infinitely scalable serverless apps, apis, and sites in seconds to AWS.

https://up.docs.apex.sh

MIT License

8.8k stars 380 forks source link

Multi-region support with StackSets #134

Open tj opened 7 years ago

tj commented 7 years ago

Support for multiple regions with Stack Sets.

stephenmathieson commented 7 years ago

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

tj commented 7 years ago

@stephenmathieson nope not yet

lukeed commented 6 years ago

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

tj commented 6 years ago

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 commented 6 years ago

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

sudhirj commented 6 years ago

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 6 years ago

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

tj commented 6 years ago

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

francocorreasosa commented 6 years ago

Hello 👋 Is there any progress on this? Thanks!

tj commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

Awesome! Thanks @tj 🎉

sanjaypojo commented 6 years ago

Hey @tj poking to see if this might be ready sometime soon? :)

tj commented 6 years ago

Hard to say, traction hasn't been as good as I was hoping so it might be too large of an addition, especially when lots of services are going this route by default (Lambda@edge, Cloudflare workers, etc)

pontusab commented 5 years ago

Is it possible to do a multi-region deployment yet? looking into serverless framework and that can currently do that. But really love up and want to continue with that. Is it possible in some other way, like manually, for now, adding to route53 etc?

tj commented 5 years ago

@pontusab not out of the box yet, the easiest manual route would probably be with https://aws.amazon.com/global-accelerator/

pontusab commented 5 years ago

@tj Thanks, will look into that 🥇