Skip to content

added lambda-s3-athena-cdk-ts pattern#2918

Open
marcojahn wants to merge 6 commits intoaws-samples:mainfrom
marcojahn:main
Open

added lambda-s3-athena-cdk-ts pattern#2918
marcojahn wants to merge 6 commits intoaws-samples:mainfrom
marcojahn:main

Conversation

@marcojahn
Copy link
Contributor

Issue #, if available: #2917

Description of changes:
This pattern demonstrates how to use Amazon S3 as a failed-event destination for AWS Lambda asynchronous invocations, with Amazon Athena for analytics on failed events. The pattern includes an AWS Lambda function with business logic that can succeed or fail, automatically capturing failed events to Amazon S3 for analysis.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@marcojahn
Copy link
Contributor Author

Thanks reviewing @bfreiberg, all fixed as proposed.

Copy link
Contributor

@bfreiberg bfreiberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, two minor adjustments before its ready

@@ -0,0 +1,74 @@
{
"title": "AWS Lambda with Amazon S3 Failed-Event Destination and Amazon Athena Analytics",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, but the title doesn't the 75 character limit anymore. Please revise

### Query Failed Events with Amazon Athena

1. Open the Amazon Athena console to run queries.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add that you might need to set up a query result location in S3 before if you haven't done so already. This can be changed in the settings later

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants