I forgot to return to this, so I figured I would post this here to assist others that may be struggling as Python is really finicky.
The following is the structure of a functional project in Lambda:
βββ README.md
βββ buildspec.yml
βββ lambda_handler.py
βββ locales
β βββ en
β β βββ LC_MESSAGES
β β βββ base.po
β βββ es
β β βββ LC_MESSAGES
β β βββ base.po
β βββ fr
β β βββ LC_MESSAGES
β β βββ base.po
βββ my_project_name
β βββ __init__.py
β βββ python_file_1.py
β βββ python_file_2.py
β βββ python_file_3.py
β βββ repositories
β β βββ __init__.py
β β βββ resolvers_1.py
β β βββ resolvers_2.py
βββ requirements-dev.txt
βββ requirements.txt
βββ template.yml
βββ tests
βββ __init__.py
βββ tests_file_1.py
βββ tests_file_2.py
βββ tests_file_3.py
βββ tests_file_4.py
Note that the base.mo files are generated in the build in the same location as the base.po files and that requirements-dev.txt has dev-only libraries, such as pep8 for formatting and is only run within my local conda environments [I set up virtual environments for each project using miniconda]. The purpose of the resolvers in the nested repositories folder is to separate out the controller-like python files from the calls to the repositories to retrieve data.
Answer from MapLion on Stack OverflowMy team and I are using 1 single repo with Python to create multiple Lambda functions that will have some shared dependencies.
Does anyone have any recommendations for how to best structure the project folder structure?
Multiple lambda functions from the same project?
Best way to structure a multi-Lambda Python project?
Lambda beginner project with python
You can use API Gateway to expose your Lambda function to the internet. Make sure you restrict access via an API key or something.
Everything else is just python.
More on reddit.com