Zizi96
Zizi96

Reputation: 519

How to launch AWS cloud formation stack with glue?

I'm trying to get this repo going: https://github.com/mydatastack/google-analytics-to-s3.

A link is provided to launch the AWS CloudFormation stack, its meant to be one click to launch the stack but it is no longer working because the S3 bucket containing the template is no longer active.

As a result I'm trying to launch the stack myself via sam deploy --guided --capabilities CAPABILITY_AUTO_EXPAND CAPABILITY_IAM since all the resources for the stack are within the repo. I've added this lambda layer for the paramiko package referenced by collector-ga.yaml to fix this error .

Frustratingly, I'm not quite up and running yet, GlueConfigurationLambda, an AWS lambda function (line 691) failed to create:

Waiting for changeset to be created..

CloudFormation stack changeset
---------------------------------------------------------------------------------------------------------------------
Operation                     LogicalResourceId             ResourceType                  Replacement
---------------------------------------------------------------------------------------------------------------------
+ Add                         GoogleAnalyticsCollectorSta   AWS::CloudFormation::Stack    N/A
                              ck
---------------------------------------------------------------------------------------------------------------------

Changeset created successfully. arn:aws:cloudformation:eu-central-1:XXXXXX:changeSet/samcli-deploy1628597635/4ee26e-46b5-4131-bdba-1b9fc34f99d6


Previewing CloudFormation changeset before deployment
======================================================
Deploy this changeset? [y/N]: y

2021-08-10 13:14:04 - Waiting for stack create/update to complete

CloudFormation events from changeset
---------------------------------------------------------------------------------------------------------------------------------------------------------
ResourceStatus                         ResourceType                           LogicalResourceId                      ResourceStatusReason
---------------------------------------------------------------------------------------------------------------------------------------------------------
CREATE_IN_PROGRESS                     AWS::CloudFormation::Stack             GoogleAnalyticsCollectorStack          -
CREATE_IN_PROGRESS                     AWS::CloudFormation::Stack             GoogleAnalyticsCollectorStack          Resource creation Initiated
CREATE_FAILED                          AWS::CloudFormation::Stack             GoogleAnalyticsCollectorStack          Embedded stack
                                                                                                                     arn:aws:cloudformation:eu-central-1:
                                                                                                                     XXXXXX:stack/GAN2S3-GoogleAnal
                                                                                                                     yticsCollectorStack-JUATDT3EBD82/e19
                                                                                                                     a4950-ff27-11ea-943e-06072e1f2808
                                                                                                                     was not successfully created: The
                                                                                                                     following resource(s) failed to
                                                                                                                     create: [GlueConfigurationLambda].

Full Trace - https://pastebin.pl/view/50b3e402

  1. My first question is if there's anywhere to get a more in-depth log of the error?
  2. My second question is if anyone knows how to fix this error.

Upvotes: 0

Views: 255

Answers (1)

stijndepestel
stijndepestel

Reputation: 3544

Can you have a look at the AWS Console CloudFormation application? You should be able to opt to view the Deleted stacks, after which you should be able to select the substack that has failed. In the events list of that deleted stack, you should be able to view a more precise error of what went wrong.

If it's still unclear from that precise error, feel free to edit the question to add the specific error and add a comment to this answer to draw my attention to it.

(Edit)

I've looked through the template file again and noticed the Lambda that's failing is still configured to use Node.js 8, which has been deprecated for some time. You should change it to a newer version, e.g., Node.js 14. Find the currently supported runtimes here: Lambda runtimes

Upvotes: 1

Related Questions