chore(layers): deploy Lambda layers in ap-south-2 and me-central-1
#2675
Conversation
This file contains 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
boring-cyborg
bot
added
automation
github-actions
bot
added
the
feature
This comment was marked as outdated.
This comment was marked as outdated.
github-actions
bot
added
do-not-merge
dreamorosi
removed
do-not-merge
12 tasks
12 tasks
|
|
@am29d - I have already backfilled the versions from 1 through 8 of the v2 layer in these two regions in the production account. |
am29d
approved these changes
Jul 1, 2024
am29d
changed the title
ap-south-2 and me-central-1ap-south-2 and me-central-1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR adds the necessary config to the CI workflows to deploy our public Lambda layers to two new commercial regions:
ap-south-2andme-central-1.Additionally, the PR also includes changes to the docs, so that these two new regions show up in the table that lists all the layer ARNs.
Issue number: #2674
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.