When your AWS-hosted application goes down, the first question is always: "Is it AWS or is it my code?" The AWS Health Dashboard helps you quickly identify AWS service issues affecting your resources. This guide explains how to use both the public Service Health Dashboard and your Personal Health Dashboard.
Quick Check: Is AWS Down Right Now?
For public AWS status:
- Visit health.aws.amazon.com
- No login required
- Shows all AWS services globally
For issues affecting YOUR resources:
- Sign in to AWS Console
- Search for AWS Health or click the bell icon
- Check Your account health
Understanding the Two Dashboards
| Feature | Service Health Dashboard | Personal Health Dashboard |
|---|---|---|
| URL | health.aws.amazon.com | AWS Console > AWS Health |
| Login required | No | Yes |
| Shows | All public AWS incidents | Issues affecting YOUR resources |
| Scope | Global, all regions | Your account, your regions |
| Alerts | RSS feed only | EventBridge, SNS, Lambda |
| History | Past incidents | 90 days of account events |
Using the Service Health Dashboard
The public dashboard at health.aws.amazon.com shows the real-time status of all AWS services:
- Go to health.aws.amazon.com
- View the status table showing all services
- Filter by:
- Region: Focus on your deployment regions
- Service: Check specific services (EC2, RDS, S3)
- Click any service for detailed status and history
Status Icons
- ✓ Green: Service operating normally
- ℹ️ Blue: Informational message
- ⚠️ Yellow: Service degradation
- ❌ Red: Service disruption
Subscribe to Updates
Click the RSS icon to subscribe to status updates in your feed reader.
Using the Personal Health Dashboard
The Personal Health Dashboard provides proactive alerts for issues that may affect YOUR specific AWS resources.
Access Personal Health Dashboard
- Sign in to AWS Management Console
- Click the bell icon in the top navigation
- Or search for AWS Health in services
- Or go to phd.aws.amazon.com directly
Dashboard Sections
Open Issues
Current events affecting your resources:
- Service issues impacting your running instances
- Scheduled maintenance for your resources
- Account-specific notifications
Scheduled Changes
Upcoming maintenance that may affect you:
- EC2 instance retirements
- RDS maintenance windows
- Certificate expirations
Other Notifications
Informational messages about:
- New features in services you use
- Security bulletins
- Billing alerts
Set Up Automated Alerts
Configure EventBridge to receive automatic notifications for AWS Health events.
Step 1: Create an SNS Topic
- Go to Amazon SNS > Topics
- Click Create topic
- Choose Standard type
- Name it:
aws-health-alerts - Click Create topic
Step 2: Create an Email Subscription
- Click on your topic
- Click Create subscription
- Protocol: Email
- Endpoint: [email protected]
- Click Create subscription
- Confirm the subscription via email
Step 3: Create EventBridge Rule
- Go to Amazon EventBridge > Rules
- Click Create rule
- Name:
aws-health-to-sns - Event bus: default
- Rule type: Rule with an event pattern
- Click Next
Step 4: Configure Event Pattern
For all AWS Health events:
{
"source": ["aws.health"],
"detail-type": ["AWS Health Event"]
}For specific services only (e.g., EC2 and RDS):
{
"source": ["aws.health"],
"detail-type": ["AWS Health Event"],
"detail": {
"service": ["EC2", "RDS"]
}
}Step 5: Set Target
- Target type: AWS service
- Select target: SNS topic
- Topic: aws-health-alerts
- Click Next, review, and create
AWS Health API
For programmatic access, use the AWS Health API (requires Business or Enterprise Support plan):
# List all events affecting your account
aws health describe-events --region us-east-1
# Get details of a specific event
aws health describe-event-details --event-arns "arn:aws:health:..."
# List affected entities (specific resources)
aws health describe-affected-entities --filter eventArns="arn:aws:health:..."Best Practices
- Check Personal Health first: More relevant than public dashboard for your issues
- Set up alerts: Don't rely on manually checking dashboards
- Monitor multiple channels: Status page + CloudWatch + third-party monitoring
- Document incidents: Keep records for post-mortems and SLA claims
- Test your alerts: Verify notification pipeline works before real incidents
When the Dashboard Shows Green But You're Down
If AWS shows healthy but your service is down, check these in order:
- Personal Health Dashboard: Account-specific issues
- CloudWatch metrics: Resource-level health
- Security groups: Network access rules
- IAM permissions: Access denied errors
- Application logs: Your code may be the issue
- DNS resolution: Check your domain points to correct IPs