Skip to content
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

Connecting to ECS from a Glue Task #1

Open
dandalf opened this issue Oct 10, 2017 · 0 comments
Open

Connecting to ECS from a Glue Task #1

dandalf opened this issue Oct 10, 2017 · 0 comments
Assignees

Comments

@dandalf
Copy link

dandalf commented Oct 10, 2017

Hello,
I am trying to replicate your solution but I am having issues. I do not have your virtualenv_python.zip file so I can't replicate exactly but I can't connect to ECS with the included boto3. Based on the error logs, It seems like the glue ETL job is creating instances inside of my default VPC (which has an internet gateway attached and public ips auto assigned). It seems like the instances Glue creates do not have external network access. I get an exception like the following:

botocore.vendored.requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='ecs.us-east-1.amazonaws.com', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<botocore.awsrequest.AWSHTTPSConnection object at 0x7fa488baa610>, 'Connection to ecs.us-east-1.amazonaws.com timed out. (connect timeout=60)'))

I have tried attaching the appropriate EC2Cotainer policies to the glue service role and I have tried just passing an ACCESS_KEY and SECRET_KEY directly to boto3, but I have had no luck.

How did you get yours to work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants