Aws architecture
Budget: $30 – $250 USD
We need to create a cloud formation for our SAAS arquitectura:
You can create one or more cloud formation to achieve the following requirements:
- The entire architecture is serverless (serverless posgres rds, lambda, apígateway, ses, S3, cloudfront, cognito, etc)
- We can create different environments. Many Dev, many QA, many Prod
Each env has to have its own deploy pipeline, url, etc.
- Every env needs to be attached to git branch. The entire project backend and frontend is in a single git repository in code commit. The frontend is a single page app and the backend are lambda functions.
- All environment can share the same Rds ddbb (with the same or different schema), or have their one ddbb
- Needs to be straightforward to create new endpoints and lambda functions, you can consider using (Sam, serverless framework, etc)
- Every cloud formation created needs to have the necessary parameters to configúrate the run as flexible as possible. (Region, schemas, names, env variables, etc)
- All running states for the cloudformation templates must be considered for successful executions. Create, update, delete. If an exception exist must be properly documented with the reason way can’t be automated.
The delivery must include:
- The required cloud formation templates
- A google doc document explaining how to use the cloud formation for creating new environments with the different options
The development of the cloud formation templates will be done in your own environments.
You will send us the deliverable and we will test them in our own environments.
It will not be accepted if the run fails
You can create one or more cloud formation to achieve the following requirements:
- The entire architecture is serverless (serverless posgres rds, lambda, apígateway, ses, S3, cloudfront, cognito, etc)
- We can create different environments. Many Dev, many QA, many Prod
Each env has to have its own deploy pipeline, url, etc.
- Every env needs to be attached to git branch. The entire project backend and frontend is in a single git repository in code commit. The frontend is a single page app and the backend are lambda functions.
- All environment can share the same Rds ddbb (with the same or different schema), or have their one ddbb
- Needs to be straightforward to create new endpoints and lambda functions, you can consider using (Sam, serverless framework, etc)
- Every cloud formation created needs to have the necessary parameters to configúrate the run as flexible as possible. (Region, schemas, names, env variables, etc)
- All running states for the cloudformation templates must be considered for successful executions. Create, update, delete. If an exception exist must be properly documented with the reason way can’t be automated.
The delivery must include:
- The required cloud formation templates
- A google doc document explaining how to use the cloud formation for creating new environments with the different options
The development of the cloud formation templates will be done in your own environments.
You will send us the deliverable and we will test them in our own environments.
It will not be accepted if the run fails