2.5 with many tunnels - Apply Changes fails
-
Is there any way you can try at least loading the IPsec portion of that configuration in a non-AWS system?
It's difficult to tell if it's related to IPsec or if there is a general problem with AWS.
The only other potentially-related report I've seen is a report of a kernel panic on AWS with someone that has even more IPsec tunnels than you, but as far as I'm aware they were not experiencing any slowness or boot delays.