Environment Variable Limit Exceeded in AWS Lambda due to many connection Strings

[pakeerubasha-mekala]

Issue Overview:
I am encountering an issue related to the 4 KB limit on environment variables in AWS Lambda. This limitation is affecting our Lambda function, which uses the Athena PostgreSQL connector, and requires us to store multiple connection strings. Unfortunately, we have reached the 4 KB limit for environment variables due to the number of connection strings we need to manage.

Issue Details:

• The AWS Lambda environment variables are limited to 4 KB in size, and this limitation is posing a challenge when storing connection strings for our Lambda function.
• Our use case requires us to store a significant number of connection strings, and this has pushed us beyond the allowed limit.
• As a result, we are seeking guidance, best practices, or potential solutions to efficiently manage and access these connection strings within the Lambda function while staying within the 4 KB limit.