Amplify Console and CLI now work together — 🚀 Five new features

Nader Dabit
Nov 26 · 4 min read

Today the Amplify Console and Amplify CLI have launched 5 new features for improving how teams manage Amplify backend environments

The Amplify Console now offers visibility into backend environment resources created by the Amplify CLI, providing a central place for development teams to view and manage their backend environments. With this launch, the Amplify Console and CLI now work together — start a project in the CLI and visit the Console to view your backend environments; or deploy a fullstack sample in the Console and continue working on the project locally using the CLI. The Amplify CLI also released the amplify pull command to streamline team workflows for sharing backend environments across multiple frontends.

Feature 1: Entire team has visibility into backend environments created from the CLI in the Amplify Console
Running amplify init on a new project creates an Amplify app with a backend environment. An Amplify app now consists of frontend environments (Git branches or manual deploy environments) and backend environments.

When you add categories or deploy updates, typing amplify console opens the Console to show you the status of the deployment, along with deep links to the backend resources. Deep links allow you to visit each service console to check configurations or make edits - for example visiting the Cognito console to add/remove users, or visiting the AppSync console to test a query or mutation. Team members getting started or admins can view instructions on how to pull, clone, update, or delete environments.

Feature 2: Well-defined workflow for teams managing multiple frontends sharing the same backend
Developers building multiple frontends (for example, a React and Android app) can now follow a streamlined workflow to share the same amplify backend with the new amplify pull command. The command operates similar to a git pull, fetching the current backend environment definition from the cloud and updating the local environment to match that definition. Users have an option to pull the entire backend definition (infrastructure templates and metadata) or only the metadata (e.g. aws-exports.js) required to connect to the backend. If you’re building a mobile and web app in separate repositories, the recommended workflow is to keep the backend definition (the amplify folder) in only one of the repositories and pull the metadata (the aws-exports or awsconfiguration.json file) in the second repository to connect to the same backend.

Feature 3: Deploy fullstack apps from the Console, any developer on the team can run amplify pull to continue working locally
You can now get started with one of the fullstack samples in the Console (or from any one-click deploy sample) and pull the project locally using the amplify pull command. Deploying a fullstack sample creates an app with one frontend branch and one backend environment. To run the sample locally, clone the forked repository, install the Amplify CLI, and run amplify pull to fetch the backend definition.

Feature 4: Better visibility into fullstack CI/CD deployments
For apps with fullstack CI/CD (frontend + backend deployments), you can now see which backend is connected to which branch. Additionally, you can also edit this setting to point a frontend to a different backend. Connect a branch from your repository, pick a target backend environment (or create a new one), and the Amplify Console will setup continuous frontend+backend deployments.

Feature 5: Debug your Lambda functions directly from the Amplify Console
Amplify Console provides an easy way to debug Lambda functions that were added to your project via amplify add function. Developers often add logs to their Lambda function to pinpoint bugs or test payloads. You can debug all functions added to your project without leaving the Amplify Console, or to view older logs Amplify Console offers deeplinks to the CloudWatch logs.

Existing Amplify CLI users simply need to upgrade to the latest version to see their projects in the Console. If you were using both the Amplify Console and CLI together, simply trigger another build to have the backend environments show up in your app. If you’re new to Amplify, get started, here (

Thanks to Nikhil Swaminathan

Nader Dabit

Written by

Developer Advocate at AWS Mobile — Specializing in Teaching and Building React & React Native —

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade