Feature request: deploy Lambda layers in `ap-south-2` and `me-central-1` regions

[dreamorosi]

Use case

As per issue title, we should start publishing our Lambda layers to these two regions starting from the next release. This will allow us to have the layer showing up in the Lambda console UI as well as allow customers to use the Layer in them.

Solution/User Experience

Following the process described here, we should do the following actions:

• enable me-central-1 opt-in region in beta account
• enable me-central-1 opt-in region in prod account
• bootstrap cdk in me-central-1 in beta account
• bootstrap cdk in me-central-1 in prod account
• bootstrap cdk in ap-south-2 in beta account
• bootstrap cdk in ap-south-2 in prod account
• add regions in .github/workflows/reusable_deploy_layer_stack.yml list
• add regions in docs/index.md table
• run layer-balancer in ap-south-2 prod account
• run layer-balancer in me-central-1 prod account

Alternative solutions

No response

Acknowledgment

• This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[dreamorosi]

@am29d - I need your help with this one. I am not sure how to enable the opt-in region in the two accounts. Also if you could help me with aligning the layer versions I'd appreciate it.

I have already bootstrapped in the enabled region and made the changes to the files in the repo, PR is here #2675

[am29d]

Will be back tomorrow and we can go thorough it 🫡

[am29d]

Access for me-central-1 requested, waiting for update.