get_available_regions does not return ec2 for the new region ca-west-1 about botocore HOT 5 CLOSED

Hi @naveenarra, thanks for reaching out. I was able to get a response that includes ca-west-1 as an available region. Could you verify that you have this region enabled, as it is an opt-in region? You can get more information about opt-in regions here.

from botocore.

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

from botocore.

Hi @naveenarra, thanks for reaching out. I was able to get a response that includes ca-west-1 as an available region. Could you verify that you have this region enabled, as it is an opt-in region? You can get more information about opt-in regions here.

Did you try this for ec2? I was able to get it for the following services (but not ec2) -

apigatewayv2
acm
dynamodbstreams
secretsmanager
cloudwatch
accessanalyzer
sagemaker
ecr
directconnect
sqs
eks
ram
lambda
logs
cloudformation
ecs
rds
redshift
cloudtrail
codedeploy
kms
kinesis
sns
elbv2
ssm
es
elb
emr
apigateway
elasticache
dynamodb

from botocore.

Hi @naveenarra, thanks for your patience. My prior comment was incorrect, my mistake. get_available_regions is known to be inaccurate, and I would recommend that you use the SSM Parameter Store API for your use case. For full context, here is a comment on a similar issue that explains it pretty thoroughly.

Upon discussing this further with a colleague we wanted to clarify that the Python SDK team is currently investigating paths forward for this method, and deprecation is one possible outcome. Here is why:

As mentioned above, the source of information returned by get_available_regions is the endpoints.json file. This file is embedded in botocore and until version 1.28.0 was used for endpoint resolution in botocore.

The get_available_regions method was introduced many years ago as a secondary use of endpoints.json data, long before other sources of service availability were available. This has always been a sub-optimal solution because the information in endpoints.json is inherently frozen at release time. And even at release time the data in endpoints.json may lag behind reality due to how it is generated internally. The boto3 documentation addresses this (the function is not documented in the botocore documentation).

Since get_available_regions was introduced, the SSM Parameter Store API was introduced to solve the same user need better in 2019. Endpoint resolution in SDKs migrated to a different data source starting with botocore 1.28.0. As a result, endpoints.json will become an even less complete and up-to-date data source.

If completeness and recency of information is important for your use, switching to the SSM API is, and has been, the recommended approach.

Hope that helps, and please let me know if you have any other questions.

from botocore.

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

from botocore.