Existing Customer Migration

Overview

This document outlines the process for migrating existing customer environments to the AskEdgi model. It includes account setup, infrastructure deployment, application migration, database and file system migration, networking configuration, secrets management, and post-migration validation. The steps ensure minimal disruption and a smooth transition to the new environment.

Purpose of the document

The purpose of this document is to provide a detailed, step-by-step procedure for migrating customer accounts and applications to the AskEdgi model while maintaining data integrity, system availability, and proper configuration across all components.

Implementation Steps

1. Account Setup

  • A new account is created for each customer through Control Tower automation.

  • Standard Operating Procedures (SOPs) are automatically created and synced with the Master account.

2. Infrastructure Deployment

CloudFormation StackSets are used to deploy resources from the Master account to child accounts. StackSets handle:

  • Bootstrapping child accounts

  • Resource provisioning templates

3. Release Migration

Component

Current Version

Target Version

Notes

Application

6.3.X

7.2.X

Migration occurs within the same account

RDS

8.0.40

8.4.6

Requires DB parameter group creation and attachment

NIFI Server

1.16.3

1.28.0

Java 17 must be used

Bridge Client Java

8

17

Requires NAR file update to 7.2.3

4. Database Migration

RDS Backup

  • Take snapshots of customer environment (UAT/PROD) before migration to 7.2.X.

RDS Upgrade

  • Modify customer RDS from 8.0.40 to 8.4.6.

  • Create and attach a DB parameter group for version 8.4.

  • Update DB parameters in the newly created parameter group.

Manual OvalEdge Backup

Command:

mysqldump -u root -p --single-transaction --skip-lock-tables ovaledgedb > ovaledgedb.sql

  • Restore backup to RDS 8.4.6 in the new account.

5. Java Upgrade

  • Update Java version from 8 to 17 (OpenJDK) in Docker files and Bridge Client.

6. OE Docker Image Building

  • Collect updated oasis.properties for run.sh.

  • Collect updated logging.properties for image building folder.

  • Use hardened Tomcat.

  • Build and push Docker image to Docker Hub.

Important: Perform all migration activities in a controlled environment with monitoring enabled to validate each operation.

ECS Deployment

  • Update the 7.2.X image in Customer UI / JOB task definition.

  • Deploy to ECS service and verify the application is running.

7. Encrypt-Decrypt Key Update

  • If the default key is used, change the encrypt-decrypt key from default to random.

8. NIFI Server Migration

Step

Details

Backup

toolkit, nificonf, nifilib, tmp, nifilogs

Migration

Upgrade from 1.16.3 to 1.28.0 using Java 17

ECS

Build image for 1.28.0, update ECS task definition, ensure service health

9. Bridge Client Java Migration

  • Uninstall Java 8 and install Java 17.

  • Download latest 7.2.3 NAR file to the lib folder.

  • Restart Bridge Client and apply UI changes.

Checklist: Bridge Client Migration

10. Migration to AskEdgi Model

EFS Migration

  • Backup all NIFI folders in zip format.

  • Copy backups to the new Bridge server’s EFS in the new account.

Networking Configuration

  • Retrieve customer IPs from the old environment and whitelist in new setup.

  • Map OE Application and NIFI server domains in Route53 with newly created Load Balancer DNS in OvalEdgeSaaS account.

Customer Whitelisting

  • Request customer to whitelist NAT IP / Network Load Balancer IP for Bridge Client VM security/firewall.

Secrets Manager Migration

  • Copy encrypt-decrypt key to the newly provisioned Secrets Manager in the new account.

NIFI Server and Client UI Changes

Bridge Client Communication Verification

  • Verify IP whitelisting and connector validation with the customer.

Connectors Validation

  • Validate all connectors after the Bridge server and client communication is confirmed.

AskEdgi Integration

  • Once application validation and connectors are healthy, edgiInsightService sinks with the application.

edgi-data-service-1001 is created, indicating AskEdgi workspace is created in the application.


Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.

Last updated

Was this helpful?