You've created a secure certificate and applied it to an edge hostname for access by requesting clients. You have your origin server configured using NetStorage and your website uploaded. And, you've set up an Ion property to streamline delivery of your website.

You're ready to test all of this and then go live with your website on the ​Akamai​ edge network.

Test your setup

While it's not required, you should thoroughly test your website or app.

1. Activate your property on staging

To start, activate your Ion property on the staging network.

1. Access ​Control Center​.
2. Log in using your primary admin user.
3. Select ☰ > CDN > Properties.
4. Find your Ion property in the table and click its Property Name.
5. In the Version History tab, click Version 1 to access it for testing.
6. Scroll down to the Property Hostnames content panel and make note of the Edge Hostname. You'll need this later.

7. Click the Activate tab.

8. Click Activate v1 on Staging. The Activation window opens. Set these options:

   • Fast Activation. To speed up activation, ensure this is set to On.
   • Notes. You can include a description of this version's activation.
   • Notify via email. This defaults to the email address set for your primary admin user. Separate multiple addresses with a comma (",").

9. Click Activating v1 on Staging.

10. With Fast Activation, your property should be ready in the Estimated Activation Time listed. This can be as quick as three minutes. Now, you can:

    • Monitor the Activate tab to track progress.
    • Click Activation Details. This lets you review settings and information regarding the Property.
    • Wait for the confirmation email. Any email set in Notify via email will get an email when the activation is complete.

2. Point to edge servers

Temporarily set up your local browser to target an edge server to access your property.

1. You need your hostname's actual IP address. You can get it by appending-staging to the edge hostname you noted earlier, and running a command from a Terminal Session or Command Prompt: For example, the appended hostname might look like this:

   docsassociates.com.edgesuite-staging.net
   

   O/S	Detail
   Linux/macOS	Open a new Terminal Session and perform a "dig" of your edge hostname: IPv4-only dig www.docsassociates.com.edgesuite-staging.net IPv4 + IPv6 dual stack dig AAAA www.docsassociates.com.edgesuite-staging.net
   Windows	Open a new Command Prompt, and perform an "nslookup" of your edge hostname. IPv4-only / IPv4 + IPv6 dual stack nslookup www.docsassociates.com.edgesuite-staging.net

