Documentation changes are given below for kn9fe-ec2 version 0.13.0.
The --aws-config-file
option allows users to reuse configuration settings from the AWS command line tools so that knife
can access EC2 resources.
The --spot-wait-mode
option allows knife to respond in different ways when the server create
subcommand is used to create a spot instance that is not immediately created when the subcommand is executed. Possible options are:
wait
-- waits indefinitely for the instance to be createdexit
-- exits if the instance is not yet created (it may be bootstrapped via theknife bootstrap
command at a later time).prompt
(default) -- interactively prompts the user for one of the above options.
The --create-ssl-listener
option is applicable only when creating a Windows instance. When specified, the subcommand will create a WinRM
listener on the new instance that uses the SSL transport, and will attempt to bootstrap the node using that listener. The default behavior is to use the SSL transport, the --no-create-ssl-listener
option can be used to override the default and instead use a less secure plaintext listener.
The --attach-network-interface
option allows the user to specify a list of network interfaces in the form ENI1,ENI2,...
as additional interfaces to attach to the instance when it is created.
The --classic-link-vpc-id
option allows the user to specify a VPC that is ClassicLink-enabled by specifying the VPC's ID as an argument. The created instance will be linked to that VPC.
The --classic-link-vpc-security-groups-ids
option allows the user to specify AWS security groups for the VPC specified with the --classic-link-vpc-id
option.
The --disable-api-termination
option allows the user to disable the termination of the instance using the Amazon EC2 console, CLI and API. However, this option won't work for spot instances
as termination protection
cannot be enabled for spot instances
.