Using BIG-IP GTM to Integrate with Amazon Web Services
This is the latest in a series of DNS articles that I've been writing over the past couple of months. This article is taken from a fantastic solution that Joe Cassidy developed. So, thanks to Joe f...
Published Jun 18, 2014
Version 1.0
BullWeivel
Nimbostratus
NimbostratusNot sure how this article is relevant since the CNAME pool would need to be against a FQDN. For example anything you do with AWS the pool members would need to be a FQDN since the IPs change based upon whatever AWS wants to do.
The original article for 11.x was perfect. Right now though that advanced button is gone in the newer versions so no clue on how to do with strictly using a GTM.
What is odd - the LTM you can put pool members with a FQDN but not with the GTM Pool members those must be a IP or server.
nabf5guyAltostratus
"What is odd - the LTM you can put pool members with a FQDN but not with the GTM Pool members those must be a IP or server."
That's not actually correct. You can use a Wide IP or an FQDN as a static entry as pool members.
In my work environment we use FQDNs when we don't care about health checking and Wide IPs when we do. We rely on federation with LTMs that are able to resolve our cloud endpoints and health check them. It's an object heavy configuration, but it does work.- BullWeivel
Why not just use a script for the health monitor on the GTM? We are trying to figure out a way to load balance between internal and external AWS resources to save $$$.
We have several issues and I think right now the big one is ensure health checking against the FQDN. Which maybe using a "Scripted" health check approach would be the answer so we can keep all of this on the GTM.
Another issue we are hitting is randomly some of the AWS won't resolve every time. Wondering if it has to do with caching so looking to try and simplify maybe our solution.