0
|
1
|
* AWS usage |
|
2
|
We're leveraging AWS for some of our public web servers for now. It's |
|
3
|
really not realistic to expect that my home desktop and spotty Comcast |
|
4
|
internet can serve any production workflow. What it /is/ capable of is |
|
5
|
a private VPN, which can communicate with AWS and other cloud VPN |
|
6
|
depots via WireGuard ([[https://dev.to/gabrieltetzner/setting-up-a-vpn-with-wireguard-server-on-aws-ec2-4a49][article]]). |
|
7
|
|
|
8
|
I currently use Google Domains for nas-t.net, otom8.dev, and |
|
9
|
rwest.io - but that business is now owned by squarespace, so I would |
|
10
|
rather move it to Route53. |
|
11
|
|
|
12
|
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 |
|
13
|
maintained, but it's a start. I'm not even sure if I should stick with |
|
14
|
arch or cave and use Ubuntu or AWS Linux. We can serve the static |
|
15
|
services with little cost, the only big spender will be the heptapod |
|
16
|
instance which requires a larger instance and some workers. |
|
17
|
|
|
18
|
We'll try to keep the cost at or around $30/month. |