CyberArk Secrets Hub incident
Secrets Hub interruption in secrets sync from PAM (Privilege Cloud & PAM Self-Hosted) to AWS in ap-southeast-1.
CyberArk Secrets Hub experienced a critical incident on August 29, 2024 affecting Singapore (ap-southeast-1), lasting 27m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 29, 2024, 09:31 AM UTC
We are encountering issues in syncing secrets from PAM (Privilege Cloud & PAM Self-Hosted) to AWS in ap-southeast-1. Our team is working on it and we’ll inform you once this issue is resolved. We apologize for any inconvenience. Best regards, CyberArk Secrets Hub
- investigating Aug 29, 2024, 09:31 AM UTC
We are continuing to investigate this issue.
- monitoring Aug 29, 2024, 09:40 AM UTC
The issue is with AWS's IAM service which impacts Secrets Hub. AWS submitted the following statement in their Status Page: Aug 29 2:31 AM PDT We are investigating connectivity issues, impacting requests made to AWS STS (Security Token Service). We are actively investigating this issue and will provide more information within the next 30 minutes. You can track this issue at: https://health.aws.amazon.com/health/status We will update once the issue is resolved on our end.
- resolved Aug 29, 2024, 09:58 AM UTC
The issue is now resolved and syncs are successful in Secrets Hub. Thank you for your patience :)