awsdocs/aws-powershell-user-guide

Official documentation source for the AWS Tools for Windows Powershell User Guide

NOTICE

This repository is archived, read-only, and no longer updated. For more information, read the announcement on the AWS News Blog.

You can find up-to-date AWS technical documentation on the AWS Documentation website, where you can also submit feedback and suggestions for improvement.

aws-powershell-user-guide's Issues

WINDOWS_2016_SQL_SERVER_STANDARD_2016 and WINDOWS_2016_SQL_SERVER_ENTERPRISE_2016 keywords no longer work.

The keywords WINDOWS_2016_SQL_SERVER_STANDARD_2016 and WINDOWS_2016_SQL_SERVER_ENTERPRISE_2016 no longer work in the Get-Ec2ImageByName cmdlet. When I try the command returns an error "Get-EC2ImageByName : Sequence contains no elements"

Has this has been deprecated/replaced or is it an error in the API?

Clarification of -WhatIf tag needed

page where error shows up: https://docs.aws.amazon.com/powershell/latest/userguide/pstools-discovery-aliases.html

The phrase: "AWS cmdlets do not support the -WhatIf switch." should be clarified:
-New-EC2Tag Respects the -whatif when running cmdlet, or when called in a procedure with [CmdletBinding(SupportsShouldProcess=$true)]
Remove-EC2Tag Respects -whatif fromcmdlet but not when called from a procedure with [CmdletBinding(SupportsShouldProcess=$true)]
"myrenamescript" does a new-ec2tag , remove-ec2tag -tag -force

So I called myrenamescript.ps1 -newtag $tag -whatif
New tag poped up with the proper whatif message and not created
Old tag was deleted.
ran script again myrenamescript.ps1 -newtag $tag
New tag was created, old tag was deleted
from Powershell pompt (not in script)
remove-ec2tag -tag -whatif
tag was NOT removed. got proper warning message

Something is wrong with Initialize-AWSDefaultConfiguration

Hi,

I've tried a few times now on different computers over a longer period, to setup AWS in powershell using the Initialize cmdlet. But it never really sticks - as in, it works for the current session (Get-EC2Instance returns data) but doesn't persist onto new powershell instances. I finally make it work each time by looking up the documentation and finding that I can put in an AWSCredential named "default", which then sticks.

When troubleshooting this, I go to the location AWS Powershell stores persisted credentials, which according to this page should be at C:\Users\<user>\.aws\ - but that directory doesn't exist after an Initialize-AWSDefaultConfiguration. Even if I create it, it doesn't get any content on reruns of the cmdlet.

Using procmon from Sysinternals, I've discovered a backing store file for Get-AWSCredential (and Set-) at this location: %LocalAppdata%\AWSToolkit. Shouldn't the docs specify this directory instead?

This directory contains a JSON file with all the details needed - making me believe the .aws directory is outdated?

This works for me (order does not seem to matter):

Set-AWSCredential -StoreAs default -AccessKey <..some access key..>
Initialize-AWSDefaultConfiguration -Region <..my region..>

After this, the JSON file in %LocalAppdata%\AWSToolkit contains both my region and credentials. Subsequent sessions will run Get-EC2Instance without error.

This does not work for me:

Initialize-AWSDefaultConfiguration -Region <..my region..>

It creates the JSON file in %LocalAppdata%\AWSToolkit, but it only contains my region - it does not contain the credentials I supplied to Initialize-AWSDefaultConfiguration.