-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(aws-lambda): docker image function fails with insightsVersion property #16642
Comments
if someone needs a workaround, skip the property in the DockerImageFunction and add the policy like this:
the docker image needs the lambda-insights-extension in any case
|
…ified Lambda insights is configured as a set of layers that are then auto-added to the lambda function when the `insightsVersion` property is specified. However, Lambda functions deployed as container images cannot contain layers. Instead, the user is expected to bring a container image with the Insights agent pre-installed. Update the CDK code, so that the layer is not added for Lambda functions that use container images. fixes #16642
…ified (#16781) Lambda insights is configured as a set of layers that are then auto-added to the lambda function when the `insightsVersion` property is specified. However, Lambda functions deployed as container images cannot contain layers. Instead, the user is expected to bring a container image with the Insights agent pre-installed. Update the CDK code, so that the layer is not added for Lambda functions that use container images. fixes #16642 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
…ified (aws#16781) Lambda insights is configured as a set of layers that are then auto-added to the lambda function when the `insightsVersion` property is specified. However, Lambda functions deployed as container images cannot contain layers. Instead, the user is expected to bring a container image with the Insights agent pre-installed. Update the CDK code, so that the layer is not added for Lambda functions that use container images. fixes aws#16642 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
when using a DockerImageFunction and trying to enable cloudwatch lambda insights through the
insightsVersion
property, lambda service fails to create the function with error:Reproduction Steps
What did you expect to happen?
to skip adding a layer and just manage the execution role instead
What actually happened?
creation failed
Environment
Other
my first idea to fix this would be to overwrite the configureLambdaInsights method in the DockerImageFunction Class and just add the manged policy there and skip the addLayers part.
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: