Exam AWS Certified SysOps Administrator - Associate topic 1 question 207 discussion

A and D https://docs.aws.amazon.com/systems-manager/latest/userguide/distributor-working-with-packages-deploy.html

Correct answer is AD: You can just read a description of each SSM document: AWS-ConfigureAWSPackage "Install or uninstall a Distributor package. You can install the latest version, default version, or a version of the package you specify." AWS-RunRemoteScript "Execute scripts stored in a REMOTE location. The following remote locations are currently supported: GitHub (public and private) and Amazon S3 (S3). The following script types are currently supported: #! support on Linux and file associations on Windows." So we need to create a Distributor package and then create State Manager association to run the AWS-ConfigureAWSPackage

With State Manager, a capability of AWS Systems Manager, you can define and maintain consistent configuration of your operating system and software. Using the AWS-ConfigureAWSPackage document in a State Manager association allows you to install, update, or remove packages. By specifying instance tags based on the appropriate tag value for Windows with a schedule (e.g., every 1 day), you can automate the deployment of updates to the agent across all your managed Windows EC2 instances.The AWS-RunRemoteScript document can be used to download and execute scripts on EC2 instances, but it requires the management and storage of the script separately and would involve more operational effort in handling package updates.

a & d instead of C

AC makes more sense for me as it is third party package

why not D : AWS-ConfigureAWSPackage is for AWS installation. why C : AWS-RunRemoteScript is for 3rd party,

Step A: Create a Systems Manager Distributor package for the third-party agent. Systems Manager Distributor allows you to package and distribute software and files to your instances using SSM. By creating a Distributor package for the third-party agent's .msi package, you can centrally manage its installation and updates across EC2 instances. Step D: 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. AWS-ConfigureAWSPackage document is used to install software packages on EC2 instances. By creating a State Manager association with AWS-ConfigureAWSPackage document and specifying the instance tags based on the appropriate tag value for Windows, you can ensure that the third-party agent package is deployed on the instances automatically.

AC third party package!

Isn't this example the answer to the question of "C" over "D"? 1st step is to create an SSM formatted "package" using any install files (AWS, MS, or whoever). Then you use the AWS-ConfigureAWSPackage "document" to create the association. # Create Association to update a Distributor package on a schedule without taking application offline aws ssm create-association --name "AWS-ConfigureAWSPackage" [...] https://docs.aws.amazon.com/systems-manager/latest/userguide/distributor-working-with-packages-deploy.html#distributor-smupdate-pkg-cli

Create a Systems Manager Distributor package for the third-party agent. 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. https://docs.aws.amazon.com/systems-manager/latest/userguide/distributor-working-with-packages-create.html

ad is correct

AC is more correct

Option D is incorrect because AWS-ConfigureAWSPackage document is used to install and configure AWS packages, not third-party packages. It is used to install packages from the Amazon Linux Extras library, AWS services such as the SSM agent, and third-party software provided by AWS Partners. To install the third-party agent on EC2 instances, the best approach is to create a Systems Manager Distributor package for the third-party agent, as mentioned in option A. The Distributor package allows you to centrally manage software deployment across your Amazon EC2 instances or on-premises servers. You can use this feature to deploy both AWS and third-party software. Once you create the package, you can use State Manager associations to schedule and deploy the package to EC2 instances based on instance tags, as mentioned in option C.

A,D Correct reference provided by zolthar. I have no idea what awsguru is referencing that says AWS-ConfigureAWSPackage can only be used for AWS-provided packages, as that would require a tremendous overhead on AWS for providing packages on an insane amount of available software. This is very similar to SCCM in which you build your package yourself with the software you want and set the install targets/requirements.

AC Not D, it is not the AWS-ConfigureAWSPackage document. The AWS-ConfigureAWSPackage document is used to install, uninstall, or update an AWS-provided package or application. In this scenario, the SysOps administrator is trying to install a third-party agent, which is not an AWS-provided package or application. Therefore, the AWS-RunRemoteScript document is the appropriate choice to install and update the third-party agent.

AD for sure