Just like gitlab, which has a full source->prod flow (for free).
Just like github actions.
Just like bitbucket+bamboo in the atlassian world.
What AWS devtools does not have is a ticket system. Gitlab/github/jira all do.
Whitney testified in congress (the House Committee on Energy and Commerce) for legislation around satellite comms technology: https://www.youtube.com/watch?v=Btx6FUP24jM. David Goldman (Senior Director of Satellite Policy, SpaceX) testified as well.
In Biden’s SOTU last night he asked for congress to increase his IRA’s 1% buyback tax to 4%. Absolutely insane.
Of the two primary liquidity opportunities for shareholders (dividends and tenders), the act is meant to discourage buybacks and push volume over to dividends as that generates more tax income for the govt (as Levine posted about today).
That’s ridiculous though – dividends are taxed as income, buybacks are taxes as cap gains. Both are taxed appropriately, and according to first principles already. To double tax tenders is just silly.
Received replacement parts for rise garden and the charcoal v3 extension. Now just missing a single screw (gonna skip this one, the top is stable with the other 3), hole covers, and pump inlet foam. Ordered the latter 2.
Poured an entire cup of coffee on my keyboard. I had a Code V2B 104-key, Cherry MX Brown. Don’t need the numpad at all, I can go back down to 87-key.
Of the Cherry MX switches (gold standard), first decide linear, tactile, or clicky (order of sound/force).
Linears: silver -> red -> nature white -> black -> grey.
Tactiles: brown -> clear -> grey
Clicky: blue -> green -> white
There’s a new brand Zeal that makes a few switches called Zealios. They’re supposed to feel really good.
Ended up going with the Code V3, 87-key, and cherry MX blue switches.
Could do some customization like the below (lol) if you order directly from the Code (WASM) website.
SBSC. Networking.
Created a single A record to point to my EC instance’s elastic IP, so there’s a single source of truth. Then any other record that wants to forward to the machine (directly, like for ssh) instead of the root domain name for website access (via the ELB) can just use an A record to point to the IP’s A record.
And an A record to point from the www subdomain to the root domain (in supercontest, can do this directly in route53; in privateer, do this through amplify – it creates the route53 A record to amplify’s cloudfront for you).
Explicitly added another listener to the load balancer which redirects all http/80 traffic to https/443 (the other listener, which forwards to my target group, which forwards to the EC2 instance). Can’t do this through DNS, of course.
Could just have the ELB continue to forward to 80 on the EC2 instance, but remove the nginx container and have the gunicorn app container ports: 80:8000
But again, better to front gunicorn with a proxy (other than ELB, which is handling the load balancing and the cert/decryption). Even though I’m not serving static files through nginx (using cloudfront instead), it is still good for buffering and other custom proxy configs.
AWS (all accounts). Did some billing analysis.
Here’s an average 3 months before the network changes
EC2 and route53 are expected and fine.
Cloudwatch seems a little expensive. And not sure why it’s only happening in the second half of every month. Maybe it’s free up to a certain number of metrics transmitted, then starts charging.
It charges for custom metrics (30c/mo), dashboards ($3/mo), alarms (10c/mo), logs (including the logs from just running the cloudwatch agent), more. Pretty expensive (relatively). Mine is about $2.60/mo.
Deleted the dashboard and changed the disk_used_percent to only push for / (it was pushing for all mount points, which is 29 custom metrics!
The other surprise is ELB. Over the past two days since starting, it’s charging about 45c per day. It’s the offseason with no traffic. This should be pennies.
This is just to HAVE the load balancer active. It’s ~$18/mo just to run one in us-west-1, then traffic costs on top of that.
ELB is crazy expensive if you’re just using it for https. It’s just a cert. It only really makes it worth it if you’re serving multiple sites with the same cert, and/or using the actual load balancing functionality to proxy to many many instances.
Therefore – if you move the app to serverless (lambda per request, fronted by API gateway) or (eks/ecs with nginx ingress), you don’t have to pay for the load balancer anymore.
There are some pretty cool cost anomaly detection and budging-reaching notification services.
Updated my root aws account’s default console layout.
