[Feature]: support installing dns53 as a service that exposes an EC2 automatically on startup

[purpleclay]

Describe your feature

Currently, dns53 has to be started by a user. It could be made simpler by offering an option of starting dns53 as a service. This will launch dns53 every time the EC2 instance is started.

Your potential solution

The service must be driven by a config file that controls how the EC2 is exposed within the PHZ. If no PHZ is provided, a hosted zone called dns53 should be created. The user should be able to change this config file and bounce the service.

Investigate how dns53 will be installed as a service across all the different installation mediums.

Any additional information?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct