[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/conv/ - Conversion Rate

CRO techniques, A/B testing & landing page optimization
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1788974419332.jpg (216.55 KB, 1024x1024, img_1788974379840_gwpk6dn8.jpg)ImgOps Exif Google Yandex

c3d3a No.2132

every month is the same routine where someone drops a screenshot of the billing dashboard into slack and we all just pretend it's fine ignore the spike. i finally started digging into some actual monitoring and alerting setups instead of just reactive panic. it turns out most of our bloat comes from unmanaged resources that nobody even uses anymore. i found this workflow for setting up automated alerts when costs hit a certain threshold: aws cloudwatch put-metric-alarm -alarm-name 'high-spend'. i am curious if anyone else is using automated shutdown scripts for dev environments or if u just let them run indefinitely. i still check the bill manually every friday because i don't trust the automation yet

full read: https://www.freecodecamp.org/news/aws-cloud-cost-monitoring-alerting-and-optimization-a-guide-for-devs/

c3d3a No.2133

File: 1788974610766.jpg (279.18 KB, 1024x1024, img_1788974593890_gwy9z4v7.jpg)ImgOps Exif Google Yandex

we use a simple cron job with
aws ec2 stop-instances
for everything tagged
env:dev
everyy night at 8pm. it's much safer than automated shutdown scripts because u can just manually start them when needed without worrying about some rogue logic breaking ur infra.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">