Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Closed
9 of 12 tasks
dreamorosi opened this issue Jun 19, 2024 · 7 comments · Fixed by #2675
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 · 7 comments · Fixed by #2675
Assignees
@am29d
Labels
feature-request This item refers to a feature request for an existing or new utility layers Items related to the Lambda Layers pipeline pending-release This item has been merged and will be released soon

Comments

@dreamorosi
Copy link
Contributor

dreamorosi commented Jun 19, 2024 •
edited
Loading

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 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 dreamorosi mentioned this issue Jun 19, 2024
Merged
@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 linked a pull request Jun 24, 2024 that will close this issue
chore(layers): deploy Lambda layers in ap-south-2 and me-central-1 #2675
Merged
@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 •
edited
Loading

Access to requested regions granted.

@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 added confirmed The scope is clear, ready for implementation and removed on-hold This item is on-hold and will be revisited in the future labels Jul 1, 2024
@github-actions GitHub Actions
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 mentioned this issue Jul 1, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@am29d am29d

Labels
feature-request This item refers to a feature request for an existing or new utility layers Items related to the Lambda Layers pipeline pending-release This item has been merged and will be released soon
Projects
Powertools for AWS Lambda (TypeScript)
Status: Coming soon
Milestone
No milestone
2 participants
@am29d @dreamorosi