4.2.2. Update launch configuration


Updates an existing launch configuration for the specified scaling group.

To change the launch configuration, specify the new configuration in the request body in JSON format. Configuration elements include from which image to create a server, which load balancers to join the server to, which networks to add the server to, and other metadata. If the update is successful, no response body is returned.


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. For more details, see Launch configurations.

This table shows the possible response codes for this operation:

Response CodeNameDescription
204Success But No ContentThe update launch configuration request succeeded.
400InvalidJsonErrorThe request is refused because the body was invalid JSON".
400ValidationErrorThe 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. ".
400InvalidLaunchConfigurationThe "imageRef" value is invalid or not active.
400InvalidLaunchConfigurationThe "flavorRef" value is invalid.
400InvalidLaunchConfigurationThe base64 encoding for the "path" argument in the "personality" parameter is invalid.
400InvalidLaunchConfigurationThe number of files in the "personality" parameter exceeds maximum limit.
400InvalidLaunchConfigurationThe content of the files in the "personality" parameter exceeds the maximum size limit allowed.
400InvalidLaunchConfigurationThe load balancer ID provided is invalid.
401InvalidCredentialsThe X-Auth-Token the user supplied is bad.
403ForbiddenThe 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.
404NoSuchScalingGroupErrorThe specified scaling group was not found.
405InvalidMethodThe method used is unavailable for the endpoint.
413RateLimitErrorThe user has surpassed their rate limit.
415UnsupportedMediaTypeThe request is refused because the content type of the request is not "application/json".
500InternalErrorAn error internal to the application has occurred, please file a bug report.
503ServiceUnavailableThe requested service is unavailable, please file a bug report. Request

This table shows the header parameters for the update launch configuration request:





A valid authentication token.

This table shows the URI parameters for the update launch configuration request:




A subscriber to the auto scaling service.



A scaling group.

This list shows the body parameters for the request:

  • args: Object. Optional.

    The configuration used to create new servers in the scaling group. You must specify server attribute, and can also specify the optional loadBalancers attribute. Most launch configurations have both a server and a load balancer configured.

    • loadBalancers: Array. Optional.

      Details about one or more load balancers to add new servers to. All servers will be added to these load balancers with the IP addresses of their ServiceNet network. All servers will be enabled and equally weighted. Any new servers that are not connected to the ServiceNet network will not be added to any load balancers.

      • port: Integer. Required.

        The port number of the service (on the new servers) to use for this particular load balancer. In most cases, this port number is 80. NOTE that when using RackConnectV3, instead of a cloud load balancer, leave this parameter empty.

      • loadBalancerId: String. Required.

        The ID of the cloud load balancer, or RackConnectV3 load balancer pool, to which new servers are added. For cloud load balancers set the ID as an integer, for RackConnectV3 set the UUID as a string. NOTE that when using RackConnectV3, this value is supplied to you by Rackspace Support after they configure your load balancer pool.

    • server: Object. Required.

      The attributes Auto Scale will use to create a new server. For more information, see: Create Servers in the cloud servers developer's guide. The attributes that are specified for the server entity will apply to all new servers in the scaling group. The configured server name is the base for created servers.

      • flavorRef: String. Required.

        The flavor of the server image. Specifies the flavor Id for the server. A flavor is a resource configuration for a server. For more information on available flavors, see the Server flavors section.

      • imageRef: String. Required.

        The ID of the cloud server image, from which new server images will be created.

      • personality: Array. Optional.

        The file path and/or the content that you want to inject into a server image. For more information, see the Server Personality documentation for Rackspace Cloud Servers.

        • path: String. Required.

          The path to the file that contains data that will be injected into the file system of the new cloud server image.

        • contents: String. Required.

          The content items that will be injected into the file system of the new cloud server image.


Example 4.10. Update launch configuration: JSON request



Contents Search
loading table of contents...