I'm having a very odd issue. I have two Windows servers (2022 Datacenter). ServerA and ServerB. As part of an automated deployment process ServerA uses a remote (WinRM) Powershell session into ServerB to execute a script. This script needs to connect to an Amazon AWS S3 bucket to download some files. I added the AWS credentials as "default" to ServerB, but it throws this error:
Get-S3Object : No credentials specified or obtained from persisted/shell defaults.
However, if you remote-desktop into ServerB using the same (local) account and run Get-AWSCredential -ListProfileDetail you can see the default credentials in the result, stored within the AWS SDK cache.
But then - this is the odd part - if you now initiate the original script on ServerA it works! It's like you need to have physically logged in as the target account on ServerB to get the credentials to load, somehow.
I've tried forcing the issue by adding lines like the following to the script:
$ENV:AWS_PROFILE = "default"
$ENV:AWS_DEFAULT_PROFILE = "default"
Set-AWSCredential -ProfileName default
$object = Get-S3Object [...]
But I just get different errors saying the profile can't be found! Note that all other aspects of this script work whether or not the Remote Desktop session is/has-been initiated, it is only the AWS SDK part that has this issue.