- Newest
- Most votes
- Most comments
Figured this out. The managed instance had the correct role, I just needed to install the awscli tools first, set the path so that powershell could use them, then issue the standard aws s3 cp command.
Part of my run document looks like this. I'm using chocolatey to get the awscli tools installed.
Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))
choco install awscli -y
setx PATH "%PATH%;C:\Program Files\Amazon\AWSCLI"
aws s3 cp s3://yadayadayada c:\
then a line to remove the cli tool when done
choco uninstall awscli -y
Too bad the ssm agent doesn't come with aws tools already installed for this kind of stuff, but that's ok.
Edited by: kleinberger on Feb 13, 2019 2:13 PM
Relevant content
- asked 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago