Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

ec2.connect_to_region fails to connect to us-east-2 #3629

Open
hrez opened this issue Oct 17, 2016 · 2 comments
Open

ec2.connect_to_region fails to connect to us-east-2 #3629

hrez opened this issue Oct 17, 2016 · 2 comments

Comments

@hrez
Copy link

hrez commented Oct 17, 2016

ec2.connect_to_region fails to connect to us-east-2.
The reason is because regions/endpoints are hardcoded in boto.ENDPOINTS_PATH json file.
Need to switch to http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeRegions.html
@michaeljamesdunn michaeljamesdunn mentioned this issue Oct 26, 2016
Open
@2rs2ts
Copy link

2rs2ts commented Nov 2, 2016

I think you can't do DescribeRegions because sometimes you will be operating in an environment which does not have the IAM access to make that call. Looks like boto has been updated for us-east-2 regardless. d146df0

kalpatel01 pushed a commit to Bridgewater/security_monkey that referenced this issue Feb 24, 2017
[secmonkey] Convert watchers to boto3
e532437 
Type: generic-bugfix

Why is this change necessary?
There is a known defect with boto that returns a None connection for
us-east-2 (boto/boto#3629)

This change addresses the need by:
Moves affected watchers to boto3 connection.

Potential Side Effects:
None
@kalpatel01 kalpatel01 mentioned this issue Feb 24, 2017
Merged
kalpatel01 pushed a commit to Bridgewater/security_monkey that referenced this issue Feb 24, 2017
[secmonkey] Convert watchers to boto3
5cc4645 
Type: generic-bugfix

Why is this change necessary?
There is a known defect with boto that returns a None connection for
us-east-2 (boto/boto#3629)

This change addresses the need by:
Moves affected watchers to boto3 connection.

Potential Side Effects:
None
scriptsrc pushed a commit to Netflix/security_monkey that referenced this issue Mar 8, 2017
@kalpatel01
[secmonkey] Convert watchers to boto3 (#566) 😈
06a75e3 
Type: generic-bugfix

Why is this change necessary?
There is a known defect with boto that returns a None connection for
us-east-2 (boto/boto#3629)

This change addresses the need by:
Moves affected watchers to boto3 connection.

Potential Side Effects:
None
@rangapv
Copy link

rangapv commented Jan 2, 2019

Hi,
Could you mention the steps need to fix this issue of us-east-2 missing in ec2.py --list .
I am not able to follow the steps needed to fix this. My understanding is use boto3 instead ? or update the endpoints.json ? . Whichever it is kindly mention the steps.
Thanks and Happy New Year
Ranga

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@2rs2ts @hrez @rangapv