I have following basic security related questions regarding AWS Lambda service:
Thanks
Lambda always encrypts files that you upload to Lambda, including deployment packages and layer archives. Amazon CloudWatch Logs and AWS X-Ray also encrypt data by default, and can be configured to use a customer managed key.
Today, we are announcing that AWS Lambda now allows you to configure ephemeral storage ( /tmp ) between 512 MB and 10,240 MB. You can now control the amount of ephemeral storage a function gets for reading or writing data, allowing you to use AWS Lambda for ETL jobs, ML inference, or other data-intensive workloads.
Amazon EFS for Lambda Amazon EFS is a fully managed, elastic, shared file system that integrates with other AWS services. It is durable storage option that offers high availability. You can now mount EFS volumes in Lambda functions, which makes it simpler to share data across invocations.
One important sidenote to the /tmp of Lambda functions is that the Lambda function containers are re-used and scratch space is not always erased. If an invocation uses a container that was spun up because of a previous invocation (this happens if you execute a few Lambda function in quick succession), the scratch space is shared.
This screwed up a functionality for me once.
I store temporary data in my lambda function, never had any issue.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With