3 ms·

We accidentally burned $40k by calling recursive patterns

• deleted 4y ago
  [deleted]
• bluelightning2k 4y ago
  This is so easily done. There are so many potential footguns in these patterns. Except the Cloud turns them from brief weird bugs into foot-nukes. Did AWS forgive any of the cost?
  • BoorishBears 4y ago
    SOP for these cases should be to write a post about it asap and post to HN, so that there's an additional carrot for AWS to forgive the cost (a happy ending update where AWS did the right thing)
  • MichaelZuo 4y ago
    Why would they forgive it when they have electricity bills to pay, which certainly won't be forgiven?
• karmakaze 4y ago
  > During migration (Step 2), we created a 2-week temporary Lambda that listens for S3 bucket events, transforms them into Parquet, and publishes them to S3. Due to the fact that both the source and destination buckets and prefixes were assigned to the same bucket, it triggered millions of times. I wouldn't so much call it recursive (as in subdivide and conquer), but rather endlessly processing work queued for yourself.