AWS

A Percona support case reveals that PostgreSQL standby replication lag on AWS FSx can stem from hidden EC2 single-flow bandwidth limits rather than storage performance issues. The root cause was tied to how EC2 instances handle bandwidth allocation for individual network flows when connected to FSx. This constraint creates a bottleneck for replication traffic, causing the standby to fall behind the primary despite adequate overall throughput.

• FSx replication lag may be caused by EC2 single-flow bandwidth caps, not storage IOPS.
• Check EC2 instance type limits for single-flow throughput when troubleshooting FSx mounts.
• AWS Support involvement is often required to clarify specific instance flow constraints.
• Monitor replication lag closely when using FSx with high-throughput database workloads.
• Consider load balancing or multiple connections if single-flow limits are exceeded.

Amazon EC2 C8gn instances powered by AWS Graviton4 processors are now available in the Europe (Paris) region. These instances deliver up to 30% better compute performance than the previous C7gn generation. They feature 6th generation AWS Nitro Cards and support up to 600 Gbps network bandwidth, the highest among network-optimized EC2 instances.

• C8gn instances are now provisionable in EU (Paris) for low-latency workloads.
• Graviton4 chips offer 30% compute uplift over Graviton3-based C7gn instances.
• 600 Gbps network bandwidth supports high-throughput network virtual appliances.
• Optimized for CPU-based AI/ML inference and data analytics tasks.
• Leverage Nitro Cards for enhanced networking without hypervisor overhead.