🚀 Implement OctoDNS for Route53 Management in MOJ DSD Account

[jasonBirchall]

User Need

As a member of the Operations Engineering team I want to implement OctoDNS for managing Route53 records in the MOJ DSD AWS account so that we can improve the efficiency and maintainability of our DNS management process.

Value

Implementing OctoDNS will streamline our DNS management workflow, reduce operational overhead, and improve performance compared to our current manual approach. This will lead to faster DNS operations, easier maintenance, and a more readable configuration format.

Functional Requirements (What):

• [x] Unarchive the ministryofjustice/dns repository
• [x] Remove existing code from the repository
• [x] Export all hosted zones from the "moj dsd" AWS account to OctoDNS format
• [x] Create an IAM user with programmatic access for CICD pipeline use
• [x] Develop a CICD pipeline that plans and applies OctoDNS changes

Non-Functional Requirements (How):

• [x] Ensure the new OctoDNS setup is more performant than the previous Terraform-based approach
• [x] Implement proper security measures for the new IAM user, following the principle of least privilege
• [x] Design the CICD pipeline to be reliable and efficient, with appropriate error handling and logging
• [x] Ensure the OctoDNS configuration is easily readable and maintainable

Acceptance Criteria:

• [x] The ministryofjustice/dns repository is successfully unarchived and cleared of existing code
• [x] All hosted zones from the "moj dsd" AWS account are accurately exported to OctoDNS format
• [x] An IAM user is created with the necessary permissions for Route53 management via OctoDNS
• [x] A functional CICD pipeline is implemented that can plan and apply OctoDNS changes
• [x] The new OctoDNS setup demonstrates improved performance over the previous Terraform approach
• [x] Documentation is updated to reflect the new DNS management process using OctoDNS

Notes:

• Consider the trade-offs mentioned in the proof of concept, such as the potential for parallel changes and the need for a CICD user access key.
• Ensure that the team is trained on the new OctoDNS workflow and understands how to manage DNS records using this new approach.
• Monitor the performance and reliability of the new setup closely during the initial implementation phase.
• Consider creating a rollback plan in case of any unforeseen issues with the new OctoDNS implementation.

[AntonyBishop]

@jasonBirchall does Documentation is updated to reflect the new DNS management process using OctoDNS mean just changes to existing runbooks or also the creation of new instructions? Just figuring out if we need a seperate story for Create documentation for the team on using octoDNS within our workflow

[jasonBirchall]

@jasonBirchall does Documentation is updated to reflect the new DNS management process using OctoDNS mean just changes to existing runbooks or also the creation of new instructions? Just figuring out if we need a seperate story for Create documentation for the team on using octoDNS within our workflow

Absolutely, @AntonyBishop. There's a fair amount in our runbooks that needs changing. I'd like to capture that later if possible.