FAQ and considerations

Frequently asked questions

Are there any cache controls?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?Managing individual objects isn't supported.
    Can I see what's in the cache?You're not able to see individual objects.
    Does Cloud Wrapper support advanced metadata configurations?Contact your account team for assistance.
    Does CW support Enhanced TLS?Not supported
    How long does data live in cache?Data is deleted 30 days after the last time it was accessed.
    Can I use a third-party CDN with Cloud Wrapper?Yes. Cloud Wrapper supports these CDN providers:
  • Level 3 (Centurylink)
  • Limelight
  • CloudFront
  • Fastly
  • Verizon (VDMS)
  • Comcast
  • StackPath
  • 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.
    • 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 indicaiton, set the threshold to a very low value (0.01% - 0.1%).

    How Cloud Wrapper works with failover

    Failover with Cloud Wrapper requires the Cloud Wrapper Advanced behavior.

    Does Cloud Wrapper work with Failover?Yes. Cloud Wrapper supports failover for MultiCDN properties by default.
    Is there a performance impact?There may be a performance impact if the failover map forwards requests to an Akamai server further than your Origin 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.

    Purge content from Cloud Wrapper

    Purge content by URL 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 3rd party delivery if the same objects are served using both workflows.
    Purge content by CP CodesTo ensure complete content removal, you must purge or invalidate all CP codes that serve your content, including both Akamai and 3rd party CDN CP codes.
    Purge by Cache-TagNot 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.

    Check the status of your configuration

    Your configuration status follows this table of definitions:

    SaveSavedThis is the initial state when your configuration version is saved.
    ActivateActivation In ProgressYour activation request is being processed. Propagation time is approximately 3-4 hours.
    ActivateActivation Failed 1 2Your activation request has failed. Create a new configuration version and try again.
    ActivateActivation Aborted 2Your activation request has been aborted.
    ActivateActive 2This configuration is now active. Note: Use Property Manager to apply this configuration to a behavior .
    DeleteDelete In ProgressYour request to delete this configuration is being processed.
    DeleteDelete Failed 1 2Your request to delete this configuration has failed.
    DeleteDelete Aborted 2Your request to delete this configuration has beenaborted.
    N/AInactivePreviously Active versions are displayed as Inactive when the latest version becomes active.

    1: The system will automatically remove this configuration version.
    2: The system sends a notification to the email associated with your Control Center login.

    Understand 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. There's a platform-level eviction that happens after an asset is idle for 30 days. Assets requested at least once within 30 days will remain in cache per normal caching / TTL rules.


    Low TTL doesn't automatically result in an object eviction

    Low TTL objects are marked for eviction, but are only evicted if the overall quota is reaching the limits, or if the objects haven’t been accessed for 30 days.

    Locations available with Cloud Wrapper

    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