Launching Amazon EC2 Spot Instances with Auto Scaling and Amazon CloudWatch avaliações

5846 avaliações

Srikanth S. · Revisado há about 9 years

Joshua M. · Revisado há about 9 years

Jason G. · Revisado há about 9 years

I was only tripped up on the point where we created a new email list. It was kind of confusing at first.

Derek H. · Revisado há about 9 years

Raghavendra K. · Revisado há about 9 years

sam c. · Revisado há about 9 years

Julien H. · Revisado há about 9 years

AWS A. · Revisado há about 9 years

Ivan P. · Revisado há about 9 years

Harry C. · Revisado há about 9 years

Mohammed K. · Revisado há about 9 years

Server crashed in middle of lab

Vincent A. · Revisado há about 9 years

Peter B. · Revisado há about 9 years

The lab is confusing. SSH from OSX didn't work with "Authentication failed". See below for verbose dump. To perform all steps from AWS Console it add quite a few guess work as terminology differs greatly. SSH error dump: OpenSSH_7.4p1, LibreSSL 2.5.0 debug1: Reading configuration data /Users/tyumnevb/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to 54.71.151.186 [54.71.151.186] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /Users/tyumnevb/Downloads/qwikLABS-L134-1107697 (1).pem type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/tyumnevb/Downloads/qwikLABS-L134-1107697 (1).pem-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.4 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1 debug1: match: OpenSSH_6.6.1 pat OpenSSH_6.6.1* compat 0x04000000 debug1: Authenticating to 54.71.151.186:22 as 'ec2-user' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:n6PArdY4ka2+lFfmctKbVQpX62SQEyUoi1alYgoSCyE debug1: Host '54.71.151.186' is known and matches the ECDSA host key. debug1: Found key in /Users/tyumnevb/.ssh/known_hosts:15 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/tyumnevb/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Offering RSA-CERT public key: /Users/tyumnevb/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Offering RSA-CERT public key: /Users/tyumnevb/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Offering RSA-CERT public key: /Users/tyumnevb/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Offering RSA-CERT public key: /Users/tyumnevb/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Offering RSA-CERT public key: /Users/tyumnevb/.ssh/id_rsa Received disconnect from 54.71.151.186 port 22:2: Too many authentication failures for ec2-user Authentication failed.

Boris T. · Revisado há about 9 years

Not sure why but I can't get the aws command to work in my Putty terminal window

Brianna Z. · Revisado há about 9 years

omar k. · Revisado há about 9 years

Christopher J. · Revisado há about 9 years

Richard H. · Revisado há about 9 years

Lab broken. AWS CLI tools not working

Eduardo G. · Revisado há about 9 years

too good

Jitesh M. · Revisado há about 9 years

Barun Y. · Revisado há about 9 years

Good stuff

Mark N. · Revisado há about 9 years

Isai M. · Revisado há about 9 years

Danny L. · Revisado há about 9 years

Danny L. · Revisado há about 9 years

Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.