# Why does 11 environment variables exceed the AWS Lambda limit?

**URL:** <https://answers.netlify.com/t/why-does-11-environment-variables-exceed-the-aws-lambda-limit/56194>\
**Category:** Support\
**Tags:** environment-vars, deployment\
**Created:** [May 9, 2022, 2:23pm UTC](https://answers.netlify.com/t/why-does-11-environment-variables-exceed-the-aws-lambda-limit/56194 "2022-05-09T14:23:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![perry](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/perry/32/16_2.png) [@perry](https://answers.netlify.com/u/perry)\
**Post date:** [May 9, 2022, 8:24pm UTC](https://answers.netlify.com/t/why-does-11-environment-variables-exceed-the-aws-lambda-limit/56194/4 "2022-05-09T20:24:37Z")

</div>

hi there, totally get what you are saying -

there are a few other threads in this forum that may contain something helpful (try searching for `4kb`)

this seems to be the most in depth one:

> [@Netlify Functions and Env Variables from netlify.toml](https://answers.netlify.com/t/netlify-functions-and-env-variables-from-netlify-toml/4404):
>
> I am trying to use Netlify lambda functions but I need access to certain environmental variables. It does not seem like I have access to those variables that I set in my Netlify.toml, but only have access to the environmental variables set up in the Netlify UI. Is there no way to access variables within the toml with a lambda function? The function needs to know what type of build (branch-deploy, production, staging, develop, etc.), but because process.env doesn’t have access to the toml enviro…

i can ask another team member to weigh in, but i am not sure we’ll have anything new to suggest that isn’t mentioned in another thread.

---

_[View the full topic](https://answers.netlify.com/t/why-does-11-environment-variables-exceed-the-aws-lambda-limit/56194)._