Hi
@Softsolutions4u,
Yes, your DNS cutover plan is basically correct. I would add the following checks, especially since you are moving mail as well.
1. Verify the image architecture first
You mentioned Ubuntu 24.04 on ARM. Please double-check that combination: your screenshot lists “Ubuntu 22.04 on ARM” separately from the general Ubuntu 24.04 image. The general Ubuntu 24.04 listing does not automatically confirm ARM support.
Check the actual instance:
Code:
cat /etc/os-release
uname -m
plesk version
“aarch64” means ARM; “x86_64” means Intel/AMD.
Compare the result against Plesk’s official requirements before continuing:
Contents Supported Operating Systems ...
docs.plesk.com
Also verify that your required PHP version and any application extensions are available for that exact OS/architecture.
2. BYOL pricing and activation
BYOL means you purchase the Plesk license separately. The $0.00 shown in your Marketplace offer is not the total hosting cost: AWS infrastructure charges still apply, and you need a valid Plesk license after the trial.
Official Plesk pricing:
Compare Plesk hosting & server management plans and find the best fit for your needs. Get 20% off your first month on monthly licenses – limited time only.
www.plesk.com
AWS infrastructure estimate:
AWS Pricing Calculator lets you explore AWS services, and create an estimate for the cost of your use cases on AWS.
calculator.aws
Use the current Plesk checkout price for your currency, billing term, and applicable taxes rather than an old forum quotation.
You do not automatically need Web Pro just because the subscription contains “10 domains/subdomains”. Genuine Plesk subdomains and domain aliases do not count towards the license’s domain limit; separately added domains do.
Official explanation:
To activate the purchased license, open:
Tools & Settings > License Information > Install Key
Enter the activation code received after purchase. Older versions may call this section “License Management”.
Official activation documentation:
To operate, Plesk requires a license. Different licenses are available, varying in price and the features they enable. Moreover, additional functions can be unlocked via additional licenses, installed together with your Plesk license.
docs.plesk.com
Installing the license does not switch traffic. You can still migrate and test before making DNS changes.
3. Initial migration and testing
Use Plesk Migrator rather than copying only website files and databases. Review its report and recreate anything not migrated, such as custom server configuration.
Assign the destination Elastic IP before final testing, verify Plesk’s public/private IP mapping, and allow the required traffic through both the AWS security group and the server firewall.
Your hosts-file approach is correct:
Code:
NEW_ELASTIC_IP example.com www.example.com
Test HTTPS, authentication, forms, uploads, database writes, and mail. Prevent the test copy from sending duplicate customer emails or running production background jobs.
4. Route 53 and Plesk DNS
Lower TTL to 300 seconds ahead of cutover, then wait at least the previous TTL before switching. Previously cached answers retain their original expiry.
Update every relevant record, not just the root A record:
- Root domain, www, and any separately addressed subdomains.
- AAAA records, if IPv6 is published.
- Mail/webmail hostnames and any other services moving with the subscription.
- SPF and DKIM records where required.
Do not change records unnecessarily. For example, an MX record pointing to mail.example.com can stay unchanged if only that hostname’s A record needs updating.
Keep Route 53 nameservers unchanged.
You may disable the local Plesk DNS service for this domain if nothing depends on it, but this is not required for cutover. Public clients use the authoritative DNS delegation. Editing a Plesk zone does not update Route 53 unless you explicitly configured an integration.
5. SSL: have a valid certificate ready before cutover
An IP change alone does not require a new certificate.
Verify that the existing certificate and private key migrated successfully, assign the certificate to the destination website, and test HTTPS with your hosts-file override. Check mail and webmail certificates separately.
Plesk documents that domain-level certificates are migrated, but certificates in the server-wide repository are not.
If you need a new certificate before switching DNS, DNS-01 validation is an option: publish the required TXT record in Route 53 and check how renewals will be handled.
For HTTP-01 issuance after cutover, public DNS must reach the destination and port 80 must be accessible. Avoid switching visitors to a server without a valid certificate while waiting for issuance.
6. Final sync and preventing data loss
The key is to avoid two writable copies of the application:
- Take verified backups.
- Put the old application into maintenance/read-only mode.
- Pause old-server cron jobs, queues, and other writers.
- Run the final website/database synchronization.
- Verify the destination, then update Route 53.
- Enable normal operation and background jobs on the new server only.
Keep the old application read-only while cached DNS answers expire. Some visitors may briefly see maintenance mode, but that is safer than accepting orders or uploads on two separate servers.
Mail needs separate attention: some messages may still reach the old server during DNS cache expiry. Keep it available and perform a final mail resynchronization after routing settles. Verify inbound/outbound mail, SPF, DKIM, reverse DNS, and AWS outbound SMTP restrictions.
Keep the old instance intact until everything is verified. However, once the new server accepts writes, simply switching DNS back can lose new data; rollback then requires data reconciliation.
Finally, test CakePHP compatibility with your target PHP version before cutover. A successful migration does not prove the application is compatible with PHP 8.x.
Official migration guide:
Applicable to: Plesk for Linux Plesk for Windows Table of contents General Information Planning migration Preparing servers Migration pre-check Migration (data transfer) ...
support.plesk.com
Migration limitations, including certificate handling and temporary migration licensing:
Regards
Tessa