GraphQL Transformer Region Support

[jexh]

I have tried modelling my application with Amplify but it doesn't currently have the multi-region support that I require.

I am building a complex service spread across multiple regions. Some of the data used by the service would most naturally fit in Dynamo global tables, other data would be region specific. It would be great to have Amplify support the tagging of @model directives to control the distribution of data and have Amplify support multi-region deployment.

Given the scope of the problem I don't want to be too specific and I can't really give a complete feature list. The small list below describes the features I am looking for right now:

• Need to abstract away the location of data - some data will be global, some will be local. Global data would be shared across all regions to which the service is deployed, changes need to be propagated to all the places that replicate the data. Local data would be held in a single region although the types of data is identical across all regions (same schema).
• Top level deployment should list the regions to include in deployment ** Adding and removing deployed regions to a live system should be supported

[haverchuck]

@jexh - thanks for reaching out. We've tagged this as a feature request.

[hisham]

This would be really helpful for me as well. Amplify CLI claims to have escape hatches when the CLI does not support features we need, but it still doesn't really have an escape hatch when I need to create a service or create a db in a region that's outside the set region in Amplify CLI. The nested stack support does help a bit with this, in that we can now add data sources that is in a different region but then I have to maintain those data sources through cloudformation files external to Amplify CLI.

[MontoyaAndres]

Any update?