No Support for new eu-north-1 region
vukomir opened this issue · comments
Hi,
I'm trying to use some API in eu-north-1 region but it's not supported.
region name: eu-north-1 likely not supported, or AWS is down. connection to region failed.
can you please add support for new AWS region?
Thanks.
Br,
Vuko
I too am having the same issue. Please Update Boto to include newer regions.
A working endpoints.json can be found here: https://raw.githubusercontent.com/aws/aws-sdk-net/master/sdk/src/Core/endpoints.json
I've dropped it right in the site-packages/boto. I've tried to get it to work with the BOTO_ENDPOINTS
variable but no dice.
Looks like nobody is merging the pull-request to support half of the AWS regions.
Related to #3783 too.
+1 - yes please update or provide workaround.
+1 - come on already!
Ran into this today and found the proper BOTO_ENDPOINTS
/ endpoints_path
file format as it isn't the same as the builtin format. With the following contents of my /etc/aws-endpoints.json
:
{
"ec2": {
"eu-north-1": "ec2.eu-north-1.amazonaws.com"
}
}
And a /etc/boto.cfg
file with contents of:
[Boto]
endpoints_path = /etc/aws-endpoints.json
I can work with ec2 in eu-north-1.
Additional services and URLs can be added as needed.
I found this poking through the code and then reading some old Eucalyptus docs:
Ran into this today and found the proper
BOTO_ENDPOINTS
/endpoints_path
file format as it isn't the same as the builtin format. With the following contents of my/etc/aws-endpoints.json
:{ "ec2": { "eu-north-1": "ec2.eu-north-1.amazonaws.com" } }
And a
/etc/boto.cfg
file with contents of:[Boto] endpoints_path = /etc/aws-endpoints.json
I can work with ec2 in eu-north-1.
Additional services and URLs can be added as needed.
I found this poking through the code and then reading some old Eucalyptus docs:
Thank you so much for sharing this!
This one bit me as well, I'd love to have native support eu-west-3 here.
This one bit me as well, I'd love to have native support eu-west-3 here.
#3783 (comment)
How its going?