Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
9 of 12 tasks
dreamorosi opened this issue Jun 19, 2024 · 10 comments · Fixed by #2675 or #2933
Closed
9 of 12 tasks

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

dreamorosi opened this issue Jun 19, 2024 · 10 comments · Fixed by #2675 or #2933
Assignees
Labels
completed This item is complete and has been merged/shipped feature-request This item refers to a feature request for an existing or new utility layers Items related to the Lambda Layers pipeline

Comments

@dreamorosi
Copy link
Contributor

dreamorosi commented Jun 19, 2024

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

Future readers

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

@dreamorosi dreamorosi added triage This item has not been triaged by a maintainer, please wait feature-request This item refers to a feature request for an existing or new utility labels Jun 19, 2024
@dreamorosi dreamorosi moved this from Triage to Backlog in Powertools for AWS Lambda (TypeScript) Jun 19, 2024
@dreamorosi dreamorosi added confirmed The scope is clear, ready for implementation layers Items related to the Lambda Layers pipeline and removed triage This item has not been triaged by a maintainer, please wait labels Jun 19, 2024
@dreamorosi
Copy link
Contributor Author

@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
Copy link
Contributor

am29d commented Jun 19, 2024

Will be back tomorrow and we can go thorough it 🫡

@am29d
Copy link
Contributor

am29d commented Jun 20, 2024

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

@dreamorosi dreamorosi moved this from Backlog to Working on it in Powertools for AWS Lambda (TypeScript) Jun 20, 2024
@dreamorosi
Copy link
Contributor Author

I have bootstrapped the accounts but still need to run the script to align the versions. Please before running it let's talk offline.

@am29d
Copy link
Contributor

am29d commented Jun 26, 2024

Access to requested regions granted.

@dreamorosi dreamorosi moved this from Working on it to On hold in Powertools for AWS Lambda (TypeScript) Jun 26, 2024
@dreamorosi dreamorosi added on-hold This item is on-hold and will be revisited in the future and removed confirmed The scope is clear, ready for implementation labels Jun 26, 2024
@dreamorosi
Copy link
Contributor Author

Putting this on hold until the next iteration (next week).

@dreamorosi dreamorosi removed the on-hold This item is on-hold and will be revisited in the future label Jul 1, 2024
@dreamorosi dreamorosi moved this from On hold to Pending review in Powertools for AWS Lambda (TypeScript) Jul 1, 2024
@dreamorosi dreamorosi added the confirmed The scope is clear, ready for implementation label Jul 1, 2024
@github-project-automation github-project-automation bot moved this from Pending review to Coming soon in Powertools for AWS Lambda (TypeScript) Jul 1, 2024
Copy link
Contributor

github-actions bot commented Jul 1, 2024

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Jul 1, 2024
@dreamorosi dreamorosi moved this from Coming soon to On hold in Powertools for AWS Lambda (TypeScript) Jul 10, 2024
@dreamorosi dreamorosi added on-hold This item is on-hold and will be revisited in the future and removed pending-release This item has been merged and will be released soon labels Jul 10, 2024
@dreamorosi dreamorosi reopened this Jul 10, 2024
@github-project-automation github-project-automation bot moved this from On hold to Pending review in Powertools for AWS Lambda (TypeScript) Jul 10, 2024
@dreamorosi
Copy link
Contributor Author

Reopening this as we'll release the layers in these regions in a future iteration.

@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed on-hold This item is on-hold and will be revisited in the future labels Jul 10, 2024
@dreamorosi dreamorosi removed the pending-release This item has been merged and will be released soon label Jul 22, 2024
@dreamorosi dreamorosi moved this from Pending review to On hold in Powertools for AWS Lambda (TypeScript) Jul 22, 2024
@dreamorosi dreamorosi moved this from On hold to Working on it in Powertools for AWS Lambda (TypeScript) Aug 12, 2024
@dreamorosi dreamorosi moved this from Working on it to Pending review in Powertools for AWS Lambda (TypeScript) Aug 16, 2024
@dreamorosi dreamorosi self-assigned this Aug 16, 2024
@github-project-automation github-project-automation bot moved this from Pending review to Coming soon in Powertools for AWS Lambda (TypeScript) Aug 16, 2024
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

@github-actions github-actions bot added the pending-release This item has been merged and will be released soon label Aug 16, 2024
Copy link
Contributor

This is now released under v2.8.0 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Sep 16, 2024
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed This item is complete and has been merged/shipped feature-request This item refers to a feature request for an existing or new utility layers Items related to the Lambda Layers pipeline
Projects
3 participants