https://github.com/wmaciejak/aws-lambda-root-service
AWS Lambda Root Service - The primary goal of the root service is to glue multiple microservices repositories together. The top part is APIGateway connecting with boilerplate repository
https://github.com/wmaciejak/aws-lambda-root-service
microservices serverless terraform
Last synced: 9 months ago
JSON representation
AWS Lambda Root Service - The primary goal of the root service is to glue multiple microservices repositories together. The top part is APIGateway connecting with boilerplate repository
- Host: GitHub
- URL: https://github.com/wmaciejak/aws-lambda-root-service
- Owner: wmaciejak
- Created: 2021-12-17T09:04:55.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2021-12-17T09:25:41.000Z (over 4 years ago)
- Last Synced: 2025-01-29T04:50:07.896Z (about 1 year ago)
- Topics: microservices, serverless, terraform
- Language: HCL
- Homepage:
- Size: 5.86 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# AWS Lambda Root Service
The primary goal of the root service is to glue multiple microservices repositories together. The top part is APIGateway connecting:
- [aws-lambda-boilerplate](https://github.com/wmaciejak/aws-lambda-boilerplate)
- more?
## Setup
If you're running the setup process locally, then check out all modules at the same filesystem level as the [aws-lambda-root-service](https://github.com/wmaciejak/aws-lambda-root-service) repository. So your working directory should look like:
```
src/
+- aws-lambda-root-service/
+- aws-lambda-boilerplate/
+- ...
```
Then execute following script to create symlinks to those repositories inside terraform/modules dir. If you have different dirs stucture, you can adjust symlinks manually.
```bash
bin/link_services_repositories
```
## Potential problems and way to solve them
1. There is a known issue with lack of tracking changes in scope of CORS configuration. It means that when we will create STACK without configured CORS for some endpoint we will not be able to provide CORS configuration during this lifecycle of this stack. The only way to manage it currently is to drop stack and create new one