Smaws_Client_SSM.CreateAssociationval request :
Smaws_Lib.Context.t ->
create_association_request ->
(create_association_result,
[> Smaws_Lib.Protocols.AwsJson.error
| `AssociationAlreadyExists of association_already_exists
| `AssociationLimitExceeded of association_limit_exceeded
| `InternalServerError of internal_server_error
| `InvalidDocument of invalid_document
| `InvalidDocumentVersion of invalid_document_version
| `InvalidInstanceId of invalid_instance_id
| `InvalidOutputLocation of invalid_output_location
| `InvalidParameters of invalid_parameters
| `InvalidSchedule of invalid_schedule
| `InvalidTag of invalid_tag
| `InvalidTarget of invalid_target
| `InvalidTargetMaps of invalid_target_maps
| `UnsupportedPlatformType of unsupported_platform_type ])
Stdlib.resultA State Manager association defines the state that you want to maintain on your managed nodes. For example, an association can specify that anti-virus software must be installed and running on your managed nodes, or that certain ports must be closed. For static targets, the association specifies a schedule for when the configuration is reapplied. For dynamic targets, such as an Amazon Web Services resource group or an Amazon Web Services autoscaling group, State Manager, a capability of Amazon Web Services Systems Manager applies the configuration when new managed nodes are added to the group. The association also specifies actions to take when applying the configuration. For example, an association for anti-virus software might run once a day. If the software isn't installed, then State Manager installs it. If the software is installed, but the service isn't running, then the association might instruct State Manager to start the service.