You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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:
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:
analytical-platform-ingestion-production
account (471112983409) in Modernisation Platform Environments.platform-production
VPC, this already exists as part of the existing ingestion account infrastructure and should be consume using data calls / theplatform_data.tf
data blocks located here.platforms-production-general-private
subnet.analytical-platform-ingestion
directory of MPE. i.e. name the new.tf
files as they are named elsewhere.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
The text was updated successfully, but these errors were encountered: