amplify-cli: Response is not valid JSON on AdminQueries

Before opening, please confirm:

  • I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
  • I have searched for duplicate or closed issues.
  • I have read the guide for submitting bug reports.
  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?

sudo npm install -g @aws-amplify/cli

If applicable, what version of Node.js are you using?

v14.16.1

Amplify CLI Version

4.45.2

What operating system are you using?

Deepin

Amplify Categories

function

Amplify Commands

push

Describe the bug

I just updated my application to enable the unathenticated users and the adminqueries; i didn’t touch anything, i followed the documentation to enable adminqueries and i didn’t modified the lambda functions, but pushing to the server gives me the following bug:

CREATE_FAILED               MFALambdaInputs                                                        Custom::LambdaCallout      Wed Apr 28 2021 06:30:56 GMT+0300 (GMT+03:00) Response is not valid JSON                                     
UPDATE_ROLLBACK_IN_PROGRESS amplify-thesiscancer-dev-104158-auththesiscancer7a6cf6e7-14VWV365GEC8A AWS::CloudFormation::Stack Wed Apr 28 2021 06:30:57 GMT+0300 (GMT+03:00) The following resource(s) failed to create: [MFALambdaInputs]. 
⠙ Updating resources in the cloud. This may take a few minutes...

UPDATE_FAILED               auththesiscancer7a6cf6e7        AWS::CloudFormation::Stack Wed Apr 28 2021 06:31:07 GMT+0300 (GMT+03:00) Embedded stack arn:aws:cloudformation:us-east-2:295982313172:stack/amplify-thesiscancer-dev-104158-auththesiscancer7a6cf6e7-14VWV365GEC8A/fa1fce70-8174-11eb-8a21-063ea9f5776c was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to create: [MFALambdaInputs]. 
UPDATE_ROLLBACK_IN_PROGRESS amplify-thesiscancer-dev-104158 AWS::CloudFormation::Stack Wed Apr 28 2021 06:31:07 GMT+0300 (GMT+03:00) The following resource(s) failed to update: [auththesiscancer7a6cf6e7].                                                                                                                                                                                                                                                           
⠹ Updating resources in the cloud. This may take a few minutes...



Following resources failed

Resource Name: amplify-thesiscancer-104158-auththesiscancer7a6cf6e7-14VWV365GEC8A-MFALambdaInputs-4G0UXVL6B4B0 (Custom::LambdaCallout)
Event Type: create
Reason: Response is not valid JSON


✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occurred during the push operation: Resource is not in the state stackUpdateComplete

Expected behavior

I should not get this bug but having the new features pushed to the platform.

Reproduction steps

  1. amplify update auth.
  2. Enable unauthenticated users.
  3. Enable AdminQueries.
  4. Select Admin user group as restricted group.
  5. Ingore others.
  6. amplify push.
  7. See the error.

GraphQL schema(s)

# Put schemas below this line


Log output

# Put your logs below this line


Additional information

My current status:

❯ amplify status

Current Environment: dev

| Category | Resource name        | Operation | Provider plugin   |
| -------- | -------------------- | --------- | ----------------- |
| Api      | AdminQueries         | Create    | awscloudformation |
| Function | AdminQueries9###### | Create    | awscloudformation |
| Auth     | thesiscancer#######| Update    | awscloudformation |
| Api      | thesiscancergraphql  | Update    | awscloudformation |
| Auth     | userPoolGroups       | No Change | awscloudformation |

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 18 (9 by maintainers)

Most upvoted comments

We were able to meet and run through this issue and we were not able to reproduce it using a very similar setup and accepting defaults. @SalahAdDin as noted in our call I’ll be marking this as non-reproducible and closing