Giter VIP home page Giter VIP logo

aws-amplify / amplify-hosting Goto Github PK

View Code? Open in Web Editor NEW
440.0 83.0 117.0 319 KB

AWS Amplify Hosting provides a Git-based workflow for deploying and hosting fullstack serverless web applications.

Home Page: https://aws.amazon.com/amplify/hosting/

License: Apache License 2.0

Dockerfile 71.17% Shell 28.83%
hosting static-site aws ci-cd serverless fullstack web-application single-page-app custom-domain git

amplify-hosting's Introduction

AWS Amplify

current aws-amplify package version weekly downloads GitHub Workflow Status (with event) code coverage join discord

Reporting Bugs / Feature Requests

Open Bugs Feature Requests Closed Issues

Note aws-amplify 6 has been released. If you are looking for upgrade guidance click here

AWS Amplify is a JavaScript library for frontend and mobile developers building cloud-enabled applications

AWS Amplify provides a declarative and easy-to-use interface across different categories of cloud operations. AWS Amplify goes well with any JavaScript based frontend workflow and React Native for mobile developers.

Our default implementation works with Amazon Web Services (AWS), but AWS Amplify is designed to be open and pluggable for any custom backend or service.

Visit our Documentation site to learn more about AWS Amplify. Please see our Amplify JavaScript page within our Documentation site for information around the full list of features we support.

Features

Category AWS Provider Description
Authentication Amazon Cognito APIs and Building blocks to create Authentication experiences.
Analytics Amazon Pinpoint Collect Analytics data for your application including tracking user sessions.
REST API Amazon API Gateway Sigv4 signing and AWS auth for API Gateway and other REST endpoints.
GraphQL API AWS AppSync Interact with your GraphQL or AWS AppSync endpoint(s).
DataStore AWS AppSync Programming model for shared and distributed data, with simple online/offline synchronization.
Storage Amazon S3 Manages content in public, protected, private storage buckets.
Geo (Developer preview) Amazon Location Service Provides APIs and UI components for maps and location search for JavaScript-based web apps.
Push Notifications Amazon Pinpoint Allows you to integrate push notifications in your app with Amazon Pinpoint targeting and campaign management support.
Interactions Amazon Lex Create conversational bots powered by deep learning technologies.
PubSub AWS IoT Provides connectivity with cloud-based message-oriented middleware.
Internationalization --- A lightweight internationalization solution.
Cache --- Provides a generic LRU cache for JavaScript developers to store data with priority and expiration settings.
Predictions Various* Connect your app with machine learning services like NLP, computer vision, TTS, and more.
  • Predictions utilizes a range of Amazon's Machine Learning services, including: Amazon Comprehend, Amazon Polly, Amazon Rekognition, Amazon Textract, and Amazon Translate.

Getting Started

AWS Amplify is available as aws-amplify on npm.

To get started pick your platform from our Getting Started home page

Notice:

Amplify 6.x.x has breaking changes. Please see the breaking changes on our migration guide

