Is AWS down today?

How to Contact AWS Technical Support?

- AWS Support Center at console.aws.amazon.com/support;

- AWS re:Post community at repost.aws;

- AWS Documentation at docs.aws.amazon.com;

- AWS Forums at forums.aws.amazon.com.

Latest News and Current Information:

- X (AWS) - https://x.com/awscloud;

- X (AWS Support) - https://x.com/AWSSupport;

- LinkedIn - https://www.linkedin.com/company/amazon-web-services;

- Facebook - https://www.facebook.com/amazonwebservices;

- YouTube - https://www.youtube.com/user/AmazonWebServices;

- Official Website - https://aws.amazon.com;

- Service Health Dashboard - https://status.aws.amazon.com;

- What's New - https://aws.amazon.com/new;

- AWS Blog - https://aws.amazon.com/blogs;

- Documentation - https://docs.aws.amazon.com;

- AWS re:Post - https://repost.aws.

Amazon Web Services Outage: Service Unavailable or Region Issues

When AWS experiences an outage, users may encounter service unavailability, API failures, or complete inability to access resources.

- Check AWS Service Health Dashboard at status.aws.amazon.com;

- Monitor AWS Health in console for account-specific issues;

- Verify region-specific outages;

- Try accessing through different AWS regions;

- Check AWS Personal Health Dashboard;

- Review AWS Status history for patterns;

- Wait 15-30 minutes during confirmed outages;

- Implement multi-region failover if critical.

EC2 Instance Problem: Instances Not Starting or Connection Issues

EC2 problems include instances not launching, SSH/RDP connection failures, or instance crashes.

- Check instance status checks in console;

- Verify security group rules allow access;

- Check network ACLs for blocking rules;

- Verify key pair for SSH access;

- Review instance system logs;

- Check if instance limits reached;

- Verify subnet has available IP addresses;

- Stop and start instance (not reboot);

- Check instance type availability in region;

- Review CloudWatch metrics for issues.

S3 Bucket Fault: Cannot Access or Upload Files

S3 issues include access denied errors, upload failures, or bucket not found messages.

- Verify bucket name and region correct;

- Check bucket policy and IAM permissions;

- Review CORS configuration if web access;

- Verify object ownership settings;

- Check bucket versioning status;

- Review access control lists (ACLs);

- Verify encryption settings compatible;

- Check if bucket blocked public access;

- Review S3 Storage Lens for insights;

- Test with AWS CLI for detailed errors.

IAM or Authentication Issue: Permission Denied or Access Errors

IAM problems include permission denied errors, credential failures, or policy issues.

- Verify IAM user or role has required permissions;

- Check policy syntax for errors;

- Review service control policies (SCPs);

- Verify MFA configured correctly if required;

- Check access keys are active and valid;

- Review resource-based policies;

- Test with IAM Policy Simulator;

- Verify trust relationships for roles;

- Check temporary credentials not expired;

- Review CloudTrail logs for denied actions.

RDS Database Problem: Cannot Connect or Query Errors

RDS issues include database connection failures, slow queries, or unavailability.

- Verify database instance status is available;

- Check security group allows inbound connections;

- Verify database endpoint and port correct;

- Check database credentials valid;

- Review parameter group settings;

- Monitor database performance metrics;

- Verify subnet group configuration;

- Check storage space not full;

- Review slow query logs;

- Test connection from bastion host.

Lambda Function Fault: Functions Not Executing or Timeout Errors

Lambda problems include function failures, timeout errors, or invocation issues.

- Check function logs in CloudWatch;

- Verify execution role has required permissions;

- Review function timeout settings (max 15 min);

- Check memory allocation sufficient;

- Verify environment variables configured;

- Review concurrent execution limits;

- Check trigger configuration correct;

- Test function with test events;

- Verify VPC configuration if applicable;

- Review reserved concurrency settings.

VPC or Networking Issue: Connection Problems or Routing Errors

VPC problems include connectivity failures, routing issues, or subnet problems.

- Verify route table configurations;

- Check internet gateway attached;

- Review NAT gateway status and routes;

- Verify security group rules;

- Check network ACL rules;

- Test VPC peering connections;

- Verify VPN or Direct Connect status;

- Review subnet CIDR blocks;

- Check elastic IP associations;

- Use VPC Reachability Analyzer.

CloudFront or CDN Problem: Content Not Delivering or Cache Issues

CloudFront issues include content not loading, SSL errors, or caching problems.

- Check distribution status is deployed;

- Verify origin server accessible;

- Review cache behaviors and settings;

- Check SSL certificate valid and configured;

- Clear CloudFront cache for objects;

- Review origin access identity settings;

- Verify DNS records point to CloudFront;

- Check geographic restrictions;

- Review CloudFront access logs;

- Test with direct origin access.

Billing or Cost Issue: Unexpected Charges or Billing Errors

Billing problems include unexpected costs, billing alerts, or payment failures.

- Review Cost Explorer for usage breakdown;

- Check AWS Cost and Usage Reports;

- Verify budgets and alerts configured;

- Review resource tags for cost allocation;

- Check for unused resources running;

- Verify Reserved Instance utilization;

- Review Savings Plans coverage;

- Check for data transfer charges;

- Monitor AWS Free Tier usage;

- Contact AWS Billing Support.

Auto Scaling Problem: Instances Not Scaling or Health Check Failures

Auto Scaling issues include scaling not triggering, unhealthy instances, or launch failures.

- Check Auto Scaling group activity history;

- Verify scaling policies configured correctly;

- Review CloudWatch alarms triggering;

- Check launch template or configuration;

- Verify health check grace period;

- Review instance capacity limits;

- Check load balancer health checks;

- Verify subnet availability zones;

- Review scaling cooldown periods;

- Test manual scaling to diagnose.

ELB or Load Balancer Fault: Load Balancer Not Distributing Traffic

Load balancer problems include unhealthy targets, connection issues, or SSL errors.

- Check target group health status;

- Verify security groups allow traffic;

- Review listener and routing rules;

- Check SSL certificate configuration;

- Verify targets registered correctly;

- Review health check settings;

- Check cross-zone load balancing;

- Monitor load balancer metrics;

- Verify subnet configuration;

- Test with load balancer DNS name.

CloudWatch or Monitoring Issue: Metrics Not Appearing or Alarm Errors

CloudWatch problems include missing metrics, alarm not triggering, or log errors.

- Verify CloudWatch agent installed and running;

- Check IAM permissions for CloudWatch;

- Review metric namespace and dimensions;

- Verify alarm configuration and thresholds;

- Check metric retention periods;

- Review log group and stream settings;

- Verify metric filters configured;

- Check SNS topic subscriptions;

- Test alarm with set alarm state;

- Review CloudWatch service limits.

Route 53 or DNS Problem: Domain Not Resolving or Routing Errors

Route 53 issues include DNS resolution failures, health check problems, or domain errors.

- Verify hosted zone configuration;

- Check name server records at registrar;

- Review DNS record sets and values;

- Test with DNS lookup tools (dig, nslookup);

- Verify health check configuration;

- Check TTL values for propagation;

- Review traffic policy if used;

- Verify domain not expired;

- Check DNSSEC configuration;

- Monitor query metrics in console.