Which set of steps should be taken next?
Configure the Systems Manager document to use the AWS-RunShellScript command to copy the files from GitHub to Amazon S3, then use the aws-downloadContent plugin with a sourceType of S3.
Configure the Systems Manager document to use the aws-configurePackage plugin with an install action and point to the Git repository.
Configure the Systems Manager document to use the aws-downloadContent plugin with a sourceType of GitHub and sourceInfo with the repository details.
Configure the Systems Manager document to use the aws:softwareInventory plugin and run the script from the Git repository.
Explanations:
The AWS-RunShellScript command can execute shell scripts, but it does not natively handle copying files from GitHub to S3. Instead, this option complicates the process by introducing unnecessary steps of transferring files to S3 first, which isn’t needed if the objective is to run the code directly from GitHub.
The aws-configurePackage plugin is designed for installing software packages, not for cloning or downloading files from a Git repository. This option does not align with the requirement of using a GitHub repository as the source for bootstrap code.
The aws-downloadContent plugin is specifically designed for downloading files from various sources, including GitHub. By using the sourceType of GitHub and providing the necessary repository details, this option effectively allows the Systems Manager document to pull the bootstrap code directly from GitHub, making it the correct choice.
The awsplugin is used for collecting inventory information about installed software, rather than executing scripts or downloading content. This option does not fulfill the requirement of bootstrapping the laptops with code from a Git repository.