GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Paws::OpsWorks::UpdateStack(3) User Contributed Perl Documentation Paws::OpsWorks::UpdateStack(3)

Paws::OpsWorks::UpdateStack - Arguments for method UpdateStack on Paws::OpsWorks

This class represents the parameters used for calling the method UpdateStack on the AWS OpsWorks service. Use the attributes of this class as arguments to method UpdateStack.

You shouln't make instances of this class. Each attribute should be used as a named argument in the call to UpdateStack.

As an example:

  $service_obj->UpdateStack(Att1 => $value1, Att2 => $value2, ...);

Values for attributes that are native types (Int, String, Float, etc) can passed as-is (scalar values). Values for complex Types (objects) can be passed as a HashRef. The keys and values of the hashref will be used to instance the underlying object.

The default AWS OpsWorks agent version. You have the following options:
  • Auto-update - Set this parameter to "LATEST". AWS OpsWorks automatically installs new agent versions on the stack's instances as soon as they are available.
  • Fixed version - Set this parameter to your preferred agent version. To update the agent version, you must edit the stack configuration and specify a new version. AWS OpsWorks then automatically installs that version on the stack's instances.

The default setting is "LATEST". To specify an agent version, you must use the complete version number, not the abbreviated number shown on the console. For a list of available agent version numbers, call DescribeAgentVersions.

You can also specify an agent version when you create or update an instance, which overrides the stack's default setting.

One or more user-defined key-value pairs to be added to the stack attributes.

A "ChefConfiguration" object that specifies whether to enable Berkshelf and the Berkshelf version on Chef 11.10 stacks. For more information, see Create a New Stack.

The configuration manager. When you clone a stack, we recommend that you use the configuration manager to specify the Chef version: 0.9, 11.4, or 11.10. The default value is currently 11.4.

A string that contains user-defined, custom JSON. It can be used to override the corresponding default stack configuration JSON values or to pass data to recipes. The string should be in the following format and escape characters such as '"':

"{\"key1\": \"value1\", \"key2\": \"value2\",...}"

For more information on custom JSON, see Use Custom JSON to Modify the Stack Configuration Attributes.

The stack's default Availability Zone, which must be in the stack's region. For more information, see Regions and Endpoints. If you also specify a value for "DefaultSubnetId", the subnet must be in the same zone. For more information, see CreateStack.

The ARN of an IAM profile that is the default profile for all of the stack's EC2 instances. For more information about IAM ARNs, see Using Identifiers.

The stack's operating system, which must be set to one of the following:
  • A supported Linux operating system: An Amazon Linux version, such as "Amazon Linux 2015.03", "Red Hat Enterprise Linux 7", "Ubuntu 12.04 LTS", or "Ubuntu 14.04 LTS".
  • "Microsoft Windows Server 2012 R2 Base".
  • A custom AMI: "Custom". You specify the custom AMI you want to use when you create instances. For more information on how to use custom AMIs with OpsWorks, see Using Custom AMIs.

The default option is the stack's current operating system. For more information on the supported operating systems, see AWS OpsWorks Operating Systems.

The default root device type. This value is used by default for all instances in the stack, but you can override it when you create an instance. For more information, see Storage for the Root Device.

A default Amazon EC2 key-pair name. The default value is "none". If you specify a key-pair name, AWS OpsWorks installs the public key on the instance and you can use the private key with an SSH client to log in to the instance. For more information, see Using SSH to Communicate with an Instance and Managing SSH Access. You can override this setting by specifying a different key pair, or no key pair, when you create an instance.

The stack's default VPC subnet ID. This parameter is required if you specify a value for the "VpcId" parameter. All instances are launched into this subnet unless you specify otherwise when you create the instance. If you also specify a value for "DefaultAvailabilityZone", the subnet must be in that zone. For information on default values and when this parameter is required, see the "VpcId" parameter description.

The stack's new host name theme, with spaces replaced by underscores. The theme is used to generate host names for the stack's instances. By default, "HostnameTheme" is set to "Layer_Dependent", which creates host names by appending integers to the layer's short name. The other themes are:
  • "Baked_Goods"
  • "Clouds"
  • "Europe_Cities"
  • "Fruits"
  • "Greek_Deities"
  • "Legendary_creatures_from_Japan"
  • "Planets_and_Moons"
  • "Roman_Deities"
  • "Scottish_Islands"
  • "US_Cities"
  • "Wild_Cats"

To obtain a generated host name, call "GetHostNameSuggestion", which returns a host name based on the current theme.

The stack's new name.

Do not use this parameter. You cannot update a stack's service role.

The stack ID.

Whether the stack uses custom cookbooks.

Whether to associate the AWS OpsWorks built-in security groups with the stack's layers.

AWS OpsWorks provides a standard set of built-in security groups, one for each layer, which are associated with layers by default. "UseOpsworksSecurityGroups" allows you to provide your own custom security groups instead of using the built-in groups. "UseOpsworksSecurityGroups" has the following settings:

  • True - AWS OpsWorks automatically associates the appropriate built-in security group with each layer (default setting). You can associate additional security groups with a layer after you create it, but you cannot delete the built-in security group.
  • False - AWS OpsWorks does not associate built-in security groups with layers. You must create appropriate EC2 security groups and associate a security group with each layer that you create. However, you can still manually associate a built-in security group with a layer on. Custom security groups are required only for those layers that need custom settings.

For more information, see Create a New Stack.

This class forms part of Paws, documenting arguments for method UpdateStack in Paws::OpsWorks

The source code is located here: https://github.com/pplu/aws-sdk-perl

Please report bugs to: https://github.com/pplu/aws-sdk-perl/issues

2015-08-06 perl v5.32.1

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.