- Newest
- Most votes
- Most comments
That error originates from the urllib3
. The goal of client_config
strategy is to find a way to get the desired configuration passed through the code down to the urllib3
level. We would need to know more about what you're doing in the Python to provide any additional help.
As mentioned in many of the comments of the github issue you cited...
- are you using any concurrency techniques in Python that might "blow out the pool"?
- do you have any global variables that could be persistent across sessions?
- which AWS service clients are you using?
- how often is your Lambda being triggered?
- how long does your Lambda run for?
Subsequent Lambda runs can retain references to global object in memory from the previous run if you're not careful to re-initialize your variables at the start of each run. I have been bitten by that this in the past. This could be happening here.
If you have concurrent Python in your Lambda (threading, multiprocessing, concurrent.futures, etc) you might try removing that and using Step Functions to manage the concurrency for you.
It is difficult to make any solid suggestions without more understanding of your current process.
Relevant content
- asked 2 months ago
- Accepted Answerasked 14 days ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago