You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the boto services (i.e. RDS) don't have a region-setting ~/.boto option, and the only way to set the connection region for them is in whatever is using boto (i.e. this project). We need to support setting regions.
For the time being, we're not adding multi-region support to awslimitchecker, we're just adding support to set regions other than boto's hard-coded us-east-1 default. We'll need to pass this to the individual service connectors, TA, and anything else that connects to AWS.
Possible options:
Make this a command-line option, and also have a way to set it on the main Checker class from Python.
In all of our service connectors, simply check for an AWS_REGION environment variable, and pass it in to the connector if it's specified.
The text was updated successfully, but these errors were encountered:
Some of the boto services (i.e. RDS) don't have a
region
-setting~/.boto
option, and the only way to set the connection region for them is in whatever is using boto (i.e. this project). We need to support setting regions.For the time being, we're not adding multi-region support to awslimitchecker, we're just adding support to set regions other than boto's hard-coded
us-east-1
default. We'll need to pass this to the individual service connectors, TA, and anything else that connects to AWS.Possible options:
AWS_REGION
environment variable, and pass it in to the connector if it's specified.The text was updated successfully, but these errors were encountered: