Cannot specify region_name on presigned URL

[richard-jones]

Describe the bug

I'm attempting to set a region_name when calling generate_presigned_url. The entry method wraps a call to the request_signer and although the request_siger.generate_presigned_url allows region_name as a parameter, the entry method is not capable of passing it on, and it always defaults to the client's pre-set region. In my case, I'm attempting to access an s3 bucket, and I don't know the region of the bucket until after construction of the client, so I must construct a client, query for the bucket region, and then destroy and recreate the client.

https://github.com/boto/botocore/blob/develop/botocore/signers.py#L681

Expected Behavior

For the client to allow me to specify the region on request

Current Behavior

You cannot specify the region on request, you must recreate the client

Reproduction Steps

client = boto3.client(
            's3',
            aws_access_key_id=access_key,
            aws_secret_access_key=secret,
            config=Config(signature_version='s3v4')
        )
bucket_location = self.client.get_bucket_location(Bucket=container_id)
location = bucket_location['LocationConstraint']
return client.generate_presigned_url('get_object',
                                           Params={"Bucket": container_id, "Key": target_name},
                                           ExpiresIn=timeout,
                                           # Nowhere to specify region ...
                   )

Possible Solution

Add region_name to generate_presigned_url method signature

Additional Information/Context

No response

SDK version used

latest

Environment details (OS name and version, etc.)

Ubuntu 18.04

[aBurmeseDev]

Hi @richard-jones - thanks for reaching out. I came across this similar issue here and there are workaround suggested in there. One of the comments was suggested by one of our team members and let me know if that's what you're trying to accomplish.

Best,
John

[github-actions]

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.