Closed JihadMotii-REISys closed 1 year ago
Hi @JihadMotii-REISys. Are you creating the S3 bucket and the folder using Terraform, or do they already exist? Is there more to the Terraform configuration?
I was not able to reproduce the error you're getting. If the folder does not exist in the bucket, I get the error you're seeing. When the folder has been created, Terraform is able to successfully create the publishing destination.
Hey @gdavison sorry for the delayed response,
Yes, they are both created using Terraform and this bucket with the same folder prefix are used in CloudWatch export logs without any issue. I'm not sure why GuarDuty is only the one complaining about it. Thanks!
@gdavison this is still a problem and the only workaround is to setup this destination through AWS Console then delete it after that you can rerun terraform and it will be executed successfully.
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.
If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. 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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Expected Behavior
The GuardDuty publishing destination should be created in the provided
destination_arn
as the S3 bucket including the prefixarn:aws:s3:::my-common-logs/MY_PREFIX_FOLDER/
do exist.Actual Behavior
Currently it throws an exception as shown in the output section.
Is this a bug or do I have to provide these information in a different structure?
Can you please help me with this issue?
Thanks in Advance!
0000