AWS AmazonRDS documentation change
Summary
Updated TCP keepalive parameter names from 'tcp_keepalive_time', 'tcp_keepalive_intvl', and 'tcp_keepalive_probes' to 'tcp_keepalives_idle', 'tcp_keepalives_interval', and 'tcp_keepalives_count' respectively
Security assessment
The changes are purely technical updates to parameter names without any indication of addressing a security vulnerability or adding security features.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.BestPractices.FastFailover.md index 8ecd5d324..d7044a087 100644 --- a/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.BestPractices.FastFailover.md +++ b/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.BestPractices.FastFailover.md @@ -51 +51 @@ Make sure to set the following TCP keepalive parameters: - * `tcp_keepalive_time` controls the time, in seconds, after which a keepalive packet is sent when no data has been sent by the socket. ACKs aren't considered data. We recommend the following setting: + * `tcp_keepalives_idle` controls the time, in seconds, after which a keepalive packet is sent when no data has been sent by the socket. ACKs aren't considered data. We recommend the following setting: @@ -53 +53 @@ Make sure to set the following TCP keepalive parameters: -`tcp_keepalive_time = 1` +`tcp_keepalives_idle = 1` @@ -55 +55 @@ Make sure to set the following TCP keepalive parameters: - * `tcp_keepalive_intvl` controls the time, in seconds, between sending subsequent keepalive packets after the initial packet is sent. Set this time by using the `tcp_keepalive_time` parameter. We recommend the following setting: + * `tcp_keepalives_interval` controls the time, in seconds, between sending subsequent keepalive packets after the initial packet is sent. Set this time by using the `tcp_keepalives_idle` parameter. We recommend the following setting: @@ -57 +57 @@ Make sure to set the following TCP keepalive parameters: -`tcp_keepalive_intvl = 1` +`tcp_keepalives_interval = 1` @@ -59 +59 @@ Make sure to set the following TCP keepalive parameters: - * `tcp_keepalive_probes` is the number of unacknowledged keepalive probes that occur before the application is notified. We recommend the following setting: + * `tcp_keepalives_count` is the number of unacknowledged keepalive probes that occur before the application is notified. We recommend the following setting: @@ -61 +61 @@ Make sure to set the following TCP keepalive parameters: -`tcp_keepalive_probes = 5` +`tcp_keepalives_count = 5` @@ -66 +66 @@ Make sure to set the following TCP keepalive parameters: -These settings should notify the application within five seconds when the database stops responding. If keepalive packets are often dropped within the application's network, you can set a higher `tcp_keepalive_probes` value. Doing this allows for more buffer in less reliable networks, although it increases the time that it takes to detect an actual failure. +These settings should notify the application within five seconds when the database stops responding. If keepalive packets are often dropped within the application's network, you can set a higher `tcp_keepalives_count` value. Doing this allows for more buffer in less reliable networks, although it increases the time that it takes to detect an actual failure. @@ -74,3 +74,3 @@ We recommend doing so by using the command line with the following commands. Thi - sudo sysctl net.ipv4.tcp_keepalive_time=1 - sudo sysctl net.ipv4.tcp_keepalive_intvl=1 - sudo sysctl net.ipv4.tcp_keepalive_probes=5 + sudo sysctl net.ipv4.tcp_keepalives_idle=1 + sudo sysctl net.ipv4.tcp_keepalives_interval=1 + sudo sysctl net.ipv4.tcp_keepalives_count=5 @@ -80,3 +80,3 @@ We recommend doing so by using the command line with the following commands. Thi - tcp_keepalive_time = 1 - tcp_keepalive_intvl = 1 - tcp_keepalive_probes = 5 + tcp_keepalives_idle = 1 + tcp_keepalives_interval = 1 + tcp_keepalives_count = 5