4,390 karma · joined November 6, 2013
See: https://github.com/aws-samples/amazon-cloudfront-functions/b...
Tech workers are mostly in good spot, (great if working remote). However, in Turkey, minimum wage is almost average wage. I feel very bad for most people, and try to give anyway I can.
Car prices are ridicolous. I could almost buy a Tesla Plaid in US at the price of a BMW 320 here. But it's due to high taxes. These taxes were introduced in the '99 earthquake, meant to be temporary. But those taxes are everywhere, named like "Luxury Consumption Tax".
All major cloud providers have similar computation pricing. As much as I love Hetzner, they are not a major cloud provider.
> Alerts from the whole team 500 5 minutes
> API requests per API key 300 5 minutes
Product looks great but those API request limits are too low, because alerts rain when you are having incidents and rate limiting all of them is harmful. That's why other products have deduplication keys / aliases so you don't miss important ones.
https://grafana.com/docs/grafana-cloud/oncall/oncall-api-ref...
https://stackoverflow.com/questions/59170391/s3-lifecycle-ex...
If you want to use a new resource and feature, %90 likely it is an issue. There was even a public project to track them. https://github.com/cfntools/cloudformation-gaps/projects/1
You want to have an IAM role, but you can not tag it with Cloudformation. These minor frustrations quickly add up. And see what you need to do to add a custom resource: https://shouldroforion.medium.com/aws-cloudformation-doesnt-...
Cloudformation lags features so bad that you end up hacks or Lambda functions with custom resources. DynamoDB Global tables took 4/5 years to be available in Cloudformation.
I've also seen wrongly constructed Cloudformation deleting critical databases, hanging (often), times out, rollback hanging not succesful, so it's not always rainbows & sunshine there either. Also I don't like Terraform for its usage of excessive state files, handling state files with DynamoDB locks, having them on S3.
I won't deny the good features of it like being managed is a huge plus, but it's so slow and lagging behind, and it's YAML is so verbose an has stack size limits, it's always a workaround with Cloudformation. My company uses it by abstraction for internal PaaS and deployment automation and it takes a lot for trivial changes to complete.
So in short, neither is perfect, but for me Terraform is easier to use, easier to debug, and faster, and features don't lag nearly as CF. Those are good enough reasons to avoid Cloudformation for me. I also don't like CDK because it's too verbose and its still CF, and I would rather generate Terraform JSONs/HCLs myself if I need more logic either.
Terraform also helps when you need to configure multiple stacks i.e for a service you can have a module that reflects your organizational best practices, a Fargate service for runnning container, automatic Datadog dashboards, cloudwatch alarms connected to Opsgenie/Pagerduty etc.
Try to replicate the freedom (no-schema, cardinality, adding a new node to cluster) of Elasticsearch with InfluxDB or others and you will hit cardinality problems real fast.
On the other hand, my personal M1 Macbook does not even go past 50C on 30+ person Zoom chats.
I'd still close my feed because the problem I have is too many meetings, and more than half of them are not important. But when you say, this Zoom session should have been an email/slack/document, I come across as "that" person and get shunned.
Chargebacks in AWS is very complex, i.e in cost explorer net amortized cost vs unblended cost is hard to understand for an average user. It'd be nice if you can have some clarifications on it, what does even amortized mean etc.
We use Cost Explorer API to identify anomalies. Even basic statistics works sometimes. But there is also new native feature that is good enough for us, so we removed that. But it was a very sensitive topic, i.e our S3 usage is steadily increasing %.x per month. Trend & seasonality analysis is a must.
Sorry for my quick and dirty English. This is a hot topic for me and I get excited.
Also, even if they are untagged, it's not like we need to tag them by hand, AWS Resource Tagging API works nice enough, and not every resource is costly that we need to tag them by resource-level.
I support what you are doing however there are too many companies working CUR data in S3 and none of them is good enough and neccessarily faster or more useful than Cost Explorer. Just wanted to understand what you can add on top of it, apart from automatic tagging? part.
Cost Explorer does all of what you mentioned. UI allows 1 level group by, API does 2. You can filter & group by API Operation (S3 put object), Service (S3), Usage Type (S3 Standard Storage GB/mo), (predefined) Tags and it works brilliantly over even 1 year of data, fast.
I'm really not convinced on what you can do additionally, since you work on the same data exactly (detailed dumps on S3) apart from nicer charts.