General questions

Question	Answer
Are there any cache controls?	*Yes. Normal cache control directives such as TTL are honored. Cloud Wrapper-specific cache control isn't supported. This includes: Pre-warming* Cache retention configuration Permanent caching
Can I manage individual cache objects?	No. Managing individual objects isn't supported.
Can I see what's in the cache?	No. You can't see individual objects.
Does Cloud Wrapper support advanced metadata configurations?	Yes. You need to contact your account team for assistance.
Does Cloud Wrapper support Enhanced TLS?	No. Currently, only Akamai's Standard TLS network is supported.
How long does data live in cache?	Data is deleted 30 days after the last time it was accessed. You can bypass this using Retain Idle Objects in the LOCATIONS settings in your configuration.
Can I use a third-party CDN with Cloud Wrapper?	*Yes. Cloud Wrapper supports these CDN providers: AT&T* CloudFront Google Fastly Jio Level3 (Centurylink) Limelight PicoNETS StackPath Verizon (VDMS) 📘 Currently, multi-CDN support is only offered with Akamai's Adaptive Media Delivery, Download Delivery, and Object Delivery products.
Is there an Access Control List (ACL) available for Cloud Wrapper?	*Yes*. The Cloud Wrapper IP space is natively part of the Akamai Origin IP Access Control List. Review the latest Access Control List for IP Allow list details. 📘 The following points apply: You don't need to use the Origin IP Access Control behavior to use this capability with Cloud Wrapper. Origin IP Access Control List is not a substitute for authentication. To further enhance your origin security, use them in combination with authentication methods such as authentication tokens.
Can I set alerts for Multi CDN auth errors?	*Yes. Configure them in the Alerts application. Create alerts for Edge Errors -- Content Delivery (HTTP 4xx and 5xx errors)* using your Multi CDN CP codes. To receive auth failures at the earliest indication, set the threshold to a very low value (0.01% - 0.1%).

Cloud Wrapper & failover

Failover with Cloud Wrapper requires the Cloud Wrapper Advanced behavior.

Question	Answer
Does Cloud Wrapper work with Failover?	*Yes*. Cloud Wrapper supports failover for MultiCDN properties by default.
Is there a performance impact?	Possibly, in a specific scenario. There may be a performance impact if the failover map forwards requests to Akamai edge servers that are geographically further than your origin server location. 📘 This failover method prevents hits to origin. If you prefer going to origin to maintain performance, contact your account team to disable the failover workflow.
What if the failover map forwards to a different geo?	Increased costs may occur when a failover map forwards requests out of an existing low-cost geo. Note: We support per-geo failover maps to reduce the chance of this happening. Discuss these options with your account team.

Question

Answer

Does Cloud Wrapper work with Failover?

Yes. Cloud Wrapper supports failover for MultiCDN properties by default.

Is there a performance impact?

Possibly, in a specific scenario. There may be a performance impact if the failover map forwards requests to Akamai edge servers that are geographically further than your origin server location.

📘
This failover method prevents hits to origin. If you prefer going to origin to maintain performance, contact your account team to disable the failover workflow.

What if the failover map forwards to a different geo?

Increased costs may occur when a failover map forwards requests out of an existing low-cost geo. Note: We support per-geo failover maps to reduce the chance of this happening. Discuss these options with your account team.

Cloud Wrapper & purging

Question	Answer
Can I purge content by URL?	*Yes*. Purge and invalidate content by URL is the recommended method of purge for complete content removal. Purge by URL will remove content completely from Akamai cache, including Cloud Wrapper. 📘 This will impact Akamai delivery along with third-party delivery if the same objects are served using both workflows.
Can I purge content by CP Codes?	Yes. To ensure complete content removal, you must purge or invalidate all CP codes that serve your content, including both Akamai and third-party CDN CP codes.
Can I purge by Cache-Tag?	*This is not recommended*. This purge method can cause unintended eviction of objects outside of the purge request, from all Akamai caching tiers, including Cloud Wrapper. This results in poor offload.

Question

Answer

Can I purge content by URL?

Yes. Purge and invalidate content by URL is the recommended method of purge for complete content removal. Purge by URL will remove content completely from Akamai cache, including Cloud Wrapper.

📘
This will impact Akamai delivery along with third-party delivery if the same objects are served using both workflows.

Can I purge content by CP Codes?

Yes. To ensure complete content removal, you must purge or invalidate all CP codes that serve your content, including both Akamai and third-party CDN CP codes.

Can I purge by Cache-Tag?

This is not recommended. This purge method can cause unintended eviction of objects outside of the purge request, from all Akamai caching tiers, including Cloud Wrapper. This results in poor offload.

Cloud Wrapper status

Your configuration status follows this table of definitions:

Action	Status	Description
Save	Saved	This is the initial state when your configuration version is saved.
Activate	Activation In Progress	Your activation request is being processed. Propagation time is approximately 3-4 hours.
Activate	Activation Failed ¹ ²	Your activation request has failed. Create a new configuration version and try again.
Activate	Activation Aborted ²	Your activation request has been aborted.
Activate	Active ²	This configuration is now active. Note: Use Property Manager to apply this configuration to a behavior .
Delete	Delete In Progress	Your request to delete this configuration is being processed.
Delete	Delete Failed ¹ ²	Your request to delete this configuration has failed.
Delete	Delete Aborted ²	Your request to delete this configuration has been aborted.
N/A	Inactive	Previously Active versions are displayed as Inactive when the latest version becomes active.

¹ The system automatically removes this configuration version.
² The system sends a notification to the email associated with your Akamai Control Center login.

TTL and object evictions

Cloud Wrapper uses two methods to determine eviction:

Cloud Wrapper cache space is full. Cloud Wrapper uses the LRU (“least recently used”) algorithm for evicting content once space is full. The eviction is based on the last time an object was accessed, with the oldest-accessed time getting evicted first.
Idle objects. Cloud Wrapper applies a platform-level eviction after an asset is not accessed in your cache for a certain amount of time. We call this its idle time to live (TTL). This time varies based on the Traffic Preference you've set for the Location in your configuration:
- Prefer Low Latency. This applies to live streaming media assets delivered through Akamai's Adaptive Media Delivery (AMD) product. Low latency content that isn't accessed for three days is considered idle.
- Prefer Redundancy. This applies to static assets like on-demand video via AMD, downloadable assets via Download Delivery or Object Delivery, or website content via Ion (Beta) or Dynamic Site Accelerator (Beta). Redundant content that isn't accessed for 30 days is considered idle. This can be overridden with the Retain Idle Objects option.

📘
Low idle TTL doesn't automatically result in an object eviction
If an object's idle TTL is low, Cloud Wrapper flags it, but doesn't evict it. It's only evicted if your cache space is close to full, or if it's reached its full idle TTL.

Cloud Wrapper locations

Your initial location and size mapping is done by your account team. Work with them to determine which Cloud Wrapper location is best for you.

Australia
Brazil
Europe
Hong Kong
India
Japan
Japan + Singapore (Dualmap)
North America (Dualmap)
Singapore
US East
US West