Solution is:

Remove Secrets from the .env File

This issue includes a critical vulnerability where an AWS secret access key was exposed in the .env file. This poses a security risk as sensitive credentials can be leaked. The key to mitigating the issue was commented out/Removed, and the recommendation is to manage secrets via environment variables or an AWS IAM role