Supported AWS Regions - Possibility of changing in the future

[WillanTheunissen]

From the documentation:

• https://docs.ymirapp.com/getting-started.html

Is this a definitive limitation at the moment? What are these limitations? Are there alternatives or is this a definitive no-go?

I have 500+ sites/apps we want to move to serverless and this tools looks really amazing - the CLI looks logical and the premis is really attractive for a team managing so many sites. Issue is an estimated 20% of our served sites are outside of the supported regions.

Carl - your project looks amazing - keep working it!

[carlalexander]

Yes, I plan on adding more regions. It's possible there are some I could add. I'm just limited in what I can work on.

The main issue is that not every region has access to all the services Ymir uses so it's why I limit things. If you know which regions you'd like me to look at, I can do a quick check to see if they added support for services to them. If I remember correctly, the main limiting one was SES.

[WillanTheunissen]

Looking at my global distribution.

The addition of Africa (Cape Town) would provide for an additional 12% coverage
The addition of Asia Pacific (Sydney) would provide for an an additional 9% coverage.

The currently supported regions combined with the above would bring my coverage up to 98% - the other 2% can be serviced on a set of micro-VMs.

[WillanTheunissen]

I see SES does support both these regions.

[carlalexander]

Ok, I just looked at the Ymir code base. I believe I'd already started working on both these regions. If I look at the ymir network:create list of region, Sydney is there:

It's also in the list of runtime layers in the other repo.

Cape town seems to be missing, but I see I started working on it internally. So I just need to review, but I think the Sydney region is just a bug in the documentation that I didn't update.