Scaling policies#

The operations described in this section help you create and manage scaling policies for a scaling group.

List policies#

GET /v1.0/{tenantId}/groups/{groupId}/policies

This operation lists scaling policies that are available to a specified scaling group.

Each policy is described in terms of an ID, name, type, adjustment, cooldown time, and links. These descriptions are returned in the response body in JSON format.

This table shows the possible response codes for this operation:

Response Code

Name

Description

200

OK

The request succeeded and the response contains a list of scaling policies for the specified scaling group.

400

InvalidQueryArgument

The “limit” query argument value is not a valid integer.

401

InvalidCredentials

The X-Auth-Token the user supplied is bad.

403

Forbidden

The user does not have permission to perform the resource; for example, the user only has an observer role and attempted to perform something only available to a user with an admin role. Note, some API nodes also use this status code for other things.

404

NoSuchScalingGroupError

The specified scaling group was not found.

405

InvalidMethod

The method used is unavailable for the endpoint.

413

RateLimitError

The user has surpassed their rate limit.

500

InternalError

An error internal to the application has occurred, please file a bug report.

503

ServiceUnavailable

The requested service is unavailable, please file a bug report.

Request#

This table shows the URI parameters for the request:

Name

Type

Description

{tenantId}

String (Required)

A subscriber to the auto scaling service.

X-Auth-Token

String (Required)

A valid authentication token.

{groupId}

Uuid (Required)

A scaling group.

This operation does not accept a request body.

Response#

Example List policies: JSON response

{
   "policies":[
      {
         "args":{
            "cron":"23 * * * *"
         },
         "changePercent":-5.5,
         "cooldown":1800,
         "id":"5f26e16c-5fa7-4d4f-8e78-257ea711389f",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/5f26e16c-5fa7-4d4f-8e78-257ea711389f/",
               "rel":"self"
            }
         ],
         "name":"scale down by 5.5 percent at 11pm",
         "type":"schedule"
      },
      {
         "args":{
            "at":"2013-12-05T03:12:00Z"
         },
         "changePercent":-5.5,
         "cooldown":1800,
         "id":"9f7c5801-6b25-4f5a-af07-4bb752e23d53",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/9f7c5801-6b25-4f5a-af07-4bb752e23d53/",
               "rel":"self"
            }
         ],
         "name":"scale down by 5.5 percent on the 5th",
         "type":"schedule"
      },
      {
         "changePercent":-5.5,
         "cooldown":1800,
         "id":"eb0fe1bf-3428-4f34-afd9-a5ac36f60511",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/eb0fe1bf-3428-4f34-afd9-a5ac36f60511/",
               "rel":"self"
            }
         ],
         "name":"scale down by 5.5 percent",
         "type":"webhook"
      },
      {
         "cooldown":1800,
         "desiredCapacity":5,
         "id":"2f45092a-fde7-4461-a67a-3519e0366cd6",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/2f45092a-fde7-4461-a67a-3519e0366cd6/",
               "rel":"self"
            }
         ],
         "name":"set group to 5 servers",
         "type":"webhook"
      },
      {
         "change":1,
         "cooldown":1800,
         "id":"e36e6a43-2a7a-433c-918c-39fa45b75d12",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/e36e6a43-2a7a-433c-918c-39fa45b75d12/",
               "rel":"self"
            }
         ],
         "name":"scale up by one server",
         "type":"webhook"
      }
   ],
   "policies_links":[

   ]
}

Create scaling policy#

POST /v1.0/{tenantId}/groups/{groupId}/policies

This operation creates one or more scaling policies for a specified scaling group.

To create a policy, specify it in the request body in JSON format. Each description must include a name, type, adjustment, and cooldown time.

Use the JSON response to obtain information about the newly-created policy or policies:

  • The response header points to the List Policies endpoint.

  • The response body provides an array of scaling policies.

