Cloudlets
Enter the hostname you want visitors to be redirected from. Anyone visiting www.akamai.com from within the UK will be redirected to a URL we will define in the next step.
Creating a Rule
You can see there are a number of match criteria to choose from to create advanced rules. For our example, we’ll begin with Country.
Redirect URL
Hit Save and you're done!
Begin typing in the country name for which you want to redirect your visitors. In this case, we want to redirect UK visitors to the local version of the Akamai site. To add another Match Type, use the + sign.
Match Type
Select the timing. Choose either a specific timeframe for this redirect, or Always On to apply the rule at all times going forward.
Hostname
Always On
The Match Operator determines how the Match Type is applied. Your option for Country is it’s either one of or not one of. Other Match Types may also include contains any of or does not contain any of.
Choose a type of redirect.301 should be used to permanently redirect a URL and is recommended in preserving link juice / page ranking for SEO purposes.302 should be used when temporarily directing users to another URL.
Country
Match Operator
Enter the URL you want users to be directed to instead. We are choosing to redirect visitors to the local UK Akamai site: uk.akamai.com.
You can add up to 5,000 redirect rules per policy and there is no limit to the number of policies you can create! You can go back in and update these rules at any time.
To begin, identify the conditions upon which you want to match your rule. You can choose from a number of options. For this example, we want to redirect all users from a country to a local version of our website. To accomplish this, we will use 2 conditions: Country and Hostname.
Redirect Type
Go Back
Continue...
Start Demo
Provide conditional visitor access to your content or application based on users’ IP or Geography.
Creates human-readable and SEO-friendly URLs for dynamically-generated pages.
Provides a visitor-friendly waiting room experience for busy sites with flash crowds.
Offloads high volumes of 301 (permanent) and 302 (temporary) redirects to the edge.
Manages flash crowds to your API for native mobile apps & single page web apps.
Input Validation
Select a Cloudlet to Demo
Edge Redirector
Visitor Prioritization
Marketplace Demo
Forward Rewrite
API Prioritization
Phased Release
Audience Segmentation
Request Control
File Extension
Contains any of
Protocol
Is one of
0 Rules Created
And
Does not contain any of
Is not one of
Query String
Redirect URL*
Create a Rule
Select
URL Regular Expression
Temporary 302
IF
Cookie
United Kingdom
Add a tag
Permanent 301
Device Characteristics
www.akamai.com
Cancel
Continent
United Arab Emirates
(Remove)
Save Rule
Copy Query String
Is one of
URL Path
Hostname
Region/State
United States of America
http://uk.akamai.com
0 Rules Created
Replay Demo
Learn How to Purchase at the Akamai Marketplace
Learn More about all Cloudets
View Marketplace Demo
AKAMAI.COM/CLOUDLETS
Learn More
You have 2 options to set up and manage your redirects:
2
Manage large numbers of redirects, quickly and easily.
You can bulk upload rules from a CSV file. For every Cloudlet, you will need to create a policy and can add up to 5,000 rules per policy. This demo will walk you through a rule set-up for a version of your policy.
Use the Akamai Policy Manager located in the Luna Customer Portal
1
Set up a customized console like the one you’ll see in this demo using the included API
Go Back To Overview
Improve your SEO and user experience by converting dynamic URLs to semantic, human-readable URLs.
You have 2 options to set up and manage your rewrites:
Both can be extended to business or operations users to manage URL rewrites on Akamai. For every Cloudlet, you will need to create a policy and can add up to 5,000 rules per policy. This demo will walk you through a rule set-up for a version of your policy.
Easily manage and activate whitelists and blacklists based on a number of match criteria including the IP/CIDR and/or geography associated with the inbound request.
You have 2 options to set up and manage your whitelists and blacklists:
Both can be extended to business or operations users to manage. For every Cloudlet, you will need to create a policy and can add up to 5,000 rules per policy. This demo will walk you through a rule set-up for a version of your policy.
Manage capacity for your application by serving an alternate static experience to a segment of users.
You have 2 options to set up and manage your prioritization:
Both can be extended to business or operations users to manage. For every Cloudlet, you will need to create a policy and can add up to 5,000 rules per policy. This demo will walk you through a rule set-up for a version of your policy.
/examples/example
302
Path & Query String
301
/cloudlets
/html/technology/cloudlets/
IP/CIDR
Allow
Deny
Rule Name*
Deny Branded
192.168.0.0/24
SamplePBlock
Allow / Deny
Request Header
Provide a user friendly waiting room experience to reduce abandonment and protect from site failure when your back-end application approaches overload.
Canada
Cayman Islands
Send All to Waiting Room
Example Rule Name
user_cookie=guest
Name
Likelihood to Origin
Request Method
11/15/2015 @ 09:30
Start Date/Time
11/17/2015 @ 20:30
End Date/Time
70%
To begin, identify the conditions upon which you want to match your rule. You can choose from a number of options. For this example, we want users to see akamai.com/cloudlets as the URL, even though we are delivering content from a longer, wordier path. To accomplish this, we will use 2 conditions: Hostname and Path.
Path
You can see there are a number of match criteria to choose from to create advanced rules. For our example, we’ll begin with Hostname.
Select the timing. You can choose a specific timeframe for this rewrite, or Always On to apply the rule at all times going forward.
Select the hostname of your site. In this case: www.akamai.com. Because we don’t want to rewrite all akamai.com URLs, we need to specify the specific path hosted on akamai.com that should be rewritten. To add another Match Type, use the + sign.
You can add up to 5,000 redirect rules per policy and there is no limit to the number of policies you can create! You can go back in and update these rules at any time.
Select the path and optional query string you want users to be directed to while maintaining a static URL. In this case, we would like users to continue to see akamai.com/cloudlets, but actually show the content from: /html/technology/cloudlets/. You can also choose whether to copy query string parameters.
The Match Operator determines how the Match Type is applied. Your option for Hostname is it’s either one of or not one of. Other Match Types may also include contains any of or does not contain any of.
Select Path from the dropdown and enter /cloudlets so that visitors of this specific URL (www.akamai.com/cloudlets) will be displayed content from the URL you define in the next step.
You can add up to 5,000 rules per policy and there is no limit to the number of policies you can create! You can go back in and update these rules at any time.
Name the rule you just created!
Select whether to Allow or Deny permission to your specific site for this group of IP addresses. You also have the option to Deny Branded if you decide to display a branded 403 page when denying access. Because we are granting access to employees, we want to select Allow.
To begin, identify the conditions upon which you want to match your rule. You can choose from a number of options. For this example, we’ll set up a whitelist to limit users to a pre-production site to just employees. To accomplish this, we will use 1 condition: IP/CIDR.You could just as easily set up a blacklist, denying access to your site to a specific set of countries, for example.
The Match Operator determines how the Match Type is applied. Your option for IP/CIDR is it’s either one of or not one of. Other Match Types may also include contains any of or does not contain any of.
You can see there are a number of match criteria to choose from to create advanced rules. For our example, we’ll begin with IP/CIDR.
Rule Name
Enter the CIDR for your employee block.
Allow/Deny
Serve an alternate API response (json, xml, or other) from Akamai Net Storage for all or a percentage of requests to preserve app capacity for prioritized API traffic.
Select the timing. You can choose a specific timeframe for this rewrite, or Always On to apply the rule at all times going forward.
You can see there are a number of match criteria to choose from to create advanced rules. For our example, we’ll begin with Query String.
Serve Alternate Response
The Match Operator determines how the Match Type is applied. Your options for Query String is it’s either one of, not one of, contains any of, or does not contain any of.
Begin typing in the query string for which you want to direct viewers through to a dynamic playlist vs. switching to an alternate response -- in this case, a static playlist. To add another Match Type, use the + sign.
Select the URL path you want to prioritize.
To begin, identify the conditions upon which you want to match your rule. You can choose from a number of options. For this example, a dynamic online video service wants to automatically resolve to a static playlist hosted on Net Storage for a percentage of viewers as their backend approaches capacity. To accomplish this, we will use 2 conditions: Query String and URL Path.
Begin typing in the country name for which you want to direct visitors to a waiting room or through to your origin. In this example, we want to direct a percentage of guest visitors within Canada to a waiting room due to the expected increase in traffic. To add another Match Type, use the + sign.
To begin, identify the conditions upon which you want to match your rule. You can choose from a number of options. For this example, a Canadian sports retailer is anticipating an increase in traffic to their site due to an upcoming holiday sale and want to ensure that their regular customers are able to get through to their carts. To accomplish this, we will use 2 conditions: Country and Hostname.
Select the timing. Choose either a specific timeframe for this rule, or Always On to apply the rule at all times going forward. For our example, we only want to send requests to a waiting room during the high traffic event we’re planning.
Select the cookie you want to use to identify customers that should be sent to a waiting room vs. through to the shopping cart.
Select whether to send the visitors you’ve selected directly to a waiting room experience or through to origin. In our example, we only want a percentage of visitors to be sent to a waiting room so we will specify the probability.
Cloudlets Policy Manager is the User Interface for creating and editing the Cloudlets policies, which are comprised of a list of rules. This is also where you would manage the {OPEN} API for each Cloudlet.
What is the Cloudlets Policy Manager?
FAQ's
Try before you buy
Self-serviceable
Yes, it requires a delivery solution and works in concert with other Akamai Intelligent Platform capabilities.
Cloudlets come with a quick reference guide and a user integration guide explaining how to configure the settings in Cloudlets Policy Manager.
As a customer, you can visit the Akamai Marketplace to learn more about each Cloudlet, check out pricing, and begin your Free Trial -- no paperwork required. You can also join the conversation, ask questions, and offer ideas for new Cloudlets in the Cloudlets Community. Easy to use and configure UI and API
Do Cloudlets require an Akamai Delivery Solution?
Infrastrucure & Development OperationsDigital Marketing OperationsSecurity & Access ControlMobile App & API Support Phased ReleaseEdge RedirectorRequest ControlAPI Prioritization Visitor PrioritizationAudience SegmentationInput Validation Forward RewriteImage Converter
How will I learn how to setup and manage my Cloudlet(s)?
Cloudlets for:
What if you could extend application logic to the edge of the Akamai platform with easy to use tools that simplify web operations -- helping to save you time and money, while improving end ­user experiences? Introducing Cloudlets: self-serviceable, scalable apps at the Edge. Cloudlets help you overcome specific business and operational challenges, all through an easy to use UI or API control. By offloading decisions to the Akamai Intelligent Platform, you gain flexibility, resource offload and increased control.
Yes, Cloudlets have been designed to be provisioned using Akamai's Property Manager in Luna Control Center.
Simplify your Web Operations with
Fast & easy to configure
Simplify your web operations
Do Cloudlets require I be using Property Manager for my Akamai configuration?
Akamai Marketplace
Increased control & reduced costs
Make changes quickly, when you wantOpen API gives users more flexibility and control
Each Cloudlet application has been designed to solve a specific business or operational challenge that is shared among a wide range of our customers. Build upon and take advantage of the performance & scale of the Akamai Intelligent Platform “Push” app logic closer to end users
Simplify web operations and spend less time on custom development Speed time to market for website and application projects
Download the Cloudlets Menu
Developer Resources & API's
FEATURES
Helps perform a traffic split with cookies for A/B testing with session stickiness.
Protect your site from behavioral or brute force attacks through misuse of web forms.
Provides conditional visitor access to your content or application based on criteria you select.
Facilitate a fast rollout of code changes to production with real users and the ability to failback.
Let's get started.
You can find a link to the Akamai Marketplace in the upper right corner of the Luna Control Center.
Next
Welcome to the Akamai Marketplace! 
Did you know that within the Luna Control Center, you can find the Akamai Marketplace? Here you can discover, learn about, evaluate, and purchase Akamai products.
You can use the navigation menu on the left to quickly scan through all of the options.
Or you may filter by category, type or solution to find exactly what you need for your business challenege. Just click in the filter products box and scroll to view the options available to you.
You can easily navigate and browse the Akamai Marketplace to find products that interest you.
Explore and Learn More
All items in the Akamai Marketplace are self-serviceable, and easy access to configuration information helps you get started quickly.
Then you can start a free trial instantly. All you have to do is click on the start trial button and follow the instructions.
Review frequently asked questions, configuration information, and pricing.
Start My 60 Day FREE Trial
Start a Free Trial
Marketplace
Purchase and Use Immediately
Done
When you’re ready to purchase, simply click buy now to start the purchase process. No paperwork required, and your product is available to use immediately!
Click. Try. Buy.
playlist/default.json
member=gold
Cloudlets Demo
Range
Default Origin
Let the property detertime the origin
Proxy
Alternate Origin
Is within this Range (Inclusive)
User Location Date
Let the property determin the origin
1%
100%
Cloudlets Origin
Both can be extended to business or operations users to manage on Akamai. For every Cloudlet, you will need to create a policy and can add up to 5,000 rules per policy. This demo will walk you through a rule set­up for a version of your policy.
Easily define & manage audience segments for A/B testing & personalization while taking advantage of the performance & security of your Akamai CDN.
You have 2 options to set up and manage your segments:
Both can be extended to business or operations users to manage on Akamai. For every Cloudlet, you will need to create a policy and can add up to 5,000 rules per policy. This demo will walk you through a rule set­up for a version of your policy.
Perform canary releases with built­in proactive failover to reduce risk during continuous software release activities.
You have 2 options to set up and manage your validation:
Strengthen your web forms against abuse or monopolization from brute force and behavioral attackers.
Path and Query String
The Match Operator determines how the Match Type is applied. Your option for Range is "within this range." Other Match Types may also include contains any of, does not contain any of, is one of, or is not one of.
You can see there are a number of match criteria to choose from to create advanced rules. For our example, we’ll begin with Range.
Select Path from the dropdown and enter /cloudlets so that visitors of this specific URL (www.akamai.com/cloudlets) will see the alternate experience.
Select the range of visitors you want to divert to an alternate experience.To add another Match Type, use the + sign.
Select the path and optional query string you want users to be directed to while maintaining a static URL.In this case, we would like users to continue to see akamai.com/cloudlets, but actually show the content from: /html/technology/cloudlets/.You can also choose whether to copy query string parameters
To begin, identify the conditions upon which you want to match your rule. You can choose from a number of options. For this example, we want to create an audience segment for A/B testing purposes. To accomplish this, we will use 2 conditions: Range and URL Path.
Change the incoming request to use the origin you select. You have the option of choosing a Cloudlets Origin configured for the associated property, or letting the property decide which origin to use. Select "Let the property determine the origin" option.
Change the incoming request to use the origin you select. You have the option of choosing a Cloudlets Origin configured for the associated property, or letting the property decide which origin to use. Select the new originthat you will shifting traffic to.
Select the timing. You can choose a specific timeframe and build out multiple rules to gradually shift over more and more traffic, or Always On to apply the rule at all times going forward.
You can see there are a number of match criteria to choose from to create advanced rules.
Select URL Path from the dropdown and enter /cloudlets so that visitors of this specific URL (www.akamai.com/cloudlets) will be shifted to the new origin.To add another Match Type, you would just use the + sign.
Percentage of Traffic
The Match Operator determines how the Match Type is applied. Your option for URL Path is it’s either one of or not one of. Other Match Types may also include contains any of or does not contain any of.
To begin, identify the conditions upon which you want to match your rule. You can choose from a number of options. For this example, we want to test our new origin by gradually, and safely, shifting over a percentage of users. To accomplish this, we will use 1 condition: URL Path.
Set the percentage of visitors you want shifted to the new origin.
The Match Operator determines how the Match Type is applied. Your option for URL Path is it’s either one of or not one of. Other Match Types may also include contains any of or does not contain any of. Select URL Path from the dropdown and enter /users/login so all authentication attempts will be validated by Input Validation Cloudlet prior to forwarding to the origin.
To begin, identify the conditions upon which you want to match your rule. You can choose from a number of options. For this example, we’ll set up a validation of login form for e­commerce site. To accomplish this, we will use 2 conditions and 2 validators.
You can see there are a number of match criteria to choose from to create advanced rules. For our example, we’ll use URL Path and Request Method.
Login form is sent using POST method and such one must be selected.
Validators
Validator - Field Value for Password
Field Name is the name of the field to validate. For our example we select "Contains" and enter "password". Field Value is the value to validate. You can use different operators:Contains - The incoming request contains the value entered in the Field Value fieldExists - The form field name is simply included in the incoming request. It does not matter whether there is an associated field value or no value at all.Regex Matches - The incoming request includes a form field which value matches the regular expression in the associated rule field. For our example, we select "Regext Matches" operator and enter the following regex in Field Value: [a-f0-9]{64}
There are two types of validators supported: Number of Fields which checks the number of form fields that need to be included in the incoming requestField Name/Value which validates the presence and/or value of specified field name For our demo will will use Field Name/Value
Hit "Save" and you’re done!
Default
/users/login
Field Name/Value
Contains
GET
Regex Matches
POST
Number of Fields
Field Name
[a-f0-9]{64}
Exists
Is
And the form data does not match
Logon Form
Password
Field Value
Is Exactly
Username