Amplify 5.x.x has breaking changes. Please see the breaking changes below:

  • If you are using default exports from any Amplify package, then you will need to migrate to using named exports. For example:

    - import Amplify from 'aws-amplify';
    + import { Amplify } from 'aws-amplify'
    
    - import Analytics from '@aws-amplify/analytics';
    + import { Analytics } from '@aws-amplify/analytics';
    // or better
    + import { Analytics } from 'aws-amplify';
    
    - import Storage from '@aws-amplify/storage';
    + import { Storage } from '@aws-amplify/storage';
    // or better
    + import { Storage } from 'aws-amplify';
  • Datastore predicate syntax has changed, impacting the DataStore.query, DataStore.save, DataStore.delete, and DataStore.observe interfaces. For example:

    - await DataStore.delete(Post, (post) => post.status('eq', PostStatus.INACTIVE));
    + await DataStore.delete(Post, (post) => post.status.eq(PostStatus.INACTIVE));
    
    - await DataStore.query(Post, p => p.and( p => [p.title('eq', 'Amplify Getting Started Guide'), p.score('gt', 8)]));
    + await DataStore.query(Post, p => p.and( p => [p.title.eq('Amplify Getting Started Guide'), p.score.gt(8)]));
  • Storage.list has changed the name of the maxKeys parameter to pageSize and has a new return type that contains the results list. For example:

    - const photos = await Storage.list('photos/', { maxKeys: 100 });
    - const { key } = photos[0];
    
    + const photos = await Storage.list('photos/', { pageSize: 100 });
    + const { key } = photos.results[0];
  • Storage.put with resumable turned on has changed the key to no longer include the bucket name. For example:

    - let uploadedObjectKey;
    - Storage.put(file.name, file, {
    -   resumable: true,
    -   // Necessary to parse the bucket name out to work with the key
    -   completeCallback: (obj) => uploadedObjectKey = obj.key.substring( obj.key.indexOf("/") + 1 )
    - }
    
    + let uploadedObjectKey;
    + Storage.put(file.name, file, {
    +   resumable: true,
    +   completeCallback: (obj) => uploadedObjectKey = obj.key
    + }
  • Analytics.record no longer accepts string as input. For example:

    - Analytics.record('my example event');
    + Analytics.record({ name: 'my example event' });
  • The JS export has been removed from @aws-amplify/core in favor of exporting the functions it contained.

  • Any calls to Amplify.Auth, Amplify.Cache, and Amplify.ServiceWorker are no longer supported. Instead, your code should use the named exports. For example:

    - import { Amplify } from 'aws-amplify';
    - Amplify.configure(...);
    - // ...
    - Amplify.Auth.signIn(...);
    
    + import { Amplify, Auth } from 'aws-amplify';
    + Amplify.configure(...);
    + // ...
    + Auth.signIn(...);

Amplify 4.x.x has breaking changes for React Native. Please see the breaking changes below:

  • If you are using React Native (vanilla or Expo), you will need to add the following React Native community dependencies:
    • @react-native-community/netinfo
    • @react-native-async-storage/async-storage
// React Native
yarn add aws-amplify amazon-cognito-identity-js @react-native-community/netinfo @react-native-async-storage/async-storage
npx pod-install

// Expo
yarn add aws-amplify @react-native-community/netinfo @react-native-async-storage/async-storage

Amplify 3.x.x has breaking changes. Please see the breaking changes below:

If you can't migrate to aws-sdk-js-v3 or rely on [email protected], you will need to import it separately.

  • If you are using exported paths within your Amplify JS application, (e.g. import from "@aws-amplify/analytics/lib/Analytics") this will now break and no longer will be supported. You will need to change to named imports:

    import { Analytics } from 'aws-amplify';
  • If you are using categories as Amplify.<Category>, this will no longer work and we recommend to import the category you are needing to use:

    import { Auth } from 'aws-amplify';

DataStore Docs

For more information on contributing to DataStore / how DataStore works, see the DataStore Docs

amplify-hosting's People

Contributors

abhi7cr avatar amplify-console-bot avatar amplify-hosting-test-pdx-beta avatar anatonie avatar arundna avatar athena96 avatar behrooziaws avatar calavera avatar carvantes avatar cunneen avatar donkahn avatar ferdingler avatar hirochachacha avatar ihao8 avatar jay2113 avatar kahdojay avatar kellertk avatar litwicki avatar mauerbac avatar mlabieniec avatar mwarkentin avatar narrator avatar nimacks avatar noid11 avatar palpatim avatar rpheuts avatar siegerts avatar swaminator avatar victorccccc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

amplify-hosting's Issues

Domain activation is Failed - [BRIEF DESCRIPTION]

App Id: d1oiy80owuxn1r
Region: ap-south-1
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.

Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.

Additional information
Please add any other relevant information. Please feel free to include screenshots.

Amplify console "Bulk add rewrites and redirects" not working

Hi,

The forum is slow and unresponsive so please excuse for me posting here.

Describe the bug

A valid Bulk add rewrites and redirects (in code) via the console, fails to save although the code is valid and formatted correctly.

This has been broken for a while now so thought I should make it known to you.

I am using Google Chrome 75.0.3770.100 on MacOS Mojave 10.14.3.

To Reproduce

I have simply opened a new Amplify project and then tried to edit and save what is already given by Amplify.

Expected behavior

It would be nice if it actually saved valid code or gave some sort of validation error message.

Screenshots

Screenshot 2019-07-05 at 14 44 17

Web Application Firewall Integration

Is your feature request related to a problem? Please describe.
We are trying to use an Amplify-CLI / Amplify-Console powered app in Production. A business (security) requirement is that we use a Web Application Firewall. Currently there is no way to implement that with the Amplify Console, so we will have to host our production app using a different service.

See: #8

We are a little sad about this, as the Amplify Console has 90% of the functionality needed for hosting a production level app, but "Only Basic Auth security" is a major deal breaker for us.

Describe the solution you'd like
Allow us to create our own CloudFront distribution, with an associated WAF, and direct the Amplify Console Hosting through that domain, instead of the automatically generated "always public" domain (e.g. production.abcxyz.amplifyapp.com)

Stuck `Retrieving deployment details...`

Describe the bug
My Amplify console is stuck with the message:

Retrieving deployment details...

To Reproduce
I was trying to deploy an S3 bucket with a GatsbyJS application, this is what I did:

  1. Create a Gatsby project and an S3 bucket using Amplify
gatsby new my-gatsby-site
cd my-gatsby-site

amplify init
amplify add storage
amplify push
  1. Deploy to S3 using the Gatsby S3 plugin:
    https://github.com/jariz/gatsby-plugin-s3#usage
npm i gatsby-plugin-s3
npm run build && npm run deploy
  1. In the Amplify Console, choose Deploy without a Git provider.
  2. For Method, choose Amazon S3, and for Bucket, choose the bucket you just created.

Expected behavior
The S3 bucket content is deployed

Has anyone used the aws SDK to create an Amplify Deployment app with CodeCommit?

** Which Category is your question related to? **
Amplify deploy

** What AWS Services are you utilizing? **
Amplify and CodeCommit

** Provide additional details e.g. code snippets **

I'm trying to use the JavaScript SDK to create an Amplify Deploy app connected to a CodeCommit repo.

I've tried everything I can think of and it kind of works but each deployment pulls in an empty repo.

When I repeat the same steps via console, it works just fine.

Has anyone created an Amplify app connected to CodeCommit using the cli or sdk or headless in any way?

Hosting a Javascript bundle for use on third-party sites

** Please describe which feature you have a question about? **
Does Amplify hosting have some kind of measure in place to prevent/throttle the use of assets outside of the Amplify domain name? I’m trying to host a Javascript bundle that will be placed on many different sites but it’s not loading successfully, but it works fine when loading from my local machine or if it is hosted on a public S3 bucket.

** Provide additional details**

  • Upload a JS bundle to Amplify and attempt to load it on a third-party domain. Script attempts to load but ultimately times out/browser runs out of memory

  • Upload the same bundle to S3 public bucket and load it on a third-party domain. note how it works as expected

How to reset amplify build - envCache

Describe the bug
I re-created dev environment using amplify cli and when i pushed the changes, amplify console was picking old stackInfo from envCache. I can't find any documentation of how to prevent using old cached values. Below are the logs:-

logs

//Getting Amplify CLI Cloud-Formation stack info from environment cache
2
019-03-27T13:32:53.066Z [INFO]: # Start initializing Amplify environment: dev
2019-03-27T13:32:53.068Z [INFO]: STACKINFO={
"awscloudformation": {
"AuthRoleName": "old-authRole",
"UnauthRoleArn": "arn:aws:iam::old-unauthRole",
"AuthRoleArn": "arn:aws:iam::old-authRole",
"Region": "us-east-1",
"DeploymentBucketName": "old-deployment",
"UnauthRoleName": "old-unauthRole",
"StackName": "old",
"StackId": "arn:aws:cloudformation:us-east-1:227484579606:stack/old"
},
"categories": {
"auth": {
"cognitols": {}
}
}
}
// Importing Amplify environment: dev (amplify env import)
2019-03-27T13:32:55.802Z [INFO]: Successfully added environment from your project
2019-03-27T13:32:55.809Z [INFO]: # Initializing existing Amplify environment: dev (amplify init)
2019-03-27T13:32:57.242Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2019-03-27T13:32:58.538Z [WARNING]: - Initializing your environment: dev
2019-03-27T13:32:58.612Z [WARNING]: ✖ There was an error initializing your environment.
2019-03-27T13:32:58.613Z [INFO]: init failed
2019-03-27T13:32:58.616Z [INFO]: { NoSuchBucket: The specified bucket does not exist

CDK Support

This is more of a placeholder, to surface existing work: aws/aws-cdk#3209

I'm currently in the final stages of the CDK construct

domain link accessible on my system but not on colleague

Note: Intermediate in Front-end development but Noobie in Domain setup and DB setup

Describe the bug
When using amplify without custom domain, my link is genrated as "https://production.*********.amplifyapp.com" and works fine as expected. However, Setting up third-party domain is painful. I agree with the level of frustration mentioned in this isse but not the language.

Where I am stuck? well, I added my domain to amplify, click on "Actions - > View DNS records" and copy-pasted everything in DNS record at Google domain except the "@ ANAME" in Google domain's DNS setting.

The link sudhirkaushk.com opens fine on my system but not on my friends'.

Screenshots
If applicable, add screenshots to help explain your problem.
site fail

Passing values with webhooks?

** Please describe which feature you have a question about? **
Amplify Incoming Webhooks

** Provide additional details**
Is it possible to add data to the JSON payload that gets sent when triggering the webhook and have it available in the build?

My use case is to build a tool to trigger builds with a bit of information that the build needs. Is this possible? How would I access the post body in the build?

Custom Domain, cannot access GraphQL API

Issue/question
After adding a custom domain, I am getting a 401 status when sending requests to my graphql API.

Error message
Uncaught (in promise) Error: Network error: Response not successful: Received status code 401

Additional information
Warning: I am very much in the beginning stages of creating this application.

I created my react amplify project using the CLI. I want all users to be able to read the data and authenticated users to be able to create, update, and delete. Therefore, I set up the API to use an API key. I am planning on using Cognito User Pools for authenticating users later on.

I recently added the app to the Amplify Console via Github. I set the dev branch to deploy to a dev environment and the master branch to deploy to a prod environment.

I added my custom domain which is registered with GoDaddy (so I had to set up Forwarding). The domain is liked to the master branch.

When I go to my custom domain, I get the 401 error. This is the same for the generated master and dev urls.

When I run amplify publish from the CLI, I do not get the 401 error when I check the url that publish deploys to.

The amplify.yml file for the build looks like this:
Screen Shot 2019-08-13 at 8 04 20 PM

When I check the logs from the last deployment, I do not see anything about setting the API key. I'm worried the API key just isn't being set or that the forwarding is causing an issue.

Any assistance would be great!

Too many redirects

Describe the bug
I deployed my simple react.js/babel/webpack application to amplify and cannot connect to the app due to "too many redirects"

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://stable.d2i4qqadma0z0i.amplifyapp.com

Expected behavior
You will see ERR_TOO_MANY_REDIRECTS on Chrome or Safari. It doesn't work on Edge or IE either.

Sample code
URL to the Github with the branch: https://github.com/yfaney/github-review-dashboard/tree/stable

Additional Context
Cleaning up cookies didn't help.

Screenshot
Screen Shot 2019-08-01 at 9 07 44 AM
Screen Shot 2019-08-01 at 9 07 58 AM

SSL verification is Failed - [BRIEF DESCRIPTION]

App Id: d45uutat1g8mv
Region: ap-northeast-2
Step: SSL verification
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.

Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.

Additional information
Please add any other relevant information. Please feel free to include screenshots.

[Feature request] Add support for self-hosted Gitlab(CE) or GitHub Enterprise

Feature request: add support for the self-hosted version of Gitlab (CE).

Currently the Amplify console has support for Gitlab.com, but not for the self-hosted variant.
At this moment it is unfortunately a dealbreaker why we do not yet use Amplify Console for all projects/sites.
As a workaround we now use the S3 and CodeCommit (by using the mirror repository function of Gitlab).

[DynamoDBEnableServerSideEncryption] do not exist in the template

Describe the bug
I am not sure if this is AmplifyCLI issue or Console issue. I am trying to deploy using Amplify Console and getting the [DynamoDBEnableServerSideEncryption] do not exist in the template error.
It didn't happen until recently and we haven't change the cloud formation template generated by the AmplifyCLI.
amplify push is working fine.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Amplify Console'
  2. Finish deploy setting
  3. Hit 'deploy' and See error
                                 # Starting phase: build
                                 # Executing command: amplifyPush --simple
2019-08-07T16:41:00.824Z [INFO]: # Getting Amplify CLI Cloud-Formation stack info from environment cache
2019-08-07T16:41:00.853Z [INFO]: # Start initializing Amplify environment: dev
2019-08-07T16:41:00.855Z [INFO]: # Initializing new Amplify environment: dev (amplify init)
2019-08-07T16:41:14.816Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2019-08-07T16:41:17.090Z [INFO]: 
2019-08-07T16:41:17.092Z [INFO]: For more information on AWS Profiles, see:
                                 https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html
2019-08-07T16:41:17.162Z [WARNING]: - Initializing your environment: dev
2019-08-07T16:41:17.708Z [WARNING]: ✔ Initialized provider successfully.
2019-08-07T16:41:24.752Z [INFO]: Could not read cloudformation template at path: /codebuild/output/src150497733/src/handbook/amplify/backend/api/nhb/build/cloudformation-template.json
2019-08-07T16:41:24.863Z [WARNING]: - Updating resources in the cloud. This may take a few minutes...
2019-08-07T16:41:30.488Z [INFO]: 
2019-08-07T16:41:30.492Z [INFO]: UPDATE_IN_PROGRESS nhb-dev-20190802090817 AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:25 GMT+0000 (Coordinated Universal Time) User Initiated
2019-08-07T16:41:30.610Z [INFO]: 
2019-08-07T16:41:30.610Z [INFO]: UPDATE_IN_PROGRESS authnhbcognito AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:30 GMT+0000 (Coordinated Universal Time)
2019-08-07T16:41:35.408Z [INFO]: 
2019-08-07T16:41:35.411Z [INFO]: UPDATE_COMPLETE    authnhbcognito       AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:31 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS apinhb               AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:33 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionnhbusersfunc AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:33 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_FAILED      apinhb               AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:33 GMT+0000 (Coordinated Universal Time) Parameters: [DynamoDBEnableServerSideEncryption] do not exist in the template
2019-08-07T16:41:35.593Z [INFO]: 
2019-08-07T16:41:35.594Z [INFO]: UPDATE_IN_PROGRESS          nhb-dev-20190802090817-functionnhbusersfunc-1L6QD27RBKVX AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:33 GMT+0000 (Coordinated Universal Time) User Initiated
                                 UPDATE_ROLLBACK_IN_PROGRESS nhb-dev-20190802090817-functionnhbusersfunc-1L6QD27RBKVX AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:34 GMT+0000 (Coordinated Universal Time) Initiated by parent stack
2019-08-07T16:41:45.410Z [INFO]: 
2019-08-07T16:41:45.412Z [INFO]: UPDATE_FAILED functionnhbusersfunc AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:44 GMT+0000 (Coordinated Universal Time) Resource update cancelled
2019-08-07T16:41:45.715Z [INFO]: 
2019-08-07T16:41:45.716Z [INFO]: UPDATE_ROLLBACK_IN_PROGRESS nhb-dev-20190802090817 AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:45 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [functionnhbusersfunc, apinhb].
2019-08-07T16:41:55.422Z [INFO]: 
2019-08-07T16:41:55.424Z [INFO]: UPDATE_IN_PROGRESS authnhbcognito       AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:51 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    authnhbcognito       AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:51 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE    apinhb               AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:52 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS functionnhbusersfunc AWS::CloudFormation::Stack Wed Aug 07 2019 16:41:52 GMT+0000 (Coordinated Universal Time)
2019-08-07T16:42:25.483Z [INFO]: 
2019-08-07T16:42:25.485Z [INFO]: UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS nhb-dev-20190802090817-functionnhbusersfunc-1L6QD27RBKVX AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:21 GMT+0000 (Coordinated Universal Time)
2019-08-07T16:42:30.432Z [INFO]: 
2019-08-07T16:42:30.434Z [INFO]: UPDATE_COMPLETE                              functionnhbusersfunc   AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:26 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS nhb-dev-20190802090817 AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:27 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS                           apinhb                 AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:28 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE                              apinhb                 AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:29 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_IN_PROGRESS                           functionnhbusersfunc   AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:29 GMT+0000 (Coordinated Universal Time)
2019-08-07T16:42:30.492Z [INFO]: 
2019-08-07T16:42:30.494Z [INFO]: UPDATE_ROLLBACK_COMPLETE nhb-dev-20190802090817-functionnhbusersfunc-1L6QD27RBKVX AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:30 GMT+0000 (Coordinated Universal Time)
2019-08-07T16:42:40.438Z [INFO]: 
2019-08-07T16:42:40.440Z [INFO]: UPDATE_COMPLETE functionnhbusersfunc AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:39 GMT+0000 (Coordinated Universal Time)
2019-08-07T16:42:45.441Z [INFO]: 
2019-08-07T16:42:45.444Z [INFO]: UPDATE_IN_PROGRESS       authnhbcognito         AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:40 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_COMPLETE          authnhbcognito         AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:41 GMT+0000 (Coordinated Universal Time)
                                 UPDATE_ROLLBACK_COMPLETE nhb-dev-20190802090817 AWS::CloudFormation::Stack Wed Aug 07 2019 16:42:41 GMT+0000 (Coordinated Universal Time)
2019-08-07T16:42:55.505Z [WARNING]: Error updating cloudformation stack
2019-08-07T16:43:00.514Z [INFO]: Following resources failed
2019-08-07T16:43:00.517Z [INFO]: init failed
2019-08-07T16:43:00.518Z [WARNING]: ✖ An error occurred when pushing the resources to the cloud
                                    ✖ There was an error initializing your environment.
2019-08-07T16:43:00.520Z [INFO]: { ResourceNotReady: Resource is not in the state stackUpdateComplete
                                 at constructor.setError (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/resource_waiter.js:182:47)
                                 at Request.CHECK_ACCEPTORS (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/resource_waiter.js:44:12)
                                 at Request.callListeners (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
                                 at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
                                 at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
                                 at Request.transition (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
                                 at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
                                 at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
                                 at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
                                 at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
                                 message: 'Resource is not in the state stackUpdateComplete',
                                 code: 'ResourceNotReady',
                                 retryable: false,
                                 time: 2019-08-07T16:42:55.504Z,
                                 statusCode: 200,
                                 retryDelay: 30000 }
2019-08-07T16:43:00.598Z [ERROR]: !!! Build failed
2019-08-07T16:43:00.599Z [ERROR]: !!! Non-Zero Exit Code detected
2019-08-07T16:43:00.600Z [INFO]: # Starting environment caching...
2019-08-07T16:43:00.600Z [INFO]: # Environment caching completed
Terminating logging...

Usage with CloudFormation and CodeCommit

I've created a CodeCommit repository with CFN and committed my Expo/Amplify project into it.

AWSTemplateFormatVersion: '2010-09-09'
Description: 'Creates a CodeCommit repository'

Parameters: 
  UserNameParam: 
    Type: String

Resources:
  Repository:
    Type: AWS::CodeCommit::Repository
    Properties: 
      RepositoryName: xyz

  Group:
    Type: AWS::IAM::Group
    Properties : 
      GroupName : xyz-devs
      Policies:
        - PolicyName: xyz-repository-access
          PolicyDocument:
            Version: "2012-10-17"
            Statement:
              - Effect: Allow
                Resource: !GetAtt Repository.Arn
                Action:
                  - "codecommit:*"

  UserToGroupAddition:
    Type: AWS::IAM::UserToGroupAddition
    Properties: 
      GroupName: !Ref Group
      Users: 
        - !Ref UserNameParam

Outputs:
  CloneUrl:
    Description: The URL where the created repository is available.
    Value: !GetAtt Repository.CloneUrlSsh

Then I wanted to connect the Amplify Console to this repository, also with CFN.

AWSTemplateFormatVersion: '2010-09-09'
Description: 'Connects a CodeCommit repository to the Amplify Console'

Resources:

  DevBranch:
    Type: AWS::Amplify::Branch
    Properties: 
      BranchName: master
      AppId: !GetAtt App.AppId
      EnableAutoBuild: yes
      EnvironmentVariables:
        - Name: USER_BRANCH
          Value: dev

  App:
    Type: AWS::Amplify::App
    Properties:
      Name: Xyz
      Repository: https://git-codecommit.eu-west-1.amazonaws.com/v1/repos/xyz
      BuildSpec: |
        version: 0.1
        backend:
          phases:
            build:
              commands:
                - amplifyPush --simple
        frontend:
          phases:
            preBuild:
              commands:
                - nvm use 10
                - npm ci
            build:
              commands:
                - npm run build
          artifacts:
            baseDirectory: web-build
            files:
              - '**/*'
          cache:
            paths:
              - node_modules/**/*
              - $(npm root --global)/**/*

But when I run a deploy I get the following error:

2019-08-06T12:21:20.686Z [INFO]: fatal: unable to access 'https://git-codecommit.eu-west-1.amazonaws.com/v1/repos/xyz/': The requested URL returned error: 403
2019-08-06T12:21:20.692Z [ERROR]: !!! Unable to clone repository.

I guess the Amplify backend service role that was created for me is used to do the checkout?
But it has Admin rights, so it should be able to access the repository, right?

amplify publish

Please describe which feature you have a question about?
When my project is deployed through the console, it is not serving my static build but seems to run npm start

Provide additional details
Not sure what I'm doing wrong, but I expect that when amplify runs my build command, it will host
my web-build directory on S3. What I see when I visit the app url is my app running in development mode.

Amplify Console Build fails - Error: ENOENT: no such file or directory

Describe the bug
Cannot get my project to build using the amplify console. No obvious causes for the build to fail.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new project using amplify init
  2. Run amplify add api to create a new graphQL API. In my case I provided my own schema from another AWS AppSync project.
  3. amplify push your project to the amplify-console service.
  4. Click "redeploy this version" from the amplify console.

Amplify console backend Logs:
build_fails

Expected behavior
I expect the app to build without errors.

Additional context
I found someone with a similar issue and they mentioned that specifying the npm version in the build script could alleviate the problem along with uninstalling and re-installing the amplify-cli. This hasn't worked for me.

Sample code
amplify.yml

version: 0.1
backend:
  phases:
    build:
      commands:
        - nvm use 10
        - npm uninstall -g @aws-amplify/cli 
        - rm -rf node_modules/@aws-amplify/
        - npm install -g @aws-amplify/[email protected]
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Switching Cloudfront+S3 => Amplify with custom domain requires downtime

Region: eu-west-2
Step: Final Step
Status: Common issue across apps

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
This is not an issue with a specific domain, just one we've encountered during the migration of several static sites from S3 bucket + Cloudfront CDN hosting to AWS Amplify.

AWS Amplify persistently fails on the last step of domain activation when the domain is already associated as a cname on another resource (Cloudfront in our case). The only way to resolve this is to seemingly deactivate the cname(s) in Cloudfront, wait for the deployment to complete, then remove and re-add the domain to the chosen Amplify App.

This is far from ideal as it is commonplace for us to migrate our projects from the old S3+Cloudfront setup to Amplify, but this means we must have downtime in order for the domain to successfully be transferred over.

Additional Information
Route53 is the DNS provider we've been using in all cases.

Can I access the CloudFront distribution with Amplify Console hosting?

How does this fit in with aws-amplify/cli ? cli implies console to a lot of people.

I just provisioned the Hugo example.

It created https://github.com/kaihendry/hugo-example but I don't see any AWS CI related files like a buildspec.yml. I expected to be able to tweak some declarative file and not spend time in the clunky Web UI to provision more sites.

After provisioning the hugo-example from my account I don't see any Cloudformation stack or CloudFront distribution or S3 bucket. Is this to be expected?

Top 20 referrers

If we deploy to our own CloudFront distribution, we can easily see the top 20 referrers.

I'd like to see the same report that is available on CloudFront for the top 20 referrers. It's fine for a period of time (eg last day, last 7 days).

Additional context
This is important to us for change management and product management purposes.

Integrating an automated test runner into the Amplify Build process.

Is your feature request related to a problem? Please describe.
I would like to run my automated jest tests as part of the Amplify Console build process.

Describe the solution you'd like
A phase in the Build Settings like:

    preBuild:
      commands:
        - npm install
    test:
      commands:
        - npm test --watchAll=false
    build:
      commands:
        - npm run build

Describe alternatives you've considered
Coupling Amplify Console with TravisCI or similar, but since I don't need the Build features from Travis CI, seems like a waste.

Additional context
I have been using the Amplify Console as a CI tool and it works really well. I would really like to utilize our test runner to catch failed tests automatically and abort a build.

Additionally, I would really like to be able to integrate the Amplify Console with the Github Checks API, so that we can catch failures at the PR review step in our process.

Inconsistent resource ARN syntax, breaks IAM policy

Describe the bug
Was attempting to create an IAM policy to grant console access to developers who can trigger builds via GitHub commits, found that the resource ARN patterns for Amplify resources are inconsistently applied.

To Reproduce

  1. Using the IAM policy generator, create a policy which grants all Amplify actions on any amplify resource. Produces the following:

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Sid": "VisualEditor0",
                "Effect": "Allow",
                "Action": [
                    "amplify:CreateApp",
                    "amplify:ListApps"
                ],
                "Resource": "*"
            },
            {
                "Sid": "VisualEditor1",
                "Effect": "Allow",
                "Action": "amplify:*",
                "Resource": "arn:aws:amplify:*:*:apps/*/branches/*"
            },
            {
                "Sid": "VisualEditor2",
                "Effect": "Allow",
                "Action": "amplify:*",
                "Resource": [
                    "arn:aws:amplify:*:*:apps/*/domains/*",
                    "arn:aws:amplify:*:*:apps/*/branches/*/jobs/*"
                ]
            },
            {
                "Sid": "VisualEditor3",
                "Effect": "Allow",
                "Action": "amplify:*",
                "Resource": "arn:aws:amplify:*:*:apps/*"
            }
        ]
    }
  2. Create an account role, attach the previously created policy.

  3. Assume the role and load the Amplify console.

  4. Click into an Amplify application. Nothing loads in the list of branches.

  5. Open the browser's JS console and look for 403s, which will look like:

    ...does not have amplify:ListDomainAssociations on resource: arn:aws:amplify:<REGION>:<ACCOUNT_ID>:/apps/<APP_HASH>/domains
    
    ...does not have amplify:ListWebhooks on resource: arn:aws:amplify:<REGION>:<ACCOUNT_ID>:/apps/<APP_HASH>/webhooks
    
  6. Note the ARN pattern difference (slash prepended to apps):

    • In the IAM statement, the resource ARNs are arn:aws:amplify:*:*:apps/...
    • In the 403 message, the resource ARNs are arn:aws:amplify:<REGION>:<ACCOUNT_ID>:/apps/...
  7. Return to primary role

  8. Alter the IAM policy statement to prepend a slash to apps in all resource ARN patterns

  9. Reassume the test role using the policy

  10. Reload the Amplify console. Some items load, but not all.

  11. In the JS console, find 403 messages like:

    ...does not have amplify:ListBranches on resource: arn:aws:amplify:<REGION>:<ACCOUNT_ID>:apps/<APP_HASH>/branches/*
    
    ...does not have arn:aws:amplify:<REGION>:<ACCOUNT_ID>:apps/<APP_HASH>/branches/*
    
  12. Return to primary role, alter IAM policy to be as follows:

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Sid": "VisualEditor0",
                "Effect": "Allow",
                "Action": [
                    "amplify:CreateApp",
                    "amplify:ListApps"
                ],
                "Resource": "*"
            },
            {
                "Sid": "VisualEditor1",
                "Effect": "Allow",
                "Action": "amplify:*",
                "Resource": [
                    "arn:aws:amplify:*:*:/apps/*/branches/*",
                    "arn:aws:amplify:*:*:apps/*/branches/*"
                ]
            },
            {
                "Sid": "VisualEditor2",
                "Effect": "Allow",
                "Action": "amplify:*",
                "Resource": [
                    "arn:aws:amplify:*:*:/apps/*",
                    "arn:aws:amplify:*:*:apps/*"
                ]
            },
            {
                "Sid": "VisualEditor3",
                "Effect": "Allow",
                "Action": "amplify:*",
                "Resource": [
                    "arn:aws:amplify:*:*:/apps/*/domains/*",
                    "arn:aws:amplify:*:*:apps/*/domains/*",
                    "arn:aws:amplify:*:*:/apps/*/branches/*/jobs/*",
                    "arn:aws:amplify:*:*:apps/*/branches/*/jobs/*"
                ]
            }
        ]
    }    
  13. Reassume test role, reload Amplify console--all features appear to be loading.

Expected behavior

Expected the IAM policy creation wizard to produce a policy capable of granting access to all Amplify actions and resources.

Additional context

Looks like there are some inconsistent resource ARN patterns in the codebase or in IAM, no idea how that all shakes out. Presumably need to standardize on whether or not to use a leading slash before apps in the pattern.

Sample code

I think it's pretty clear from the repro, but @ me if you need info.

Amplify Console Backend Role

** Please describe which feature you have a question about? **
When setting up the backend role for the Amplify Console, the docs use the AdministratorAccess policy.

We try to limit the usage of that blanket policy, what exact IAM permissions does that role need?

SSL verification is Running - [BRIEF DESCRIPTION]

App Id: d1dmgnwdmwopvw
Region: us-east-1
Step: SSL verification
Status: Running

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
SSl verification pending, message :
"
We validated that the CNAME record exists in your DNS file. We will now verify ownership of the domain. If this takes longer than 8 hours, please create an issue in our GitHub issue tracker.
"

Error message
No error, just pending
Note: Be sure to check the message for sensitive information.

Additional information
Im using Cloudflare

SSL verification is Running - [BRIEF DESCRIPTION]

App Id: d3m0wg6wtlsyor
Region: us-east-2
Step: Domain Activation
Status: Complete

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
I recently added a domain, matterintake.mosaic-consulting.com, and the first time I did it, it worked. I was able to use my subdomain (root excluded). Then, someone on my team didn't realize that I had done that, and they deleted it. I had to readd the domain. After readding the domain exactly the same and going through the same steps, it no longer works. It got all the way through domain activation, but going to my domain does not load anything anymore.

Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.

Additional information
Please add any other relevant information. Please feel free to include screenshots.
domain1
domain2

Custom domain for pattern-based branch deployments

Is your feature request related to a problem? Please describe.
The new pattern-based branch deployments are neat but they get endpoint only from builtin amplifyapp.com domain.

Describe the solution you'd like
I'd like have an option to use my custom domain also on pattern-based branch deployments.

Add a pre-provision filter to determine whether build should commence

Is your feature request related to a problem? Please describe.
I'm using a monorepo on GitHub and and have CI/CD set up in Amplify console with several apps watching the same repo/branch. I'm currently exiting builds with a custom pre-build script that determines if the changes affect the current Amplify app, and if not, I exit with a non-zero status code which marks the build as failed, but more accurately, the build should have never began at all and I am likely being charged for the instance being provisioned.

Describe the solution you'd like
A clear and concise description of what you want to happen.
I'd like to have the ability to run a script from the .yml before provisioning to determine whether the build should happen at all, and also a way to exit gracefully without marking the build as errored.

How to run functional tests in build script?

** Please describe which feature you have a question about? **
I'm trying to run functional tests with TestCafe when building. Here are my build settings:

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

And here is how the "validate" script looks like:

"validate": "yarn -s unit-tests && yarn -s lint && yarn -s functional-tests",
"functional-tests": "testcafe 'chrome:headless' src/functional-tests/",

But this throws the error:

2019-08-08T15:36:17.385Z [WARNING]: ERROR Unable to find the browser. "chrome:headless" is not a browser alias or path to an executable file.

How can I add Chrome to the Amplify console, or run functional tests with it?

** Provide additional details**

Backend build warning: "Could not read cloudformation template at path"

Which Category is your question related to?

CLI and Console at the same time.

What AWS Services are you utilizing?

I'm running multienv, got the usual dev and prod. Project is live. To push API or function changes faster I like to use the CLI. To release in full and to deploy to production, I like to merge to my master branch and have it trigger the automatic production build. For testing major changes before deploying to production, I like to push to my develop branch and have it build also using the Console.

Here's what I'm confused about:

  • The Console seems to not really care much about the overall state and just pushes according to the CloudFormation templates pulled from the branch, but could it be missing some files that are ignored in my Git?
  • The CLI seems to get out of sync and not know what's the current status when Console is also deploying
  • Doing amplify env pull does not get the CLI up to speed if I my latest deployment is with the Console. Only when I do amplify push, the CLI will say "No Change" for all functions and API's.

So my question is. How do I bring both in sync and do I risk any bad overwrites doing amplify push if I don't do amplify env pull after having deployed with Console?

I thought amplify env pull would also pull the cloud down? amplify pull env --restore seems a bit dangerous and I'm worried it could overwrite locally changed files?

Possible to use custom SSL certificate?

Regarding the provisioning of SSL certificates for Amplify apps. I can see the SSL certificate is usually provisioned by AWS Certificate Manager (ACM). ACM allows you to import external certs, but I can't see an option anywhere to choose the cert that is used by the Amplify app.

Environment mirroring

Is your feature request related to a problem? Please describe.
Sometimes, it is helpful to mirror an environment (i.e. mirroring production on pre-production or mirroring dev on feature branches specific environments)

Describe the solution you'd like
It would be nice if the console can show options to mirror an environment on a branch pattern (like the new automated branch autodetection flow)

Additional context
I don't know if this is too difficult since it may depend on N+ AWS categories, another idea will be to provide a seeding mechanism.

amplify push with new env doesn't reflect the env list in Amplify Deploy immediately

Describe the bug
running amplify env add doesn't reflect the env list available in the Amplify Console.
the issue also remains same even after amplify push
(Some of the env are showing up correctly)

To Reproduce
Steps to reproduce the behavior:

  1. create 3 env
  2. create a new branch & checkout
  3. add new env based off of one of them
  4. commit and push the new branch
  5. go to Amplify Console and "connect branch"
  6. env list in the Amplify Console is not up to date.
  7. run amplify push
  8. env list in the Amplify Console is still not up to date.

Expected behavior
amplify env add should update the env list on Amplify Console immediately

Screenshots
Screen Shot 2019-07-18 at 2 13 34 PM
Screen Shot 2019-07-18 at 2 13 01 PM
Screen Shot 2019-07-18 at 2 18 18 PM

Saving rewrites and redirects to configuration file?

** Please describe which feature you have a question about? **
Rewrites and Redirects

** Provide additional details**
I plan on having a bunch of rewrites and redirects and would feel more secure if I could save them in my repository. Is it possible to have the rewrite data saved in a config file like the amplify.yml file?

[Feature request] IP allowlisting: How to block specific IPs from accessing the backend?

Note: If your question is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

** Which Category is your question related to? **
Security

** What AWS Services are you utilizing? **
Appsync, Amplify, Cloudfront, Lambda

** Provide additional details e.g. code snippets **
I created an amplify graphql project thru AWS Amplify pipeline with custom domain. I need to block some ip ranges for some security reasons. Is it currently possible to add allowed IP ranges thru paramaters/templates?

SSL verification is Failed - When trying to add domain to blog from Amplify Console

App Id: d1dxfezyi4jluz
Region: us-east-2
Step: SSL verification
Status: Failed

Issue/question
I keep getting an error when trying to attach a domain name to a new blog via Amplify Console.

Error message
The status of this certificate request is "Failed". One or more domain names have failed DNS validation. Please check your domain name validation routes and try re-adding the custom domain to your app.

Additional information
The CNAMEs appear to resolve in WhatIsMyDNS.net. (Except for one in China.) It's been 24 hours since the CNAMEs started resolving.

Amplify console build successful but fails to move to deploy

Hi,

I am using Amplify to build my companies new website using Gatsby and it has been a huge success until Thursday (16th May 2019).

The build logs say that our app has built successfully however, the Amplify console status is saying that they build has failed. After Googling the issue I found this solution on Github aws-amplify/amplify-cli#1415.

It states that the cache was too large - so I removed the cache rules in the build settings Yaml file (in code and in the console) but still no luck. Without any additional logging, I cannot pinpoint the issue other than it could possibly be within Amplify itself.

Note: I get a green notification bar at the top say that the build was successful.

2019-05-20T11:58:42.054Z [INFO]: success run page queries — 126.669 s — 200/200 1.58 queries/second
2019-05-20T11:58:42.067Z [INFO]: success write out page data — 0.007 s
2019-05-20T11:58:42.069Z [INFO]: success write out redirect data — 0.001 s
2019-05-20T12:04:20.109Z [INFO]: 
2019-05-20T12:04:20.308Z [INFO]: success Build manifest and related icons — 0.097 s
2019-05-20T12:04:20.309Z [INFO]: success onPostBootstrap — 0.099 s
                                 info bootstrap finished - 494.906 s
2019-05-20T12:05:12.082Z [INFO]: success Building production JavaScript and CSS bundles — 51.745 s
2019-05-20T12:05:23.194Z [INFO]: success Building static HTML for pages — 11.111 s — 200/200 117.51 pages/second
2019-05-20T12:05:23.241Z [INFO]: info Done building in 557.838 sec
2019-05-20T12:05:23.517Z [INFO]: Done in 572.20s.
2019-05-20T12:05:23.522Z [INFO]: # Completed phase: build
                                 # Starting phase: postBuild
2019-05-20T12:05:23.525Z [INFO]: # Executing command: du -sh ./public/
2019-05-20T12:05:23.556Z [INFO]: 995M	./public/
2019-05-20T12:05:23.557Z [INFO]: # Executing command: du -sh ./node_modules/
2019-05-20T12:05:23.669Z [INFO]: 518M	./node_modules/
2019-05-20T12:05:23.669Z [INFO]: # Completed phase: postBuild
2019-05-20T12:05:23.670Z [INFO]: ## Build completed successfully
2019-05-20T12:05:23.671Z [INFO]: # Starting caching...
2019-05-20T12:05:23.761Z [INFO]: Creating cache artifact...
2019-05-20T12:06:08.305Z [INFO]: Uploading cache artifact...
2019-05-20T12:06:14.769Z [INFO]: # Caching completed

The ARN is: arn:aws:amplify:eu-west-1:193471113837:apps/d30v7a1bgav5mq

Any ideas?

Pattern-based branch deployments, behaviour on branch deletion

Is your feature request related to a problem? Please describe.
Pattern-based branch deployments allows ephemeral deployments but the deployments remain there until they're manually removed, despite the source branches are deleted from VCS.

Describe the solution you'd like
I'd like to have an option to delete deployments automatically, if and when the source branch is deleted from VCS.

Wildcard subdomains in AWS Amplify

So we recently decided to remove server side rendering from our react app to use Amplify, since it provides us all that we need (serverless, high availabilty, speed and no need to test in two environments).

However now I have a question regarding how to configure AWS Amplify to have a wildcard CNAME record. I want that any subdomain can reach my app, not just the ones I manually select in the Amplify Console.

I have a wildcard CNAME in Route 53 pointing to the cloudfront, and the subdomains I added manually in the console are working, but the ones that are not (due to the nature of the wildcard CNAME), just get a 403 from cloudfront.

Is there support for wildcard subdomains in Amplify?

How does one configure it? Assuming there is no support for this.

Is there an API I can use to create the Amplify subdomains for me rather than doing it manually everytime a client purchases access?

Domain activation is Failed - [BRIEF DESCRIPTION]

App Id: d2ztv3yodufzv8
Region: us-east-1
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.

Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.

Additional information
Please add any other relevant information. Please feel free to include screenshots.

Automatically Enable notifications for all connected branches

** Which Category is your question related to? **

Amplify Console

** What AWS Services are you utilizing? **

Auth/Storage/Console

I'm using amplify console as our CI/CD system but I'm having a hard time finding features in it that are available in other alternatives like CircleCI. My problem right now is trying to create a build complete/failed webhook for slack. It works ok for complete if I put it in frontend postBuild. But obviously if a step fails beforehand it never gets to that point.

So my question is how can I catch a build error and then run a bash command afterwards?

Thanks for looking into this!

Unable to build and deploy app which works locally

Hi,
I created https://github.com/JamieMason/serverless-graphql-aws-gatsby by following along with the Tutorial at https://www.youtube.com/watch?v=U6trl0_ynuM&t=4127s. It works locally, yarn start will launch a site which hits GraphQL in AWS that calls a Function in AWS and returns the expected data.

Attempting to deploy the App fails for Resource is not in the state stackUpdateComplete and I don't know how to proceed.

Please could you let me know what I can do to get past this issue?

AMPLIFY APP
serverless-graphql-aws-gatsby

SOURCE
https://github.com/JamieMason/serverless-graphql-aws-gatsby

APP ARN
arn:aws:amplify:eu-west-1:693340411157:apps/d131w18e6nt47w

BUILD SETTINGS
Using default amplify.yml displayed in Amplify Console

BRANCHES
master

NUMBER OF BACKEND ENVIRONMENTS CREATED WITH THE AMPLIFY CLI
Just one, as far as I know

BUILD ERROR OUTPUT
--------------------------------------------------------------------------------
# Starting phase: build
# Executing command: amplifyPush --simple
2019-08-12T23:21:24.625Z [INFO]: # Getting Amplify CLI Cloud-Formation stack info from environment cache
2019-08-12T23:21:24.635Z [INFO]: # Start initializing Amplify environment: dev
# Initializing new Amplify environment: dev (amplify init)
2019-08-12T23:21:35.681Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2019-08-12T23:21:37.519Z [INFO]:
2019-08-12T23:21:37.522Z [INFO]: For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html
2019-08-12T23:21:37.614Z [WARNING]: - Initializing your environment: dev
2019-08-12T23:21:37.961Z [WARNING]: ✔ Initialized provider successfully.
2019-08-12T23:21:40.293Z [INFO]: GraphQL schema compiled successfully.
Edit your schema at /codebuild/output/src110245001/src/serverless-graphql-aws-gatsby/amplify/backend/api/confweather/schema.graphql or place .graphql files in a directory at /codebuild/output/src110245001/src/serverless-graphql-aws-gatsby/amplify/backend/api/confweather/schema
2019-08-12T23:21:41.386Z [WARNING]: - Updating resources in the cloud. This may take a few minutes...
2019-08-12T23:21:46.802Z [INFO]:
2019-08-12T23:21:46.806Z [INFO]: UPDATE_IN_PROGRESS conf-weather-dev-20190812225817 AWS::CloudFormation::Stack Mon Aug 12 2019 23:21:41 GMT+0000 (Coordinated Universal Time) User Initiated
UPDATE_IN_PROGRESS functionweather                 AWS::CloudFormation::Stack Mon Aug 12 2019 23:21:45 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS apiconfweather                  AWS::CloudFormation::Stack Mon Aug 12 2019 23:21:46 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:21:46.897Z [INFO]:
2019-08-12T23:21:46.897Z [INFO]: UPDATE_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741 AWS::CloudFormation::Stack Mon Aug 12 2019 23:21:46 GMT+0000 (Coordinated Universal Time) User Initiated
2019-08-12T23:21:46.955Z [INFO]:
2019-08-12T23:21:46.956Z [INFO]: UPDATE_IN_PROGRESS conf-weather-dev-20190812225817-functionweather-1TSECBPID1P0O AWS::CloudFormation::Stack Mon Aug 12 2019 23:21:46 GMT+0000 (Coordinated Universal Time) User Initiated
2019-08-12T23:21:51.889Z [INFO]:
2019-08-12T23:21:51.891Z [INFO]: UPDATE_IN_PROGRESS LambdaFunction AWS::Lambda::Function Mon Aug 12 2019 23:21:49 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE    LambdaFunction AWS::Lambda::Function Mon Aug 12 2019 23:21:50 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:21:56.835Z [INFO]:
2019-08-12T23:21:56.837Z [INFO]: UPDATE_IN_PROGRESS GraphQLSchema AWS::AppSync::GraphQLSchema Mon Aug 12 2019 23:21:52 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS GraphQLAPIKey AWS::AppSync::ApiKey        Mon Aug 12 2019 23:21:52 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE    GraphQLAPIKey AWS::AppSync::ApiKey        Mon Aug 12 2019 23:21:54 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:21:56.892Z [INFO]:
2019-08-12T23:21:56.894Z [INFO]: UPDATE_COMPLETE_CLEANUP_IN_PROGRESS conf-weather-dev-20190812225817-functionweather-1TSECBPID1P0O AWS::CloudFormation::Stack Mon Aug 12 2019 23:21:52 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:22:01.902Z [INFO]:
2019-08-12T23:22:01.903Z [INFO]: UPDATE_COMPLETE functionweather AWS::CloudFormation::Stack Mon Aug 12 2019 23:21:56 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:22:06.862Z [INFO]:
2019-08-12T23:22:06.865Z [INFO]: UPDATE_COMPLETE GraphQLSchema AWS::AppSync::GraphQLSchema Mon Aug 12 2019 23:22:06 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:22:11.837Z [INFO]:
2019-08-12T23:22:11.838Z [INFO]: UPDATE_IN_PROGRESS FunctionDirectiveStack AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:08 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS Conference             AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:09 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:22:12.030Z [INFO]:
2019-08-12T23:22:12.030Z [INFO]: UPDATE_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-Conference-8WEWZC4QTMIL AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:09 GMT+0000 (Coordinated Universal Time) User Initiated
2019-08-12T23:22:12.117Z [INFO]:
2019-08-12T23:22:12.118Z [INFO]: UPDATE_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-FunctionDirectiveStack-8YJDFM7X5EBK AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:09 GMT+0000 (Coordinated Universal Time) User Initiated
2019-08-12T23:22:17.032Z [INFO]:
2019-08-12T23:22:17.034Z [INFO]: UPDATE_IN_PROGRESS DeleteConferenceResolver AWS::AppSync::Resolver Mon Aug 12 2019 23:22:15 GMT+0000 (Coordinated Universal Time)
UPDATE_FAILED      ConferenceTable          AWS::DynamoDB::Table   Mon Aug 12 2019 23:22:15 GMT+0000 (Coordinated Universal Time) CloudFormation cannot update a stack when a custom-named resource requires replacing. Rename Conference-zpgb2rzmqnfwnabcrnfrtti2qu-dev and update the stack again.
UPDATE_FAILED      GetConferenceResolver    AWS::AppSync::Resolver Mon Aug 12 2019 23:22:16 GMT+0000 (Coordinated Universal Time) Resource update cancelled
UPDATE_FAILED      DeleteConferenceResolver AWS::AppSync::Resolver Mon Aug 12 2019 23:22:16 GMT+0000 (Coordinated Universal Time) Resource update cancelled
2019-08-12T23:22:17.126Z [INFO]:
2019-08-12T23:22:17.127Z [INFO]: UPDATE_IN_PROGRESS InvokeWeatherLambdaDataSource AWS::AppSync::FunctionConfiguration Mon Aug 12 2019 23:22:15 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE    InvokeWeatherLambdaDataSource AWS::AppSync::FunctionConfiguration Mon Aug 12 2019 23:22:16 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:22:17.340Z [INFO]:
2019-08-12T23:22:17.340Z [INFO]: UPDATE_ROLLBACK_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-Conference-8WEWZC4QTMIL AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:17 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [DeleteConferenceResolver, GetConferenceResolver, ConferenceTable].
2019-08-12T23:22:21.852Z [INFO]:
2019-08-12T23:22:21.854Z [INFO]: UPDATE_FAILED Conference AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:20 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:eu-west-1:693340411157:stack/conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-Conference-8WEWZC4QTMIL/adf02a00-bd4d-11e9-b172-0254d350c81a was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [DeleteConferenceResolver, GetConferenceResolver, ConferenceTable].
2019-08-12T23:22:22.150Z [INFO]:
2019-08-12T23:22:22.150Z [INFO]: UPDATE_ROLLBACK_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-FunctionDirectiveStack-8YJDFM7X5EBK AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:20 GMT+0000 (Coordinated Universal Time) Initiated by parent stack
UPDATE_IN_PROGRESS          ConferenceweatherResolver                                                                       AWS::AppSync::Resolver     Mon Aug 12 2019 23:22:20 GMT+0000 (Coordinated Universal Time)
UPDATE_FAILED               ConferenceweatherResolver                                                                       AWS::AppSync::Resolver     Mon Aug 12 2019 23:22:20 GMT+0000 (Coordinated Universal Time) Resource update cancelled
2019-08-12T23:22:31.862Z [INFO]:
2019-08-12T23:22:31.865Z [INFO]: UPDATE_FAILED               FunctionDirectiveStack                                      AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:31 GMT+0000 (Coordinated Universal Time) Resource update cancelled
UPDATE_ROLLBACK_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741 AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:31 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [Conference, FunctionDirectiveStack].
2019-08-12T23:22:36.769Z [INFO]:
2019-08-12T23:22:36.771Z [INFO]: UPDATE_FAILED               apiconfweather                  AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:33 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:eu-west-1:693340411157:stack/conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741/a2d091a0-bd4d-11e9-adb7-02135cc8443e was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [Conference, FunctionDirectiveStack].
UPDATE_ROLLBACK_IN_PROGRESS conf-weather-dev-20190812225817 AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:34 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [apiconfweather].
2019-08-12T23:22:51.842Z [INFO]:
2019-08-12T23:22:51.843Z [INFO]: UPDATE_IN_PROGRESS apiconfweather  AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:48 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS functionweather AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:48 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:22:51.900Z [INFO]:
2019-08-12T23:22:51.901Z [INFO]: UPDATE_ROLLBACK_IN_PROGRESS conf-weather-dev-20190812225817-functionweather-1TSECBPID1P0O AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:49 GMT+0000 (Coordinated Universal Time) User Initiated
UPDATE_IN_PROGRESS          LambdaFunction                                                AWS::Lambda::Function      Mon Aug 12 2019 23:22:50 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE             LambdaFunction                                                AWS::Lambda::Function      Mon Aug 12 2019 23:22:51 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:22:56.834Z [INFO]:
2019-08-12T23:22:56.836Z [INFO]: UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS conf-weather-dev-20190812225817-functionweather-1TSECBPID1P0O AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:52 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:23:01.808Z [INFO]:
2019-08-12T23:23:01.809Z [INFO]: UPDATE_COMPLETE functionweather AWS::CloudFormation::Stack Mon Aug 12 2019 23:22:59 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:23:21.955Z [INFO]:
2019-08-12T23:23:21.957Z [INFO]: UPDATE_IN_PROGRESS GraphQLSchema AWS::AppSync::GraphQLSchema Mon Aug 12 2019 23:23:17 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS GraphQLAPIKey AWS::AppSync::ApiKey        Mon Aug 12 2019 23:23:18 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE    GraphQLAPIKey AWS::AppSync::ApiKey        Mon Aug 12 2019 23:23:19 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:23:31.911Z [INFO]:
2019-08-12T23:23:31.913Z [INFO]: UPDATE_COMPLETE    GraphQLSchema          AWS::AppSync::GraphQLSchema Mon Aug 12 2019 23:23:30 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS Conference             AWS::CloudFormation::Stack  Mon Aug 12 2019 23:23:31 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS FunctionDirectiveStack AWS::CloudFormation::Stack  Mon Aug 12 2019 23:23:31 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:23:52.100Z [INFO]:
2019-08-12T23:23:52.102Z [INFO]: UPDATE_IN_PROGRESS                           InvokeWeatherLambdaDataSource                                                                   AWS::AppSync::FunctionConfiguration Mon Aug 12 2019 23:23:47 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE                              InvokeWeatherLambdaDataSource                                                                   AWS::AppSync::FunctionConfiguration Mon Aug 12 2019 23:23:50 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE                              ConferenceweatherResolver                                                                       AWS::AppSync::Resolver              Mon Aug 12 2019 23:23:51 GMT+0000 (Coordinated Universal Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-FunctionDirectiveStack-8YJDFM7X5EBK AWS::CloudFormation::Stack          Mon Aug 12 2019 23:23:51 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:23:52.210Z [INFO]:
2019-08-12T23:23:52.211Z [INFO]: UPDATE_COMPLETE                              GetConferenceResolver                                                               AWS::AppSync::Resolver     Mon Aug 12 2019 23:23:48 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE                              DeleteConferenceResolver                                                            AWS::AppSync::Resolver     Mon Aug 12 2019 23:23:48 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE                              ConferenceTable                                                                     AWS::DynamoDB::Table       Mon Aug 12 2019 23:23:48 GMT+0000 (Coordinated Universal Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-Conference-8WEWZC4QTMIL AWS::CloudFormation::Stack Mon Aug 12 2019 23:23:48 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:23:56.921Z [INFO]:
2019-08-12T23:23:56.924Z [INFO]: UPDATE_COMPLETE                              Conference                                                  AWS::CloudFormation::Stack Mon Aug 12 2019 23:23:53 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE                              FunctionDirectiveStack                                      AWS::CloudFormation::Stack Mon Aug 12 2019 23:23:53 GMT+0000 (Coordinated Universal Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741 AWS::CloudFormation::Stack Mon Aug 12 2019 23:23:55 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:24:11.832Z [INFO]:
2019-08-12T23:24:11.833Z [INFO]: UPDATE_COMPLETE                              apiconfweather                  AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:07 GMT+0000 (Coordinated Universal Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS conf-weather-dev-20190812225817 AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:07 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS                           apiconfweather                  AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:08 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS                           functionweather                 AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:08 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:24:11.891Z [INFO]:
2019-08-12T23:24:11.894Z [INFO]: UPDATE_ROLLBACK_COMPLETE conf-weather-dev-20190812225817-functionweather-1TSECBPID1P0O AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:09 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:24:21.845Z [INFO]:
2019-08-12T23:24:21.847Z [INFO]: UPDATE_COMPLETE functionweather AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:19 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:24:22.048Z [INFO]:
2019-08-12T23:24:22.049Z [INFO]: UPDATE_IN_PROGRESS       Conference                                                  AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:09 GMT+0000 (Coordinated Universal Time)
UPDATE_IN_PROGRESS       FunctionDirectiveStack                                      AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:09 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE          Conference                                                  AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:20 GMT+0000 (Coordinated Universal Time)
UPDATE_COMPLETE          FunctionDirectiveStack                                      AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:20 GMT+0000 (Coordinated Universal Time)
UPDATE_ROLLBACK_COMPLETE conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741 AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:20 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:24:22.207Z [INFO]:
2019-08-12T23:24:22.207Z [INFO]: UPDATE_ROLLBACK_COMPLETE conf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-FunctionDirectiveStack-8YJDFM7X5EBK AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:10 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:24:31.855Z [INFO]:
2019-08-12T23:24:31.857Z [INFO]: UPDATE_COMPLETE          apiconfweather                  AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:30 GMT+0000 (Coordinated Universal Time)
UPDATE_ROLLBACK_COMPLETE conf-weather-dev-20190812225817 AWS::CloudFormation::Stack Mon Aug 12 2019 23:24:30 GMT+0000 (Coordinated Universal Time)
2019-08-12T23:24:41.991Z [WARNING]: Error updating cloudformation stack
2019-08-12T23:24:42.071Z [INFO]: Following resources failed
2019-08-12T23:24:42.073Z [INFO]: Resource Name: arn:aws:appsync:eu-west-1:693340411157:apis/zpgb2rzmqnfwnabcrnfrtti2qu/types/Mutation/resolvers/deleteConference (AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-west-1#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-1%3A693340411157%3Astack%2Fconf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-Conference-8WEWZC4QTMIL%2Fadf02a00-bd4d-11e9-b172-0254d350c81a/events
Resource Name: arn:aws:appsync:eu-west-1:693340411157:apis/zpgb2rzmqnfwnabcrnfrtti2qu/types/Query/resolvers/getConference (AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-west-1#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-1%3A693340411157%3Astack%2Fconf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-Conference-8WEWZC4QTMIL%2Fadf02a00-bd4d-11e9-b172-0254d350c81a/events
Resource Name: Conference-zpgb2rzmqnfwnabcrnfrtti2qu (AWS::DynamoDB::Table)
Event Type: update
Reason: CloudFormation cannot update a stack when a custom-named resource requires replacing. Rename Conference-zpgb2rzmqnfwnabcrnfrtti2qu-dev and update the stack again.
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-west-1#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-1%3A693340411157%3Astack%2Fconf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-Conference-8WEWZC4QTMIL%2Fadf02a00-bd4d-11e9-b172-0254d350c81a/events
Resource Name: arn:aws:appsync:eu-west-1:693340411157:apis/zpgb2rzmqnfwnabcrnfrtti2qu/types/Conference/resolvers/weather (AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL: https://console.aws.amazon.com/cloudformation/home?region=eu-west-1#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-1%3A693340411157%3Astack%2Fconf-weather-dev-20190812225817-apiconfweather-CJ4TKER9E741-FunctionDirectiveStack-8YJDFM7X5EBK%2Fadee0720-bd4d-11e9-aaac-06c34fd08df4/events
init failed
2019-08-12T23:24:42.074Z [WARNING]: ✖ An error occurred when pushing the resources to the cloud
   ✖ There was an error initializing your environment.
2019-08-12T23:24:42.076Z [INFO]: { ResourceNotReady: Resource is not in the state stackUpdateComplete
at constructor.setError (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/resource_waiter.js:182:47)
at Request.CHECK_ACCEPTORS (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/resource_waiter.js:44:12)
at Request.callListeners (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
message: 'Resource is not in the state stackUpdateComplete',
code: 'ResourceNotReady',
retryable: false,
time: 2019-08-12T23:24:41.990Z,
statusCode: 200,
retryDelay: 30000 }
2019-08-12T23:24:42.129Z [ERROR]: !!! Build failed
2019-08-12T23:24:42.129Z [ERROR]: !!! Non-Zero Exit Code detected
2019-08-12T23:24:42.129Z [INFO]: # Starting environment caching...
2019-08-12T23:24:42.130Z [INFO]: # Environment caching completed
Terminating logging...

Thanks a lot.

test issue

App Id:
Region:
Step:
Status:

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.

Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.

Additional information
Please add any other relevant information. Please feel free to include screenshots.

additional sample code or a sample repository to help us reproduce the issue. (Be sure to remove any sensitive data)

SSL verification is Failed - [BRIEF DESCRIPTION]

App Id: d1dmgnwdmwopvw
Region: us-east-1
Step: SSL verification
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.

Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.

Additional information
Please add any other relevant information. Please feel free to include screenshots.

One click deploy - choose branch

Is your feature request related to a problem? Please describe.
It would be nice to allow us to choose the branch we'd like to deploy when using the one-click deploy.

CloudFront with Web Application Firewall?

** Which Category is your question related to? **
Amplify Console Hosting

If I'm using the Amplify Console to host a Static Website, where is it stored? It doesn't look like there is an S3 bucket being used by the Amplify Console to host the website?

If we use the Amplify CLI add hosting, it will use an S3 bucket, does the Amplify Console do something similar, but we just can't access it?

Not Getting updated Deployment appearing in Browser after Refresh.

Describe the bug
I have setup deployments with Amplify Console. I have multiple Apps to the same branch so they all update and I can manage seperate domains with seperate environment variables (maintaining domain assets)

When I merge to a Bitbucket branch, it goes through the process to build and deploy.

After completion, I got to the site, Hit Ctrl+R to refresh but it appears still that I'm pulling from a cache as it's not updating to the latest version I just deployed.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Bicketbucket
  2. Click on 'Merge' in Pull request
  3. Wait for Deployment to all go Green
  4. Click on URL link under App image
  5. Open Page and click Ctrl+R

Expected behavior
I thought the Console was updated so as to cause a forced refresh of the CDN. This would mean the Refresh would pull the new Vue application down from Bucket.

Additional context
I have noticed that it can be out of sync across multiple computers.

Backend build error: The runtime parameter of nodejs6.10 is no longer supported for creating or updating AWS Lambda functions

Describe the bug
Getting the following error when deploying from GitHub to the Amplify Console

2019-07-26T19:06:32.488Z [INFO]: CREATE_FAILED UserPoolClientLambda AWS::Lambda::Function Fri Jul 26 2019 19:06:32 GMT+0000 (Coordinated Universal Time) The runtime parameter of nodejs6.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs10.x) while creating or updating functions. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: f066bf5a-2f16-4e63-b69a-239a73578f69)

The Amplify project on GitHub is configured with Node.JS 8.10: https://github.com/aws-samples/appsync-refarch-realtime/blob/3c15513e6cd1333eb945bc6d470d3f76b87af173/amplify/backend/auth/realtime99d78ebe/realtime99d78ebe-cloudformation-template.yml#L249

To Reproduce
Test with one click deploy https://github.com/aws-samples/appsync-refarch-realtime#one-click-deploy-with-the-amplify-console

Expected behavior
If I follow the manual setup with the CLI, it works fine: https://github.com/aws-samples/appsync-refarch-realtime#manual-setup

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.