Isso foi resolvido. Atualizamos a versão do AWS PowerShell para 3.1.95.0. Instalado o AWSToolsAndSDKForNet_sdk-3.1.95.0_ps-3.1.95.0_tk-1.10.0.2. Defina o proxy usando abaixo: Set-AWSProxy -Hostname < > -Port < >
Instalamos as ferramentas do AWS PowerShell com a versão abaixo indicada. Quando tentamos executar os comandos da AWS, recebemos um erro de conexão conforme especificado abaixo:
---- AWS Powershell version---
PS C:\Users> Get-AWSPowerShellVersion
AWS Tools for Windows PowerShell
Version 2.3.8.1
Copyright 2012-2014 Amazon.com, Inc. or its affiliates. All Rights Reserved.
Amazon Web Services SDK for .NET
Version 2.3.8.1
Copyright 2009-2014 Amazon.com, Inc. or its affiliates. All Rights Reserved.
--- PSVersion 4.0 ------
.
--- Error ---
ConnectionError: ('Connection aborted.', error(10060, 'A connection attempt failed because the connected party did not p
roperly respond after a period of time or established connection failed because connected host has failed to respond'))
2016-08-23 09:43:30,944 - MainThread - awscli.clidriver - DEBUG - Exiting with rc 255
('Connection aborted.', error(10060, 'A connection attempt failed because the connected party did not properly respond a
fter a period of time or established connection failed because connected host has failed to respond'))
PS C:\Users> curl http://ec2.eu-central-1.amazonaws.com
curl : Unable to connect to the remote server
At line:1 char:1
+ curl http://ec2.eu-central-1.amazonaws.com
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
eption
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
As portas 80 e 443 são abertas adequadamente nos SGs. Tentei / sem exportar o proxy na máquina.
Isso foi resolvido. Atualizamos a versão do AWS PowerShell para 3.1.95.0. Instalado o AWSToolsAndSDKForNet_sdk-3.1.95.0_ps-3.1.95.0_tk-1.10.0.2. Defina o proxy usando abaixo: Set-AWSProxy -Hostname < > -Port < >