This project makes it really easy (or at least as easy as it can be) to run a lightning node cheaply in the cloud. It contains a CDK (https://docs.aws.amazon.com/cdk/latest/guide/home.html) stack that sets up the required networking and an EC2 instance to run your node, and a setup script that installs and configures LND using neutrino as the backend. The EC2 instance used is a t4g.micro, an ARM-based instance with a gig of memory and two cores which runs just over $6/month, or just below $4/month if you commit to a year through a Reserved Instance (https://aws.amazon.com/ec2/pricing/reserved-instances/). So for ~$6 a month you can run a lightning node and not worry about hardware, power, networking, etc. Or if you want to run it for 2 weeks to try some experiment or something, you can and then just tear it down and stop the meter!

Things you need to do first

Install the AWS CLI (https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) and set it up with AWS creds.
Install the CDK CLI (https://docs.aws.amazon.com/cdk/latest/guide/cli.html)

Instructions

update "lightningnode-stack.ts" depending on your Availability Zones (AZs)
cd into the ThunderCloud root and do npm install
run cdk bootstrap (only needed once per account)
run cdk deploy
watch the pretty bars fill up
It will spit out something like this:

Outputs:
ThundercloudStack.DownloadKeyCommand = aws secretsmanager get-secret-value --secret-id ec2-ssh-key/cdk-keypair/private --query SecretString --output text > cdk-key.pem && chmod 400 cdk-key.pem
ThundercloudStack.IPAddress = 54.159.56.96
ThundercloudStack.KeyName = cdk-keypair
ThundercloudStack.sshcommand = ssh -i cdk-key.pem -o IdentitiesOnly=yes ec2-user@54.159.56.96

Copy and paste that first command (aws secretsmanager ...) to download the SSH key for your node

Copy and paste the ssh command (last line) to SSH to your node.
Do ps ax on the instance and look for lnd. if its not running, give it a minute, the setup script is stil running.
cat ~/.lnd/wallet_password and copy it down. Then do lncli create to create a new lightning wallet. Supply the password you just wrote down (or copy/paste it). choose "no" when it asks if you want to encrypt the wallet. It will spit out a 24 word seed phrase WRITE DOWN YOUR SEED WORDS
That's it! you're done! you now have an LND node running in the cloud!

You can use lncli to open channels, create invoices, do all the fun lightning things. bos is also installed if you want to use it for bos-flavored channel balancing, batch channel opens, etc.

By default, the grpc port will not be accessible. There's a security group that get's created for it, but isn't attached to the node. If you uncomment the line that says // instance.addSecurityGroup(rpcSg); and run cdk deploy, it'll attach that security group and you'll be able to get to the grpc ports. Want to close them up? comment that line out and do cdk deploy again and it'll detach the security group.

Want to add a second (or third or fourth) node? Go into bin/thundercloud.ts and add a line at the end like new LightningNode(app, 'SecondLightningNode', {stackName: "SecondLightningNode"});, then do cdk deploy SecondLightningNode.

Shutting down the node

Go into the project root and do cdk destroy

There is no step 2. You can also go find the stack in CloudFormation and delete it there. either way works.

Stuff to look at and customize

You'll want to change the node alias. Either set the right line in lib/configure-node.sh before you run cdk deploy, or update ~/.lnd/lnd.conf and restart lnd on the instance. either works.
Want to see the CFn template that CDK creates? do cdk synth from the project root and it'll spit out the yaml template that Cloudformation will use to create the resources.
When your node first boots, it'll execute lib/configure-node.sh as root. This is where lnd gets downloaded and configured. Feel free to tweak it to your needs.
All the infrastructure is defined in lib/lightningnode-stack.ts. You can add/remove/change things there to your liking. doing a cdk deploy will update the stack. Changing some instance properties will result in the node being deleted and recreated. Be careful changing the instance.
If you need to change the AZs that the stack uses for VPC subnets, check out the get availabilityZones() in lib/lightningnode-stack.ts
This stack will also create an S3 bucket to hold static channel backups, and the instance will be configured to upload a channel backup everytime it changes. You can find the name of the bucket in the stack outputs (along wih the IP and keyname). Check out /etc/incron.d/channelbackup to see the configuration. The aws s3 ... command will run whenever the ~/.lnd/data/chain/bitcoin/mainnet/channel.backup file is closed after writing.

FAQ

Why neutrino? I wanted to make the instance small and cheap. If you want to run a full bitcoind backend (even in pruned node), you'll need an instance with more memory to get through the IBD. You're welcome to do that! edit the config file in the configure script and add bitcoind.
Does this run RTL or Thunderhub? No. Maybe it will in the future. Right now it's lncli and bos only.

Possible future enhancements (PR's welcome!)

set up RTL or Thunderhub
would be cool to do a 1/1 autoscaling group, but need to make sure channel backup is SOLID
second instance for a watchtower
use ec2 instance-connect instead of the ssh key

Credits

Most of the lnd.conf and the systemd unit script were cribbed from Alex Bosworth's run-lnd repo (https://github.com/alexbosworth/run-lnd)