aws_ops_works_chef_automate

AWS OpsWorks CM

AWS OpsWorks for configuration management (CM) is a service that runs and manages configuration management servers. You can use AWS OpsWorks CM to create and manage AWS OpsWorks for Chef Automate and AWS OpsWorks for Puppet Enterprise servers, and add or remove nodes for the servers to manage.

Glossary of terms

• Server: A configuration management server that can be highly-available. The configuration management server runs on an Amazon Elastic Compute Cloud (EC2) instance, and may use various other AWS services, such as Amazon Relational Database Service (RDS) and Elastic Load Balancing. A server is a generic abstraction over the configuration manager that you want to use, much like Amazon RDS. In AWS OpsWorks CM, you do not start or stop servers. After you create servers, they continue to run until they are deleted.

• Engine: The engine is the specific configuration manager that you want to use. Valid values in this release include ChefAutomate and Puppet.

• Backup: This is an application-level backup of the data that the configuration manager stores. AWS OpsWorks CM creates an S3 bucket for backups when you launch the first server. A backup maintains a snapshot of a server's configuration-related attributes at the time the backup starts.

• Events: Events are always related to a server. Events are written during server creation, when health checks run, when backups are created, when system maintenance is performed, etc. When you delete a server, the server's events are also deleted.

• Account attributes: Every account has attributes that are assigned in the AWS OpsWorks CM database. These attributes store information about configuration limits (servers, backups, etc.) and your customer account.

Endpoints

AWS OpsWorks CM supports the following endpoints, all HTTPS. You must connect to one of the following endpoints. Your servers can only be accessed or managed within the endpoint in which they are created.

• opsworks-cm.us-east-1.amazonaws.com

• opsworks-cm.us-east-2.amazonaws.com

• opsworks-cm.us-west-1.amazonaws.com

• opsworks-cm.us-west-2.amazonaws.com

• opsworks-cm.ap-northeast-1.amazonaws.com

• opsworks-cm.ap-southeast-1.amazonaws.com

• opsworks-cm.ap-southeast-2.amazonaws.com

• opsworks-cm.eu-central-1.amazonaws.com

• opsworks-cm.eu-west-1.amazonaws.com

For more information, see AWS OpsWorks endpoints and quotas in the AWS General Reference.

Throttling limits

Summary

Functions

• associate_node(Client, Input)
  Associates a new node with the server.
• associate_node(Client, Input, Options)
• create_backup(Client, Input)
  Creates an application-level backup of a server.
• create_backup(Client, Input, Options)
• create_server(Client, Input)
  Creates and immedately starts a new server.
• create_server(Client, Input, Options)
• delete_backup(Client, Input)
  Deletes a backup.