2. Open your local hosts file in a text editor. Based on your operating system, you may be able to find your host file as follows:

   O/S	Detail
   Linux/macOS	Navigate to /etc/hosts. (You'll need superuser access -- sudo su -.)
   Windows	Navigate to \system32\drivers\etc\hosts (You'll need Administrator-level access.)

📘

The above paths are only examples of where this file might be found. Please see the relevant user documentation for the location of the Hosts file for your selected operating system.

3. At the end of the hosts file, add an entry for the actual domain to your website that includes the edge hostname's IP address.

   1.23.45.78 docsassociates.com
   

4. Save and close your hosts file. All requests from your local system to your domain will now go to an edge server.

   • This applies to your local system, only.
   • To undo the redirection to the edge server, remove the new entry from your hosts file.

3. Check your connection

When a browser requests your content on staging edge servers, ​Akamai​ adds the X-Akamai-Staging HTTP response header to the request. Look for this header in a request to make sure your browser is pointed to the staging network.

1. Close all browser windows, reopen your browser, and clear the browser cache.

2. Access the Network functionality in your browser:

   • Chrome. Right-click (Command+click on macOS) in the browser window and select Inspect. Click the Network tab. (You may need to click >> to reveal it in the toolbar.)
   • Edge. Press F12, and then press Ctrl+4 to open the Network utility.
   • Firefox. Press Ctrl+Shift+I (Windows) or Command+Opt+E (macOS). This takes you to the Network tool.
   • Safari. If necessary, select Safari > Preferences, click Advanced, then enable Show Develop menu in menu bar. Select Developer > Show Web Inspector and select the Network tab.

3. Point your browser to the domain you included in your local hosts file.

4. In the Network section, click the first file listed. (This is typically the domain for your actual site.)

5. Review the response headers. If you see X-Akamai-Staging: EdgeSuite, you're good. If not, go back to 2. Point your browser to edge servers and make sure you followed the process correctly.

6. Check for the X-Cache entry.

   HTTP/1.1 200 OK
   Server: Apache/2.4.9 (Unix) OpenSSL/1.0.1-fips
   Last-Modified:Wed, 26 Jun 2022 18:28:37 GMT
   ETag: "1234-5a678b9012c34"
   Accept-Ranges: bytes
   Content-Length: 13162
   Content-Type: image/gif
   Cache-Control: max-age=603241
   Expires: Mon, 14 Apr 2022 16:48:38 GMT
   Date: Mon, 07 Apr 2022 17:04:37 GMT
   X-Akamai-Staging: EdgeSuite
   X-Cache: TCP_MEM_HIT from b128-48-122- 38.deploy.akamaitechnologies.com (AkamaiGHost/6.15.0.3-12528292) (-)
   X-Cache-Key: /L/12345/678910/1a/orign-example.com/images/samplepicture.gif?234567
   Connection: keep-alive
   

7. Use this table to interpret the results.

   Did the page load as expected?	Is the X-Cache entry present?	Result
   Yes	Yes	Success! You're ready to test.
   No	Yes	You reached an edge server, but something isn't working. The value of the X-Cache entry might help you identify the problem.
   Yes	No	You reached your origin server, not an edge server. Check the entry you added to your hosts file.
   No	No	You haven't reached your origin server or an edge server. Check the entry you added to your hosts file.

4. You're ready to test

Access your website the same way you normally would to test it.

🚧

When testing, use your actual domain for requests—don't use its edge hostname. Edge hostnames are applied automatically by your DNS to reroute requests to the ​Akamai​ edge network.

1. Check key functionality, such as logging in, playback, and so on.
2. Once you're satisfied that your property works, remove the hosts file entry you added and then save it.
3. On macOS 10.6 and later, flush your DNS cache again with the dscacheutil -flushcache command.

Go live

Begin delivering your website or app to your end users through the ​Akamai​ edge network.

1. Activate your cert on production

To start, push your domain-validated Standard TLS certificate to ​Akamai​'s production network.

1. Access ​Control Center​.
2. Log in using your primary admin user.
3. Select ☰ > CDN > Certificates.
4. Select the Active tab.
5. Find your certificate in the table, based on the common name (CN) you set for it.
6. Click Yes under Always test on Staging before deployment, then select No in the pop-up. This enables automatic renewal of your cert when it expires. (You added the Auto Domain Validation behavior to your property for this.)

📘

If you don't complete this step, you'll have to manually renew your certificate on its expiration date.

7. Note the date listed under Staging Network and click it.
8. Click Push to Production and then Yes to confirm.

It may take up to a half hour to deploy your certificate to production. Once it's done, Production Network should list the expiration date you noted, and Staging Network should read: Same as production.

2. Activate your property on production

Next, push your Ion property to the production network.

1. If necessary, access ​Control Center​ and log in using your primary admin user.
2. Select ☰ > CDN > Properties.
3. Find your Ion property in the table and click its Property Name.
4. In the Active Staging Version content panel, click Version 1.

6. Click the Activate tab.

7. Click Activate v<#> on Production. The Activation window opens. Set these options:

   • Fast Activation. To speed up activation, ensure this is set to On.
   • Notes. You can include a description of the production version's activation.
   • Notify via email. This defaults to the email address set for the active ​Control Center​ user. You can change it or add more. Separate multiple addresses with a comma (",").

8. Leave all other options at their default setting and click Activating v<#> on Production.

9. With Fast Activation, your property should be ready in the Estimated Activation Time listed, but typically no longer than 15 minutes. Now, you can:

   • Monitor the Activate tab to track progress.
   • Click Activation Details. This lets you review settings and information regarding the Property.
   • Wait for the confirmation email. Any email set in Notify via email will get an email when the activation is complete.

3. Point to your configuration

Next, you need to change the existing DNS record for your site or application to be a CNAME record that points to the ​Akamai​ edge hostname. This will reroute requests for your site or app to the ​Akamai​ edge network.

📘

Make note of the existing DNS entries for use in troubleshooting.

Before

Here's an example of a generic DNS record for a domain, before you move it to the ​Akamai​ edge network. In it, 111.222.3.4 represents the IP address for your origin server:

docsassociates.com. IN A 111.222.3.4

After

Here's an example of that same domain in a DNS record, pointing to ​Akamai​'s Standard TLS network:

docsassociates.com. IN CNAME docsassociates.com.edgesuite.net

How long does the DNS change take?

The update to your DNS needs to apply before edge network delivery will start. This depends on the time to live (TTL) you've set for your site's DNS record. In most environments, this is set to one day by default. So, it could take up to 24 hours to reroute requests. To shorten this:

1. Reduce your DNS TTL before you change to the ​Akamai​ edge.
2. Revert it back after the change.

You can switch your website or application to the edge network at any time after completing the activation steps and testing. No additional activation or monitoring is required.

Troubleshooting

If you notice a problem after switching your content to the production network:

1. Roll back the DNS change to point your website or application back to your servers.
2. Report the problem to ​Akamai​.

This helps you and ​Akamai​ identify the problem in a controlled environment without affecting live end users.