1.1--- a/20231101.org	Tue Aug 27 21:35:44 2024 -0400
     1.2+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.3@@ -1,21 +0,0 @@
     1.4-* AWS usage
     1.5-:PROPERTIES:
     1.6-:ID:       b2f8d58f-a486-4fe9-895b-504987c0f63d
     1.7-:END:
     1.8-We're leveraging AWS for some of our public web servers for now. It's
     1.9-really not realistic to expect that my home desktop and spotty Comcast
    1.10-internet can serve any production workflow. What it /is/ capable of is
    1.11-a private VPN, which can communicate with AWS and other cloud VPN
    1.12-depots via WireGuard ([[https://dev.to/gabrieltetzner/setting-up-a-vpn-with-wireguard-server-on-aws-ec2-4a49][article]]).
    1.13-
    1.14-I currently use Google Domains for nas-t.net, otom8.dev, and
    1.15-rwest.io - but that business is now owned by squarespace, so I would
    1.16-rather move it to Route53.
    1.17-
    1.18-We have archlinux ec2 image builds [[https://wiki.archlinux.org/title/Arch_Linux_AMIs_for_Amazon_Web_Services][here]] and [[https://gitlab.com/anemos-io/archlinux-ec2][here]] - only half work and not
    1.19-maintained, but it's a start. I'm not even sure if I should stick with
    1.20-arch or cave and use Ubuntu or AWS Linux. We can serve the static
    1.21-services with little cost, the only big spender will be the heptapod
    1.22-instance which requires a larger instance and some workers.
    1.23-
    1.24-We'll try to keep the cost at or around $30/month.