chore(ci): temporarily disable me-central-1 deployments #5111
Merged
Conversation
…e disruptions Comment out me-central-1 from the deploy layer and SSM update workflow matrices, and add a note in the Lambda layers docs.
|
sdangol
approved these changes
Mar 19, 2026
svozza
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Changes
Temporarily disable
me-central-1from the layer deployment and SSM update workflow matrices due to service disruptions in the region. A note has been added to the Lambda layers documentation.me-central-1inreusable_deploy_layer_stack.ymlregion matrixme-central-1inupdate_ssm.ymlregion matrixdocs/getting-started/lambda-layers.mdnoting new layer versions are pausedIssue number: closes #5110
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.