The examples that are provided below show several methods for creating a scaling policy:

  • A request to create a policy based on desired capacity.

  • A request to create a policy based on incremental change.

  • A request to create a policy based on change percentage.

  • A request to create a policy based on change percentage scheduled daily, at a specific time of day.

  • A request to create a policy based on change percentage scheduled once, for a specific date and time.

  • A request to create multiple policies, followed by the matching response.

This table shows the possible response codes for this operation:

Response Code

Name

Description

201

Created

The scaling policy has been created.

400

InvalidJsonError

The request is refused because the body was invalid JSON”.

400

ValidationError

Both “at” and “cron” values for the “args” parameter are supplied. Only one such value is allowed.

400

ValidationError

More than one of “change” or “changePercent” or “desiredCapacity” values are supplied. Only one such value is allowed.

400

ValidationError

Neither “at” or “cron” values for the “args” parameter are supplied and this is a “schedule” type policy.

400

ValidationError

Neither “change” or “changePercent” or “desiredCapacity” values are supplied.

400

ValidationError

The “args” parameter is not supplied and this is a “schedule” type policy.

400

ValidationError

The “at” value does not correspond to “YYYY-MM- DDTHH:MM:SS.SSSS” format.

400

ValidationError

The “cron” value is invalid. It either contains a seconds component or is invalid cron expression.

400

ValidationError

The request body had valid JSON but with unexpected properties or values in it. Please note that there can be many combinations that cause this error. We will try to list the most common mistakes users are likely to make in a particular request. “.

401

InvalidCredentials

The X-Auth-Token the user supplied is bad.

403

Forbidden

The user does not have permission to perform the resource; for example, the user only has an observer role and attempted to perform something only available to a user with an admin role. Note, some API nodes also use this status code for other things.

404

NoSuchScalingGroupError

The specified scaling group was not found.

405

InvalidMethod

The method used is unavailable for the endpoint.

413

RateLimitError

The user has surpassed their rate limit.

415

UnsupportedMediaType

The request is refused because the content type of the request is not “application/json”.

422

PoliciesOverLimitError

The user has reached their quota for scaling policies, currently 100.

500

InternalError

An error internal to the application has occurred, please file a bug report.

503

ServiceUnavailable

The requested service is unavailable, please file a bug report.

Request#

This table shows the URI parameters for the request:

Name

Type

Description

{tenantId}

String (Required)

A subscriber to the auto scaling service.

X-Auth-Token

String (Required)

A valid authentication token.

{groupId}

Uuid (Required)

A scaling group.

This table shows the body parameters for the request:

Name

Type

Description

[*]

Array (Required)

An array of scaling policies.

[*].args

Object (Optional)

Additional configuration information for policies of type schedule. This parameter is not required for policies of type webhook. This parameter must be set to either at or cron, which are mutually exclusive.

[*].args.cron

String (Optional)

The time when the policy will be executed, as a cron entry. For example, if this is parameter is set to 1 0 * * *, the policy will be executed at one minute past midnight (00:01) every day of the month, and every day of the week. For more information about cron, read: http://en.wikipedia.org/wiki/Cron

[*].args.at

String (Optional)

The time when this policy will be executed. The time must be formatted according to this service’s custom :ref: Date and Time format <date-time-format> with seconds, otherwise a 400 error may be returned. The policy will be triggered within a 10-second range of the time specified, so if you set the at time to 2013-05-19T08:07:08Z, it will be triggered anytime between 08:07:08 to 08:07:18. This property is mutually exclusive with the cron parameter.

[*].changePercent

Number (Optional)

The percent change to make in the number of servers in the scaling group. If this number is positive, the number of servers will increase by the given percentage. If this parameter is set to a negative number, the number of servers decreases by the given percentage. The absolute change in the number of servers will be rounded to the nearest integer. This means that if -X% of the current number of servers translates to -0.5 or -0.25 or -0.75 servers, the actual number of servers that will be shut down is 1. If X% of the current number of servers translates to 1.2 or 1.5 or 1.7 servers, the actual number of servers that will be launched is 2

[*].cooldown

Number (Required)

The cooldown period, in seconds, before this particular scaling policy can be executed again. The policy cooldown period does not affect the global scaling group cooldown. The minimum value for this parameter is 0 seconds, the maximum value is 86400 seconds (24 hrs).

