171–180 of 284 posts
Earlier quoted context omitted.
Gateway endpoints are free. Network endpoints (which are basically AWS-managed ENIs that can tunnel through VPC boundaries) are not free. S3 can use either, and we recommend establishing VPC Gateway endpoints by default whenever you need S3 access. (Disclaimer: I work for AWS, opinions are my own.)
Why don't you have gateway endpoints for all your APIs?
> You don’t have to randomize the first part of your object keys to ensure they get spread around and avoid hotspots. From my understanding, I don't think this is completely accurate. But, to be fair, AWS doesn't really document this very well. From my (informal) conversations with AWS engineers a few months ago, it works approximately like this (modulo some details I'm sure the engineers didn't really want to share)…
Hit it when building an iceberg Lakehouse using pre existing data. Using object prefixes fixed the issue.
Earlier quoted context omitted.
They probably are an LLM and if they aren't, their higher management is pushing for them to be LLMs by 2027 at the latest.
I still get strong Hyderabad vibes from the copy/pasting plus the occasional original sentence. Perhaps they trained the LLM using that data though. (Small customer though: yearly AWS spend around 80k. Support is 10% of that.)
> You don’t have to randomize the first part of your object keys to ensure they get spread around and avoid hotspots. As of when? According to internal support, this is still required as of 1.5 years ago.
The auto partitioning is different. It can isolate hot prefixes on its own and can intelligently pick the partition points. Problem is the process is slow and you can be throttled for more than a day before it kicks in.
Earlier quoted context omitted.
In terms of cost, from cheapest to most expensive: 1. Spot with autoscaling to adjust to demand and a savings plan that covers the ~75th percentile scale 2. On-demand with RIs (RIs will definitely die some day) 3. On-demand with savings-plans (More flexible but more expensive than RIs) 3. Spot 4. On-demand I definitely recommend spot instances. If you're greenfielding a new service and you're not tied to AWS, some ot…
To "me, too" this, it's not like that AWS spot instance just go "poof," they do actually warn you (my recollection is 60s in advance of the TerminateInstance call), and so a resiliency plane on top of the workloads (such as the cited Kubernetes) can make that a decided "non-event". Shout out to the reverse uptime crew, a subset of Chaos Engineering
Earlier quoted context omitted.
It's designed to be a declarative DSL, but then you have to do all sorts of filters and maps in any group of resources and suddenly you are programming in yaml with both hands tied behind your back
Yeah it’s just terrible. If Amazon knew what was good they’d just replace it with almost anything else. Heck just got all in on terraform and call it a day.
Earlier quoted context omitted.
Looks like something that you could solve easily through their support, no?
Support don't talk to you unless you pay for support
Can no longer login to my AWS account, because I never set up MFA. Want to set up MFA ... login required to request device. Yes, I know, they warned us far ahead of time. But not being able to request one of their MFA devices without a login is ... sucky.
S3: "Block Public Access is now enabled by default on new buckets." On the one hand, this is obviously the right decision. The number of giant data breeches caused by incorrectly configured S3 buckets is enormous. But... every year or so I find myself wanting to create an S3 bucket with public read access to I can serve files out of it. And every time I need to do that I find something has changed and my old recipe d…