Proper way to move 3CX from Lightsail to AWS while keeping free 3CX domain

[checkinyyz]

Hi everyone, just want to make sure I do this right. We had the 16 call professional version on AWS and it ran great. When it came time to renew we only needed 8, so we bought that and instead deployed it on Lightsail and set up a new company.3cx.ca domain for us. I'm not as happy with Lightsail and want to move it back to AWS so that I can set up a VPN on AWS as well for us to do better networking, but just wondering the proper way to do this.

I'm asking as this guide here https://www.3cx.com/docs/manual/pbx-backup-restore-failover/#h.2a3yvcw23lo4/ doesn't seem correct as I don't see any way to deactivate a licence to make it free as per the guide.

I just need to make sure that I can deploy it on AWS, restore it in full from backup, and then have it keep our custom company.3cx.ca domain name so that users don't need to go reconfigure anything since all apps and phones connect remotely via the domain and not IP.

 

[StefanW]

Hey,

the guide indeed is due for an update.

Best would be to make a backup of the current install
use Cloud Restore of Pbxexpress (pbxexpress.3cx.com) to restore your backup, here is a guide
https://www.3cx.com/blog/docs/cloud-pbx-backup-restore/

once restored shutdown your current instance in LightSail and you are in AWS.
Some pacance is needed as outlined in the guide

• IP phones might need to be reconfigured. This depends on the current setting, local LAN must be updated to STUN or SBC setting. Existing STUN phone will reconnect automatically when the FQDN with the updated IP becomes available. Check with ‘nslookup [3CX-FQDN]’ when IP caches have been updated. To see if 3CX has updated the IPs use ‘nslookup [3CX-FQDN] 8.8.8.8’. This can take a few minutes up to 6 hours.

hope you currently are already on 443 and 5060 port so for your users is just a matter of "waiting" until they are on the new install..