I haven't used Route53 custom A records, but we use many origins with hostnames, generally CNAME records. For your situation, you could treat them as one "DNS name" origin, and that should work pretty well.
Elastic IPs would be ideal for Imperva Cloud WAF Edge Load Balancing, if you have that feature in your subscription, but you're probably not trying to re-architect your system.
------------------------------
David Sloane
VP Production IT
Bonterra LLC
MA
------------------------------
Original Message:
Sent: 12-15-2022 11:08
From: Steven Richards
Subject: Deployment Models with AWS Elastic IPs and NLB
Hi,
Are there any links to documentation/best practices/guides on setting up the Cloud WAF where the domain name is in Route53 as an A record which then distributes traffic across 3 Elastic IPs which are attached to a NLB?
I cannot find anything in the main guides that cover the above. We utilise a NLB as we need to accept traffic at Layer 4 and not just Layer 7. The use of Elastic IPs is so that our clients can whitelist the IPs (if needed) in their Firewalls.
Thanks.
#CloudWAF(formerlyIncapsula)
------------------------------
Steve Richards
------------------------------