There appear to be two things going on here. First, the US standard region is actually either Virginia or Oregon. You just need to realize that you are being redirected because Amazon has chosen Oregon for your bucket. The URL explaining the regions is currently here:
http://docs.aws.amazon.com/AmazonS3/latest/dev/LocationSelection.html
The second thing going on is redirection. You are being redirected to Oregon when you connect, because the typical S3 endpoint you will see is the closest one by latency DNS. When you later hard code in Virginia, you don't see your bucket as it is in Oregon.
Amazon has some documentation here regarding how S3 will redirect you and how to handle this.
http://docs.aws.amazon.com/AmazonS3/latest/dev/RESTRedirect.html
Since you are using a toolkit and rather than an API, I didn't see anything specifically in the ruby forge or Amazon documentation that would tell why the redirect is not followed. It looks as though other people with the AWS ruby SDK had this problem last year. It may be fixed in the newer versions.
The documentation that I am referring to is here:
http://amazon.rubyforge.org/doc/
Amazon appears to have newer documentation here:
http://docs.aws.amazon.com/AWSRubySDK/latest/
Another thing is that I saw complaints that the redirect URL was malformed. While I was not able to duplicate that behavior, I would try to send the request to the Oregon endpoint to see if this resolves your issue.