Amazon EC2 now offers configurable idle timeouts for TCP established, UDP stream, and UDP non-stream connections, allowing customers to optimize connection tracking resource usage and prevent connection exhaustion for various workloads by aligning the timeouts with their traffic patterns and network service configurations.

<div>
<p>This article introduces a new feature in Amazon EC2 that allows configuring idle timeout values for connection tracking. It explains how connection tracking works and the default timeout values for different connection states (e.g., TCP established, UDP stream). Previously, EC2 had predefined timeout values, but now users can customize these timeouts for their workloads.</p>
<p>Specifically, the article covers:</p>
<ul>
<li>Overview of the new configurable idle timeout feature for connection tracking</li>
<li>Refresher on connection tracking and default timeout values</li>
<li>How to configure timeouts using AWS CLI, SDKs, Console, or CloudFormation</li>
<li>Common scenarios where adjusting timeouts can be beneficial:
<ul>
<li>TCP connections through AWS services like Network Load Balancers</li>
<li>UDP-based workloads like DNS</li>
<li>High number of TCP connections that need to be closed properly</li>
<li>UDP authentication protocols with delays between request and reply</li>
</ul>
</li>
<li>Conclusion highlighting the benefits of configurable timeouts</li>
</ul>
</div>


Related articles