391 points kinj28 | 1 comments | 21 Oct 25 15:55 UTC | HN request time: 0.233s | source

Could there be any link between the two events?

Here is what happened:

Some 600 instances were spawned within 3 hours before AWS flagged it off and sent us a health event. There were numerous domains verified and we could see SES quota increase request was made.

We are still investigating the vulnerability at our end. our initial suspect list has 2 suspects. api key or console access where MFA wasn’t enabled.

Show context

defraudbah ◴[22 Oct 25 07:31 UTC] No.45665892[source]▶

>>45657345 (OP) #

weird, can you send me your API key so I can verify it's not in the list of compromised credentials?

replies(1): >>45666501 #

darkamaul ◴[22 Oct 25 09:04 UTC] No.45666501[source]▶

>>45665892 #

I know this is just a playful joke, but I wanted to gently flag something important. Even in humor, we should never casually discuss sharing API keys or credentials.

You never know when or if someone might misinterpret a message like this.

replies(3): >>45666803 #>>45667451 #>>45668155 #

wiether ◴[22 Oct 25 09:46 UTC] No.45666803[source]▶

>>45666501 #

Now that we have people browsing with an "AI browser", it could become quite interesting though

replies(1): >>45667489 #

1. 1oooqooq ◴[22 Oct 25 11:28 UTC] No.45667489[source]▶

>>45666803 #

win-win

↑

Ask HN: Our AWS account got compromised after their outage