*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2. * **ecs:** remove unnecessary error when adding volume to external task definition (( #19774)) (( 5446ded)), closes ( #19259) * **core:** reduce CFN template indent size to save bytes (( #19656)) (( fd63ca3)) * **core:** `Fn.select` incorrectly short-circuits complex expressions (( #19680)) (( 7f26fad)) * **codedeploy:** the Service Principal is wrong in isolated regions (( #19729)) (( 7e9a43d)), closes ( #19399) * **codedeploy:** add name validation for Application, Deployment Group and Deployment Configuration (( #19473)) (( 9185042)) * **cloudwatch:** automatic metric math label cannot be suppressed (( #17639)) (( 7fa3bf2)) * **cli:** support attributes of DynamoDB Tables for hotswapping (( #19620)) (( 2321ece)), closes ( #19421) * **cli:** apps with many resources scroll resource output offscreen (( #19742)) (( 053d22c)), closes ( #19160) * **aws_applicationautoscaling:** Add missing members to PredefinedMetric enum (( #18978)) (( 75a6fa7)), closes ( #18969) To configure the size of a function’s /tmp directory, set a whole number value between 512 MB and 10,240 MB, in 1-MB increments. You can increase or decrease this amount using the Ephemeral storage (MB) setting. * **core:** throw error when stack name exceeds max length (( #19725)) (( 1ffd45e)) Configuring ephemeral storage (console) By default, Lambda allocates 512 MB for a function’s /tmp directory. *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*įor convenience, extracted the relevant CHANGELOG entry: * Did you use `cdk-integ` to deploy the infrastructure and generate the snapshot (i.e. * Have you added the new feature to an ( )? * This PR adds new unconventional dependencies following the process described ( ) # Adding new Unconventional Dependencies:
Ephemeral storage lambda install#
I was currently only executing the pip install aws-sam-cli command on my CodeBuild image with the assumption that it was installing the latest version.* Have you followed the guidelines in our ( ) I am using aws/codebuild/amazonlinux2-x86_64-standard:3.0. It was my assumption CodePipeline uses the latest version of all CLIs in their standard CodeBuild Images. I am not defining a SAM CLI version in my Template.yaml or CodePipeline. If i was deploying the SAM locally with the CLI, this would be an easy fix.
Ephemeral storage lambda upgrade#
You’ll need to upgrade SAM CLI for this to be recognised.īut none of this is local. The Error you’re seeing is that SAM CLI doesn’t recognise the new property ‘EphemeralStorage’ during the transform. SAM CLI will transform your template to one which CloudFormation will accept. The plain CloudFormation type for Lambda is AWS::Lambda::Function. Resource type AWS::Serverless::Function is SAM not plain CloudFormation.
Ephemeral storage lambda code#
This is in cloudformation so why would my local cli version matter? Code gets pushed to GH, aws codepipeline stage picks it up and uses CF template to create changesets and apply changesets. Are you sure you have the latest version of the cli installed? 1.43.0 is working for me w/o teardown.
0 kommentar(er)
