Creating a new Amplify App Instance per customer based on a backend configuration

[menkari]

I've been using Amplify for a while now and have successfully developed several standalone apps and for that its been great. Am posting here as I'm looking to provision the app in an automated fashion (preferably a API based sales funnel trigger).

I've been working on an angular website which makes use of Authentication and the API libraries and the requirement is to have the application provisioned per customer with unique and isolated resources (own Cognito user group, own DynamoDB tables, etc). The requirement is that each customer can purchase an "license" to the application and from there a process is kicked off to create the necessary resources to setup that customers instance of the app. These have been put forward as requirements for compliance and security. Also speed of provisioning is important as customers and ideally this would be < 5mins.

I've already looked into aws-cdk and what libraries are exposed there: From the looks of it, the closest I can get is cloning the environment resources - Not suitable for what I'm trying to achieve. I've also looked into aws-cdk parameters and this doesn't help much either as these are set at the "cdk deploy" command stage - something I could potentially script out and call from a long running EC2 instance.

I'm new to aws-cdk so this maybe a case of I'm not looking in the right place, but it doesn't look as though this is easily achievable using AWS Amplify - it seems to be designed to be "single backend" / multi-tenanted / multi environment yes, but essentially one backend that can be plugged into multiple interfaces.

The summary is basically this:

The app instance is made up of the following:

• Angular application
• Amplify Backend (Auth, API)
• AWS API Gateway (Websocket + Lambdas to drive it)

I'm looking for an automated way to duplicate the above per customer with their own cloud resources and do it on demand. Also considered posting to the Amplify team, but this falls outside the tools to build the app and more on rolling out the app after its built, hence the posting here and not there.

Any guidance/suggestions would be greatly appreciated and happy to share findings if a solution comes out.