AWS imposes a hard limit of 4KB on Lambda config data which is soon met when using a few encrypted environment variables.
There should be the ability to set the source of an env var to an s3 json file, the contents of which can be cached in memory, meaning we only request it on cold starts.
aceew
commented
7 years ago
AWS imposes a hard limit of 4KB on Lambda config data which is soon met when using a few encrypted environment variables.
There should be the ability to set the source of an env var to an s3 json file, the contents of which can be cached in memory, meaning we only request it on cold starts.