aws opsworks create-layer
Creates a layer. For more information, see How to Create a Layer. You should use CreateLayer for noncustom layer types such as PHP App Server only if the stack does not have an existing layer of that type. A stack can have at most one instance of each noncustom layer; if you attempt to create a second instance, CreateLayer fails. A stack can have an arbitrary number of custom layers, so you can call CreateLayer as many times as you like for that layer type. Required Permissions: To use this action, an IAM user must have a Manage permissions level for the stack, or an attached policy that explicitly grants permissions. For more information on user permissions, see Managing User Permissions
Options
| Name | Description |
|---|---|
--stack-id <string> | The layer stack ID |
--type <string> | The layer type. A stack cannot have more than one built-in layer of the same type. It can have any number of custom layers. Built-in layers are not available in Chef 12 stacks |
--name <string> | The layer name, which is used by the console |
--shortname <string> | For custom layers only, use this parameter to specify the layer's short name, which is used internally by AWS OpsWorks Stacks and by Chef recipes. The short name is also used as the name for the directory where your app files are installed. It can have a maximum of 200 characters, which are limited to the alphanumeric characters, '-', '_', and '.'. The built-in layers' short names are defined by AWS OpsWorks Stacks. For more information, see the Layer Reference |
--attributes <map> | One or more user-defined key-value pairs to be added to the stack attributes. To create a cluster layer, set the EcsClusterArn attribute to the cluster's ARN |
--cloud-watch-logs-configuration <structure> | Specifies CloudWatch Logs configuration options for the layer. For more information, see CloudWatchLogsLogStream |
--custom-instance-profile-arn <string> | The ARN of an IAM profile to be used for the layer's EC2 instances. For more information about IAM ARNs, see Using Identifiers |
--custom-json <string> | A JSON-formatted string containing custom stack configuration and deployment attributes to be installed on the layer's instances. For more information, see Using Custom JSON. This feature is supported as of version 1.7.42 of the AWS CLI |
--custom-security-group-ids <list> | An array containing the layer custom security group IDs |
--packages <list> | An array of Package objects that describes the layer packages |
--volume-configurations <list> | A VolumeConfigurations object that describes the layer's Amazon EBS volumes |
--enable-auto-healing | Whether to disable auto healing for the layer |
--no-enable-auto-healing | Whether to disable auto healing for the layer |
--auto-assign-elastic-ips | Whether to automatically assign an Elastic IP address to the layer's instances. For more information, see How to Edit a Layer |
--no-auto-assign-elastic-ips | Whether to automatically assign an Elastic IP address to the layer's instances. For more information, see How to Edit a Layer |
--auto-assign-public-ips | For stacks that are running in a VPC, whether to automatically assign a public IP address to the layer's instances. For more information, see How to Edit a Layer |
--no-auto-assign-public-ips | For stacks that are running in a VPC, whether to automatically assign a public IP address to the layer's instances. For more information, see How to Edit a Layer |
--custom-recipes <structure> | A LayerCustomRecipes object that specifies the layer custom recipes |
--install-updates-on-boot | Whether to install operating system and package updates when the instance boots. The default value is true. To control when updates are installed, set this value to false. You must then update your instances manually by using CreateDeployment to run the update_dependencies stack command or by manually running yum (Amazon Linux) or apt-get (Ubuntu) on the instances. To ensure that your instances have the latest security updates, we strongly recommend using the default value of true |
--no-install-updates-on-boot | Whether to install operating system and package updates when the instance boots. The default value is true. To control when updates are installed, set this value to false. You must then update your instances manually by using CreateDeployment to run the update_dependencies stack command or by manually running yum (Amazon Linux) or apt-get (Ubuntu) on the instances. To ensure that your instances have the latest security updates, we strongly recommend using the default value of true |
--use-ebs-optimized-instances | Whether to use Amazon EBS-optimized instances |
--no-use-ebs-optimized-instances | Whether to use Amazon EBS-optimized instances |
--lifecycle-event-configuration <structure> | A LifeCycleEventConfiguration object that you can use to configure the Shutdown event to specify an execution timeout and enable or disable Elastic Load Balancer connection draining |
--cli-input-json <string> | Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally |
--generate-cli-skeleton <string> | Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command |