Skip to content
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

Amplify multi region app #13908

Closed
stam0912 opened this issue Aug 29, 2024 · 3 comments
Closed

Amplify multi region app #13908

stam0912 opened this issue Aug 29, 2024 · 3 comments
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question

Comments

@stam0912
Copy link

Amplify CLI Version

12.12.1

Question

I need help to deploy the app in multiple regions. I created an Amplify app in ca-central-1 and now I would like to deploy it to ap-northeast-1 (both app sharing the same table).

I created a replica of the table to ap-northeast-1. After that, I created an appsync api using the global table as the data source with CDK and deployed it to ap-northeast-1. How can I create an Amplify app with an existing appsync api?

I don't know if I'm on the right track. What is the proper way to deploy the app in multiple regions?

@stam0912 stam0912 added pending-triage Issue is pending triage question General question labels Aug 29, 2024
@ykethan
Copy link
Member

ykethan commented Aug 29, 2024

Hey @stam0912, thank you for reaching out. I would suggest posting this in our Amplify discord community as the community of developers using Amplify may suggest alternatives and their implementation on your use case.

But you can you can utilize the Amplify.configure to pass in your existing API and config to reuse your existing or if you have an existing amplify_configuration.json you could utilize this to deploy in a new region.

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Aug 29, 2024
@ykethan
Copy link
Member

ykethan commented Oct 21, 2024

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Oct 21, 2024
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question
Projects
None yet
Development

No branches or pull requests

2 participants