-
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
guardduty.list_findings API call states invalid value #3890
Comments
Hi @gyoza, thanks for reaching out. I wasn't able to reproduce this behavior using the sample code you provided. Could you provide debug logs of this behavior? You can get debug logs by adding |
|
Thanks for providing those. Could you tell me how you're making the call after you create the page iterator? It'd also be helpful to know the format of your Also, it looks like PageSize is required to be 50 or less. That's not part of the problem, just thought I'd mention that. |
Yea sure.. Thanks for the pagesize tip :D but the detectorid is something like Also after creating the iterator the next thing is a simple for loop through the Just anecdotally, this page iterator works describe_instances, etc. |
Is your |
I might have missed one char
…On Fri, Oct 6, 2023, 5:25 PM Ryan F. ***@***.***> wrote:
Is it actually only 30 characters? If so, that would explain this.
—
Reply to this email directly, view it on GitHub
<#3890 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEJWBT75TUX6XMXBKONXZTX6CHPDAVCNFSM6AAAAAA5WCOTZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGQ4TMOJSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ya its 31 Characters still having issues. |
Those are supposed to be 32 characters. Try deleting your detector and making a new one, which should (hopefully) generate one that is 32 characters long. |
Hey thank you very much! It does appear I had a bad value. |
|
Describe the bug
Using guardduty.list_findings with DetectorId="string" produces an error stating 'detectorId has an invalid value'
Expected Behavior
The api call to accept my str.
Current Behavior
Produces this
Reproduction Steps
Possible Solution
None avail:(
Additional Information/Context
I am 100% sending a string and it is the correct detector ID as I am using it in terraform so.. I think i found an actual bug.
SDK version used
boto3==1.28.61 botocore==1.31.61
Environment details (OS name and version, etc.)
The text was updated successfully, but these errors were encountered: