mirror of
https://github.com/rclone/rclone.git
synced 2024-12-13 10:45:16 +01:00
76 lines
3.3 KiB
Go
76 lines
3.3 KiB
Go
// Code generated by private/model/cli/gen-api/main.go. DO NOT EDIT.
|
|
|
|
// Package opsworkscm provides the client and types for making API
|
|
// requests to AWS OpsWorks for Chef Automate.
|
|
//
|
|
// AWS OpsWorks for Chef Automate is a service that runs and manages configuration
|
|
// management servers.
|
|
//
|
|
// Glossary of terms
|
|
//
|
|
// * Server: A configuration management server that can be highly-available.
|
|
// The configuration manager runs on your instances by using various AWS
|
|
// services, such as Amazon Elastic Compute Cloud (EC2), and potentially
|
|
// Amazon Relational Database Service (RDS). A server is a generic abstraction
|
|
// over the configuration manager that you want to use, much like Amazon
|
|
// RDS. In AWS OpsWorks for Chef Automate, you do not start or stop servers.
|
|
// After you create servers, they continue to run until they are deleted.
|
|
//
|
|
// * Engine: The specific configuration manager that you want to use (such
|
|
// as Chef) is the engine.
|
|
//
|
|
// * Backup: This is an application-level backup of the data that the configuration
|
|
// manager stores. A backup creates a .tar.gz file that is stored in an Amazon
|
|
// Simple Storage Service (S3) bucket in your account. AWS OpsWorks for Chef
|
|
// Automate creates the S3 bucket when you launch the first instance. A backup
|
|
// maintains a snapshot of all of a server's important attributes at the
|
|
// time of the backup.
|
|
//
|
|
// * Events: Events are always related to a server. Events are written during
|
|
// server creation, when health checks run, when backups are created, etc.
|
|
// When you delete a server, the server's events are also deleted.
|
|
//
|
|
// * AccountAttributes: Every account has attributes that are assigned in
|
|
// the AWS OpsWorks for Chef Automate database. These attributes store information
|
|
// about configuration limits (servers, backups, etc.) and your customer
|
|
// account.
|
|
//
|
|
// Endpoints
|
|
//
|
|
// AWS OpsWorks for Chef Automate supports the following endpoints, all HTTPS.
|
|
// You must connect to one of the following endpoints. Chef 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-west-2.amazonaws.com
|
|
//
|
|
// * opsworks-cm.eu-west-1.amazonaws.com
|
|
//
|
|
// Throttling limits
|
|
//
|
|
// All API operations allow for five requests per second with a burst of 10
|
|
// requests per second.
|
|
//
|
|
// See https://docs.aws.amazon.com/goto/WebAPI/opsworkscm-2016-11-01 for more information on this service.
|
|
//
|
|
// See opsworkscm package documentation for more information.
|
|
// https://docs.aws.amazon.com/sdk-for-go/api/service/opsworkscm/
|
|
//
|
|
// Using the Client
|
|
//
|
|
// To AWS OpsWorks for Chef Automate with the SDK use the New function to create
|
|
// a new service client. With that client you can make API requests to the service.
|
|
// These clients are safe to use concurrently.
|
|
//
|
|
// See the SDK's documentation for more information on how to use the SDK.
|
|
// https://docs.aws.amazon.com/sdk-for-go/api/
|
|
//
|
|
// See aws.Config documentation for more information on configuring SDK clients.
|
|
// https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config
|
|
//
|
|
// See the AWS OpsWorks for Chef Automate client OpsWorksCM for more
|
|
// information on creating client for this service.
|
|
// https://docs.aws.amazon.com/sdk-for-go/api/service/opsworkscm/#New
|
|
package opsworkscm
|