-
We've been using self-mutating pipelines for a while now with no issues and it's been a great experience. During yesterday's AWS outage (Operational issue - ElasticContainerService (N. Virginia)) we saw several of the deployments fail in the "Wave" (deploy phase) due to the ECS outage. Fine. We waited for the outage to end... However this morning when we tried to run the pipeline execution again (release change) we saw the following error in the "Build" phase of the self-mutating pipeline :
That's it. No other explanation. We also tried to run the execute pipeline that was successful back on the 4th of August in our production account (no changes at all, just "Release Change" again, no source triggered) and it's failing at the exact same place, with this really terse error message. We're running CDK v1 (1.151.0). Any ideas on what's going on ? What "limit" is exceeded ? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
We were observing the same but it just started working again. I suspect AWS had a service outage but did not announce it. |
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
We were observing the same but it just started working again. I suspect AWS had a service outage but did not announce it.