Add a configuration

Next in the process, you need to create your Cloud Wrapper configuration, to determine how to use its capacity as your cache.

Before you begin

You need to meet some prerequisites before you get started.

  • You need a compatible delivery product. You need a delivery configuration ("property") set up and actively delivering content on ​Akamai​'s production network. See the guidelines for optimizing your property.

  • Your contract needs capacity. After you determined your requirements, your account team should have set up Cloud Wrapper locations and capacity on your ​Akamai​ contract. You should have also set up the property that's delivering your content on that same contract. Verify this contract has capacity inventory.

  • Support for web delivery products is Limited Availability. Support forCloud Wrapperwith our Dynamic Acceleration and Ion web delivery products is in Limited Availability. Talk to your account team about access to it.

🚧

Web and media products can't use the same footprint

If you configure a footprint and then add it to an Ion or Dynamic Site Acceleration (web) property, you can't use the same footprint with Adaptive Media Delivery, Download Delivery, or Object Delivery (media) properties.

Implementation

To add a new configuration, follow these steps:

  1. Go to ☰ > ORIGIN SERVICES > Cloud Wrapper.

  2. Select the Configurations entity.

  3. Click Add Configuration.

  4. Set options in each window of the wizard:

1. Apply GENERAL SETTINGS

Define some basics for your configuration.

OptionDescription

Name

Give your configuration a unique name to differentiate it.

Comments

Optionally add notes to help identify the configuration during later use.

Contract Selection

Select the Cloud Wrapper contract you're assigning this configuration to.

Properties Selection

Select the delivery configurations ("properties") to include in the Cloud Wrapper configuration. The list of available properties is contingent on:

  • A supported delivery product. Your property needs to be configured using Adaptive Media Delivery, Download Delivery, Dynamic Site Acceleration, Ion, or Object Delivery.
  • The property is in production. It needs to be actively delivering content on the ​Akamai​ production network.

Contact your account team if the properties you expect to see aren't listed. You can also pre-populate many of these fields by creating a configuration from an analysis report.

Capacity Alerts

Enable this to be alerted when your quota usage passes your configured threshold. You set this threshold with your ​Akamai​ account team when setting up your Cloud Wrapper instance. Emails are sent to the address you've set for your ​Control Center​ user.

2. Set LOCATIONS

Define the locations to distribute your Cloud Wrapper capacity:

OptionDescription

Locations

Select a geographic region to use. Depending on your workflow, decide if you want it closer to the origin server where you store your content, or to the clients that are requesting it.

Traffic Preference

Set this based on the type of content you'll be delivering through this cache:

  • Prefer Low Latency. Pick this if you're delivering live streaming media via Adaptive Media Delivery. Content has a 3-day time to live—If low latency content isn't accessed for three days, it's removed.

  • Prefer Redundancy Pick this if you're delivering on-demand video via Adaptive Media Delivery, direct downloads via Download Delivery or Object Delivery, or website content via Ion (Limited Availability) or Dynamic Site Accelerator (Limited Availability). This content is held in your cache for 30 days. If it hasn't been accessed for 30 days, it's removed.

    • Retain Idle Objects. This is available if you've selected Prefer Redundancy. Enable it to extend the time to live beyond the default 30 days.

📘

Traffic Preference depends on the Location you've selected. Not all locations offer both Traffic Preference choices. Contact your account team if you need help optimizing your traffic preferences.

Capacity (TB)

Set the amount of cache space to allocate for the Location you selected.

Usage Notes

Include any additional information to help you identify the purpose of this configuration.

3. Set up MULTI CDN (Optional)

Enable and customize third-party content delivery network (CDN) access to Cloud Wrapper.

📘

Multi-CDN support is currently only offered with ​Akamai​'s Adaptive Media Delivery, Download Delivery, and Object Delivery products.

  1. Set Enable Multi CDN to On.

  2. Select the Properties associated with your contract to include in this configuration.

  3. Click Extract Origin Details to extract Origin settings associated with your selected properties.

  4. You can assign an Origin ID to help identify it later.

  5. Click Add CDN. The Add CDN window launches.

OptionDescription

Name

Select the CDN provider that you currently use.

Enable Header Based Auth

Enable this to use Simple Header authentication. Later, you'll use the Secret

  1. Your selected CDN will populate a default Header Name.

  2. Enter an Auth Key Name to use with the Secret provided and select an expiration date.

  3. Specify the Expiry date for this auth key.

  4. Copy the Secret by clicking the clipboard icon (). You'll use this later to generate the final header.

  5. Select the Auth Key Name.

Rotate a key before expiration

You need to create a new auth key prior to key expiration, then delete the old auth key.

Enable IP ACL

Enable this to specify a list of IP addresses that your CDN generates requests from. Cloud Wrapper will restrict access to only these IP addresses. IP ACL is not a substitute for authentication. To further enhance your origin security, use them in combination with authentication methods such as authentication tokens.

Prevent denial of traffic

Consider these points:

  • You need to maintain the IP/CIDR list in this configuration to ensure it’s up-to-date with your CDN’s list.

  • Cloud Wrapper can receive traffic from your downstream CDN using both IPv4 and IPv6 addresses. Include both IPv4 and IPv6 CDN addresses in your ACLs.

  • Denial of traffic will occur if your CDN makes requests from IPs that are not part of the list configured here. View the FAQ for information about setting up auth alerts.

HTTPs Only

Enable this to only accept HTTPS connections. Both HTTP & HTTPS connections are accepted when disabled.

  1. Review Multi CDN tasks for additional processes you need to complete to set up this support.

4. Review the SUMMARY

View your summarized configuration:

  1. Assign email addresses to be notified about the status of your configuration.

  2. Click Submit.

  3. Decide if you want to Activate now, or Activate Later.

📘

You can edit an existing configuration as necessary, but it can't be activated.