From Connected to Resilient: Cloud-Native Payment Connectivity on AWS

This article presents four production-hardening patterns for payment connectivity on AWS using PrivateLink and Resource Gateway, addressing operational challenges with persistent-session payment protocols like ISO 8583.

• Pattern A: TCP keepalive configuration prevents NLB idle timeout disconnections during off-peak windows
• Pattern B: Weighted target groups and lifecycle hooks enable zero-downtime maintenance of stateful payment backends
• Pattern C: Dedicated NLBs per tenant provide connection-level isolation and independent capacity guarantees
• Pattern D: External health monitoring and scoped security groups harden FMI-initiated Resource Gateway data pulls
• Patterns apply independently; start with A as baseline, layer B-D based on operational maturity
• Security includes MACsec encryption on Direct Connect, TLS across PrivateLink, and private DNS failover
• Observability via CloudWatch metrics, NLB access logs, and Route 53 health checks for sub-minute failover

These patterns provide architects with production-ready operational playbooks for resilient payment connectivity on AWS, moving beyond reference architectures to battle-tested infrastructure patterns.