AWS not working in India today?

How to Contact Amazon Web Services (AWS) Technical Support

- By Hotline Phone for customers: 000 800 100 9640 (India Toll-Free, 24x7); 1-888-610-2915 (USA & Canada Toll-Free, 24x7); For Business and Enterprise Support, sign in to your AWS Console and create a support case or call numbers provided under your support plan.

- E-mail: AWS does not provide a general support email; all technical inquiries and case tracking are handled through the AWS Support Center after login.

- Through Feedback Form or Personal Account: https://aws.amazon.com/support (sign in required to open a support case or use live chat).

- In the AWS Console Mobile App for Android and iOS devices.

- For billing and account-specific inquiries: https://aws.amazon.com/contact-us/, where you can request a callback or initiate a live chat after logging in with your AWS account.

Latest News and Updates:

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

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

- Instagram: https://www.instagram.com/amazonwebservices;

- X: https://x.com/awscloud;

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

- Reddit: https://www.reddit.com/r/aws.

EC2 Instance Not Working or Down?

Possible Issues:

- Instance is unreachable, not starting, or becomes unresponsive.

- Connection timeout or SSH/RDP failures.

- Instance status checks failing or reboot loops.

How to Fix:

- Verify the instance’s state in the AWS Management Console (running, stopped, or terminated).

- Check security group and network ACL settings to ensure inbound/outbound traffic is allowed.

- Review instance logs and system status checks for hardware or underlying host issues.

- Restart or stop/start the instance if possible.

- If persistent, restore from an AMI backup or contact AWS Support for assistance.

S3 Service Outage or Access Failure?

Possible Issues:

- Unable to upload, download, or list objects in buckets.

- Access denied errors or missing bucket.

- Increased latency or repeated timeout errors.

How to Fix:

- Check the AWS Service Health Dashboard (​https://​status.​aws.​amazon.​com/) to see if there is a region-wide S3 outage.

- Verify IAM policies and bucket permissions to ensure proper access.

- Review request settings and try from a different region or account if applicable.

- If access is still denied, audit your credentials and contact AWS Support if needed.

AWS Console Not Loading or Login Failure?

Possible Issues:

- Web console pages not loading or showing errors.

- Unable to sign in or access resources.

- Console loops or session expired issues.

How to Fix:

- Clear browser cache/cookies or try another browser/device.

- Ensure your AWS credentials and MFA (if enabled) are correct.

- Check if there is a known regional outage (use AWS Service Health Dashboard).

- Reset password or use alternative login methods where possible.

- Contact AWS Support if you still cannot access your account.

RDS Database Instance Down or Unavailable?

Possible Issues:

- Database not accessible, slow queries, or connection failures.

- Automated backups or snapshots not being created.

- Failover not completing or stuck on maintenance.

How to Fix:

- Check RDS instance metrics and logs via the Console.

- Confirm network and security group configurations permit database connections.

- Reboot the RDS instance or initiate a manual failover if possible.

- If linked to a VPC, validate routing tables and NACLs.

- Contact AWS Support if the issue persists or is impacting production.

Lambda Function Failure or Throttling?

Possible Issues:

- Function not executing or erroring out.

- Significant delays, timeouts, or throttling due to request limits.

How to Fix:

- Review logs in CloudWatch for error messages and execution times.

- Check if you’ve reached regional or account resource limits.

- Verify function permissions, triggers, and environment variables.

- Consider increasing allocated memory or timeout settings.

- Contact AWS Support for advanced troubleshooting.

VPC Network Issues or Outage?

Possible Issues:

- Connectivity failures between resources within VPC or to the internet.

- Routing, DNS issues, or PrivateLink failures.

- Peering, VPN, or Direct Connect links down.

How to Fix:

- Review VPC route tables, security groups, and NACLs for misconfigurations.

- Check status of attached gateways and endpoints.

- Use VPC Reachability Analyzer for deeper diagnostics.

- Refer to AWS Health Dashboard for regional VPC outages.

- If resolution is complex, open a support case.

IAM Authentication or Permission Failure?

Possible Issues:

- Users or applications unable to access AWS resources.

- “Access Denied” errors on console or API requests.

How to Fix:

- Review and update IAM policies, roles, and group attachments.

- Check for changes in trust relationships or authentication method.

- Rotate keys or credentials if needed.

- Use IAM Policy Simulator to debug permission issues.

- Escalate to AWS Support if critical business processes are blocked.

CloudFront Distribution Down or Content Not Loading?

Possible Issues:

- Stale, missing, or slow-loading content.

- Distribution returns 403, 404, or 5xx errors.

- SSL certificate issues or domain validation failures.

How to Fix:

- Invalidate cache or update origin configurations in the CloudFront console.

- Check CloudFront and origin server health and permissions.

- Ensure DNS records are correct and certificates are valid.

- Monitor via AWS CloudWatch and enable logging for diagnosis.

- Reach out to AWS Support for urgent distribution problems.

Stay updated on AWS service issues through our platform!