Akamai CDN With Wasabi
    • 11 Nov 2024
    • 4 Minutes to read
    • PDF

    Akamai CDN With Wasabi

    • PDF

    Article summary

    How do I use Akamai CDN with Wasabi?

    Akamai's Adaptive media delivery product has been validated for use with Wasabi. To activate Wasabi cloud storage with Akamai's CDN network, follow the steps below.

    Requirements

    • Active Akamai account

    • Active Wasabi account

    • Active public domain

    • Administrator access to domain provider

      The instructions provided below use a test domain, "www.wasabi-support.com", that will be associated with Akamai's CDN network. The test domain is owned and managed by godaddy.com and includes administrative rights to edit domain information (such as DNS values).

    Uploading Data to Wasabi Storage

    Wasabi has verified many S3, FTP, and FTPS clients for uploading data. For more detail on the products and vendors that are verified for use with Wasabi, refer to our KBs. To deliver uploaded data to a CDN vendor, such as Akamai, the data stored in Wasabi must be enabled for public access. There are two ways to enable public access:

    Configuring Akamai

    1. Log in to your Akamai Control Center portal.

      mceclip0.png

    2. Select Properties. Click Create property.

      mceclip0.png

    3. In the Property Name field, provide a name. Click Create Property.

      The property name is only for internal Akamai use. For recommendations, contact Akamai.

      mceclip1.png

    4. Under Property Hostnames, click Add.

      mceclip2.png

    5. A pop-up window will appear and request you to provide the following:

      • Hostname — In the example below, we are using the hostname akamaitest.wasabi-support.com, where “wasabi-support.com” is the top-level domain and “akamaitest” is the sub-domain. Click Next.

        mceclip3.png

      • IP Version — Select IPv4 only. Click Next.

        mceclip4.png

      • Mapping Solution — Select a mapping solution. In this integration, we are using VOD. Click Next.

        mceclip5.png

      • Edge Hostnames — Verify the Edge Hostname and click Submit.

        mceclip6.png

    6. You will be presented with a confirmation that the a property hostname was successfully changed. Click Close.

      mceclip7.png

    7. Select the Property Configuration Settings tab. Under Behaviors, click the Origin Type drop-down and select Your Origin.

      mceclip8.png

    8. Provide the following information:

      • Origin Type — Your Origin

      • Origin Server Hostname — s3.us-west-1.wasabisys.com

      • Forward host header — Origin Hostname

      • Cache key Hostname — Origin Hostname

      This example discusses the use of Wasabi's us-west-1 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL as described in Service URLs for Wasabi's Storage Regions.

      Additional information is provided below on configuring Akamai using different Wasabi storage regions as part of the same property.

      mceclip32.png

    9. Leave the default values for SSL and Ports, as shown below. Under Content Provider Code, click Create New.

      The content provider code is used for Akamai's billing & reporting purposes. For more detail, contact Akamai.

      mceclip10.png

    10. A pop-up window will provide a default Content Provider Code name. Click Create.

      mceclip11.png

    11. Leave the defaults for the configuration elements.

    12. Scroll down to the end of the page and click Add Behavior.

      mceclip12.png

    13. In the Add a Behavior for this Rule pop-up type- field, enter "Origin Base Path".

      mceclip13.png

    14. Click Insert Behavior.

      mceclip14.png

      Be sure that the Base Path value matches your cloud storage account. In the example below, the Wasabi account has a bucket named "akamawasabitest". We created a folder called "Videos" and inside this folder is a video asset named "Why Wasabi is Different_Wasabi.mp4". In this case, the base path provided in the Akamai control center would be "/akamaiwasabitest/Videos/".

      mceclip15.png

    15. Click Save.

      mceclip16.png

    Staging and Activating the Akamai Property

    1. Select the Activate tab.

      mceclip18.png

    2. Click Activate v1 on Staging. The configuration, created above, will be verified.

      mceclip19.png

    3. Click Activating v1 on Staging.

      mceclip20.png

      The activation process will take several minutes to complete.

      mceclip21.png

    4. Once the staging activation is successfully completed, click Activate on Production.    

      mceclip33.png

    5. Provide an email address. Click Activating v2 on Production.

      mceclip35.png

      The Activation on Production may take one hour to complete.

      mceclip36.png

    Changes Required at DNS Hosting Provider

    The wasabi-support.com domain is held by the GoDaddy hosting provider. Log in to your hosting provider's portal and add a CNAME entry, as shown below. Be sure to set:

    • Host —  akamaitest

    • Points to — akamaitest.wasabi-support.com

    • TTL — 60 mins (can be different)

    mceclip17.png

    Enabling HTTPS Access

    1. Click Create and select Certificate from the list.

      mceclip22.png

    2. Click Create New Certificate.

      mceclip0.png

    3. Select the best option to validate the website's identity. In the example below, Domain Validation (DV) is selected. Click Next.

      mceclip1.png

    4. For the Certificate Type, select Subject Alternative Names (SAN). Click Next.

      mceclip2.png

    5. Provide following information and click Next.

      • common-name for the certificate.

      • Company information (such as address, contact information, and so on).

      mceclip10.png

    6. Provide contact details.

      mceclip5.png

    7. Select Standard TLS. Click Review.

      mceclip6.png

    8. Click Submit.

      mceclip7.png

    9. A pop-up will appear and request to validate the domain, as shown below. Click Validate Domain Control. Be sure to take the appropriate steps with the website hosting vendor to validate the domain.

      mceclip8.png

      In the example below, the domain is validating via DNS Token and a TXT value.

      mceclip9.png

    Accessing Hosted Content Using Akamai CDN

    In a new browser, navigate to https://akamaitest.wasabi-support.com/Why%20Wasabi%20is%20Different%20_%20Wasabi.mp4.

    • URL is HTTPS based.

    • Top level URL contains akamaitest.wasabi-support.com.

    • Since the base path is "akamaiwasabitest/Videos", the asset needs to be called out after the URL.

    mceclip11.png

    Adding Different Wasabi Regions to the Same Property

    1. Under Property Configuration Settings click Add Rule.

      mceclip23.png

    2. Select Blank Rule Template and click Insert Rule.

      mceclip24.png

    3. Hover over the right of the newly created rule (New Rule) and click the gear icon. Select Edit Name.

      mceclip25.png

    4. Provide a name. In the example below, the name is East2 Rule. Click Add Match, select Path in the first drop-down list, and select matches one of in the second drop-down list. Provide the bucket/folder path.

      mceclip27.png

    5. Click Add Behavior. In the pop-up, search for "Origin Server". Click Insert Behavior.

      mceclip30.png

    6. Provide the following information and click Save.

      • Origin Type — Your Origin

      • Origin Server Hostname — s3.us-east-2.wasabisys.com

      • Forward Host Header — Origin Hostname

      • Cache Key Hostname — Origin Hostname

      mceclip31.png

    Repeat the above steps in Adding Different Wasabi Regions to the Same Property to add additional Wasabi regions to your Akamai property.