-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sporadic Issues with Boto3 in a Python Microservice Accessing S3 #4277
Comments
Hey @itburkealert, thanks for reaching out. S3 has some pretty detailed documentation about this particular error. I'd recommend taking a look at that. If nothing there helps resolve your issue, I can investigate further with debug logs. You can get debug logs by adding |
Hey @RyanFitzSimmonsAK thanks for looking into this matter with me. The documentation is definitely thorough however we are dealing with a scenario here where the error starts occurring randomly and a restart of our micro service resolves the matter for what appears to be a random period of time. We'll look into providing more details logs per your second option. |
This might have been due to a refresh issue that was fixed in 1.34.41. I'd recommend upgrading to Python 3.8 and a minimum Boto3 version of 1.34.41. Please let me know if you continue to have issues. |
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
Original issue : aws/aws-sdk#817
Expected Behavior
N/A
Current Behavior
N/A
Reproduction Steps
N/A
Possible Solution
N/A
Additional Information/Context
N/A
SDK version used
N/A
Environment details (OS name and version, etc.)
N/A
The text was updated successfully, but these errors were encountered: