-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seahorse::Client::NetworkingError: execution expired when calling Aws::EC2::Instance#start #904
Comments
In your configuration, you gave the name of an availability zone where a region is expected. You should be able to simply replace Another note, it looks like you are trying to create an instance. Constructing an instance of the instance = Aws::EC2::Instance.new('i-12345678')
instance.state.name #=> "running"
instance.terminate If you want to run a new instance you should use ec2 = Aws::EC2::Resource.new(region: '...', access_key_id: '...', secret_access_key: '...')
instances = ec2.create_instances(instance_type: 'sample.type', image_id: 'sample-id', min_count: 2, max_count: 2) Hope this helps! |
I think you nailed it, thanks! |
+1 I just had this problem with AWS S3 upload in ruby, doing this:
I had It would be nice if the error could be more informative. |
got this error when my network upload speed was low. got it working when i connected my system to other network with good speed |
I'm using v2.1.11 and I'm trying to create and/or interact with EC2 instances thusly:
When I call
ec2.start
(or any other method that might reach out to AWS itself), I get the following error:After some searching, I thought this might be related to SSL issues (though the error doesn't state anything about that), so for kicks I tried the following options, each in isolation:
Aws.use_bundled_cert!
Aws.config[:ssl_verify_peer] = false
In the same console and in the same codebase, I'm able to create Kinesis, S3, and AutoScale services without any errors using a similar pattern.
Thanks for your time!
The text was updated successfully, but these errors were encountered: