Creates and immedately starts a new server. The server is ready to use
when it is in the HEALTHY state. By default, you can create a maximum
of 10 servers.
opsworkscm_create_server(AssociatePublicIpAddress, CustomDomain,
CustomCertificate, CustomPrivateKey, DisableAutomatedBackup, Engine,
EngineModel, EngineVersion, EngineAttributes, BackupRetentionCount,
ServerName, InstanceProfileArn, InstanceType, KeyPair,
PreferredMaintenanceWindow, PreferredBackupWindow, SecurityGroupIds,
ServiceRoleArn, SubnetIds, Tags, BackupId)Associate a public IP address with a server that you are launching.
Valid values are true or false. The default value is true.
Supported on servers running Chef Automate 2. An optional public
endpoint of a server, such as https://aws.my-company.com. To access
the server, create a CNAME DNS record in your preferred DNS service that
points the custom domain to the endpoint that is generated when the
server is created (the value of the CreateServer Endpoint attribute).
You cannot access the server by using the generated Endpoint value if
the server is using a custom domain. If you specify a custom domain, you
must also specify values for CustomCertificate and CustomPrivateKey.
Supported on servers running Chef Automate 2. A PEM-formatted HTTPS
certificate. The value can be be a single, self-signed certificate, or a
certificate chain. If you specify a custom certificate, you must also
specify values for CustomDomain and CustomPrivateKey. The following
are requirements for the CustomCertificate value:
You can provide either a self-signed, custom certificate, or the full certificate chain.
The certificate must be a valid X509 certificate, or a certificate chain in PEM format.
The certificate must be valid at the time of upload. A certificate
can\'t be used before its validity period begins (the certificate\'s
NotBefore date), or after it expires (the certificate\'s
NotAfter date).
The certificate's common name or subject alternative names (SANs),
if present, must match the value of CustomDomain.
The certificate must match the value of CustomPrivateKey.
Supported on servers running Chef Automate 2. A private key in PEM
format for connecting to the server by using HTTPS. The private key must
not be encrypted; it cannot be protected by a password or passphrase. If
you specify a custom private key, you must also specify values for
CustomDomain and CustomCertificate.
Enable or disable scheduled backups. Valid values are true or false.
The default value is true.
The configuration management engine to use. Valid values include
ChefAutomate and Puppet.
The engine model of the server. Valid values in this release include
Monolithic for Puppet and Single for Chef.
The major release version of the engine that you want to use. For a Chef
server, the valid value for EngineVersion is currently 12. For a
Puppet server, the valid value is 2017.
Optional engine attributes on a specified server.
Attributes accepted in a Chef createServer request:
CHEF_AUTOMATE_PIVOTAL_KEY: A base64-encoded RSA public key. The
corresponding private key is required to access the Chef API. When
no CHEF\_AUTOMATE\_PIVOTAL\_KEY is set, a private key is generated
and returned in the response.
CHEF_AUTOMATE_ADMIN_PASSWORD: The password for the administrative
user in the Chef Automate web-based dashboard. The password length
is a minimum of eight characters, and a maximum of 32. The password
can contain letters, numbers, and special characters
(!/@\#\$%\^&+=\_). The password must contain at least one lower case
letter, one upper case letter, one number, and one special
character. When no CHEF\_AUTOMATE\_ADMIN\_PASSWORD is set, one is
generated and returned in the response.
Attributes accepted in a Puppet createServer request:
PUPPET_ADMIN_PASSWORD: To work with the Puppet Enterprise console,
a password must use ASCII characters.
PUPPET_R10K_REMOTE: The r10k remote is the URL of your control
repository (for example,
ssh://git\@your.git-repo.com:user/control-repo.git). Specifying an
r10k remote opens TCP port 8170.
PUPPET_R10K_PRIVATE_KEY: If you are using a private Git
repository, add PUPPET\_R10K\_PRIVATE\_KEY to specify a PEM-encoded
private SSH key.
The number of automated backups that you want to keep. Whenever a new
backup is created, AWS OpsWorks CM deletes the oldest backups if this
number is exceeded. The default value is 1.
[required] The name of the server. The server name must be unique within your AWS account, within each region. Server names must start with a letter; then letters, numbers, or hyphens (-) are allowed, up to a maximum of 40 characters.
[required] The ARN of the instance profile that your Amazon EC2 instances use. Although the AWS OpsWorks console typically creates the instance profile for you, if you are using API commands instead, run the service-role-creation.yaml AWS CloudFormation template, located at https://s3.amazonaws.com/opsworks-cm-us-east-1-prod-default-assets/misc/opsworks-cm-roles.yaml. This template creates a CloudFormation stack that includes the instance profile you need.
[required] The Amazon EC2 instance type to use. For example, m5.large.
The Amazon EC2 key pair to set for the instance. This parameter is optional; if desired, you may specify this parameter to connect to your instances by using SSH.
The start time for a one-hour period each week during which AWS OpsWorks
CM performs maintenance on the instance. Valid values must be specified
in the following format: DDD:HH:MM. The specified time is in
coordinated universal time (UTC). The default value is a random one-hour
period on Tuesday, Wednesday, or Friday. See TimeWindowDefinition for
more information.
Example: Mon:08:00, which represents a start time of every Monday
at 08:00 UTC. (8:00 a.m.)
The start time for a one-hour period during which AWS OpsWorks CM backs up application-level data on your server if automated backups are enabled. Valid values must be specified in one of the following formats:
HH:MM for daily backups
DDD:HH:MM for weekly backups
The specified time is in coordinated universal time (UTC). The default value is a random, daily start time.
Example: 08:00, which represents a daily start time of 08:00 UTC.
Example: Mon:08:00, which represents a start time of every Monday
at 08:00 UTC. (8:00 a.m.)
A list of security group IDs to attach to the Amazon EC2 instance. If
you add this parameter, the specified security groups must be within the
VPC that is specified by SubnetIds.
If you do not specify this parameter, AWS OpsWorks CM creates one new security group that uses TCP ports 22 and 443, open to 0.0.0.0/0 (everyone).
[required] The service role that the AWS OpsWorks CM service backend uses to work with your account. Although the AWS OpsWorks management console typically creates the service role for you, if you are using the AWS CLI or API commands, run the service-role-creation.yaml AWS CloudFormation template, located at https://s3.amazonaws.com/opsworks-cm-us-east-1-prod-default-assets/misc/opsworks-cm-roles.yaml. This template creates a CloudFormation stack that includes the service role and instance profile that you need.
The IDs of subnets in which to launch the server EC2 instance.
Amazon EC2-Classic customers: This field is required. All servers must run within a VPC. The VPC must have \"Auto Assign Public IP\" enabled.
EC2-VPC customers: This field is optional. If you do not specify subnet IDs, your EC2 instances are created in a default subnet that is selected by Amazon EC2. If you specify subnet IDs, the VPC must have \"Auto Assign Public IP\" enabled.
For more information about supported Amazon EC2 platforms, see Supported Platforms.
A map that contains tag keys and tag values to attach to an AWS OpsWorks for Chef Automate or AWS OpsWorks for Puppet Enterprise server.
The key cannot be empty.
The key can be a maximum of 127 characters, and can contain only
Unicode letters, numbers, or separators, or the following special
characters: + - = . _ : /
The value can be a maximum 255 characters, and contain only Unicode
letters, numbers, or separators, or the following special
characters: + - = . _ : /
Leading and trailing white spaces are trimmed from both the key and value.
A maximum of 50 user-applied tags is allowed for any AWS OpsWorks-CM server.
If you specify this field, AWS OpsWorks CM creates the server by using the backup represented by BackupId.
svc$create_server(
AssociatePublicIpAddress = TRUE|FALSE,
CustomDomain = "string",
CustomCertificate = "string",
CustomPrivateKey = "string",
DisableAutomatedBackup = TRUE|FALSE,
Engine = "string",
EngineModel = "string",
EngineVersion = "string",
EngineAttributes = list(
list(
Name = "string",
Value = "string"
)
),
BackupRetentionCount = 123,
ServerName = "string",
InstanceProfileArn = "string",
InstanceType = "string",
KeyPair = "string",
PreferredMaintenanceWindow = "string",
PreferredBackupWindow = "string",
SecurityGroupIds = list(
"string"
),
ServiceRoleArn = "string",
SubnetIds = list(
"string"
),
Tags = list(
list(
Key = "string",
Value = "string"
)
),
BackupId = "string"
)
This operation is asynchronous.
A LimitExceededException is thrown when you have created the maximum
number of servers (10). A ResourceAlreadyExistsException is thrown
when a server with the same name already exists in the account. A
ResourceNotFoundException is thrown when you specify a backup ID that
is not valid or is for a backup that does not exist. A
ValidationException is thrown when parameters of the request are not
valid.
If you do not specify a security group by adding the SecurityGroupIds
parameter, AWS OpsWorks creates a new security group.
Chef Automate: The default security group opens the Chef server to the world on TCP port 443. If a KeyName is present, AWS OpsWorks enables SSH access. SSH is also open to the world on TCP port 22.
Puppet Enterprise: The default security group opens TCP ports 22, 443, 4433, 8140, 8142, 8143, and 8170. If a KeyName is present, AWS OpsWorks enables SSH access. SSH is also open to the world on TCP port 22.
By default, your server is accessible from any IP address. We recommend that you update your security group rules to allow access from known IP addresses and address ranges only. To edit security group rules, open Security Groups in the navigation pane of the EC2 management console.
To specify your own domain for a server, and provide your own
self-signed or CA-signed certificate and private key, specify values for
CustomDomain, CustomCertificate, and CustomPrivateKey.