I thought the point of ec2-upload-bundle was to get bundles created by ec2-bundle-image outside Amazon into S3 so you can boot images in EC2. ☺
However, it seems to expect to run from within EC2. That is, the magic “META_DATA_URL” http://169.254.169.254/latest/meta-data/ must work, it seems; at least, with –debug I get a ruby stack trace through get_availability_zone whether or not I specify –location after it fetches the LocationConstraint for my bucket.
What am I missing? Is it expecting that URL not to time out when going through a web proxy when run outside of EC2?
Cristian Gafton April 17, 2012 23:31
the AWS forums is the proper place to ask and get a good answer to this question. the guys that actually wrote the thing are monitoring the forums.
Michael K Johnson April 18, 2012 10:37
Well, I had already found https://forums.aws.amazon.com/thread.jspa?threadID=36370
None of “the guys that actually wrote the thing” had helped the earlier forum poster out when setting proxy environment variables didn’t work, though. (Not even a suggestion to use strace -f -s 2048 and/or wireshark to see what was happening…)
Michael K Johnson April 18, 2012 10:41
…furthermore, none of the responses in that thread are obviously from amazon folks, and the thread is from September 2009. So it doesn’t seem obviously crazy to me to try asking on G+ if anyone has a clue about this.
Imported from Google+ — content and formatting may not be reliable