FAQ: CDK Migration

Browse by products and services

  • Applies to: Amazon Web Services
    • Difficulty: N/A
    • Time Needed: N/A
    • Tools Required: AWS


What is the CDK?

Cloud Development Kit. It is the recommended open-source software development framework by AWS. This is an upgrade to the custom tooling software we currently use to manage AWS infrastructure.

How will Media Temple ensure that the migration process will be seamless?

Although we cannot ensure a seamless experience, we are being proactive and immediately addressing issues which are found as high priority and put into production.

Will there be downtime?

No. Downtime is anticipated except for extenuating circumstances.

How much is it going to cost me?

  • Infrastructure Costs: Media Temple will cover the new CDK environment costs for a one-time period of 7 days.
  • Migration Costs: Media Temple will cover a one-time migration of your existing applications from the legacy environment to the new CDK environment.

What do I gain?

The upgrade to CDK will allow us to offer you a wider breadth of AWS’ managed services. Some other notable upgrades are:

  • Removal of NFS (single point of failure).
  • CDK has more comprehensive support for auto-scaling.

What do I lose?

Elastic IP’s

Will I need to perform a migration?

No. Media Temple is performing migrations free of charge.

We will use AWS technology such as DataSync/DMS. DMS is an online data transfer service Media Temple engineers use to simplify, automate, and accelerate copying large amounts of data between your infrastructures. We can use this tool in the vast majority of cases. For more information you can visit https://aws.amazon.com/datasync/faqs/ or reach out to support or your CSM.

What do we have to do?

  • Test the site after migration/before going live! This is the most critical step.
  • You may also want to add dummy data.

How much time do I have to invest?

This will vary per environment.

When do we need to get it done by?

The timeline will be planned between you and your customer success manager.

What are the migration options? 

Media Temple Migration - You will be responsible for the following:

  • Testing your application.
  • DNS:
    • If DNS is hosted externally and pointed to a Load Balancer or EC2 instance.
    • If MT controls DNS or DNS is pointed to CloudFront we will manage the DNS update when ready and testing is complete.

Self-Migration - You will be responsible for the following:

  • Migrating web content between environments.
  • Migrating database content between database instances.
  • Migrating S3 content (If applicable).
  • Testing your application.
  • DNS:
    • If DNS is hosted externally and pointed to a Load Balancer or EC2 instance.
    • If MT controls DNS or DNS is pointed to CloudFront we will manage the DNS update when ready and testing is complete.

Application Code

Do we need to update the application code? 

Typically no. All filesystem references should remain the same (/var/www/html), and all database/redis/etc connections using internal dns entries will remain the same.

Do we need to update CodeDeploy application code?

You may need to update your code deployment packages with new bucket names and credentials. The code itself for deploying the application should remain the same.

Do we need to make any updates since we use… ?

  • SES - Only if IAM Creds are needed. This will be handled during infra creation and handoff.
  • API Gateway - This will vary on the environment.
  • DocumentDb - Will require a migration. Per documentation DMS would work for this service as well.
  • SQS - Queues managed in code will be recreated so updates may need to be made. Queues not managed in code will not be affected.


Will my data be synchronized after testing and before DNS cutover?

Native services on AWS such DMS and Data Sync Services allows for continuous data synchronization on certain services. This will be discussed in more detail during your planning phases of migration.

Will we lose any data?

Data loss is not anticipated for this migration.

Can we keep backups? 

  • We will retain a snapshot of RDS for 30 days.
  • Your EBS volume will remain active for 30 days.

Will data be carried over in services such as Redshift, Redis, Dynamodb, elasticSearch?

Data in services that are meant to house temporary data will not be carried over and will require a rebuild. However, if there are any special circumstances, we will evaluate on a case-by-case basis. Typically, data in Redis/Dynamo is dynamic. Elasticsearch may be different. For Redshift, if this is in use, it will be migrated to being picked up by CDK and new vaults created using CDK.


Will we require a new VPC?

A new VPC will be created during the build phase.

Will we have to update DNS if it’s pointed to CloudFront?

No. However, if your DNS is not pointed to Cloudfront, please contact your CSM to further review.

Will anything change with my NAT Gateway?

A new NAT IP will be provided during the build phase for you to submit to whitelist.


Will the ACM SSLs need to be re-issued?

Existing ACM’s will not be re-issued, however new ACM’s may be needed in the local region (if not us-east-1) for ALB usage. DNS should match existing records so no customer intervention is expected.

Will we lose our IP?

EIP’s will be lost/replaced.

What will we provide you once the new infrastructure is built

  • New bastion server with a new IP address.
  • New IAM user/credentials.
  • New S3 bucket information.