question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

dask-ec2 security group VPC error

See original GitHub issue

I’m getting a Amazon VPC security error when I try to run dask-ec2 up. I followed the directions in http://distributed.readthedocs.io/en/latest/ec2.html exactly. If I run the dask-ec2 up a second time it successfully starts images, but the ssh step fails. I’m guessing this is an EC2 permissions problem…

Thanks, Nick

MyMac$ dask-ec2 up --keyname aws_key_pair --keypair ~/.ssh/aws_key_pair.pem 
Launching nodes
DEBUG: Checking that keyname 'aws_key_pair' exists on EC2
DEBUG: Checking that security group 'dask-ec2-default' exists on EC2
DEBUG: Default security group 'dask-ec2-default' not found, creating it
DEBUG: Creating default (very open) security group 'dask-ec2-default'
DEBUG: Setting up default values for the 'dask-ec2-default' security group
Unexpected EC2 error: An error occurred (InvalidParameterValue) when calling the AuthorizeSecurityGroupEgress operation: Only Amazon VPC security groups may be used with this operation.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
ngcrawfordcommented, Jun 24, 2016

Letting the script run longer fixed my issue. Thanks for your help Daniel.

0reactions
danielfrgcommented, Jun 23, 2016

Yes, unfortunately dask-ec2 only uses whatever its the default for the AWS account even when you create a default VPC. There is an issue to track that here: https://github.com/dask/dask-ec2/issues/17

Since you changed region i think it should work. On this case the error I see is different. Those ssh errors are “expected” since the EC2 instance state is running but SSH is not available immediately and there is no event from AWS to tell us that. So we have to poll and retry a couple of times. If you let that command run it should connect eventually and start the bootstrap process.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Connection errors when attempting dask.distributed cluster on ...
I haven't found a way of telling dask-worker the external address of the aws instance that runs the container.
Read more >
Dask Cloud Provider Documentation
This creates a Dask scheduler and workers on EC2 instances. All instances will run a single configurable Docker container which should ...
Read more >
Task networking with the awsvpc network mode
Using the awsvpc network mode simplifies container networking, you have more control over how containerized applications communicate with each other and other ...
Read more >
arXiv:1910.05896v2 [cs.DC] 15 Oct 2019
When multiplying 50, 000 × 50, 000 matrices, both setups of Dask. (Laptop and EC2) suffered from out-of-memory (OOM) errors, failing to complete ......
Read more >
Distributed Data Pre-processing using Dask, Amazon ECS ...
Then I will select the same VPC and Subnets that were selected earlier in the CloudFormation template: NOTE: You can select any other...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found