Using VPC Endpoints with Cloud Failover Extension
Introduction
Have you heard of the new F5 Cloud Failover Extension? Well if you haven’t, I encourage you to go out and read about this new feature. CFE is an iControl LX extension that provides L3...
Published Apr 27, 2020
Version 1.0
Arnulfo_Hernand
Employee
EmployeeArnulfo_HernandEmployee
Employee
TJ_Vreugdenhil
Cirrus
CirrusHey - Thanks
I just opened an issue at Github.
The setup is an F5 HA Pair in the same AZ. HA Configsync/Failover is working over internal NIC. However there is 2 NICS for internal, and 1 NIC for external, both acting as reverse proxies, so all three NICS are added to the declaration. Yes I created both the S3 gateway endpoint and S3 endpoint as indicated in this article. I will look at the S3 bucket - It does have the proper tag matching the declaration. Here is the "f5cloudfailoverstate.json" in the F5 S3 bucket:
{"taskState":"FAILED","message":"Failover failed because Recovery operations are empty, advise reset via the API","timestamp":"2020-05-05T17:03:39.568Z","instance":"ip-10-10-8-10.us-east-2.compute.internal","failoverOperations":{"addresses":null,"routes":null}}