When working with Cloudlets, familiarize yourself with these terms:
|Behavior||Each Cloudlet has its own special behavior. In Property Manager, a behavior contains the settings for handling and processing the content passing through the Akamai network. Behaviors are essentially the building blocks for a property's rules.|
|Conditional Origin||For Cloudlets that can change the forward origin and path, this is an origin server where you can forward Cloudlets requests to.|
An origin is a source of traffic sent from your network to the Akamai portal. An origin may be a hostname, a data center, or a piece of networking equipment, like a server or a load balancer.
You configure Conditional Origins in Property Manager.
|Cloudlets Policy Manager||The Control Center application you use to set up and manage Cloudlets policies and rules.|
|Groups||Groups control access to both properties and Cloudlets policies.|
If you have editor-level permissions, you can only edit Cloudlets policies within the groups you have access to.
In addition, you can only associate a Cloudlets policy with a property that is in a compatible group. A compatible group can be the same group, or be an ancestor of the group containing the Cloudlets policy.
In Cloudlets Policy Manager, you can move a policy to a different group.
|Policy||The non-shared policy type available for all Cloudlets except for Virtual Waiting Room. A non-shared policy requires activation each time you wish to reuse it for another property.|
|Load Balancing Manager||Application you use to set up and manage load balancing settings for the Application Load Balancer Cloudlet.|
|Policies||A policy is a container for the rules that govern how a Cloudlet behaves. All policies are the same between Cloudlets: you select the type of Cloudlet you are configuring, give it a name, and add a description.|
For each Cloudlet instance on your contract, there can be any number of policies. Each policy is tied to a specific property.
You can create multiple versions of a policy.
|Policy version||A specific revision of a Cloudlet policy. Version numbers start at 1 and increment as new versions are created.|
You may want to create different versions of a policy to support different business requirements or to test new functionality. When you activate a Cloudlet, you are activating a specific version of a Cloudlet policy.
Within a policy version you define rules. These rules determine what happens when an incoming request matches on the criteria for triggering the Cloudlet.
|Properties||A property includes all the rules for processing incoming requests for web assets. You configure properties using Property Manager, available on Control Center.|
In Property Manager, you add a Cloudlets behavior to a property and activate the updated property version.
|Rules||Policy versions contain rules that govern a Cloudlet's behavior.|
These rules include both the criteria that need to be met in an incoming request, as well as the resulting actions to take when those conditions are met.
You can add 5000 rules to a Cloudlets policy.
Note: If your rules aren't working as expected before the 5000 limit, contact support. You may have hit a cost limit.
|Shared Policy||A type of policy that, once created (or upgraded into) and activated, is available and fully usable for an unlimited number of properties. Unlike non-shared policies, it does not require any further work to be performed, and the activation time is slightly reduced.|
The following Cloudlets support the Shared Policy type;
- API Prioritization
- Audience Segmentation
- Edge Redirector
- Forward Rewrite
- Phased Release
- Request Control
- Virtual Waiting Room (Beta)
Updated 17 days ago