Strictly off topic:
Everything you know is wrong.
Weird Al. https://www.youtube.com/watch?v=W8tRDv9fZ_c
Firesign Theatre. https://www.youtube.com/watch?v=dAcHfymgh4Y
AWS in 2025: Stuff you think you know that's now wrong
21–30 of 284 posts
Re: AWS in 2025: Stuff you think you know that's now wrong
#22Earlier quoted context omitted.
Not the OP but I’ve had AWS-staff recommend different prefixes even as recently as last year. If key prefixes don’t matter much any more, then it’s a very recent change that I’ve missed.
Might just be that the AWS staff wasn't up to date on this
That’s possible but they did consult with the storage team prior to our consultation.
But I don’t know what conversations did or did not happen behind the scenes.
Re: AWS in 2025: Stuff you think you know that's now wrong
#23It would've been nice if each of those claims in the article also linked to either the relevant announcement or to the documentation. If I'm interested in any of these headline items, I'd like to learn more.
Re: AWS in 2025: Stuff you think you know that's now wrong
#24You know what's still stupid? That if you have an S3 bucket in the same region as your VPC that you will get billed on your NAT Gateway to send data out to the public internet and right back in to the same datacenter. There is simply no reason to not default that behavior to opt out vs opt in (via a VPC endpoint) beyond AWS profiting off of people's lack of knowledge in this realm. The amount of people who would want…
That is price segmentation. People who are price insensitive will not invest the time to fix it People who are probably shouldn't be on aws - but they usually have to for unrelated reasons, and they will work to reduce their bill.
> People who are price insensitive will not invest the time to fix it
This just sounds like a polite way of saying "we're taking peoples' money in exchange for nothing of value, and we can get away with it because they don't know any better".
Re: AWS in 2025: Stuff you think you know that's now wrong
#25> Glacier restores are also no longer painfully slow.
Wouldn't this always depend on the length of the queue to access the robotic tape library? Once your tape is loaded it should move really quickly:
https://www.ibm.com/docs/en/ts4500-tape-library?topic=perfor...
Re: AWS in 2025: Stuff you think you know that's now wrong
#26> 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.
Re: AWS in 2025: Stuff you think you know that's now wrong
#27I've had two people tell me in the last week that SQS doesn't support FIFO queues.
Re: AWS in 2025: Stuff you think you know that's now wrong
#28You know what's still stupid? That if you have an S3 bucket in the same region as your VPC that you will get billed on your NAT Gateway to send data out to the public internet and right back in to the same datacenter. There is simply no reason to not default that behavior to opt out vs opt in (via a VPC endpoint) beyond AWS profiting off of people's lack of knowledge in this realm. The amount of people who would want…
That is price segmentation. People who are price insensitive will not invest the time to fix it People who are probably shouldn't be on aws - but they usually have to for unrelated reasons, and they will work to reduce their bill.
>People who are price insensitive will not invest the time to fix it
Hideous.
Re: AWS in 2025: Stuff you think you know that's now wrong
#29Earlier quoted context omitted.
That is price segmentation. People who are price insensitive will not invest the time to fix it People who are probably shouldn't be on aws - but they usually have to for unrelated reasons, and they will work to reduce their bill.
> People who are price insensitive will not invest the time to fix it This just sounds like a polite way of saying "we're taking peoples' money in exchange for nothing of value, and we can get away with it because they don't know any better".
Price segmentation happens all the time in pretty much every industry.
Re: AWS in 2025: Stuff you think you know that's now wrong
#30You know what's still stupid? That if you have an S3 bucket in the same region as your VPC that you will get billed on your NAT Gateway to send data out to the public internet and right back in to the same datacenter. There is simply no reason to not default that behavior to opt out vs opt in (via a VPC endpoint) beyond AWS profiting off of people's lack of knowledge in this realm. The amount of people who would want…
The problem is that VPC endpoints aren't free.
They should be, of course, at least when the destination is an AWS service in the same region.
[edit: I'm speaking about interface endpoints, but S3 and DynamoDB can use gateway endpoints, which are free to the same region]