amazon web services - AWS CLI for EBS snapshots -


i trying aws cli going backup ec2 instances. can't see why aws don't make easy schedule via console don't pushing ahead cli.

i installed on 1 of instances. problem 1, won't work unless setup nat instance instance has no public ip. trying avoid used server @ different isp have public ip. setup credentials , profiles using aws configure. have config , credentials files in .aws directory. should work. try:

aws ec2 describe-instances --profile tmpevaluate  not connect endpoint url: "https://ec2.us-west-2b.amazonaws.com/" 

i tried

nslookup ec2.us-west-2b.amazonaws.com 

but doesn't resolve. weird resolves on mac , dns working on server trying can resolve other domains can think of. debug installed , configured aws cli on mac. know can resolve ec2.us-west-2b.amazonaws.com. tried:

aws ec2 describe-instances --profile tmpevaluate 

and get:

httpsconnectionpool(host='ec2.us-west-2b.amazonaws.com', port=443): max retries exceeded url: / (caused connecttimeouterror(<botocore.awsrequest.awshttpsconnection object @ 0x10c0ac6d0>, 'connection ec2.us-west-2b.amazonaws.com timed out. (connect timeout=60)')) 

i @ loss. should simple has me totally stumped , no 1 else seems having same problem.

ideas?

use us-west-2 instead of us-west-2b in endpoint url. probably, value of region in configuration file created running aws configure

us-west-2 region us-west-2b availability zone in region.

you should connecting region , not specific availability zone


Comments

  1. Thanks for sharing nice script for scheduled back up of AWS EC2 scheduled snapshot. I will definitely try this script.

    ReplyDelete

Post a Comment

Popular posts from this blog

facebook - android ACTION_SEND to share with specific application only -

python - Creating a new virtualenv gives a permissions error -

go - Idiomatic way to handle template errors in golang -