Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

An error occurred when creating the CloudFormation stack 🛑 #13469

Closed
2 tasks done
NoellaMarie501 opened this issue Dec 10, 2023 · 11 comments
Closed
2 tasks done

An error occurred when creating the CloudFormation stack 🛑 #13469

NoellaMarie501 opened this issue Dec 10, 2023 · 11 comments
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-init Issues related to initializing a new Amplify project

Comments

@NoellaMarie501
Copy link

How did you install the Amplify CLI?

npm

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

v21.4.0

Amplify CLI Version

12.8.2

What operating system are you using?

Ubuntu

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

"No manual changes made"

Describe the bug

  1. First I tried initializing a project with amplify 3 times but got this error: "
    An error occurred when creating the CloudFormation stack
    🛑 The following resources failed to deploy:
    🛑 Initialization of project failed
    "
  2. I tried again and now had this error: "🛑 You have reached the Amplify App limit for this account and region" whereas on my amplify console there are no apps.
  3. I changed the region in the configurations and went back to the error: "An error occurred when creating the CloudFormation stack
    🛑 The following resources failed to deploy:
    🛑 Initialization of project failed"
  4. I have searched about the problem it all I find is that it is related to having a new account, but I do not find a solution

Expected behavior

-To be able to initialize an amplify project and push afterwards.

Reproduction steps

  • Have an existing React js project
  • Run amplify init

Project Identifier

No response

Log output

# Put your logs below this line


An error occurred when creating the CloudFormation stack
🛑 The following resources failed to deploy:
🛑 Initialization of project failed

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Resource is not in the state stackCreateComplete
AccessDenied: Resource is not in the state stackCreateComplete
    at Request.extractError (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/protocol/query.js:50:29)
    at Request.callListeners (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:686:14)
    at Request.transition (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:688:12)
    at Request.callListeners (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
    at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:686:14)
    at Request.transition (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:688:12)
    at Request.callListeners (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
    at callNextListener (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
    at IncomingMessage.onEnd (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/event_listeners.js:417:13)
    at IncomingMessage.emit (node:events:525:35)
    at IncomingMessage.emit (node:domain:489:12)
    at endReadableNT (node:internal/streams/readable:1359:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@NoellaMarie501 NoellaMarie501 added the pending-triage Issue is pending triage label Dec 10, 2023
@ykethan
Copy link
Member

ykethan commented Dec 11, 2023

Hey @NoellaMarie501, thank you for reaching out. Could you try running amplify init --debug?
Additionally, in the AWS CloudFormation console could you check the stacks of the application for any failure messages.

@ykethan ykethan added pending-response Issue is pending response from the issue author platform-init Issues related to initializing a new Amplify project labels Dec 11, 2023
@NoellaMarie501
Copy link
Author

Hello @ykethan as for the stacks of the application i do not have any yet as i am still trying to initiate the project and create stacks. here is the output i get from using the debug. "
An error occurred when creating the CloudFormation stack
🛑 The following resources failed to deploy:
🛑 Initialization of project failed

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Resource is not in the state stackCreateComplete
AccessDenied: Resource is not in the state stackCreateComplete
at Request.extractError (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/protocol/query.js:50:29)
at Request.callListeners (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:688:12)
at Request.callListeners (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /snapshot/amplify-cli/build/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/request.js:688:12)
at Request.callListeners (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
at callNextListener (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
at IncomingMessage.onEnd (/snapshot/amplify-cli/build/node_modules/aws-sdk/lib/event_listeners.js:417:13)
at IncomingMessage.emit (node:events:525:35)
at IncomingMessage.emit (node:domain:489:12)
at endReadableNT (node:internal/streams/readable:1359:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Dec 11, 2023
@ykethan
Copy link
Member

ykethan commented Dec 11, 2023

Hey @NoellaMarie501, are you running init on a project that contains a Amplify folder?
from the error message Resource is not in the state stackCreateComplete it does look like the CloudFormation deployment did start to create the application and a stack creation was initiated. Do check the deleted section as well as the stack may have been deleted.
The issue appears to be similar to #353. Checking the stack would help us in understanding if the issue is due to limits on the underlying resources created or if any resource failed to create.

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Dec 11, 2023
@NoellaMarie501
Copy link
Author

Hello @ykethan No the project does not contain an Amplify folder. It is a React project that I am trying to use amplify for hosting and lamda as the backend but get this error when trying to initialize the project with amplify init command

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Dec 12, 2023
@NoellaMarie501
Copy link
Author

@ykethan i just checked the deleted stacks as you said but there are none

image

@NoellaMarie501
Copy link
Author

@ykethan I honestly have no idea what the issue is. And i will love to know why i receive the "🛑 You have reached the Amplify App limit for this account and region" error when i try the init command again to the point i get to change the region. whereas i have no application that was actually created

@ykethan
Copy link
Member

ykethan commented Dec 12, 2023

Hey @NoellaMarie501, thank you for the information. The error message appears to be similar to aws-amplify/amplify-hosting#2797.

But from the information provided I believe the issue may be occurring on a account level,
As a quick confirmation to check if this is occurring on a account level, could you try creating a backend application on AWS Amplify console using the build an app.
image

Additionally, is this a new account?

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Dec 12, 2023
@NoellaMarie501
Copy link
Author

yes @ykethan
it is a new account

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Dec 12, 2023
@ykethan
Copy link
Member

ykethan commented Dec 12, 2023

@NoellaMarie501 when creating the new app on the Amplify console, if you run experience a error message similar to We are unable to process your request. Please reach out to your support representative, we can confirm that the issue is occurring on a account level.

to mitigate the issue, we will need to reach out to the AWS support team
If you have a premium support plan, open a support case under the Amplify Console Support with a brief explanation with the error message and being unable to create resources. Do link the Github issue to the support case.

If you do not have a support plan and see a Basic Support Plan in the AWS support console,
create a new support case under Account and Billing using the following headings:

Service: Account
Category: Other Account Issues
General Question
add a subject line say Check Account Status - Amplify Console and describe the issue you are experiencing such as the error message and unable to create a app. Do link the GitHub issue to the support ticket to help track the issue.

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Dec 12, 2023
@josefaidt
Copy link
Contributor

Closing due to inactivity

@josefaidt josefaidt closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 2, 2024

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-init Issues related to initializing a new Amplify project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@josefaidt @ykethan @NoellaMarie501