I've noticed that the AWS_DEFAULT_REGION env var is not set by the assume command. Is this intentional? There are scenarios where AWS_REGION is not used/parsed by some AWS tools, namely boto3.
For example:
$ assume <profile>
$ python
>>> import boto3
>>> boto3.client('ssm').list_parameters()
Traceback (most recent call last):
...
File "/<REDACTED>/.pyenv/versions/3.8.2/lib/python3.8/site-packages/botocore/regions.py", line 215, in _endpoint_for_partition
raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region.
Would it be possible to have the tool set this environment variable as well? I'm happy to take a crack at it, assuming there aren't any underlying problems with doing so.
I've noticed that the
AWS_DEFAULT_REGION
env var is not set by theassume
command. Is this intentional? There are scenarios whereAWS_REGION
is not used/parsed by some AWS tools, namelyboto3
.For example:
Would it be possible to have the tool set this environment variable as well? I'm happy to take a crack at it, assuming there aren't any underlying problems with doing so.