aws_flow_log - add support for sending to S3

[ryandeivert]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Support S3 as a delivery destination for VPC Flow Logs. As of 2018-08-08, AWS announced support for sending vpc flow logs to s3 (as oppose to the currently supported CloudWatch Logs group). The API docs are updated to include this support, and the aws-sdk-go has been updated to support this. The interface has changed a bit for this API, and different parameters are now used.

New or Affected Resource(s)

• aws_flow_log

Potential Terraform Configuration

resource "aws_flow_log" "test_flow_log" {
  log_destination_type = "s3"
  log_destination      = "${aws_s3_bucket.test_bucket.arn}"
  iam_role_arn         = "${aws_iam_role.test_role.arn}"
  resource_type        = "VPC"
  resource_ids         = ["${aws_vpc.default.id}"]
  traffic_type         = "ALL"
}

References

• N/A

[ryandeivert]

note - I am happy to work on this (can you assign to me?)

[bflad]

Support for new log_destination and log_destination_type arguments to enable sending to S3 has been merged and will release with version 1.42.0 of the AWS provider sometime in the next week or so. Thanks @ryandeivert and @ewbankkit!

[bflad]

This has been released in version 1.42.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!