EC2 deploy fails when ipsec is enabled but wireguard is not enabled in config.cfg

[alanning]

Describe the bug

Using the "./algo" deployment method on macOS fails when wireguard_enabled: true is set in config.cfg.

In the country I am currently in, I am only able to connect successfully using IPSec; I have never successfully connected to my existing Digital Ocean instances of algo with Wireguard. From the wireguard clinet logs, the "handshake" never succeeds for my macOS and iOS devices. So I tried disabling Wireguard when setting up a new algo instance in EC2.

This causes the EC2 instance creation step in the CloudFormation stack to fail, however, with an "...did not stabilize" error and then a stack rollback is attempted. The rollback also fails due to lack of permissions but that is a separate issue.

Enabling both ipsec and wireguard works as expected, the algo instance is created successfully.

I realize most people will use wireguard with algo so this is probably a low-priority issue. Wanted to post here in case others run into it, though, and it's easy to reproduce.

To Reproduce

Steps to reproduce the behavior:

1. Set up EC2 as instructed here
2. Edit config.cfg to ipsec_enabled: true, wireguard_enabled: true
3. Follow steps in Deploy the Algo Server
4. Choose 3 (EC2) when prompted for where to install

Expected behavior

Algo server deployed successfully to EC2 with IPSec enabled but without wireguard.

Additional context

None

Full log

I don't have a copy of the log failure message.