Cloud.gov incident

Minor outage for brokered services - RDS, Elasticache/Redis, Elasticsearch/OpenSearch

Notice Resolved View vendor source →

Cloud.gov experienced a notice incident on March 5, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2025, 09:20 PM UTC
Resolved
Mar 05, 2025, 07:00 PM UTC
Duration
Detected by Pingoru
Mar 05, 2025, 09:20 PM UTC

Update timeline

  1. resolved Mar 05, 2025, 09:20 PM UTC

    At 2:13 PM ET, the broker which allows cloud.gov customers to create and to update AWS managed services (RDS, Elasticache/Redis, Elasticsearch/OpenSearch) became unreachable. During this time, requests to create or to update any managed services may have failed with 404 errors. At 2:39 PM ET, the broker was successfully restored and became reachable again. The cause of the outage was misconfiguration in the deployment pipeline for the broker which caused the broker application to be deployed without a public URL. Without a public URL, the broker itself is not reachable from the internet and thus customer requests to it will fail with 404 errors. The misconfiguration had been present in the code since December, but the broker had not been redeployed in production since before then, so the problem only became apparent when attempting to redeploy the broker in production today. The deployment misconfiguration was fixed with this PR: https://github.com/cloud-gov/aws-broker/pull/400. As always, cloud.gov takes any outages seriously and we will work to avoid a recurrence of this incident in the future.