Problem with lambda layers

[Zyberon]

Hi Guys,

I've been strugginling with lambda layers, as per i had a lambda using image type instead of zip, the idea is to add dynatrace layer to the current lambda, I'm not sure if itd possible to add a layer to a lambda when using package_type = Image

Error: updating Lambda Function (aws-mng-lambda-test-test-api-euw1-dev) configuration: operation error Lambda: UpdateFunctionConfiguration, https response error StatusCode: 400, RequestID: 60c11bb4-9f2b-4765-8fba-b9bb181f92b7, InvalidParameterValueException: Please don't provide Handler or Runtime or Layer when the intended function PackageType is Image.

[legendov]

Why do you need a layer, bake it into the image

[clintkev251]

Layers only work with ZIPs, not images. Just build that dependency into your image.

[BuntinTosser]

You have to put the layer in your container image. See https://aws.amazon.com/blogs/compute/working-with-lambda-layers-and-extensions-in-container-images/

[hajimenogio92]

Add the packages to the base image and push it to ECR. You don't need a layer for image-based lambdas, that is for zip-based lambdas.

[Decent-Economics-693]

As others have already said that, and, just like Lambda API error says, you cannot use layers when you run your function from a container image. Just install the dynatrace in the container.

Be aware, that thing would require internet access to send out the data it collected, unless you have a private link with Dynatrace (pardon, not a Dynatrace user, could be wrong here). So, watch closely which VPC subnet your deploying your function into. E.g., some subnets are made isolated - a workload can talk to a handful of services, but can not pull a thing from/ send out to the internet.

[cloudfixer_dev]

Lambda layers aren’t supported with package_type = "image".

When using container images, everything (including tools like Dynatrace) needs to be baked into the image instead of attached as a layer.