How Cloud Wrapper works

The problem

Each time content is retrieved from the cloud, it's done so at a cost, often referred to as "egress fees." Large volumes of requests to your origin server can result in soaring cloud provider charges, potentially impacting delivery performance. In extreme situations, large spikes in origin requests or traffic can even act like DDoS attacks leading to origin failure.

Excessive egress costs and performance issues when contacting cloud origins

The Cloud Wrapper solution

Cloud Wrapper serves as a highly-efficient custom caching layer that wraps around centralized cloud providers, shielding them to improve offload from your origin. As clients request streaming video, downloads, or website content, it's served from ‚ÄčAkamai‚Äč, resulting in lower cloud egress charges and a more consistent, high-quality end-user experience.

Cloud Wrapper: Cache from the cloud to improve origin offload

What about my origin server?

You might have some questions...

  • Is there anything special I need to do to configure my origin server?
  • Is there specific origin-related information I need to provide to Cloud Wrapper?

The answer to both questions is No.

To enable support for your Cloud Wrapper's caching layer, you'll add a behavior to your delivery configuration ("property"). You'll also configure specifics for your origin server in that same property. Cloud Wrapper inherits all the information it needs from your property. So, there's no additional information you need to provide.

How to add Cloud Wrapper

Now that you understand how it works, check out the steps required to get Cloud Wrapper added.