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, and 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.
How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?
There is no comprehensive template for the tool to generate all AWS infrastructures. 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 know about AWS services. All they need to do is manage the applications inside the servers.
If the users no longer use the service, they can remove the whole infrastructure cleanly by deleting the CloudFormation stacks.
How do you intend to measure the success of your project?
For a new user, using a simple template that spawns the entire infrastructure following best practices will ensure a stable, smooth, and controllable system. Customers now take care of the service running inside that server, saving a lot of time on the operation and maintenance of the infrastructure on AWS.
Please describe your plans to share the outputs and results of your project?
The codebase is open source, and you can find all the resources and materials on GitHub :)