chore: temporarily remove Bahrain (me-south-1) region from layer publishing#5169
Merged
chore: temporarily remove Bahrain (me-south-1) region from layer publishing#5169
Conversation
sdangol
approved these changes
Apr 7, 2026
powertools-for-aws-oss-automation
Bot
added
size/XS
|
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
Temporarily disable the Bahrain (
me-south-1) region from layer publishing and SSM parameter updates due to ongoing service disruptions.Changes
me-south-1from the region matrix inreusable_deploy_layer_stack.ymlme-south-1from the region matrix inupdate_ssm.ymlme-south-1as temporarily paused indocs/getting-started/lambda-layers.mdIssue number: closes #5168
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.