AWS EKS - CloudFormation Script fails (just the documented tutorial with no changes)

0

Summary:

  1. I have successfully deployed EKS via AWS Cloudformation template in the past (about an year ago).
  2. Now when I am trying to deploy EKS via AWS Cloudformation its failing.
  3. The error message is NOT clear enough for me to go and fix the reason of the crash, any tips on how to go about this error message?

Documentation and Steps Used

  1. Page: https://aws.amazon.com/quickstart/architecture/amazon-eks/
  2. Deploy using AWS CloudFormation with new VPC

Error Message

Stack nameStatus
eks-quickstart-RegionalSharedResourcesDELETE_FAILED
eks-quickstart-AccountSharedResourcesCREATE_COMPLETE
Amazon-EKSROLLBACK_COMPLETE

Amazon EKS (ROLLBACK_COMPLETE) has the following events that Failed

  • AutoDetectSharedResources > CREATE_FAILED with log Embedded stack arn:aws:cloudformation:us-east-2:SOME_ID : stack/Amazon-EKS-AutoDetectSharedResources-SOME_UUID was not successfully created: The following resource(s) failed to create: [ PreReqs ].
  • Amazon-EKS > ROLLBACK_IN_PROGRESS with log The following resource(s) failed to create: [AutoDetectSharedResources]. Rollback requested by user.

One more log seems to be important (BUT the Cloudformation Script is from AWS so I doubt it might be a root cause)

RegisterHelmType  CREATE_FAILED
CloudFormation did not receive a response from your Custom Resource. Please check your logs for requestId [SOME_UUID]. If you are using the Python cfn-response module, you may need to update your Lambda function code so that CloudFormation can attach the updated version.
asked 2 years ago806 views
2 Answers
0

To detect issue properly it would help to avoid rolling back. You can try that using aws cloudformation create-stack --stack-name myteststack --template-body file://DOC-EXAMPLE-BUCKET.json -–disable-rollback

AWS
answered 2 years ago
0

Hi,

We are facing the same issue in our accounts to create an EKS service. Basically the lambda fails: "Reason": "UnknownEndpoint: Inaccessible host: lambda.eu-west-1.amazonaws.com' at port undefined'. This service may not be available in the `eu-west-1' region.\n at Request.ENOTFOUND_ERROR (/var/runtime/node_modules/aws-sdk/lib/event_listeners.js:529:46)\n at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)\n at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)\n at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:686:14)\n at error (/var/runtime/node_modules/aws-sdk/lib/event_listeners.js:361:22)\n at ClientRequest.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/http/node.js:99:9)\n at ClientRequest.emit (events.js:400:28)\n at ClientRequest.emit (domain.js:475:12)\n at TLSSocket.socketErrorListener (_http_client.js:475:9)\n at TLSSocket.emit (events.js:400:28)",

The step that returns this error is Authentication Manifest.

regards, Nuno

answered a year 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