Closed ilg closed 1 week ago
FWIW, this does seem to occur every time Secrets Manager rotates the credentials, but only within the already-running web application server. As soon as the worker thread/process restarts, the boto3 client creation call works fine. Given this, I should be able to debug or test further by manually triggering credential rotation.
Thanks for reaching out. When you're able to, please provide a code snippet for reproducing the issue, as well as debug logs (with sensitive info redacted) by adding boto3.set_stream_logger('')
to your script.
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.
Describe the bug
Unfortunately, I don't have much in the way of detail nor consistent repro steps, but the stack trace seems to point at botocore. This most likely happened when AWS Secrets Manager rotated a credential, leading to my code's call to create a secrets manager client to get the new secret, and that led into
RecursionError: maximum recursion depth exceeded in comparison
(though the code works fine most of the time). This is running inside a docker container on an EC2 instance, all managed with Elastic Beanstalk.Expected Behavior
No infinite recursion
Current Behavior
Reproduction Steps
boto3.client("secretsmanager", "us-west-2")
seems pretty self-contained, but works fine the vast majority of the time, so I'm not sure what happened here.Possible Solution
No response
Additional Information/Context
No response
SDK version used
boto3==1.34.100
Environment details (OS name and version, etc.)
Linux [hostname] 5.10.214-202.855.amzn2.x86_64 #1 SMP Tue Apr 9 06:57:12 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux