Amplify

Framework that creates and manages a bunch of services in AWS, see also the alternative, Serverless.

By choosing Amplify as infrastructure and CI there are certain choises that are made and desisoins that are taken for you.

Notes:

  • Some adjustments to make nextjs fit to Amplify
    • "next build && next export" identifies that it´s a SSG (static site generation) app.
    • Amplify needs a trailing slash at the end of signin URI
  • User yarn and not npm
  • Need to use the "amplify" command from adding/removing components from your app and for CI commands.
  • Mono/multi-repo - Choose the best match for local dev and CI env.
  • Folder structure - Find a structure for best matching local dev and CI env

What took time:

  • Trying to remove phantom Amplify app
  • Change repo and path for multi-repo
  • Force push on master made it break

Errors:

  • There was an issue connecting to your repo provider, click "Reconnect repository" in General Settings, and then try your build again.
  • Module not found: Error: Can't resolve ‘./aws-exports' in ‘/codebuild/output/src049202397/src/demo-amplify-blue/src'

Warnings:

Build Settings

If you change from mono- to multi-repo, or react to nextjs, you might need to change baseDirectory and appRoot in the Build Settings to reflect the change.

AWS Amplify -> App Settings -> Build settings

version: 1
applications:
  - frontend:
      phases:
        preBuild:
          commands:
            - yarn install
        build:
          commands:
            - yarn run build
      artifacts:
        baseDirectory: build
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*
    appRoot:

Toolchain

Some AWS Amplify toolchain commands:

amplify

Used to configure AWS resources.

Install and configure for use:

npm install -g @aws-amplify/cli

amplify configure

Creating Amplify app:

Init:
amplify init

Add Authentication:
amplify add auth

Add API:
amplify add api

Continue working on another machine:
amplify pull --appId <appid> --envName dev

If you change something in the web-portal, you need to pull the changes:
amplify pull

If you change something with the cli, you need to push the changes:
amplify push

Continue working on another machine:
amplify pull --appId <appid> --envName dev

Status:
amplify status

User status:
amplify user status

amplifyPush.sh

Amplify UI

Services

Amplify