Policy

Create and update a cloudlet policy.

For each Cloudlet instance on your contract, you can have any number of policies. A single policy is associated with a single property configuration. Within a policy version, define the rules that determine when the Cloudlet executes. You may want to create a new version of a policy to support a different business requirement or to test a new functionality.

resource "akamai_cloudlets_policy" "my_cloudlet_policy" {
  resource "akamai_cloudlets_policy" "my-new-cloudlet-policy" {
  name          = "policy1"
  cloudlet_code = "ER"
  group_id      = "12345"
  match_rules   = file("${path.root}/cloudlet-policy.json")
}

Arguments

Pass a name for your policy, the code representing the type of cloudlet you're using, your group ID, and any optional arguments to create a policy.

Argument	Required	Description
`name`	✔	A user created name for a policy.
`cloudlet_code`	✔	The character code for your cloudlet type. `ALB`. Application load balancer. `AP`. API prioritization. `AS`. Audience segmentation. `CD`. Phased release. `ER`. Edge redirector. `FR`. Forward rewrite `IG`. Request control. `VP`. Visitor prioritization.
`group_id`	✔	Your group ID.
`description`		A human-readable description about your policy version.
`match_rule_format`		Your `match_rules` version.
`match_rules`		The rules for your policy in JSON format, in the resource or a pointer to the file.

Attributes

Returned to you are your cloudlet's ID and version along with a jsonencoded list of warnings.