changeset 6: |
e0ef412d04f8 |
parent 5: |
81af1bf9793e |
child 7: |
e0ee195bea7d |
author: |
ellis <ellis@rwest.io> |
date: |
Wed, 01 Nov 2023 19:58:30 -0400 |
files: |
scratch/20231101.org |
description: |
scratch |
1.1--- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2+++ b/scratch/20231101.org Wed Nov 01 19:58:30 2023 -0400
1.3@@ -0,0 +1,18 @@
1.4+* AWS usage
1.5+We're leveraging AWS for some of our public web servers for now. It's
1.6+really not realistic to expect that my home desktop and spotty Comcast
1.7+internet can serve any production workflow. What it /is/ capable of is
1.8+a private VPN, which can communicate with AWS and other cloud VPN
1.9+depots via WireGuard.
1.10+
1.11+I currently use Google Domains for nas-t.net, otom8.dev, and
1.12+rwest.io - but that business is now owned by squarespace, so I would
1.13+rather move it to Route53.
1.14+
1.15+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.16+maintained, but it's a start. I'm not even sure if I should stick with
1.17+arch or cave and use Ubuntu or AWS Linux. We can serve the static
1.18+services with little cost, the only big spender will be the heptapod
1.19+instance which requires a larger instance and some workers.
1.20+
1.21+We'll try to keep the cost at or around $30/month.