-
Notifications
You must be signed in to change notification settings - Fork 376
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
Publish layer to Gov Cloud regions #1166
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Thanks a lot for raising this @bryantbiggs - I'm moving to the Roadmap under Backlog as it's something we want to do, but require additional permissions internally given its purpose and regulations. |
Update: @am29d is working on migrating our internal Lambda Layers pipeline to CodePipeline in a Powertools AWS account. Once that's done (~H2), we should be able to expand to more AWS regions - that said, GovCloud is a special region and might take longer for us to get approval to do so. You can follow progress here: https://github.com/orgs/awslabs/projects/51/views/11 |
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
any updates on this one? |
Hi @kb-fusus I'm actively looking for an update on this, and will get back to you shortly. Publishing the layer to the Gov Cloud regions is a very complex operation, but we're looking to understand the best way to making it work. Thank you for your ping! |
@rubenfonseca Also wanted to +1 from a customer side how great it would be to have this available in GovCloud. Specifically, the added optimization the team does compared to just pip installing or packaging ourselves would be a huge win. Thanks! |
thanks a lot @dannellyz! We're still looking for US specific controls and procedures to work on this. You could help us prioritize this by sending an email from your corporate address to aws-lambda-powertools-feedback at amazon dot com. We're collecting customer names / gov agencies to help expedite some of these controls. Thank you! |
Will do! |
Adding this to our public roadmap as of now to make it easier for agencies to reach out to us to help prioritize: https://docs.powertools.aws.dev/lambda/python/stage/roadmap/#lambda-layer-in-govcloud-and-china-region Sent an internal email asking about GovCloud region requirements to publish this Layer. |
Adding the |
Hi everyone, we're still researching this feature. Because of the complexities of GovCloud, this is taking us longer than expected. We'll share any updates as we have them. Thank you |
Update: we found a way to move forward and to add the Layer to GovCloud regions. Expect to have news by the end of the week! Stay tunned :) |
Update: we’ve completed our infrastructure changes and we are going through additional security and compliance requirements. We’ll keep you posted as soon as we have updates on a plausible ETA; tentatively after re:invent / early next year. |
It would be really interesting to read on the additional measures you have to take to qualify for the requirements |
it's all internal @drissamri the only extra bit we will need to do is to create provenance for the Layer w/ all dependencies, or SBOM (easy). If you'd like to learn more about AppSec & supply chain security in general, reach out to @sthulb (Simon is on Discord!) |
Hey, everyone! We are still working on this with internal teams and we may have some good news next month. Changing the status to "Working on it" |
greetings! we have a production system that relies on power tools and this is the only blocker to migrating this to GovCloud. :-) can we support this in any way? |
Hi folks! We've been making steps towards our releases on GovCloud (us-gov-west-1, us-gov-east-1). If all goes well, we aim to have releases by the end of July. We'll post weekly updates here to document progress (or lack of it, if we have no new news to share). Thanks |
Hi folks! We have created the accounts and in the process of bootstrapping them, hopefully this time next week we'll be in a position to deploy into them. A question for anyone reading: Do you want:
Thanks |
just the latest - motivation for folks to update 😉 |
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: