In this workshop we'll learn how to use Amplify DataStore to create Chatty
a single room realtime multi-user chat app using React & AWS Amplify.
- Authentication
- GraphQL API with AWS AppSync
- Setup Amplify DataStore
- Deploying via the Amplify Console
- Removing / Deleting Services
- Appendix and trobleshooting
- Node:
13.12.0
. Visit Node - npm:
6.14.4
. Packaged with Node otherwise run upgrade
npm install -g npm
To get started, we first need to create a new React project & change into the new directory using the Create React App CLI.
If you already have this installed, skip to the next step. If not, either install the CLI & create the app or create a new app using npx:
npm install -g create-react-app
create-react-app amplify-datastore
Or use npx to create a new app:
npx create-react-app amplify-datastore
Now change into the new app directory & install the AWS Amplify & AWS Amplify React libraries:
cd amplify-datastore
npm install --save aws-amplify aws-amplify-react moment
If you have issues related to EACCESS try using sudo:
sudo npm <command>
.
Next, we'll install the AWS Amplify CLI:
npm install -g @aws-amplify/cli
Now we need to configure the CLI with our credentials:
amplify configure
If you'd like to see a video walkthrough of this configuration process, click here.
Here we'll walk through the amplify configure
setup. Once you've signed in to the AWS console, continue:
- Specify the AWS Region: eu-west-2 (London)
- Specify the username of the new IAM user: amplify-workshop-user
In the AWS Console, click Next: Permissions, Next: Tags, Next: Review, & Create User to create the new IAM user. Then, return to the command line & press Enter.
- Enter the access key of the newly created user:
accessKeyId: (<YOUR_ACCESS_KEY_ID>)
secretAccessKey: (<YOUR_SECRET_ACCESS_KEY>) - Profile Name: amplify-workshop-user
amplify init
- Enter a name for the project: amplifydatastore
- Enter a name for the environment: dev
- Choose your default editor: Visual Studio Code (or your default editor)
- Please choose the type of app that you're building javascript
- What javascript framework are you using react
- Source Directory Path: src
- Distribution Directory Path: build
- Build Command: npm run-script build
- Start Command: npm run-script start
- Do you want to use an AWS profile? Y
- Please choose the profile you want to use: amplify-workshop-user
Now, the AWS Amplify CLI has iniatilized a new project and you will see a new folder: amplify and a new file called aws-exports.js
in the src directory. The files in this folder hold your project configuration.
<amplify-app>
|_ amplify
|_ .config
|_ #current-cloud-backend
|_ backend
team-provider-info.json
In order to display the user sending messages for our chat, we will require users to register and login. We can implement this requirement using the auth
category.
To add authentication, we can use the following command:
amplify add auth
When prompted choose
- Do you want to use default authentication and security configuration?: Default configuration
- How do you want users to be able to sign in when using your Cognito User Pool?: Username
- Do you want to configure advanced settings? Yes, I want to make some additional changes.
- What attributes are required for signing up? (Press <space> to select, <a> to toggle all, <i> to invert selection): Email
- Do you want to enable any of the following capabilities? (Press <space> to select, <a> to toggle all, <i> to invert selection): None
To select none just press
Enter
in the last option.
Now, we'll run the push command and the cloud resources will be created in our AWS account.
amplify push
Current Environment: dev
| Category | Resource name | Operation | Provider plugin |
| -------- | ------------------ | --------- | ----------------- |
| Auth | amplifyappuuid | Create | awscloudformation |
? Are you sure you want to continue? Yes
To quickly check your newly created Cognito User Pool you can run
amplify status
To access the AWS Cognito Console at any time, go to the dashboard at https://console.aws.amazon.com/cognito/. Also be sure that your region is set correctly.
Now, our resources are created & we can start using them!
The first thing we need to do is to configure our React application to be aware of our new AWS Amplify project. We can do this by referencing the auto-generated aws-exports.js
file that is now in our src folder.
To configure the app, open src/index.js and add the following code below the last import:
import Amplify from 'aws-amplify'
import config from './aws-exports'
Amplify.configure(config)
Now, our app is ready to start using our AWS services.
To add authentication, we'll go into src/App.js and first import the withAuthenticator
HOC (Higher Order Component) from aws-amplify-react
:
import { withAuthenticator } from 'aws-amplify-react'
Next, we'll wrap our default export (the App component) with the withAuthenticator
HOC:
export default withAuthenticator(App, { includeGreetings: true })
# run the app
npm start
Now, we can run the app and see that an Authentication flow has been added in front of our App component. This flow gives users the ability to sign up & sign in.
To view the new user that was created in Cognito, go back to the dashboard at https://console.aws.amazon.com/cognito/. Also be sure that your region is set correctly.
We can access the user's info now that they are signed in by calling Auth.currentAuthenticatedUser()
.
import React, { useEffect } from 'react'
import { Auth } from 'aws-amplify'
function App() {
useEffect(() => {
Auth.currentAuthenticatedUser()
.then(user => console.log({ user })
})
return (
<div className="App">
<p>
Edit <code>src/App.js</code> and save to reload.
</p>
</div>
)
}
export default withAuthenticator(App, { includeGreetings: true })
To add a GraphQL API, we can use the following command:
amplify add api
Answer the following questions
- Please select from one of the below mentioned services: GraphQL
- Provide API name: chattyAPI
- Choose an authorization type for the API API key
- Enter a description for the API key: API description
- After how many days from now the API key should expire (1-365): 7
- Do you want to configure advanced settings for the GraphQL API? Yes, I want to make some additional changes
- Configure additional auth types? N
- Configure conflict detection? Y
- Select the default resolution strategy Auto Merge
- Do you want to override default per model settings? N
- Do you have an annotated GraphQL schema? N
- Do you want a guided schema creation? Y
- What best describes your project: Single object with fields (e.g. “Todo” with ID, name, description)
- Do you want to edit the schema now? Y
When prompted, update the schema to the following:
type Chatty @model {
id: ID!
user: String!
message: String!
createdAt: AWSDateTime
}
This will allow us to display each user messages together with the creation date and time.
Next, let's push the configuration to our account:
amplify push
- Do you want to generate code for your newly created GraphQL API Y
- Choose the code generation language target: javascript
- Enter the file name pattern of graphql queries, mutations and subscriptions: (src/graphql/**/*.js)
- Do you want to generate/update all possible GraphQL operations - queries, mutations and subscriptions? Y
- Enter maximum statement depth [increase from default if your schema is deeply nested] 2
To view the service you can run the console
command the feature you'd like to view:
amplify console api
Next, we'll install the necessary dependencies:
npm install --save @aws-amplify/core @aws-amplify/datastore
Next, we'll generate the models to access our messages from our ChattyAPI
amplify codegen models
Important: DO NOT forget to generate models every time you introduce a change in your schema.
Now, the AWS Amplify CLI has generated the necessary data models and you will see a new folder in your source: models. The files in this folder hold your data model classes and schema.
<amplify-app>
|_ src
|_ models
Now that the GraphQL API and Data Models are created we can begin interacting with them!
The first thing we'll do is create a new message using the generated Data Models and save.
import { DataStore } from "@aws-amplify/datastore";
import { Chatty } from "./models";
await DataStore.save(
new Chatty({
user: "amplify-user",
message: "Hi everyone!",
createdAt: new Date().toISOString()
})
)
This will create a record locally in your browser and synchronise it in the background using the underlying GraphQL API.
Let's now see how we can query data using Amplify DataStore. In order to query our Data Model we will use a query and a predicate to indicate that we want all records.
import { DataStore, Predicates } from "@aws-amplify/datastore";
import { Chatty } from "./models";
const messages = await DataStore.query(Chatty, Predicates.ALL);
This will return an array of messages that we can display in our UI.
Predicates also support filters for common types like Strings, Numbers and Lists.
Find all supported filters at Query with Predicates
Now, let's look at how we can create the UI to create and display messages for our chat. We will use useReducer
hook to keep our state.
import React, { useEffect, useReducer } from 'react'
import './App.css';
import { withAuthenticator } from 'aws-amplify-react'
import { Auth } from 'aws-amplify'
import { DataStore, Predicates } from "@aws-amplify/datastore";
import { Chatty } from "./models";
import moment from 'moment'
const initialState = {
username: "",
messages: [],
message: ""
}
function reducer(state, action) {
switch(action.type) {
case 'setUser':
return { ...state, username: action.username }
case 'set':
return { ...state, messages: action.messages }
case 'add':
return { ...state, messages: [ ...state.messages, action.message ] }
case 'updateInput':
return { ...state, [action.inputValue]: action.value }
default: new Error()
}
}
async function getMessages(dispatch) {
try {
const messagesData = await DataStore.query(Chatty, Predicates.ALL);
const sorted = [...messagesData].sort((a, b) => -a.createdAt.localeCompare(b.createdAt))
dispatch({ type: 'set', messages: sorted })
} catch (err) {
console.log('error fetching messages...', err)
}
}
async function createMessage(state, dispatch) {
if (state.message === '') return;
try {
await DataStore.save(
new Chatty({
user: state.username,
message: state.message,
createdAt: new Date().toISOString()
})
);
state.message = '';
getMessages(dispatch);
} catch (err) {
console.log('error creating message...', err)
}
}
function updater(value, inputValue, dispatch) {
dispatch({ type: 'updateInput', value, inputValue })
}
function App() {
const [state, dispatch] = useReducer(reducer, initialState)
useEffect(() => {
Auth.currentAuthenticatedUser().then(user => {
dispatch({ type: 'setUser', username: user.username })
})
getMessages(dispatch)
}, [])
return (
<div className="app">
<div>
<input
type="text" placeholder="Enter your message..."
onChange={ e => updater(e.target.value, 'message', dispatch) }
value={ state.message }
/>
<button onClick={() => createMessage(state, dispatch)}>Create Message</button>
{ state.messages.map((message, index) => (
<div key={ message.id }>
<div> { message.user }</div>
<div> { message.message }</div>
<div> { moment(message.createdAt).format('HH:mm:ss')}</div>
</div>
))}
</div>
</div>
);
}
export default withAuthenticator(App, { includeGreetings: true })
One of the main advantages of working using Amplify DataStore is being able to run batch mutations without having to use a series of individual operations.
See below how we can use delete together with a predicate to remove all messages.
await DataStore.delete(Chatty, Predicates.ALL);
Next, let's see how we can create a subscription to subscribe to changes of data in our API.
To do so, we need to define the subscription, listen for the subscription, & update the state whenever a new piece of data comes in through the subscription.
// subscribe in useEffect
useEffect(() => {
Auth.currentAuthenticatedUser().then(user => {
dispatch({ type: 'setUser', username: user.username })
})
getMessages(dispatch)
const subscription = DataStore.observe(Chatty).subscribe(msg => {
console.log(msg.model, msg.opType, msg.element);
getMessages(dispatch)
});
return () => subscription.unsubscribe();
}, [])
For hosting, we can use the Amplify Console to deploy the application.
The first thing we need to do is create a new GitHub repo for this project. Once we've created the repo, we'll copy the URL for the project to the clipboard & initialize git in our local project:
git init
git remote add origin git@github.com:username/project-name.git
git add .
git commit -m 'initial commit'
git push origin master
Next we'll visit the Amplify Console in our AWS account at https://eu-west-2.console.aws.amazon.com/amplify/home.
Here, we'll click Get Started to create a new deployment. Next, authorize Github as the repository service.
Next, we'll choose the new repository & branch for the project we just created & click Next.
In the next screen, we'll create a new role & use this role to allow the Amplify Console to deploy these resources & click Next.
Finally, we can click Save and Deploy to deploy our application!
Now, we can push updates to Master to update our application.
If at any time, or at the end of this workshop, you would like to delete a service from your project & your account, you can do this by running the amplify remove
command:
amplify remove auth
amplify push
If you are unsure of what services you have enabled at any time, you can run the amplify status
command:
amplify status
amplify status
will give you the list of resources that are currently enabled in your app.
amplify delete
In order to follow this workshop you need to create and activate an Amazon Web Services account.
Follow the steps here
Message: The AWS Access Key Id needs a subscription for the service
Solution: Make sure you are subscribed to the free plan. Subscribe
Message: TypeError: fsevents is not a constructor
Solution: npm audit fix --force
Behaviour: data seems not to be synchronising with the cloud and or viceversa
Solution:
amplify update api
amplify push
Make sure you answer the following questions as
- Configure conflict detection? Y
- Select the default resolution strategy Auto Merge
- Do you want to override default per model settings? N