CloudFormation stack CREATE_FAILED because of "Internal Error"


Hey folks,

I was trying to replicate the service I work on to a separate burner account. I was able to replicate all the other stacks except the ECS Service stack (the main one for the service). I get an error while running bb cdk deploy <ECSServiceStackName> which says:

Received response status [FAILED] from custom resource. Message returned: Internal Error (RequestId: f67e9cec-b153-47fa-8bf6-8c1ac962394c)

I believe it is due to other resources that failed to create:

The following resource(s) failed to create: [LoadBalancerBE9EEC3A, LambdaCanary44B53221, SslCertificateArnSsmParameterFBC7F579]. Rollback requested by user.

Based on the events and time stamps I can see that the SslCertificateArnSsmParameter resource failed first (also started creating first) due to which the other 2 are failing. Is this Certificate resource an issue with regards to a burner account? Is it okay that I am trying to replicate this resource in a separate AWS account apart from the original Alpha account (Yes, I am replicating all the resources from the alpha account)?

If anyone is curious about why I am replicating everything to a burner account- The goal is to get the service up and running in a separate AWS account and for that I am trying it on a burner account first before going ahead with a new permanent Conduit account.

TIA :)

Attached 1 images 1) the CloudFormation ConsoleEnter image description here

  1. CW logs associated with the resource.

{ "Status": "FAILED", "Reason": "Internal Error", "PhysicalResourceId": "2022/09/13/[$LATEST]<id>", "StackId": "arn:aws:cloudformation:us-west-2:<aws_accountID>:stack/IhmPrimsDecouplerEcsService-<aws_accountID>/<some_ID>, "RequestId": "<RequestID>", "LogicalResourceId": "SslCertificateArnSsmParameterFBC7F579", "NoEcho": false, "Data": {} }

INFO ParameterNotFound: null at Request.extractError (/tmp/node_modules/aws-sdk/lib/protocol/json.js:52:27) at Request.callListeners (/tmp/node_modules/aws-sdk/lib/sequential_executor.js:106:20) at Request.emit (/tmp/node_modules/aws-sdk/lib/sequential_executor.js:78:10) at Request.emit (/tmp/node_modules/aws-sdk/lib/request.js:686:14) at Request.transition (/tmp/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/tmp/node_modules/aws-sdk/lib/state_machine.js:14:12) at /tmp/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/tmp/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/tmp/node_modules/aws-sdk/lib/request.js:688:12) at Request.callListeners (/tmp/node_modules/aws-sdk/lib/sequential_executor.js:116:18) { code: 'ParameterNotFound'

1 Answer


Below is the article to go through for the same. It states all the possible reasons for the internal error which look quite similar to what you are facing.

Link- -- [1]

profile picture
answered 3 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions