CfnAssociationProps
- class aws_cdk.aws_ssm.CfnAssociationProps(*, name, apply_only_at_cron_interval=None, association_name=None, automation_target_parameter_name=None, calendar_names=None, compliance_severity=None, document_version=None, instance_id=None, max_concurrency=None, max_errors=None, output_location=None, parameters=None, schedule_expression=None, schedule_offset=None, sync_compliance=None, targets=None, wait_for_success_timeout_seconds=None)
Bases:
object
Properties for defining a
CfnAssociation
.- Parameters:
name (
str
) – The name of the SSM document that contains the configuration information for the instance. You can specifyCommand
orAutomation
documents. The documents can be 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
orMy-Document
.apply_only_at_cron_interval (
Union
[bool
,IResolvable
,None
]) – By default, when you create a new association, 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. This parameter is not supported for rate expressions.association_name (
Optional
[str
]) – Specify a descriptive name for the association.automation_target_parameter_name (
Optional
[str
]) – Choose the parameter that will define how your automation will branch out. This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a capability of AWS Systems Manager .calendar_names (
Optional
[Sequence
[str
]]) – The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under. The associations only run when that Change Calendar is open. For more information, see AWS Systems Manager Change Calendar .compliance_severity (
Optional
[str
]) – The severity level that is assigned to the association.document_version (
Optional
[str
]) – The version of the SSM document to associate with the target. .. epigraph:: Note the following important information. - State Manager doesn’t support running associations that use a new version of a document if that document is shared from another account. State Manager always runs thedefault
version of a document if shared from another account, even though the Systems Manager console shows that a new version was processed. If you want to run an association using a new version of a document shared form another account, you must set the document version todefault
. -DocumentVersion
is not valid for documents owned by AWS , such asAWS-RunPatchBaseline
orAWS-UpdateSSMAgent
. If you specifyDocumentVersion
for an AWS document, the system returns the following error: “Error occurred during operation ‘CreateAssociation’.” (RequestToken: , HandlerErrorCode: GeneralServiceException).instance_id (
Optional
[str
]) – The ID of the instance that the SSM document is associated with. You must specify theInstanceId
orTargets
property. .. epigraph::InstanceId
has been deprecated. To specify an instance ID for an association, use theTargets
parameter. If you use the parameterInstanceId
, you cannot use the parametersAssociationName
,DocumentVersion
,MaxErrors
,MaxConcurrency
,OutputLocation
, orScheduleExpression
. To use these parameters, you must use theTargets
parameter.max_concurrency (
Optional
[str
]) – 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 managed node starts and attempts to run an association while Systems Manager is runningMaxConcurrency
associations, the association is allowed to run. During the next association interval, the new managed node will process its association within the limit specified forMaxConcurrency
.max_errors (
Optional
[str
]) – 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 managed nodes and setMaxError
to 10%, then the system stops sending the request when the sixth error is received. Executions that are already running an association whenMaxErrors
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, setMaxConcurrency
to 1 so that executions proceed one at a time.output_location (
Union
[IResolvable
,InstanceAssociationOutputLocationProperty
,Dict
[str
,Any
],None
]) – An Amazon Simple Storage Service (Amazon S3) bucket where you want to store the output details of the request.parameters (
Optional
[Any
]) – The parameters for the runtime configuration of the document.schedule_expression (
Optional
[str
]) – A cron expression that specifies a schedule when the association runs. The schedule runs in Coordinated Universal Time (UTC).schedule_offset (
Union
[int
,float
,None
]) – Number of days to wait after the scheduled day to run an association.sync_compliance (
Optional
[str
]) – The mode for generating association compliance. You can specifyAUTO
orMANUAL
. InAUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association isCOMPLIANT
. If the association execution doesn’t run successfully, the association isNON-COMPLIANT
. InMANUAL
mode, you must specify theAssociationId
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 useAUTO
mode.targets (
Union
[IResolvable
,Sequence
[Union
[IResolvable
,TargetProperty
,Dict
[str
,Any
]]],None
]) – The targets for the association. You must specify theInstanceId
orTargets
property. You can target all instances in an AWS account by specifying theInstanceIds
key with a value of*
. To view a JSON and a YAML example that targets all instances, see “Create an association for all managed instances in an AWS account ” on the Examples page.wait_for_success_timeout_seconds (
Union
[int
,float
,None
]) – The number of seconds the service should wait for the association status to show “Success” before proceeding with the stack execution. If the association status doesn’t show “Success” after the specified number of seconds, then stack creation fails.
- Link:
http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ssm-association.html
- ExampleMetadata:
fixture=_generated
Example:
# The code below shows an example of how to instantiate this type. # The values are placeholders you should change. import aws_cdk.aws_ssm as ssm # parameters: Any cfn_association_props = ssm.CfnAssociationProps( name="name", # the properties below are optional apply_only_at_cron_interval=False, association_name="associationName", automation_target_parameter_name="automationTargetParameterName", calendar_names=["calendarNames"], compliance_severity="complianceSeverity", document_version="documentVersion", instance_id="instanceId", max_concurrency="maxConcurrency", max_errors="maxErrors", output_location=ssm.CfnAssociation.InstanceAssociationOutputLocationProperty( s3_location=ssm.CfnAssociation.S3OutputLocationProperty( output_s3_bucket_name="outputS3BucketName", output_s3_key_prefix="outputS3KeyPrefix", output_s3_region="outputS3Region" ) ), parameters=parameters, schedule_expression="scheduleExpression", schedule_offset=123, sync_compliance="syncCompliance", targets=[ssm.CfnAssociation.TargetProperty( key="key", values=["values"] )], wait_for_success_timeout_seconds=123 )
Attributes
- apply_only_at_cron_interval
By default, when you create a new association, 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. This parameter is not supported for rate expressions.
- association_name
Specify a descriptive name for the association.
- automation_target_parameter_name
Choose the parameter that will define how your automation will branch out.
This target is required for associations that use an Automation runbook and target resources by using rate controls. Automation is a capability of AWS Systems Manager .
- calendar_names
The names or Amazon Resource Names (ARNs) of the Change Calendar type documents your associations are gated under.
The associations only run when that Change Calendar is open. For more information, see AWS Systems Manager Change Calendar .
- compliance_severity
The severity level that is assigned to the association.
- document_version
The version of the SSM document to associate with the target.
Note the following important information.
State Manager doesn’t support running associations that use a new version of a document if that document is shared from another account. State Manager always runs the
default
version of a document if shared from another account, even though the Systems Manager console shows that a new version was processed. If you want to run an association using a new version of a document shared form another account, you must set the document version todefault
.DocumentVersion
is not valid for documents owned by AWS , such asAWS-RunPatchBaseline
orAWS-UpdateSSMAgent
. If you specifyDocumentVersion
for an AWS document, the system returns the following error: “Error occurred during operation ‘CreateAssociation’.” (RequestToken: , HandlerErrorCode: GeneralServiceException).
- instance_id
The ID of the instance that the SSM document is associated with.
You must specify the
InstanceId
orTargets
property. .. epigraph:``InstanceId`` has been deprecated. To specify an instance ID for an association, use the ``Targets`` parameter. 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.
- max_concurrency
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 managed node 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 managed node will process its association within the limit specified forMaxConcurrency
.
- max_errors
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 managed nodes 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, setMaxConcurrency
to 1 so that executions proceed one at a time.
- name
The name of the SSM document that contains the configuration information for the instance.
You can specify
Command
orAutomation
documents. The documents can be 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
orMy-Document
.
- output_location
An Amazon Simple Storage Service (Amazon S3) bucket where you want to store the output details of the request.
- parameters
The parameters for the runtime configuration of the document.
- schedule_expression
A cron expression that specifies a schedule when the association runs.
The schedule runs in Coordinated Universal Time (UTC).
- schedule_offset
Number of days to wait after the scheduled day to run an association.
- sync_compliance
The mode for generating association compliance.
You can specify
AUTO
orMANUAL
. InAUTO
mode, the system uses the status of the association execution to determine the compliance status. If the association execution runs successfully, then the association isCOMPLIANT
. If the association execution doesn’t run successfully, the association isNON-COMPLIANT
.In
MANUAL
mode, you must specify theAssociationId
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.
- targets
The targets for the association.
You must specify the
InstanceId
orTargets
property. You can target all instances in an AWS account by specifying theInstanceIds
key with a value of*
. To view a JSON and a YAML example that targets all instances, see “Create an association for all managed instances in an AWS account ” on the Examples page.
- wait_for_success_timeout_seconds
The number of seconds the service should wait for the association status to show “Success” before proceeding with the stack execution.
If the association status doesn’t show “Success” after the specified number of seconds, then stack creation fails.