[*].type

Enum (Required)

The type of policy that will be executed for the current release, this value can be either webhook or schedule.

[*].change

Integer (Optional)

The change to make in the number of servers in the scaling group. This parameter must be an integer. If the value is a positive integer, the number of servers increases. If the value is a negative integer, the number of servers decreases.

[*].desiredCapacity

Integer (Optional)

The desired server capacity of the scaling the group; that is, how many servers should be in the scaling group. This value must be an absolute number, greater than or equal to zero. For example, if this parameter is set to ten, executing the policy brings the number of servers to ten. The minimum allowed value is zero. Note that maxEntities and minEntities for the configured group take precedence over this setting.

Example Create policy: JSON request

The examples that are provided below show several methods for creating a scaling policy: * A request to create a policy based on desired capacity * A request to create a policy based on incremental change * A request to create a policy based on change percentage * A request to create a policy based on change percentage scheduled daily, at a specific time of day * A request to create a policy based on change percentage scheduled once, for a specific date and time * A request to create multiple policies,followed by the matching response

The following example shows how to create a webhook-based policy specifying that the desired capacity be five servers and setting the cooldown period to 1800 seconds.

[
   {
      "name":"set group to 5 servers",
      "desiredCapacity":5,
      "cooldown":1800,
      "type":"webhook"
   }
]

[
   {
      "name":"scale up by one server",
      "change":1,
      "cooldown":1800,
      "type":"webhook"
   }
]

[
   {
      "name":"scale down by 5.5 percent",
      "changePercent":-5.5,
      "cooldown":1800,
      "type":"webhook"
   }
]

[
   {
      "name":"scale down by 5.5 percent at 11pm",
      "changePercent":-5.5,
      "cooldown":1800,
      "type":"schedule",
      "args":{
         "cron":"23 * * * *"
      }
   }
]

[
  {
    "name": "scale down by 5.5 percent on the 5th",
    "changePercent": -5.5,
    "cooldown": 1800,
    "type": "schedule",
    "args": {
      "at": "2013-12-05T03:12:00Z"
    }
  }
]

[
   {
      "change":1,
      "cooldown":1800,
      "name":"scale up by one server",
      "type":"webhook"
   },
   {
      "changePercent":-5.5,
      "cooldown":1800,
      "name":"scale down by 5.5 percent",
      "type":"webhook"
   },
   {
      "cooldown":1800,
      "desiredCapacity":5,
      "name":"set group to 5 servers",
      "type":"webhook"
   },
   {
      "args":{
         "cron":"23 * * * *"
      },
      "changePercent":-5.5,
      "cooldown":1800,
      "name":"scale down by 5.5 percent at 11pm",
      "type":"schedule"
   },
   {
      "args":{
         "at":"2013-12-05T03:12:00Z"
      },
      "changePercent":-5.5,
      "cooldown":1800,
      "name":"scale down by 5.5 percent on the 5th",
      "type":"schedule"
   }
]

Response#

Example Create policy: JSON response

