Cloudlets are value-added applications that complement Akamai's core delivery solutions to solve specific business challenges. Cloudlets bring a site's business logic closer to the end user by placing it on the edge of the content delivery platform.

The Cloudlets API v3 allows you to create and view Cloudlet policies and policy versions for shared policies only. In addition, use this API to:

  • Activate a Cloudlet policy version on either the staging or production networks.

  • Delete a Cloudlet policy.

  • Upgrade a legacy policy to a shared policy.

  • View the activation history of a Cloudlet policy.

Use this API to set up these Cloudlets:

  • API Prioritization. Lets you specify which calls are given priority and are sent to the origin during high-demand situations. Based on information in the inbound request, you configure the rules that determine which calls are prioritized.

  • Audience Segmentation. Provides hassle-free traffic segmentation and stickiness without degrading performance. This is often beneficial for A/B and multivariate testing.

  • Edge Redirector. Helps you more efficiently manage a large numbers of redirects. By executing redirects at the Akamai Edge, you can reduce round trips to the origin and offload hits from your origin infrastructure.

  • Forward Rewrite. Helps you create, based on in-bound request information, human-readable and search engine optimization-friendly (SEO-friendly) URLs for dynamically-generated pages.

  • Phased Release. Lets you define the percentage of your visitors to direct to a different experience or origin while maintaining visitor stickiness. This Cloudlet can help facilitate a fast rollout of code changes to production with real users, allowing you to gradually move some visitors to a new experience or deployment while retaining the flexibility to roll back immediately should you encounter challenges.

  • Request Control. Provides conditional access to your website or application by defining and managing allow lists and deny lists based on a number of match criteria, including the IP address and geography associated with incoming requests. You can have a branded 403 (Deny) page display when a user is denied access.