Use docker image for pipeline orchestrator lambda #1
Comments
nicolaei
added a commit
that referenced
this issue
Dec 10, 2021
Trying again by adding gcc, g++ and make. This is just a workaround and adds a lot of time to terraform apply. Mitigations for this issue (both should be implemented): 1. Build a docker container for the lambda (see #1) 2. Get the issue in stepfunctions fixed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This announcement from AWS in November managed to sneak past me: https://aws.amazon.com/about-aws/whats-new/2021/11/aws-lambda-support-cross-account-image-amazon-elastic-container-registry/
Why?
This would allow us to have a central place to update the pipeline orchestrator, and thus update all pipelines from one centrally managed repo, while still keeping pipelines account-local.
How?
By using a cross account ECR registry, we can manage the orchestrator centrally.
The central ECR registry will have to allow the entire org to pull from it, which is possible with a conditional policy.
Relevant documentation: https://docs.aws.amazon.com/lambda/latest/dg/configuration-images.html#configuration-images-permissions
The text was updated successfully, but these errors were encountered: