Recently I used an AWS Fortigate cloud VM and got the SSL-VPN setup and running within a couple hours. If I recall, you pay an hourly price for the EC2 instance, an hourly price for the EBS (what AWS calls hard drive space) partitioned for the EC2 instance, and an hourly price for the Fortigate VM. There’s also a cost associated for having an elastic IP address associated to a server that’s not running, but it’s pretty minimal if I recall correctly. Also, I believe Fortinet pushes that you get a FortiCare license for the VM, but I never did, so YMMV.
You’re over thinking it. Try nordvpn, you can get a static IP assigned just for you. SaaS service so you don’t need to worry about managing the backend.
I was using the Fortigate’s built-in NATing and it worked like a charm after I setup the IPv4 routing policies for the SSL-VPN, so you probably wouldn’t need a NAT gateway from AWS!