• delete_backup(Client, Input, Options)
• delete_server(Client, Input)
  Deletes the server and the underlying AWS CloudFormation stacks (including the server's EC2 instance).
• delete_server(Client, Input, Options)
• describe_account_attributes(Client, Input)
  Describes your OpsWorks-CM account attributes.
• describe_account_attributes(Client, Input, Options)
• describe_backups(Client, Input)
  Describes backups.
• describe_backups(Client, Input, Options)
• describe_events(Client, Input)
  Describes events for a specified server.
• describe_events(Client, Input, Options)
• describe_node_association_status(Client, Input)
  Returns the current status of an existing association or disassociation request.
• describe_node_association_status(Client, Input, Options)
• describe_servers(Client, Input)
  Lists all configuration management servers that are identified with your account.
• describe_servers(Client, Input, Options)
• disassociate_node(Client, Input)
  Disassociates a node from an AWS OpsWorks CM server, and removes the node from the server's managed nodes.
• disassociate_node(Client, Input, Options)
• export_server_engine_attribute(Client, Input)
  Exports a specified server engine attribute as a base64-encoded string.
• export_server_engine_attribute(Client, Input, Options)
• list_tags_for_resource(Client, Input)
  Returns a list of tags that are applied to the specified AWS OpsWorks for Chef Automate or AWS OpsWorks for Puppet Enterprise servers or backups.
• list_tags_for_resource(Client, Input, Options)
• restore_server(Client, Input)
  Restores a backup to a server that is in a CONNECTION_LOST, HEALTHY, RUNNING, UNHEALTHY, or TERMINATED state.
• restore_server(Client, Input, Options)
• start_maintenance(Client, Input)
  Manually starts server maintenance.
• start_maintenance(Client, Input, Options)
• tag_resource(Client, Input)
  Applies tags to an AWS OpsWorks for Chef Automate or AWS OpsWorks for Puppet Enterprise server, or to server backups.
• tag_resource(Client, Input, Options)
• untag_resource(Client, Input)
  Removes specified tags from an AWS OpsWorks-CM server or backup.
• untag_resource(Client, Input, Options)
• update_server(Client, Input)
  Updates settings for a server.
• update_server(Client, Input, Options)
• update_server_engine_attributes(Client, Input)
  Updates engine-specific attributes on a specified server.
• update_server_engine_attributes(Client, Input, Options)

Functions

Associates a new node with the server. For more information about how to disassociate a node, see DisassociateNode.

On a Chef server: This command is an alternative to knife bootstrap.

Example (Chef): aws opsworks-cm associate-node --server-name MyServer --node-name MyManagedNode --engine-attributes "Name=CHEF_ORGANIZATION,Value=default" "Name=CHEF_NODE_PUBLIC_KEY,Value=public-key-pem"

On a Puppet server, this command is an alternative to the puppet cert sign command that signs a Puppet node CSR.

Example (Puppet): aws opsworks-cm associate-node --server-name MyServer --node-name MyManagedNode --engine-attributes "Name=PUPPET_NODE_CSR,Value=csr-pem"

Creates an application-level backup of a server. While the server is in the BACKING_UP state, the server cannot be changed, and no additional backup can be created.

Backups can be created for servers in RUNNING, HEALTHY, and UNHEALTHY states. By default, you can create a maximum of 50 manual backups.

This operation is asynchronous.

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.

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.

Deletes a backup. You can delete both manual and automated backups. This operation is asynchronous.

Deletes the server and the underlying AWS CloudFormation stacks (including the server's EC2 instance). When you run this command, the server state is updated to DELETING. After the server is deleted, it is no longer returned by DescribeServer requests. If the AWS CloudFormation stack cannot be deleted, the server cannot be deleted.

This operation is asynchronous.

Describes your OpsWorks-CM account attributes.

Describes backups. The results are ordered by time, with newest backups first. If you do not specify a BackupId or ServerName, the command returns all backups.

This operation is synchronous.

Describes events for a specified server. Results are ordered by time, with newest events first.

This operation is synchronous.

Returns the current status of an existing association or disassociation request.

Lists all configuration management servers that are identified with your account. Only the stored results from Amazon DynamoDB are returned. AWS OpsWorks CM does not query other services.

This operation is synchronous.

Disassociates a node from an AWS OpsWorks CM server, and removes the node from the server's managed nodes. After a node is disassociated, the node key pair is no longer valid for accessing the configuration manager's API. For more information about how to associate a node, see AssociateNode.

Exports a specified server engine attribute as a base64-encoded string. For example, you can export user data that you can use in EC2 to associate nodes with a server.

This operation is synchronous.

Returns a list of tags that are applied to the specified AWS OpsWorks for Chef Automate or AWS OpsWorks for Puppet Enterprise servers or backups.

Restores a backup to a server that is in a CONNECTION_LOST, HEALTHY, RUNNING, UNHEALTHY, or TERMINATED state. When you run RestoreServer, the server's EC2 instance is deleted, and a new EC2 instance is configured. RestoreServer maintains the existing server endpoint, so configuration management of the server's client devices (nodes) should continue to work.

Restoring from a backup is performed by creating a new EC2 instance. If restoration is successful, and the server is in a HEALTHY state, AWS OpsWorks CM switches traffic over to the new instance. After restoration is finished, the old EC2 instance is maintained in a Running or Stopped state, but is eventually terminated.

This operation is asynchronous.

Manually starts server maintenance. This command can be useful if an earlier maintenance attempt failed, and the underlying cause of maintenance failure has been resolved. The server is in an UNDER_MAINTENANCE state while maintenance is in progress.

Applies tags to an AWS OpsWorks for Chef Automate or AWS OpsWorks for Puppet Enterprise server, or to server backups.

Removes specified tags from an AWS OpsWorks-CM server or backup.

Updates settings for a server.

Updates engine-specific attributes on a specified server. The server enters the MODIFYING state when this operation is in progress. Only one update can occur at a time. You can use this command to reset a Chef server's public key (CHEF_PIVOTAL_KEY) or a Puppet server's admin password (PUPPET_ADMIN_PASSWORD).

This operation is asynchronous.