You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Class: Aws::SSM::Types::CreateAssociationRequestWhen passing CreateAssociationRequest as input to an Aws::Client method, you can use a vanilla Hash:
{
name: "DocumentARN", document_version: "DocumentVersion",
instance_id: "InstanceId",
parameters: {
"ParameterName" => ["ParameterValue"],
},
targets: [
{
key: "TargetKey",
values: ["TargetValue"],
},
],
schedule_expression: "ScheduleExpression",
output_location: {
s3_location: {
output_s3_region: "S3Region",
output_s3_bucket_name: "S3BucketName",
output_s3_key_prefix: "S3KeyPrefix",
},
},
association_name: "AssociationName",
automation_target_parameter_name: "AutomationTargetParameterName",
max_errors: "MaxErrors",
max_concurrency: "MaxConcurrency",
compliance_severity: "CRITICAL", sync_compliance: "AUTO", apply_only_at_cron_interval: false,
}
Instance Attribute Summary collapse
By default, when you create a new associations, the system runs it immediately after it is created and then according to the schedule you specified.
Specify a descriptive name for the association.
Specify the target for the association.
The severity level to assign to the association.
The document version you want to associate with the target(s).
The instance ID.
The maximum number of targets allowed to run the association at the same time.
The number of errors that are allowed before the system stops sending requests to run the association on additional targets.
The name of the SSM document that contains the configuration information for the instance.
An S3 bucket where you want to store the output details of the request.
The parameters for the runtime configuration of the document.
A cron expression when the association will be applied to the target(s).
The mode for generating association compliance.
The targets for the association.
By default, when you create a new associations, the system runs it immediately after it is created and then according to the schedule you specified. Specify this option if you don\'t want an association to run immediately after you create it.
#association_name ⇒ StringSpecify a descriptive name for the association.
#automation_target_parameter_name ⇒ StringSpecify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
#compliance_severity ⇒ StringThe severity level to assign to the association.
Possible values:
The document version you want to associate with the target(s). Can be a specific version or the default version.
#instance_id ⇒ StringThe instance ID.
InstanceId
has been deprecated. To specify an instance ID for an association, use the Targets
parameter. Requests that include the parameter InstanceID
with SSM documents that use schema version 2.0 or later will fail. In addition, if you use the parameter InstanceId
, you cannot use the parameters AssociationName
, DocumentVersion
, MaxErrors
, MaxConcurrency
, OutputLocation
, or ScheduleExpression
. To use these parameters, you must use the Targets
parameter.
The maximum number of targets allowed to run the association at the same time. You can specify a number, for example 10, or a percentage of the target set, for example 10%. The default value is 100%, which means all targets run the association at the same time.
If a new instance starts and attempts to run an association while Systems Manager is running MaxConcurrency associations, the association is allowed to run. During the next association interval, the new instance will process its association within the limit specified for MaxConcurrency.
#max_errors ⇒ StringThe number of errors that are allowed before the system stops sending requests to run the association on additional targets. You can specify either an absolute number of errors, for example 10, or a percentage of the target set, for example 10%. If you specify 3, for example, the system stops sending requests when the fourth error is received. If you specify 0, then the system stops sending requests after the first error is returned. If you run an association on 50 instances and set MaxError to 10%, then the system stops sending the request when the sixth error is received.
Executions that are already running an association when MaxErrors is reached are allowed to complete, but some of these executions may fail as well. If you need to ensure that there won\'t be more than max-errors failed executions, set MaxConcurrency to 1 so that executions proceed one at a time.
#name ⇒ StringThe name of the SSM document that contains the configuration information for the instance. You can specify Command or Automation documents.
You can specify AWS-predefined documents, documents you created, or a document that is shared with you from another account.
For SSM documents that are shared with you from other AWS accounts, you must specify the complete SSM document ARN, in the following format:
arn:partition:ssm:region:account-id:document/document-name
For example:
arn:aws:ssm:us-east-2:12345678912:document/My-Shared-Document
For AWS-predefined documents and SSM documents you created in your account, you only need to specify the document name. For example, AWS-ApplyPatchBaseline
or My-Document
.
The parameters for the runtime configuration of the document.
#schedule_expression ⇒ StringA cron expression when the association will be applied to the target(s).
#sync_compliance ⇒ StringThe mode for generating association compliance. You can specify AUTO
or MANUAL
. In AUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association is COMPLIANT
. If the association execution doesn\'t run successfully, the association is NON-COMPLIANT
.
In MANUAL
mode, you must specify the AssociationId
as a parameter for the PutComplianceItems API action. In this case, compliance data is not managed by State Manager. It is managed by your direct call to the PutComplianceItems API action.
By default, all associations use AUTO
mode.
Possible values:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4