Default endpoints cause Certification Validation to fail #530

Closed
garnaat opened this Issue Jan 29, 2012 · 0 comments

1 participant

@garnaat
the boto project member

A number of boto modules such as ec2 use the old, non-region-aware endpoints such as ec2.amazonaws.com rather than ec2.us-east-1.amazonaws.com. This causes certificate validation to fail if it is enabled in your boto config file.

These default endpoints should be changed to us the us-east-1 endpoints by default rather than the non-region-aware endpoints.

@garnaat garnaat added a commit that closed this issue Jan 29, 2012
@garnaat garnaat Changing default endpoints for some of the older services to be regio…
…n-aware to avoid certificate validation issues. Closes #530.
46e36bf
@garnaat garnaat closed this in 46e36bf Jan 29, 2012
@msabramo msabramo pushed a commit to msabramo/boto that referenced this issue Nov 28, 2012
@garnaat garnaat Changing default endpoints for some of the older services to be regio…
…n-aware to avoid certificate validation issues. Closes #530.
2c42b21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment