[Enhancement]: Elastic Network Interface configurable idle timeout for connection tracking

[flipsed]

Description

In November last year, aws introduced configurable idle timeout on the network interfaces. It would a great enhancement to be able to customise this in the aws_network_interface resource.

Affected Resource(s) and/or Data Source(s)

aws_network_interface

Potential Terraform Configuration

resource "aws_network_interface" "test" {
  subnet_id       = aws_subnet.public_a.id
  private_ips     = ["10.0.0.50"]
  security_groups = [aws_security_group.web.id]
  idle_timeout    = 432000

  attachment {
    instance     = aws_instance.test.id
    device_index = 1
  }
}

References

https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-configurable-idle-timeout-for-connection-tracking/

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-connection-tracking.html#connection-tracking-timeouts

in this blog post AWS recommends tuning the timeout all the way down to 45s, given the a 2h default timeout for idle TCP connections is very high https://aws.amazon.com/blogs/networking-and-content-delivery/implementing-long-running-tcp-connections-within-vpc-networking/

Would you like to implement a fix?

No

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.