Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PARENT: Backup of MoJ DNS estate #4183

Closed
AntonyBishop opened this issue Feb 15, 2024 · 5 comments
Closed

PARENT: Backup of MoJ DNS estate #4183

AntonyBishop opened this issue Feb 15, 2024 · 5 comments
Assignees
Labels

Comments

@AntonyBishop
Copy link
Contributor

AntonyBishop commented Feb 15, 2024

User Need

As a Operations Engineering Team
I want a way to-back-up our DNS estate
so that in the event of loss or a failure we are able to recover DNS records in part or as a whole.

Value

AWS Route53 is highly available but doesn't offer a back-up. All DNS processes in MoJ are manual and therefore back-up is a manual process. Without a backup we are reliant on the manual process of recovery via audit logs.

We know we have others user in this account who could make changes. We are guarding against the risk of DNS being changes by someone that could could have a negative impact on services. Having a backup could allows us to revert changes/restore on a known configuration.

Without a backup of records there is a risk that reverting changes could take longer, or worse, case we have no previous configuration to revert back to.

Having a regular, automated process for back-up would de-risk change, or loss of one or more entire Hostedzones

Functional Requirements:

  1. We can back-up all our hostedzones and associated DNS records from the MoJDSD account.
  2. We are able to use back-up to revert changes.
  3. We should be able to restore whole zones or individual records.
  4. We should back-up at least once a week.
  5. Easy to read format e.g. JSON, YAML.
  6. Any repos should be classified as "Internal".

Non-Functional Requirements:

  1. Process should be secure
  2. Process should be documented

Acceptance Criteria:

  1. We should check with Security how securely we should store this information.
  2. We identify a process to back-up.
  3. We have a working process to bac-up.
    Notes:
@AntonyBishop AntonyBishop changed the title DNS - Backup of DNS Backup of MoJ DNS estate Feb 15, 2024
@levgorbunov1 levgorbunov1 self-assigned this Feb 19, 2024
@levgorbunov1
Copy link
Contributor

@levgorbunov1
Copy link
Contributor

@levgorbunov1
Copy link
Contributor

levgorbunov1 commented Feb 19, 2024

@tamsinforbes tamsinforbes added this to the DNS milestone Feb 20, 2024
@levgorbunov1
Copy link
Contributor

Security's response:
Yes that should be good, as long as the bucket access is restricted to a specific S3 Access IAM role such that only authorised internal users can access this data, and block public access to the S3 bucket.
Once it's done please let us know.

@levgorbunov1 levgorbunov1 changed the title Backup of MoJ DNS estate PARENT: Backup of MoJ DNS estate Feb 23, 2024
@connormaglynn connormaglynn removed this from the DNS milestone Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

4 participants