{
   "policies":[
      {
         "args":{
            "at":"2013-12-05T03:12:00Z"
         },
         "changePercent":-5.5,
         "cooldown":1800,
         "id":"9f7c5801-6b25-4f5a-af07-4bb752e23d53",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/9f7c5801-6b25-4f5a-af07-4bb752e23d53/",
               "rel":"self"
            }
         ],
         "name":"scale down by 5.5 percent on the 5th",
         "type":"schedule"
      },
      {
         "cooldown":1800,
         "desiredCapacity":5,
         "id":"b0555a35-b2cb-4f0e-8743-d59e1621b980",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/b0555a35-b2cb-4f0e-8743-d59e1621b980/",
               "rel":"self"
            }
         ],
         "name":"set group to 5 servers",
         "type":"webhook"
      },
      {
         "args":{
            "cron":"23 * * * *"
         },
         "changePercent":-5.5,
         "cooldown":1800,
         "id":"30707675-8e7c-4ea5-9358-c21648afcf29",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/30707675-8e7c-4ea5-9358-c21648afcf29/",
               "rel":"self"
            }
         ],
         "name":"scale down by 5.5 percent at 11pm",
         "type":"schedule"
      },
      {
         "change":1,
         "cooldown":1800,
         "id":"1f3bdd08-7aae-4009-a3b7-49aa47fc0876",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/1f3bdd08-7aae-4009-a3b7-49aa47fc0876/",
               "rel":"self"
            }
         ],
         "name":"scale up by one server",
         "type":"webhook"
      },
      {
         "changePercent":-5.5,
         "cooldown":1800,
         "id":"5afac18c-41e5-49d6-aba8-dec17c0d8ed7",
         "links":[
            {
               "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/5afac18c-41e5-49d6-aba8-dec17c0d8ed7/",
               "rel":"self"
            }
         ],
         "name":"scale down by 5.5 percent",
         "type":"webhook"
      }
   ]
}

Show policy details#

GET /v1.0/{tenantId}/groups/{groupId}/policies/{policyId}

This operation retrieves scaling policy details.

Details include an ID, name, type, adjustment, cool-down time, and links.

The details appear in the response body in JSON format.

This table shows the possible response codes for this operation:

Response Code

Name

Description

200

OK

The request succeeded and the response contains details about the specified scaling policy.

401

InvalidCredentials

The X-Auth-Token the user supplied is bad.

403

Forbidden

The user does not have permission to perform the resource; for example, the user only has an observer role and attempted to perform something only available to a user with an admin role. Note, some API nodes also use this status code for other things.

404

NoSuchPolicyError

The requested scaling policy was not found in the specified scaling group.

404

NoSuchScalingGroupError

The specified scaling group was not found.

405

InvalidMethod

The method used is unavailable for the endpoint.

413

RateLimitError

The user has surpassed their rate limit.

500

InternalError

An error internal to the application has occurred, please file a bug report.

503

ServiceUnavailable

The requested service is unavailable, please file a bug report.

Request#

This table shows the URI parameters for the request:

Name

Type

Description

{tenantId}

String (Required)

A subscriber to the auto scaling service.

X-Auth-Token

String (Required)

A valid authentication token.

{groupId}

Uuid (Required)

A scaling group.

{policyId}

Uuid (Required)

A scaling policy.

This operation does not accept a request body.

Response#

Example Show policy details: JSON response

{
   "policy":{
      "args":{
         "cron":"23 * * * *"
      },
      "changePercent":-5.5,
      "cooldown":1800,
      "id":"5f26e16c-5fa7-4d4f-8e78-257ea711389f",
      "links":[
         {
            "href":"https://dfw.autoscale.api.rackspacecloud.com/v1.0/676873/groups/605e13f6-1452-4588-b5da-ac6bb468c5bf/policies/5f26e16c-5fa7-4d4f-8e78-257ea711389f/",
            "rel":"self"
         }
      ],
      "name":"scale down by 5.5 percent at 11pm",
      "type":"schedule"
   }
}

Update scaling policy#

PUT /v1.0/{tenantId}/groups/{groupId}/policies/{policyId}

This operation updates an existing scaling policy for the specified tenant.

To update the policy, specify the name, type, adjustment, and cooldown time for the policy in the request body in JSON format. If the change succeeds, no response body is returned.

Note

All Rackspace Auto Scale update (PUT) operations completely replace the configuration being updated. Empty values (for example, { } )in the update are accepted and overwrite previously specified parameters. New parameters can be specified. All create (POST) parameters, even optional ones, are required for the update operation.

This table shows the possible response codes for this operation:

Response Code

Name

Description

204

Success But No Content

The update scaling policy request succeeded.

400

InvalidJsonError

The request is refused because the body was invalid JSON”.

400

ValidationError

Both “at” and “cron” values for the “args” parameter are supplied. Only one such value is allowed.

400

ValidationError

More than one of “change” or “changePercent” or “desiredCapacity” values are supplied. Only one such value is allowed.

