Which combination of steps will meet these requirements with the LEAST operational effort?
(Choose two.)
Create a Systems Manager Distributor package for the third-party agent.
Make sure that Systems Manager Inventory is configured. If Systems Manager Inventory is not configured, set up a new inventory for instances that is based on the appropriate tag value for Windows.
Create a Systems Manager State Manager association to run the AWS-RunRemoteScript document. Populate the details of the third-party agent package. Specify instance tags based on the appropriate tag value for Windows with a schedule of 1 day.
Create a Systems Manager State Manager association to run the AWS-ConfigureAWSPackage document. Populate the details of the third-party agent package. Specify instance tags based on the appropriate tag value for Windows with a schedule of 1 day.
Create a Systems Manager OpsItem with the tag value for Windows. Attach the Systems Manager Distributor package to the OpsItem. Create a maintenance window that is specific to the package deployment. Configure the maintenance window to cover 24 hours a day.
Explanations:
Creating a Systems Manager Distributor package for the third-party agent allows for efficient management and deployment of the .msi package across EC2 instances. This package can be easily updated as new versions are released, facilitating automatic deployment of the latest version with minimal operational effort.
While configuring Systems Manager Inventory is useful for tracking installed software on EC2 instances, it does not directly help in deploying or updating the third-party agent. Inventory management alone does not fulfill the requirement for automatic installation and updates of the agent.
Using AWS-RunRemoteScript to run a script for installing the third-party agent does not leverage the capabilities of Systems Manager specifically designed for package management. This approach can be more complex and less efficient than using the appropriate AWS document for package installation, such as AWS-ConfigureAWSPackage.
Creating a Systems Manager State Manager association with the AWS-ConfigureAWSPackage document allows for the automatic installation and periodic updating of the third-party agent on EC2 instances. This method leverages Systems Manager’s built-in functionality for package management, reducing operational overhead.
While creating a Systems Manager OpsItem and a maintenance window could be part of a strategy for managing deployments, it adds unnecessary complexity and does not provide a direct method for automatic updates of the agent. OpsItems are generally used for incident management, not for deploying packages automatically.
As I see it, the answer is:
Create a Systems Manager Distributor package for the third-party agent.