Please describe your proposed solution.
The diagram below describes comparing when customers/developers use templates and without a template:
All relay nodes and core nodes will be deployed to at least 2 AZs, then if one AZ goes down, the remaining AZ can still handle the load.(detail the architect below:)
We also configure alerting rules to check service endpoints' health and notify administrators if there are any incidents. The whole system will follow the security standard and best practices.
We leverage cost budgets to track cost usage and trigger alerts when the usage exceeds a predefined threshold.
Backups for core and relay servers will be created daily at 00:00 UTC.
Please describe how your proposed solution will address the Challenge that you have submitted it in.
There is no comprehensive template of the tool to generate all of the infrastructures on AWS. The developer needs a tool to create a quick start without creating many resources on AWS
This will not only be good for onboarding developers but it will provide existing developers with an easily searchable template of the tools
With the use of CloudFormation, users do not need to have knowledge about AWS services, all they need to do is manage the applications inside the servers.
In case the users does not used the service anymore, they can remove the whole infrastructure cleanly by deleting the CloudFormation stacks.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
With the use of AWS, the cost will often be higher than other providers, in exchange, the service quality is very high. To reduce cost, we can apply AWS pricing models such that reserved instances and saving plans, the cost can be decreased by about 30-50% compared to the on-demand model.