Goal
Build a React content management system that persists data (videos, images, etc.) to multiple React Native mobile apps.
Utilizing the followingAWS Services for the backend:
- Hosting: Amplify Console
- Database: DynamoDB
- User Authentication: Cognito
- Storage: S3
UtilizingReact for the website andReact Native for the mobile apps.
Step 1: Create your GraphQL API
Run the following command:
amplify add api
Edit your schema:
typeUser@model(queries:{get:"getUser"},mutations:{create:"registerUser",update:"updateUser"},subscriptions:null){id:ID!username:String!email:String!registered:Booleanavatar:S3Object!createdAt:String}typePost@model@searchable@auth(rules:[{allow:owner,identityClaim:"sub"}]){id:ID!name:String!description:String!tags:[String]thumbnail:S3Object!video:S3Object!owner:StringcreatedAt:StringupdatedAt:String}typeS3Object{bucket:String!region:String!key:String!}
Deploy the API:
amplify api push
You should now have agraphql folder in your project that lists all of yourqueries,mutations andsubscriptions.
You can view your database in the DynamoDB dashboard.
Step 2: Add Authentication
amplify add auth
Create user groups:
❯ Manual configurationDo you want to add User Pool Groups? (Use arrow keys)❯ Yes? Provide a name for your user pool group: Admins? Do you want to add another User Pool Group Yes? Provide a name for your user pool group: Editors? Do you want to add another User Pool Group No? Sort the user pool groups in order of preference … (Use <shift>+<right/left> to change the order) Admins Editors
You can view user information in the Cognito dashboard.
Configure your Amplify application:
npm install aws-amplify
InApp.js:
importAmplify,{Auth}from'aws-amplify';importawsconfigfrom'./aws-exports';Amplify.configure(awsconfig);
For more details on adding theAuthentication UI, read theAmplify docs.
Step 3: Add Storage
amplify add storage
? Please select from one of the below mentioned services (Use arrow keys)❯ Content (Images, audio, video, etc.) NoSQL Database
amplify push
Note: If you would like public read access for your files, be sure toset the appropriate permissions.
Configure:
importAmplify,{Storage}from'aws-amplify';importawsconfigfrom'./aws-exports';Amplify.configure(awsconfig);
You can view your files in the S3 dashboard.
For more details on addingStorage, read theAmplify docs.
Step 4: The fun part
Now let's connect the backend you created to a different frontend.
- Go to your Amplify Console.
- Click on the app you're working on.
- Click "Backend Environments".
- Click "Edit Backend".
Copy the line of code that looks like this:
amplify pull --appId ************* --envName *******
and run that command in your new frontend environment.
Important: Choose‘No’ when asked if you want to modify or add new categories to your backend. Choosing ‘Yes’ will work, but it is highly recommended that you don't have your backend stored in two separate repositories for this can lead to unintended consequences with multiple sources of truth.
You will now have access to youramplifyconfiguration folder in src. This means you can now use the following in this second frontend:
importawsconfigfrom'./aws-exports';Amplify.configure(awsconfig);
You can now also copy over thegraphql folder from your initial frontend over to your second frontend to utilize all of yourqueries,mutations andsubscriptions.
Note: Whenever updating your API in your backend, make sure to copy over the new graphql files into your new frontend.
You did it!
You can now use AWS Amplify to access your backend data with multiple frontends. This can especially be useful when you need to share data between web and mobile.
If you have any questions, please feel free to send me a message or ask in the comments!
Top comments(11)

- LocationJohannesburg
- WorkFront end developer at Wits
- Joined
That's an issue, thanks for bringing it up. You actually need to be in the same repo and have different branches there.

I think this link answer your question
docs.amplify.aws/cli/teams/multi-f...

- If is started a project with "amplify init" command everyting is OK.
- But if started with "amplify pull" (for example on a second frontend APP), I've got this error:
ˇˇˇ
amplify pull --appId d45659npivltuns --envName test
EPERM: operation not permitted, rename 'D:\web-nodejs\test\amplify' -> 'D:\web-nodejs\test\amplify-backup'
Error: EPERM: operation not permitted, rename 'D:\web-nodejs\test\amplify' -> 'D:\web-nodejs\test\amplify-backup'
at Object.renameSync (fs.js:741:3)
ˇˇˇ
Same error if just run an "amplify pull".
Im on Windows10, latest
I tried to:
- reinstall npm and libs, with clearing all cache, dirs, so on
- reinstall amplify-cli
- reinstall amplify-cli with --unsafe-perm=true prameterAnd try this whole workflow:
- with admin or simple user roles,
- different consloles,
- in WSL2
- different & fully clean directories,
but i got tha same error.
If I copy the first APP's amplify directory to the second, every "amplify pull" command works..
Now, I have no idea..

- Email
- LocationLondon
- WorkSoftware Engineer at Game Analytics
- Joined
Isn’t it better to have a project only for the amplify backend?

If I have two Vue frontends for the same backend. Will amplify publish push the frontend code in same repo or different?
For further actions, you may consider blocking this person and/orreporting abuse