Why does 11 environment variables exceed the AWS Lambda limit?

[perry]

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

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.