Open julianbueno opened 4 years ago
Hey @julianbueno π Thank you for taking the time to file this issue! Given that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still experiencing this behavior?
Community Note
Terraform Version
Terraform v0.12.15
Affected Resource(s)
Terraform Configuration Files
Debug Output
Error: Creating GuardDuty Member failed: BadRequestException: The request is rejected because the input detectorId is not owned by the current account. status code: 400, request id: cff90ae4-cecc-4d87-8157-47eb6e4f237b
on ../../modules/guardduty/main.tf line 14, in resource "aws_guardduty_member" "child_account": 14: resource "aws_guardduty_member" "child_account" {
Panic Output
N/A
Expected Behavior
The member account is added to the master account in GD
Actual Behavior
Error: The request is rejected because the input detectorId is not owned by the current account.
Steps to Reproduce
terraform apply
on the HCL above from you master accountImportant Factoids
The master account has already the GD enabled, that's the reason is commented If I uncomment L5-7, L16 and L26 I got:
References