F5 A/P Deployment on AWS stack failure after things running for 15 minutes+

[cnelvitigala]

While performing F5 A/P Deployment on AWS , i am getting stack failure after things running for 15 minutes+ at last .

https://github.com/F5Networks/f5-aws-cloudformation-v2/tree/main/examples/failover
-New Stack via Cloud formation
-All parameters I used as default , except SSH public key, 0.0.0.0/0 access and cfeS3Bucket (tried default and my own too)
-Form image default it load as 16.1.3.3-0.0.3**PAYG-Best Plus 25Mbps .. I have PAYG as well as BYOL subscription Enable

It does all back ground work and fail last moment with this 3 errors ..

BigIpInstance02 - Embedded stack arn:aws:cloudformation:us-east-2:039184453827:stack/BigIp-Failover-Example-BigIpInstance02-xxxxxxxxxxxxx/5fbd3310-258f-11ee-8d06-02c0efc76543 was not successfully created: Internal Failure

BigIpInstance01 - Embedded stack arn:aws:cloudformation:us-east-2:039184453827:stack/BigIp-Failover-Example-BigIpInstance01-xxxxxxxxxxxxx/5fc437f0-258f-11ee-9d9a-02b027893695 was not successfully created: Internal Failure

Application - Embedded stack arn:aws:cloudformation:us-east-2:039184453827:stack/BigIp-Failover-Example-Application-xxxxxxxxxxxxx/5fcfa9a0-258f-11ee-be82-0a3b5bfa2093 was not successfully created: Internal Failure

[mikeshimkus]

Hi @cnelvitigala, since both the BIG-IP and application instances failed to create, this tells me it's not an error with BIG-IP but probably something environmental.

Can you check the EC2 console and see if the instances were created? If so, are they in a running state?

If the instances are running, can you SSH into the BIG-IP instance and gather the /var/log/cloud/bigIpRuntimeInit.log?

If the instances were not created or are not running, you may want to check the EC2 events for any indication of why it failed. Issues we've seen in the past are 1) not enough compute quota to provision the instances or 2) instance type unavailable in the selected region, etc.

thanks

[cnelvitigala]

Thanks Mike . I checked quota and instance type .. It looks good ..As u described, seems to be IAM issue becaue it does not kickoff EC2 .. let me test it with global Admin rights and keep u update ..

Also , if I do a BYOL for 3 NIC ... Does bellow parameters good ...

runtime-init-conf-3nic-byol-instance01-with-app.yaml
runtime-init-conf-3nic-byol-instance02-with-app.yaml

{
"ParameterKey": "bigIpImage",
"ParameterValue": "15.1.8.2-0.0.17**BYOL-All Modules 2Boot"
}