Error during deployment: create failed DataLakeKibanaCognito

[nickboucart]

While deploying to the Frankfurt region, I got an error deploying. I just ran the default cloudformation template.

While deploying, it gave an error deploying the resource with logical id DataLakeKibanaCognito.

the cloudformation console showed:
Failed to create resource. https://console.aws.amazon.com/cloudwatch/home?region=eu-central-1#logEventViewer:group=/aws/lambda/data-lake-helper;stream=2020/02/11/[$LATEST]29339c5ea4a94ec58a8afb15c81f1c0f

Any ideas?

Thanks!
Nick.

[beomseoklee]

@nickboucart Thanks for reaching out to us, and I'm sorry to hear that you faced an issue.
Can you verify what error happened at CloudWatch Logs? It should provide more information.

[nickboucart]

Scrolling through the logs, I see

error copying solutions-eu-central-1/data-lake-solution/v2.2/site/lib/bower_components/moment/min/moment.min.js
NoSuchBucket: The specified bucket does not exist

and the next line in CloudWatch logs showed:

{
    "Status": "FAILED",
    "Reason": "https://console.aws.amazon.com/cloudwatch/home?region=eu-central-1#logEventViewer:group=/aws/lambda/data-lake-helper;stream=2020/02/11/[$LATEST]29339c5ea4a94ec58a8afb15c81f1c0f",
    "PhysicalResourceId": "DataLakeWebsite",
    "StackId": "arn:aws:cloudformation:eu-central-1:xxxxxxx:stack/datalake/8620e1d0-4ccd-11ea-a1b6-060cd1f69c1a",
    "RequestId": "ec127bc3-5150-4854-94b3-fe2d109a5451",
    "LogicalResourceId": "DataLakeWebsite",
    "Data": {
        "Error": "Failed to copy data lake website assets."
    }
}

[nickboucart]

I did manage to deploy in the Ohio region... Not sure what happened here.

[beomseoklee]

Thanks for the log, and it seems like it's different from the error you mentioned at the first time.
I was able to launch the solution in the Frankfurt region, so it should work for you.

Would you mind deploying the solution in the Frankfurt region again? To deploy again, you need to delete 1) AWS CloudFormatoin stack (if you haven't done) and 2) Amazon S3 buckets created by the solution (e.g. data-lake-eu-central-1-YOUR_ACCOUNT_ID).

When you deploy the solution again, can you select "Disabled" for "Rollback on failure" at Stack creation options?

Then, if an error happens again, you might can find the first error which would cause the actual stack failure.