400

ValidationError

Neither “at” or “cron” values for the “args” parameter are supplied and this is a “schedule” type policy.

400

ValidationError

Neither “change” or “changePercent” or “desiredCapacity” values are supplied.

400

ValidationError

The “args” parameter is not supplied and this is a “schedule” type policy.

400

ValidationError

The “at” value does not correspond to “YYYY-MM- DDTHH:MM:SS.SSSS” format.

400

ValidationError

The “cron” value is invalid. It either contains a seconds component or is invalid cron expression.

400

ValidationError

The request body had valid JSON but with unexpected properties or values in it. Please note that there can be many combinations that cause this error.

401

InvalidCredentials

The X-Auth-Token the user supplied is bad.

403

Forbidden

The user does not have permission to perform the resource; for example, the user only has an observer role and attempted to perform something only available to a user with an admin role. Note, some API nodes also use this status code for other things.

404

NoSuchPolicyError

The requested scaling policy was not found in the specified scaling group.

404

NoSuchScalingGroupError

The specified scaling group was not found.

405

InvalidMethod

The method used is unavailable for the endpoint.

413

RateLimitError

The user has surpassed their rate limit.

415

UnsupportedMediaType

The request is refused because the content type of the request is not “application/json”.

500

InternalError

An error internal to the application has occurred, please file a bug report.

503

ServiceUnavailable

The requested service is unavailable, please file a bug report.

Request#

This table shows the URI parameters for the request:

Name

Type

Description

{tenantId}

String (Required)

A subscriber to the auto scaling service.

X-Auth-Token

String (Required)

A valid authentication token.

{groupId}

Uuid (Required)

A scaling group.

{policyId}

Uuid (Required)

A scaling policy.

This table shows the body parameters for the request:

Name

Type

Description

scalingPolicies.[*].name

String (Required)

A name for the scaling policy. This name must be unique for each scaling policy.

scalingPolicies.[*].args

Object (Optional)

Additional configuration information for policies of type “schedule.” This parameter is not required for policies of type webhook. This parameter must be set to either at or cron, which are mutually exclusive.

scalingPolicies.[*].args.cron

String (Optional)

The time when the policy runs, as a cron entry. For example, if you set this parameter to 1 0 * * *, the policy runs at one minute past midnight (00:01) every day of the month, and every day of the week. For more information about cron, see http://en.wikipedia.org/wiki/Cron <http://en.wikipedia.org/wiki/Cron>.

scalingPolicies.[*].args.at

String (Optional)

The time when this policy will be executed. The time must be formatted according to this service’s custom :ref: Date and Time format <date-time-format>, with seconds, otherwise a 400 error may be returned. The policy will be triggered within a 10-second range of the time specified, so if you set the``at`` time to``2013-05-19T08:07:08Z``, it will be triggered anytime between 08:07:08 to 08:07:18. This property is mutually exclusive with the cron parameter.

scalingPolicies.[*].changePercent

Number (Optional)

The percent change to make in the number of servers in the scaling group. If this number is positive, the number of servers increases by the given percentage. If this parameter is set to a negative number, the number of servers decreases by the given percentage. The absolute change in the number of servers is rounded to the nearest integer. This means that if -X% of the current number of servers translates to -0.5 or -0.25 or -0.75 servers, the actual number of servers that are shut down is 1. If X% of the current number of servers translates to 1.2 or 1.5 or 1.7 servers, the actual number of servers that are launched is 2.

scalingPolicies.[*].cooldown

Number (Required)

The cooldown period, in seconds, before this particular scaling policy can run again. The policy cooldown period does not affect the global scaling group cooldown. The minimum value for this parameter is 0 seconds. The maximum value is 86400 seconds (24 hrs).

scalingPolicies.[*].type

Enum (Required)

The type of policy that runs. Currently, this value can be either webhook or schedule.

scalingPolicies.[*].change

Integer (Optional)

The change to make in the number of servers in the scaling group. This parameter must be an integer. If the value is a positive integer, the number of servers increases. If the value is a negative integer, the number of servers decreases.

