-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: aws_guardduty_invite_accepter BadRequestException #38833
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hey @connor-tyndall 👋 Thank you for taking the time to raise this! So that we have the information we need to look into this, can you supply a sample Terraform configuration that can be used to reproduce this and, if possible, debug logging (redacted as needed)? |
I can confirm the same thing started happening for us as well. With no changes to the code we can see the invitation is being sent, but the client can't accept it with the same error as above:
And the error:
No code changes happened to this area in recent weeks and we notice this behavior now. |
Maybe relates #38400? |
I can reproduce with our acceptance tests: % AWS_GUARDDUTY_MEMBER_ACCOUNT_ID=... AWS_GUARDDUTY_MEMBER_EMAIL=... make testacc TESTARGS='-run=TestAccGuardDuty_serial/InviteAccepter' PKG=guardduty
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.23.0 test ./internal/service/guardduty/... -v -count 1 -parallel 20 -run=TestAccGuardDuty_serial/InviteAccepter -timeout 360m
=== RUN TestAccGuardDuty_serial
=== PAUSE TestAccGuardDuty_serial
=== CONT TestAccGuardDuty_serial
=== RUN TestAccGuardDuty_serial/InviteAccepter
=== RUN TestAccGuardDuty_serial/InviteAccepter/basic
invite_accepter_test.go:29: Step 1/2 error: Error running apply: exit status 1
Error: accepting GuardDuty Invitation (): operation error GuardDuty: AcceptInvitation, https response error StatusCode: 400, RequestID: 6cf0bab9-d10a-4c58-bb42-040346540c7e, BadRequestException: The request is rejected because an invalid or out-of-range value is specified as an input parameter.
with aws_guardduty_invite_accepter.test,
on terraform_plugin_test.tf line 37, in resource "aws_guardduty_invite_accepter" "test":
37: resource "aws_guardduty_invite_accepter" "test" {
--- FAIL: TestAccGuardDuty_serial (71.01s)
--- FAIL: TestAccGuardDuty_serial/InviteAccepter (71.01s)
--- FAIL: TestAccGuardDuty_serial/InviteAccepter/basic (71.01s)
FAIL
FAIL github.com/hashicorp/terraform-provider-aws/internal/service/guardduty 75.719s
FAIL
make: *** [testacc] Error 1 |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.65.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I confirm this now works on aws provider v 5.65.0. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.5.4
AWS Provider Version
5.62.0
Affected Resource(s)
Expected Behavior
Actual Behavior
aws_guardduty_invite_accepter
resource is failing to accept the GuardDuty invite."The request is rejected because an invalid or out-of-range value is specified as an input parameter."
Relevant Error/Panic Output Snippet
The request is rejected because an invalid or out-of-range value is specified as an input parameter.
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: