- Newest
- Most votes
- Most comments
Severity is still „Disrupted“ -> https://health.aws.amazon.com/health/status
Affected AWS services
The following AWS services have been affected by this issue:
- AWS Client VPN
- AWS Cloud WAN
- AWS Cloud9
- AWS CloudHSM
- AWS CodeBuild
- AWS Compute Optimizer
- AWS Control Tower
- AWS Database Migration Service
- AWS Directory Service
- AWS Elastic Beanstalk
- AWS Elastic Disaster Recovery
- AWS Fargate
- AWS Lambda
- AWS Management Console
- AWS NAT Gateway
- AWS Network Firewall
- AWS Resource Explorer
- AWS Resource Groups Tagging API
- AWS Site-to-Site VPN
- AWS Transit Gateway
- AWS VPCE PrivateLink
- Amazon ElastiCache
- Amazon Elastic Compute Cloud
- Amazon Elastic Container Service
- Amazon Elastic File System
- Amazon Elastic Kubernetes Service
- Amazon Elastic Load Balancing
- Amazon Elastic MapReduce
- Amazon FSx
- Amazon Inspector
- Amazon Kinesis Firehose
- Amazon MQ
- Amazon Managed Streaming for Apache Kafka
- Amazon OpenSearch Service
- Amazon Redshift
- Amazon Relational Database Service
- Amazon Simple Notification Service
- Amazon VPC Lattice
- Auto Scaling
I don't have access to real-time AWS service health status or current incident information in the sources provided. To get the most accurate and up-to-date information about any ongoing issues in the AWS Bahrain (me-south-1) region, I recommend:
-
Check the AWS Service Health Dashboard - This provides real-time status of AWS services across all regions, including any ongoing incidents or maintenance activities.
-
Review your AWS Personal Health Dashboard - This is available in your AWS Console and provides personalized alerts and guidance for events that might affect your specific AWS resources.
-
Contact AWS Support - If you have an AWS Support plan, open a support case for immediate assistance with connectivity issues affecting your workloads.
Since you mentioned you're using MongoDB Atlas (a third-party service) hosted on AWS infrastructure, you should also:
-
Check MongoDB Atlas Status Page - MongoDB Atlas has its own status page that reports issues with their service, which may be independent of AWS infrastructure issues.
-
Contact MongoDB Atlas Support - They can provide specific information about any issues affecting their service in the me-south-1 region.
For immediate troubleshooting, you might want to verify your security group rules, network ACLs, and DNS configurations to rule out configuration issues on your end while investigating the connectivity problems.
Relevant content
- asked a year ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 8 months ago
Thank you for the update.
Do you have any estimated time for resolution (ETA) for the disruption in the Bahrain (me-south-1) region?
We currently have important data hosted there and access is critical for us.
Any guidance or workaround in the meantime would also be appreciated.
Thank you.
Please note that this is a community forum; an official statement can only be provided by AWS Support.
Accordingly, I recommend that you get in touch with AWS Support or, if available to you, your Technical Account Manager (TAM), Solutions Architect, or AWS Account Manager. I assume you have already opened a support case within the affected AWS account!?!