For new environments, you won’t need to change the way you build environments. When you deploy new environments, the new Artifakt domains format will be used.
However, if you work with already existing environments, a few configuration steps are needed before migrating your domains to the new format. Once you have configured your domains for the migration, you need to launch the migration from the Domain Management settings of your environment.
Instructions for Artifakt Domains (artitest.io domains)
You need to update any references you may have to the deprecated domains, including browser bookmarks, CMS internal configuration, hyperlinks or any other third party integrations.
From the Domain Management settings of your environment, you can see a breakdown of what your Artifakt Domains will look like after the migration.
Instructions for your Custom Domains
Your current Custom Domains (e.g www.example.com, blog.example.com, etc.) are pointing to a load balancer endpoint like ‘XXX-elb-XXX-vpc-XXX-XXX.eu-west-1.elb.amazonaws.com’. These Custom Domains need their CNAME to be updated to point to ‘dns.artifakt.dev’ instead.
For APEX domains (e.g example.com), you need to add two A records pointing to these IP addresses: 220.127.116.11 and 18.104.22.168. However, Artifakt strongly recommends avoiding using APEX domains entirely.
Triggering the migration of domains
Once you have completed the above steps for your domains you can launch the migration from within the Artifakt console. This can be accessed from the Domain Management Settings of your environments. Please take considerable precautions before launching this migration as it cannot be undone and may cause service interruptions.