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

📖 Assist CICA to Implement Database Migration Service in Analytical Platform Ingestion Account #6733

Open
3 tasks
julialawrence opened this issue Feb 5, 2025 · 0 comments
Labels

Comments

@julialawrence
Copy link
Contributor

julialawrence commented Feb 5, 2025

User Story

As a customer who would like to bring CICA data into Analytical Platform using Database Management Service and would like some assistance in implementing that in Modernisation Platform Ingestion account.

Value / Purpose

Value for CICA: bring data into a modern analytical platform and migrate away from an outdated database instane.
Value for AP: use the work CICA carries out as a potential blueprint for a DMS as a service offering.
Value for broader AP userbase: Additional well-curated datasets.

Useful Contacts

@Gary-H9 @julialawrence

User Types

No response

Hypothesis

If we assist CICA with this task, it will simplify onboarding for them.

Proposal

We will provide to CICA the following:

  • Agreed design for the DMS solution
  • Requirements/DevOps Principles we would like them to adhere to.
  • Some hands-on assistance in overcoming implementation and deployment issues.

The agreed scope of this work for AP is to be an occasional point for assistance, not key implementors.

Key Note Network connectivity to CICA is outside the scope of this work.

Additional Information

Implementation details:

  • DMS will be created in the analytical-platform-ingestion-production account (471112983409) in Modernisation Platform Environments.
  • DMS will adopt a component approach i.e. new resources added via terraform will be added in this directory.
  • DMS ought to exist in the platform-production VPC, this already exists as part of the existing ingestion account infrastructure and should be consume using data calls / the platform_data.tf data blocks located here.
  • Further to the above create resources in the platforms-production-general-private subnet.
  • Secrets ought to be defined in in AWS Secrets Manager - an example of this is here.
  • Adopt the naming schema laid out elsewhere in the analytical-platform-ingestion directory of MPE. i.e. name the new .tf files as they are named elsewhere.
  • Logs should output to CloudWatch.

AP team will create a separate ticket to replicate data from analytical-platform-ingestion-production -> analytical-platform-data-production as we already have experience in this area.

Definition of Done

Example

  • Design agreed and shared

  • Constraints/Principles communicated and agreed

  • DMS work completed and reviewed by AP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: TODO
Development

No branches or pull requests

1 participant