-
Notifications
You must be signed in to change notification settings - Fork 260
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
Silo Multi-tenant Flutter app using AWS Amplify with one frontend #4335
Comments
@Vumcam can you explain what you mean by multiple backends? Are you looking to add multiple instances of each category (auth, storage, data) to your amplify app? This is not something that is supported. One option you could consider is to use separate amplify apps and then load the config for the appropriate app. Please not that Amplify Flutter does not support re-configuration at runtime so you would need to load the appropriate config prior to initializing amplify. |
@Jordan-Nelson Like I mentioned in my question, due to regulatory requirements all tenant data must be separated, so what I meant by multiple backends is that each tenant must have its own user pool and databases - therefore I create a single backend for each tenant. I don't really need to have the functions and APIs separate, but I don't know if you can have multiple databases and storage buckets(the same for each tenant) under 1 backend and also have the automatic deployments. You nailed it on point with the reconfiguration at runtime which would make what I need possible easily, is this something that is in the works or even feasible with Amplify? |
Ok, great. |
I see your comment on that issue. I am going to close this issue out since I believe the question was answered. |
I'm building a multi-tenant app with Flutter using AWS Amplify.
My regulatory requirement makes it so I must have separate databases and storage(all user data) for each tenant.
The Flutter web version of the app is hosted on AWS Amplify Hosting, so as of now I have a full CI/CD pipeline to commit the app in the staging environment, then make a pull request to deploy it to the production environment.
My issue is, that after creating this process I discovered that each AWS Amplify Frontend can only have 1 backend connected to it.
This makes it impossible(at least from what I know until now) to create multiple backend environments(each environment for each tenant) that have a shared frontend.
My idea was having a prefix that is a name of the tenant in every username, then in the shared login using that prefix I'll authenticate using the matching user pool and then have IAM credentials to access the rest of that tenant environment.
Discovering that you can't(from what I know up to now) connect multiple backend environments to a single frontend made this unfeasible...
Does anyone have an idea of how I can make this happen?
Any help would be very appreciated 🙏
The text was updated successfully, but these errors were encountered: