My Amazon S3 Mistake

Re:My Amazon S3 Mistake by moe on Tuesday December 30, 2014 @06:49PM (#8817451)

Lesson 1: Don't publish your passwords.

Lesson 2: When using AWS then use Billing Alarms[1].

It takes about 1 minute to setup and enables e-mail or SMS notifications at dollar-thresholds of your choice.

[1] http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/...

[ Parent | on HN ]

Re:My Amazon S3 Mistake by FireBeyond on Tuesday December 30, 2014 @06:52PM (#8817472)

The corollary to that is the first thing such people/scripts do when they have access to your account is disable Billing Alarms.

[ Parent | on HN ]

Re:My Amazon S3 Mistake by rifung on Tuesday December 30, 2014 @06:54PM (#8817484)

Are you sure you can disable billing alarms with just your access/secret key? I thought you would need to know the user name + password for that

[ Parent | on HN ]

Re:My Amazon S3 Mistake by TheDong on Tuesday December 30, 2014 @09:19PM (#8817985)

Having root credentials is sufficient, and based on the fact that this guy said "apparently the s3 api lets you spin up ec2 instances" it looks like he didn't touch IAM.

Root credentials are deprecated, but can still be used and if this guy used them then yes, his billing alarms could have been disabled.

There's a difference between an admin iam user (can't do billing stuff) and the root credentials (just as powerful as username / password).

[ Parent | on HN ]

Re:My Amazon S3 Mistake by mkale on Tuesday December 30, 2014 @11:22PM (#8818242)

Maybe they should send an email/SMS to notify you that email/SMS had been disabled. (And, an email/SMS to the old address when the email/SMS is changed too.)

[ Parent | on HN ]