Sine I am using the BYOL lic received from F5, I did the bellow modifications and ran the stack back after deleting old PAYG one ..
It seems Clod formation does not like the Modification and get an exit error again .. According to Github documentation , it looks ok .. Can f5 you help to check if the parameters given bellow are OK
Custom parameters which I used for POC
+++++++++++++++++++++++++++++
Restricted Source Address to BIG-IP - 0.0.0.0/0
Restricted Source Address to Application - 0.0.0.0/0
Hi,
I was able to deploy the “https://github.com/F5Networks/f5-aws-cloudformation-v2/tree/main/examples/failover” New Stack without any errors .. However by default it support 16.1.3.3-0.0.3 PAYG-Best Plus 25Mbps ..
Sine I am using the BYOL lic received from F5, I did the bellow modifications and ran the stack back after deleting old PAYG one ..
It seems Clod formation does not like the Modification and get an exit error again .. According to Github documentation , it looks ok .. Can f5 you help to check if the parameters given bellow are OK
Custom parameters which I used for POC +++++++++++++++++++++++++++++ Restricted Source Address to BIG-IP - 0.0.0.0/0 Restricted Source Address to Application - 0.0.0.0/0
Runtime Init Package : - https://cdn.f5.com/product/cloudsolutions/f5-bigip-runtime-init/v1.6.1/dist/f5-bigip-runtime-init-1.6.1-1.gz.run BIG-IP Runtime Init config used for BIGIP instance A :-https://f5-cft-v2.s3.amazonaws.com/f5-aws-cloudformation-v2/v3.0.0.0/examples/failover/bigip-configurations/runtime-init-conf-3nic-byol-instance01-with-app.yaml BIG-IP Runtime Init config used for BIGIP instance B :-https://f5-cft-v2.s3.amazonaws.com/f5-aws-cloudformation-v2/v3.0.0.0/examples/failover/bigip-configurations/runtime-init-conf-3nic-byol-instance02-with-app.yaml
License key for BIG-IP instance 01 : XXXXXXX License key for BIG-IP instance 02 : XXXXXXX
F5 BIG-IP Image : 16.1.3.3-0.0.3**BYOL-All Modules 2Boot
All stuff run as Global Admin now , so there cant be IAM issues ..