https://github.com/jeshan/aws-error-logger
Catch errors across dozens of AWS services
https://github.com/jeshan/aws-error-logger
aws aws-lambda cloudformation-template serverless
Last synced: 7 months ago
JSON representation
Catch errors across dozens of AWS services
- Host: GitHub
- URL: https://github.com/jeshan/aws-error-logger
- Owner: jeshan
- License: bsd-2-clause
- Created: 2020-06-16T18:41:31.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2023-03-21T22:34:06.000Z (about 3 years ago)
- Last Synced: 2025-08-31T03:45:46.366Z (8 months ago)
- Topics: aws, aws-lambda, cloudformation-template, serverless
- Language: Python
- Homepage:
- Size: 2.59 MB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# aws-error-logger
Catch errors in dozens of AWS services
# Intro
There are many errors that can happen in the AWS Cloud. We want to know about them so that we can take the proper action.
This solution is a Cloudformation template that catches errors across of dozens of services.
Errors caught include:
- EC2 instance launch failures
- codebuild build project failures
- codepipeline deployment failures
but you also need to know when more obscure ones like `AWS Health Abuse Event` occur.
This is made possible by Cloudwatch Events which integrate with many services. This project sets up event rules that matches failure patterns recognised by Cloudwatch Events.
The target to receive notifications can be [Sentry](https://sentry.io/welcome/), SNS, or webhooks. This means that you can receive notifications by
- SMS
- Email
- any application that supports a webhook
# Example: build failure -> Sentry
# Instructions
The project is deployed via the [AWS SAM CLI](https://github.com/awslabs/aws-sam-cli).
First, set some parameters in [samconfig.toml](samconfig.toml), like:
- s3 bucket that SAM will need
- aws profile
- parameter overrides like SentryUrl, phone number or webhook endpoint
## Deployment
If you use Docker, you may deploy with command:
`docker-compose up`
Otherwise, run:
- `sam build`
- `sam deploy --guided`
This will deploy the following template in us-east-1. Note that since Cloudwatch Events is a regional service, you need to repeat the deployment in all regions.
This depicts what will get deployed:
*Image automatically generated with [cfnbuddy](https://www.cfnbuddy.com)*
# Contributing
Did you find an error that should have been caught but is not? Raise an issue or send a pull request!
# Licence
Released under the simplified BSD Licence. See [LICENCE](/LICENCE) for details.