Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

App fails to deploy with Amplify 1-click #366

Open
brianz opened this issue Jun 30, 2022 · 1 comment
Open

App fails to deploy with Amplify 1-click #366

brianz opened this issue Jun 30, 2022 · 1 comment

Comments

@brianz
Copy link

brianz commented Jun 30, 2022

I followed the directions for the Amplify 1-click deployment. The Backend build failed.

The relevant parts of the Amplify Build console show:

2022-06-30T17:12:58.779Z [INFO]: CREATE_IN_PROGRESS AmplifyResourcesPolicy AWS::IAM::Policy      Thu Jun 30 2022 17:12:54 GMT+0000 (Coordinated Universal Time)
  CREATE_IN_PROGRESS LambdaFunction         AWS::Lambda::Function Thu Jun 30 2022 17:12:54 GMT+0000 (Coordinated Universal Time)
  CREATE_IN_PROGRESS AmplifyResourcesPolicy AWS::IAM::Policy      Thu Jun 30 2022 17:12:55 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
  CREATE_IN_PROGRESS LambdaFunction         AWS::Lambda::Function Thu Jun 30 2022 17:12:56 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
2022-06-30T17:13:03.775Z [INFO]: 
2022-06-30T17:13:03.776Z [INFO]: CREATE_FAILED LambdaFunction AWS::Lambda::Function Thu Jun 30 2022 17:13:00 GMT+0000 (Coordinated Universal Time) 
    Resource handler returned message: "User: arn:aws:sts::111111111111:assumed-role/amplifyconsole-backend-role/BuildSession is not authorized to perform: lambda:PutFunctionConcurrency on resource: 
    arn:aws:lambda:us-west-2:111111111111:function:S3Trigger984fb593-devb because no identity-based policy allows the lambda:PutFunctionConcurrency 
    action (Service: Lambda, Status Code: 403, Request ID: 3a417a78-3416-4ab9-a589-0e6945fe3947)" (RequestToken: 1a65c44a-93cb-86c6-b612-4a48af0dfe0f, HandlerErrorCode: AccessDenied)
2022-06-30T17:13:18.778Z [INFO]: 
2022-06-30T17:13:18.781Z [INFO]: CREATE_COMPLETE AmplifyResourcesPolicy                                                 AWS::IAM::Policy           Thu Jun 30 2022 17:13:13 GMT+0000 (Coordinated Universal Time)
                                 CREATE_FAILED   amplify-photoshare-devb-170520-functionS3Trigger984fb593-19MV1K7RNRV4I AWS::CloudFormation::Stack Thu Jun 30 2022 17:13:14 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to create: [LambdaFunction].
2022-06-30T17:13:28.887Z [INFO]: 
2022-06-30T17:13:28.888Z [INFO]: CREATE_FAILED functionS3Trigger984fb593 AWS::CloudFormation::Stack Thu Jun 30 2022 17:13:28 GMT+0000 (Coordinated Universal Time) 
    Embedded stack arn:aws:cloudformation:us-west-2:111111111111:stack/amplify-photoshare-devb-170520-functionS3Trigger984fb593-19MV1K7RNRV4I/d0a04fc0-f897-11ec-abb8-02cf258d1d13 
   was not successfully created: The following resource(s) failed to create: [LambdaFunction].
@charliejllewellyn
Copy link

I also have this issue. The workaround is to update the amplifyconsole-backend-role with an additional policy allowing "lambda:PutFunctionConcurrency". Would be good to get the guide updated to include this step.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants