API Monitoring

Monitor AWS API

Get alerted when AWS services have issues that could affect your infrastructure.

Why Monitor AWS?

Infrastructure dependencies — Most modern apps depend on multiple AWS services.
Regional issues — AWS outages are often region-specific. Monitor your specific regions.
Service-specific problems — S3 might be fine while Lambda is struggling.

Endpoints to Monitor

https://s3.{region}.amazonaws.com/{bucket}/health.txt

Create a health check file in S3 and monitor its accessibility.

https://{api-id}.execute-api.{region}.amazonaws.com/health

API Gateway health endpoint. Monitor your API Gateway deployments.

https://{function-url}.lambda-url.{region}.on.aws/

Lambda function URL. Direct monitoring of Lambda functions.

AWS APIs often require signed requests. Create public health endpoints for easier monitoring.

Official AWS Status

AWS maintains a status page at health.aws.amazon.com. However, it's notoriously slow to update during major outages.

Key services to watch:

• EC2 (Compute)
• S3 (Storage)
• Lambda (Serverless)
• RDS (Database)
• CloudFront (CDN)
• API Gateway

Monitoring Strategy

Monitor your endpoints, not AWS's — Your app's health matters more than AWS's status page.
Multi-region checks — Monitor from outside AWS to detect network issues.
Create canary endpoints — Simple Lambda functions that test your dependencies.
Monitor CloudWatch too — Set up CloudWatch alarms as a backup.

Start monitoring AWS

Add your AWS endpoints to your monitors and get alerted on issues instantly.

Start monitoring free →

Monitor Other APIs

Vercel API GitHub API Stripe API OpenAI API