feat(parameters): Allow settings boto3.client() arguments
See original GitHub issueIs your feature request related to a problem? Please describe.
I’m using VPC endpoints with private DNS disabled, so I have to pass endpoint_url
to boto3.client
to use the endpoint-specific host name. I am not able to use parameters
because this is not supported.
Describe the solution you’d like
Perhaps allowing to pass additional keyword arguments to the client
method.
Issue Analytics
- State:
- Created 2 years ago
- Comments:17 (10 by maintainers)
Top Results From Across the Web
Configuration — Boto3 Docs 1.26.34 documentation - AWS
A Config object that's created and passed as the config parameter when creating a client; Environment variables; The ~/.aws/config file.
Read more >Session reference — Boto3 Docs 1.26.33 documentation - AWS
A session stores configuration state and allows you to create service clients and resources. Parameters. aws_access_key_id (string) -- AWS access key ID ...
Read more >Credentials — Boto3 Docs 1.26.33 documentation - AWS
Passing credentials as parameters in the boto.client() method; Passing credentials as parameters when creating a Session object; Environment variables ...
Read more >Extensibility guide — Boto3 Docs 1.26.33 documentation - AWS
An introduction to the event system¶ ; add_my_bucket is registered such that the handler will inject the value ; 'mybucket for the ;...
Read more >Low-level clients — Boto3 Docs 1.26.32 documentation - AWS
Service operations map to client methods of the same name and provide access to the same operation parameters via keyword arguments:.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Releasing it first thing tomorrow morning @gshpychka
Thanks everyone! The more I look into the Parameters utility the more I find we should’ve accepted a whole boto Client only. It would simplify our logic to maintain it, and also make it easier for customers to stub for unit testing, use snapshot testing with placebo, or in this case pass a different endpoint_url.
We won’t be able to add this now due to our pause and bandwidth. I do believe there are other customers who will eventually be blocked by this too, so if anyone could create a PR to accept a Client I’ll happily work with you to get it merged as an exception.
Note: I’m following this issue for boto to eventually add support to
endpoint_url
via environment variables as it’s a common ask.