scalingPolicies.[*].desiredCapacity

Integer (Optional)

The desired server capacity of the scaling the group; that is, how many servers should be in the scaling group. This value must be an absolute number, greater than or equal to zero. For example, if this parameter is set to ten, executing the policy brings the number of servers to ten. The minimum allowed value is zero. Note that the configured group maxEntities and minEntities takes precedence over this setting.

Example Update policy: JSON request

{
   "change":1,
   "cooldown":1800,
   "name":"scale up by one server",
   "type":"webhook"
}

Response#

This operation does not return a response body.

Delete scaling policy#

DELETE /v1.0/{tenantId}/groups/{groupId}/policies/{policyId}

This operation deletes a specified scaling policy from the specified tenant.

If deletion is successful, no response body is returned.

This table shows the possible response codes for this operation:

Response Code

Name

Description

204

Success But No Content

The delete scaling policy request succeeded.

401

InvalidCredentials

The X-Auth-Token the user supplied is bad.

403

Forbidden

The user does not have permission to perform the resource; for example, the user only has an observer role and attempted to perform something only available to a user with an admin role. Note, some API nodes also use this status code for other things.

404

NoSuchPolicyError

The requested scaling policy was not found in the specified scaling group.

404

NoSuchScalingGroupError

The specified scaling group was not found.

405

InvalidMethod

The method used is unavailable for the endpoint.

413

RateLimitError

The user has surpassed their rate limit.

500

InternalError

An error internal to the application has occurred, please file a bug report.

503

ServiceUnavailable

The requested service is unavailable, please file a bug report.

Request#

This table shows the URI parameters for the request:

Name

Type

Description

{tenantId}

String (Required)

A subscriber to the auto scaling service.

X-Auth-Token

String (Required)

A valid authentication token.

{groupId}

Uuid (Required)

A scaling group.

{policyId}

Uuid (Required)

A scaling policy.

This operation does not accept a request body.

Response#

This operation does not return a response body.

Execute policy#

POST /v1.0/{tenantId}/groups/{groupId}/policies/{policyId}/execute

This operation runs a specified scaling policy.

If the operation succeeds, a response body is returned.

This table shows the possible response codes for this operation:

Response Code

Name

Description

202

Accepted

The execute policy request was accepted. The actual execution may be delayed, but will be attempted if no errors are returned. Use the “GET scaling group state” method to see if the policy was executed.

400

InvalidJsonError

The request is refused because the body was invalid JSON”.

400

ValidationError

The request body had valid JSON but with unexpected properties or values in it. There can be many combinations that can cause this error.

401

InvalidCredentials

The X-Auth-Token the user supplied is bad.

403

CannotExecutePolicyError

The policy did not run because a scaling policy or scaling group cooldown was still in effect.

403

CannotExecutePolicyError

The policy did not run because applying the changes would not result in the addition or deletion of any servers.

403

GroupPausedError

The policy did not run because the group is paused. You can resolve this error by resuming the group.

403

Forbidden

The user does not have permission to perform the resource; for example, the user only has an observer role and attempted to perform something only available to a user with an admin role. Note, some API nodes also use this status code for other things.

404

NoSuchPolicyError

The requested scaling policy was not found in the specified scalilng group.

404

NoSuchScalingGroupError

The specified scaling group was not found.

405

InvalidMethod

The method used is unavailable for the endpoint.

413

RateLimitError

The user has surpassed their rate limit.

415

UnsupportedMediaType

The request is refused because the content type of the request is not “application/json”.

500

InternalError

An error internal to the application has occurred, please file a bug report.

503

ServiceUnavailable

The requested service is unavailable, please file a bug report.

Request#

This table shows the URI parameters for the request:

Name

Type

Description

{tenantId}

String (Required)

A subscriber to the auto scaling service.

X-Auth-Token

String (Required)

A valid authentication token.

{groupId}

Uuid (Required)

A scaling group.

{policyId}

Uuid (Required)

A scaling policy.

This operation does not accept a request body.

Response#

This operation does not return a response body.