- Mais recentes
- Mais votos
- Mais comentários
On reddit someone suggested I look at environment vars, which got me thinking to check for any profiles. When I dumped the credentials it showed "NetSDKCredentialsFile"
Get-AWSCredential -ListProfileDetail
ProfileName StoreTypeName ProfileLocation
----------- ------------- ---------------
For_Move NetSDKCredentialsFile
default NetSDKCredentialsFile
I found the file here and deleted it: %userprofile%\AppData\Local\AWSToolkit\RegisteredAccounts.json
Everything works as expected now. Must have got installed by accident.
I went ahead and swapped to use forward slashes.
Rebooted the instance that is not working and it still doesn't work.
I've run out of things to test. I don't want to create an IAM user with secret key and have to use that but I suppose that is the next step.
I'm wondering whether the issue here is with the backslash in the key name (Junk3\junk1.txt
) and whether you need to escape that (if you want to use a backslash) or whether it's better to use a forward slash (/
). That doesn't explain why it behaves differently on the two EC2 instances though.
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
No, don't do that - that's definitely an anti-pattern and it leaves you rotating credentials. Not a good idea. The whole point of an instance role is that you don't have to do that. Have you tried copying a file to the same bucket using the AWS CLI? I'm trying to eliminate things to get to the bottom of this.