←back to thread

I Followed the Official AWS Amplify Guide and Was Charged $1,100

(elliott-king.github.io)
461 points thunderbong | 2 comments | 14 Nov 24 06:48 UTC | HN request time: 0.455s | source
Show context
jstrong ◴[14 Nov 24 08:13 UTC] No.42134094[source]▶
unrelated rant, but I'm still salty about it.

needed to send "raw" http requests instead of using their bloated sdk for reasons, and requests failed with "content-type: application/json" header, but succeeded with "content-type: application/x-amz-json-1.0". get out of here with that nonsense.

replies(3): >>42134256 #>>42134259 #>>42134301 #
urbandw311er ◴[14 Nov 24 08:46 UTC] No.42134259[source]▶
Didn't you know, Amazon owns JSON? They acquired it this week, please update all your Content-Type headers within 12 months otherwise you will be in violation of their IP holdings.
replies(1): >>42134589 #
1. jeroenhd ◴[14 Nov 24 09:51 UTC] No.42134589[source]▶
If they use a non-standard version of JSON (for example, one supporting comments, or one with rules about duplicate keys, or any other rule that's not part of the underspecified JSON spec) they should use a custom content type. Something can be valid JSON but invalid AmazJSON and this is exactly how you would distinguish between the two.
replies(1): >>42135078 #
2. ◴[14 Nov 24 11:09 UTC] No.42135078[source]▶