AWS SDK for C++
1.8.152
AWS SDK for C++
|
#include <UpdateAssociationRequest.h>
Additional Inherited Members | |
![]() | |
virtual void | DumpBodyToUrl (Aws::Http::URI &uri) const |
Definition at line 28 of file UpdateAssociationRequest.h.
Aws::SSM::Model::UpdateAssociationRequest::UpdateAssociationRequest | ( | ) |
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 153 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 139 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 146 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 132 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 160 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 167 of file UpdateAssociationRequest.h.
|
inline |
A location is a combination of AWS Regions and AWS accounts where you want to run the association. Use this action to update an association in multiple Regions and multiple accounts.
Definition at line 1072 of file UpdateAssociationRequest.h.
|
inline |
A location is a combination of AWS Regions and AWS accounts where you want to run the association. Use this action to update an association in multiple Regions and multiple accounts.
Definition at line 1079 of file UpdateAssociationRequest.h.
|
inline |
The targets of the association.
Definition at line 453 of file UpdateAssociationRequest.h.
|
inline |
The targets of the association.
Definition at line 458 of file UpdateAssociationRequest.h.
|
inline |
By default, when you update an association, the system runs it immediately after it is updated and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you update it. This parameter is not supported for rate expressions.
Also, if you specified this option when you created the association, you can reset it. To do so, specify the no-apply-only-at-cron-interval
parameter when you update the association from the command line. This parameter forces the association to run immediately after updating it and according to the interval specified.
Definition at line 996 of file UpdateAssociationRequest.h.
|
inline |
The ID of the association you want to update.
Definition at line 52 of file UpdateAssociationRequest.h.
|
inline |
The name of the association that you want to update.
Definition at line 469 of file UpdateAssociationRequest.h.
|
inline |
This parameter is provided for concurrency control purposes. You must specify the latest association version in the service. If you want to ensure that this request succeeds, either specify $LATEST
, or omit this parameter.
Definition at line 516 of file UpdateAssociationRequest.h.
|
inline |
Specify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
Definition at line 579 of file UpdateAssociationRequest.h.
|
inline |
The severity level to assign to the association.
Definition at line 858 of file UpdateAssociationRequest.h.
|
inline |
The document version you want update for the association.
Definition at line 178 of file UpdateAssociationRequest.h.
|
inline |
By default, when you update an association, the system runs it immediately after it is updated and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you update it. This parameter is not supported for rate expressions.
Also, if you specified this option when you created the association, you can reset it. To do so, specify the no-apply-only-at-cron-interval
parameter when you update the association from the command line. This parameter forces the association to run immediately after updating it and according to the interval specified.
Definition at line 983 of file UpdateAssociationRequest.h.
|
inline |
The ID of the association you want to update.
Definition at line 47 of file UpdateAssociationRequest.h.
|
inline |
The name of the association that you want to update.
Definition at line 464 of file UpdateAssociationRequest.h.
|
inline |
This parameter is provided for concurrency control purposes. You must specify the latest association version in the service. If you want to ensure that this request succeeds, either specify $LATEST
, or omit this parameter.
Definition at line 508 of file UpdateAssociationRequest.h.
|
inline |
Specify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
Definition at line 572 of file UpdateAssociationRequest.h.
|
inline |
The severity level to assign to the association.
Definition at line 853 of file UpdateAssociationRequest.h.
|
inline |
The document version you want update for the association.
Definition at line 173 of file UpdateAssociationRequest.h.
|
inline |
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.
Definition at line 763 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 638 of file UpdateAssociationRequest.h.
|
inline |
The 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:aws: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
.
Definition at line 305 of file UpdateAssociationRequest.h.
|
inline |
An S3 bucket where you want to store the results of this request.
Definition at line 263 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 90 of file UpdateAssociationRequest.h.
|
overridevirtual |
Reimplemented from Aws::SSM::SSMRequest.
|
inline |
The cron expression used to schedule the association that you want to update.
Definition at line 215 of file UpdateAssociationRequest.h.
|
inlineoverridevirtual |
Implements Aws::AmazonWebServiceRequest.
Definition at line 37 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 894 of file UpdateAssociationRequest.h.
|
inline |
A location is a combination of AWS Regions and AWS accounts where you want to run the association. Use this action to update an association in multiple Regions and multiple accounts.
Definition at line 1030 of file UpdateAssociationRequest.h.
|
inline |
The targets of the association.
Definition at line 423 of file UpdateAssociationRequest.h.
|
inline |
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.
Definition at line 775 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 654 of file UpdateAssociationRequest.h.
|
inline |
The 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:aws: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
.
Definition at line 321 of file UpdateAssociationRequest.h.
|
inline |
An S3 bucket where you want to store the results of this request.
Definition at line 268 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 97 of file UpdateAssociationRequest.h.
|
inline |
The cron expression used to schedule the association that you want to update.
Definition at line 221 of file UpdateAssociationRequest.h.
|
overridevirtual |
Convert payload into String.
Implements Aws::AmazonSerializableWebServiceRequest.
|
inline |
By default, when you update an association, the system runs it immediately after it is updated and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you update it. This parameter is not supported for rate expressions.
Also, if you specified this option when you created the association, you can reset it. To do so, specify the no-apply-only-at-cron-interval
parameter when you update the association from the command line. This parameter forces the association to run immediately after updating it and according to the interval specified.
Definition at line 1009 of file UpdateAssociationRequest.h.
|
inline |
The ID of the association you want to update.
Definition at line 62 of file UpdateAssociationRequest.h.
|
inline |
The ID of the association you want to update.
Definition at line 57 of file UpdateAssociationRequest.h.
|
inline |
The ID of the association you want to update.
Definition at line 67 of file UpdateAssociationRequest.h.
|
inline |
The name of the association that you want to update.
Definition at line 479 of file UpdateAssociationRequest.h.
|
inline |
The name of the association that you want to update.
Definition at line 474 of file UpdateAssociationRequest.h.
|
inline |
The name of the association that you want to update.
Definition at line 484 of file UpdateAssociationRequest.h.
|
inline |
This parameter is provided for concurrency control purposes. You must specify the latest association version in the service. If you want to ensure that this request succeeds, either specify $LATEST
, or omit this parameter.
Definition at line 532 of file UpdateAssociationRequest.h.
|
inline |
This parameter is provided for concurrency control purposes. You must specify the latest association version in the service. If you want to ensure that this request succeeds, either specify $LATEST
, or omit this parameter.
Definition at line 524 of file UpdateAssociationRequest.h.
|
inline |
This parameter is provided for concurrency control purposes. You must specify the latest association version in the service. If you want to ensure that this request succeeds, either specify $LATEST
, or omit this parameter.
Definition at line 540 of file UpdateAssociationRequest.h.
|
inline |
Specify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
Definition at line 593 of file UpdateAssociationRequest.h.
|
inline |
Specify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
Definition at line 586 of file UpdateAssociationRequest.h.
|
inline |
Specify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
Definition at line 600 of file UpdateAssociationRequest.h.
|
inline |
The severity level to assign to the association.
Definition at line 868 of file UpdateAssociationRequest.h.
|
inline |
The severity level to assign to the association.
Definition at line 863 of file UpdateAssociationRequest.h.
|
inline |
The document version you want update for the association.
Definition at line 188 of file UpdateAssociationRequest.h.
|
inline |
The document version you want update for the association.
Definition at line 183 of file UpdateAssociationRequest.h.
|
inline |
The document version you want update for the association.
Definition at line 193 of file UpdateAssociationRequest.h.
|
inline |
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.
Definition at line 799 of file UpdateAssociationRequest.h.
|
inline |
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.
Definition at line 787 of file UpdateAssociationRequest.h.
|
inline |
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.
Definition at line 811 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 686 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 670 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 702 of file UpdateAssociationRequest.h.
|
inline |
The 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:aws: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
.
Definition at line 353 of file UpdateAssociationRequest.h.
|
inline |
The 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:aws: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
.
Definition at line 337 of file UpdateAssociationRequest.h.
|
inline |
The 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:aws: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
.
Definition at line 369 of file UpdateAssociationRequest.h.
|
inline |
An S3 bucket where you want to store the results of this request.
Definition at line 273 of file UpdateAssociationRequest.h.
|
inline |
An S3 bucket where you want to store the results of this request.
Definition at line 278 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 111 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 104 of file UpdateAssociationRequest.h.
|
inline |
The cron expression used to schedule the association that you want to update.
Definition at line 233 of file UpdateAssociationRequest.h.
|
inline |
The cron expression used to schedule the association that you want to update.
Definition at line 227 of file UpdateAssociationRequest.h.
|
inline |
The cron expression used to schedule the association that you want to update.
Definition at line 239 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 939 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 924 of file UpdateAssociationRequest.h.
|
inline |
A location is a combination of AWS Regions and AWS accounts where you want to run the association. Use this action to update an association in multiple Regions and multiple accounts.
Definition at line 1051 of file UpdateAssociationRequest.h.
|
inline |
A location is a combination of AWS Regions and AWS accounts where you want to run the association. Use this action to update an association in multiple Regions and multiple accounts.
Definition at line 1044 of file UpdateAssociationRequest.h.
|
inline |
The targets of the association.
Definition at line 438 of file UpdateAssociationRequest.h.
|
inline |
The targets of the association.
Definition at line 433 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 909 of file UpdateAssociationRequest.h.
|
inline |
A location is a combination of AWS Regions and AWS accounts where you want to run the association. Use this action to update an association in multiple Regions and multiple accounts.
Definition at line 1037 of file UpdateAssociationRequest.h.
|
inline |
The targets of the association.
Definition at line 428 of file UpdateAssociationRequest.h.
|
inline |
By default, when you update an association, the system runs it immediately after it is updated and then according to the schedule you specified. Specify this option if you don't want an association to run immediately after you update it. This parameter is not supported for rate expressions.
Also, if you specified this option when you created the association, you can reset it. To do so, specify the no-apply-only-at-cron-interval
parameter when you update the association from the command line. This parameter forces the association to run immediately after updating it and according to the interval specified.
Definition at line 1022 of file UpdateAssociationRequest.h.
|
inline |
The ID of the association you want to update.
Definition at line 77 of file UpdateAssociationRequest.h.
|
inline |
The ID of the association you want to update.
Definition at line 72 of file UpdateAssociationRequest.h.
|
inline |
The ID of the association you want to update.
Definition at line 82 of file UpdateAssociationRequest.h.
|
inline |
The name of the association that you want to update.
Definition at line 494 of file UpdateAssociationRequest.h.
|
inline |
The name of the association that you want to update.
Definition at line 489 of file UpdateAssociationRequest.h.
|
inline |
The name of the association that you want to update.
Definition at line 499 of file UpdateAssociationRequest.h.
|
inline |
This parameter is provided for concurrency control purposes. You must specify the latest association version in the service. If you want to ensure that this request succeeds, either specify $LATEST
, or omit this parameter.
Definition at line 556 of file UpdateAssociationRequest.h.
|
inline |
This parameter is provided for concurrency control purposes. You must specify the latest association version in the service. If you want to ensure that this request succeeds, either specify $LATEST
, or omit this parameter.
Definition at line 548 of file UpdateAssociationRequest.h.
|
inline |
This parameter is provided for concurrency control purposes. You must specify the latest association version in the service. If you want to ensure that this request succeeds, either specify $LATEST
, or omit this parameter.
Definition at line 564 of file UpdateAssociationRequest.h.
|
inline |
Specify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
Definition at line 614 of file UpdateAssociationRequest.h.
|
inline |
Specify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
Definition at line 607 of file UpdateAssociationRequest.h.
|
inline |
Specify the target for the association. This target is required for associations that use an Automation document and target resources by using rate controls.
Definition at line 621 of file UpdateAssociationRequest.h.
|
inline |
The severity level to assign to the association.
Definition at line 878 of file UpdateAssociationRequest.h.
|
inline |
The severity level to assign to the association.
Definition at line 873 of file UpdateAssociationRequest.h.
|
inline |
The document version you want update for the association.
Definition at line 203 of file UpdateAssociationRequest.h.
|
inline |
The document version you want update for the association.
Definition at line 198 of file UpdateAssociationRequest.h.
|
inline |
The document version you want update for the association.
Definition at line 208 of file UpdateAssociationRequest.h.
|
inline |
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.
Definition at line 835 of file UpdateAssociationRequest.h.
|
inline |
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.
Definition at line 823 of file UpdateAssociationRequest.h.
|
inline |
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.
Definition at line 847 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 734 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 718 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 750 of file UpdateAssociationRequest.h.
|
inline |
The 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:aws: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
.
Definition at line 401 of file UpdateAssociationRequest.h.
|
inline |
The 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:aws: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
.
Definition at line 385 of file UpdateAssociationRequest.h.
|
inline |
The 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:aws: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
.
Definition at line 417 of file UpdateAssociationRequest.h.
|
inline |
An S3 bucket where you want to store the results of this request.
Definition at line 283 of file UpdateAssociationRequest.h.
|
inline |
An S3 bucket where you want to store the results of this request.
Definition at line 288 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 125 of file UpdateAssociationRequest.h.
|
inline |
The parameters you want to update for the association. If you create a parameter using Parameter Store, you can reference the parameter using {{ssm:parameter-name}}
Definition at line 118 of file UpdateAssociationRequest.h.
|
inline |
The cron expression used to schedule the association that you want to update.
Definition at line 251 of file UpdateAssociationRequest.h.
|
inline |
The cron expression used to schedule the association that you want to update.
Definition at line 245 of file UpdateAssociationRequest.h.
|
inline |
The cron expression used to schedule the association that you want to update.
Definition at line 257 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 969 of file UpdateAssociationRequest.h.
|
inline |
The 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.
Definition at line 954 of file UpdateAssociationRequest.h.
|
inline |
A location is a combination of AWS Regions and AWS accounts where you want to run the association. Use this action to update an association in multiple Regions and multiple accounts.
Definition at line 1065 of file UpdateAssociationRequest.h.
|
inline |
A location is a combination of AWS Regions and AWS accounts where you want to run the association. Use this action to update an association in multiple Regions and multiple accounts.
Definition at line 1058 of file UpdateAssociationRequest.h.
|
inline |
The targets of the association.
Definition at line 448 of file UpdateAssociationRequest.h.
|
inline |
The targets of the association.
Definition at line 443 of file UpdateAssociationRequest.h.