All Shared Platforms: AWS Connector Validation failures [IM-12562]

Update timeline

1. investigating Apr 01, 2026, 06:55 AM UTC

   Qualys Cloud Platform Operations is investigating an issue causing Connector Validation Runscope failures in AWS Connector processing. Users may experience issues where endpoints are not reachable from AWS. Further updates will be shared as they become available.

2. investigating Apr 01, 2026, 10:13 AM UTC

   Qualys Cloud Platform Operations is investigating an issue causing Connector Validation failures in AWS Connector processing. Users may experience issues when endpoints are unreachable from AWS. Based on current observations, AWS connectors will enter an ERROR state if any of the affected region are selected. Also, due to the same issue, AWS connectors are in a queued state on the US Platform 1 If me-south-1 (Bahrain) remains enabled in your multi-region connectors, the connector will enter an Error state and stop processing ALL regions, including healthy ones. This means your visibility into security posture will be completely lost across all AWS regions until it is resolved. Impacted regions: AWS Middle East (Bahrain) – me-south-1 As a workaround, customers/users can temporarily unselect this region until AWS services are fully restored. Immediate Action Required, to restore connector functionality for your other regions: 1. Navigate to TotalCloud → Connectors → [Your AWS Connector] 2. Click Edit Connector 3. Under Regions, uncheck me-south-1 (Bahrain) 4. Click Save 5. Connector will resume scanning other regions within 5-10 minutes Alternative (API): bash# Remove me-south-1 from connector regions curl -X PATCH https://api.totalcloud.io/v1/connectors/{connector-id} \ -H "Authorization: Bearer YOUR_TOKEN" \ -d '{"regions": ["us-east-1", "us-west-2", "eu-west-1"]}' # exclude me-south-1 AWS service status can be tracked here: https://health.aws.amazon.com/health/status Further updates will be shared as they become available. The incident ticket for reference is IM-12562.

3. identified Apr 01, 2026, 10:56 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Apr 04, 2026, 07:01 AM UTC

   A fix has been implemented and currently monitoring it. Note:- Please make a note that if a connector is in an error or queued state, please rerun to get appropriate results.

5. resolved Apr 06, 2026, 03:36 AM UTC

   This incident has been resolved.