Bonsai Hosted ElasticSearch Is Down

How were they 0wned? Lack of MFA, rogue API key, or something else? Are full-access accounts being handed out willy-nilly instead of IAM accounts?<p>AWS Multi-Factor Authentication (MFA):<p><a href="http://aws.amazon.com/iam/details/mfa/" rel="nofollow">http:&#x2F;&#x2F;aws.amazon.com&#x2F;iam&#x2F;details&#x2F;mfa&#x2F;</a><p>AWS Identity Access and Management (IAM):<p><a href="http://docs.aws.amazon.com/IAM/latest/UserGuide/IAMBestPractices.html" rel="nofollow">http:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;IAM&#x2F;latest&#x2F;UserGuide&#x2F;IAMBestPract...</a><p>Managing your AWS API Keys:<p><a href="http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSGettingStartedGuide/AWSCredentials.html" rel="nofollow">http:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;AWSSimpleQueueService&#x2F;latest&#x2F;SQSG...</a><p>Go a step further with your AWS API keys and use AWS&#x27; API access logging (CloudTrail):<p><a href="http://aws.amazon.com/cloudtrail/" rel="nofollow">http:&#x2F;&#x2F;aws.amazon.com&#x2F;cloudtrail&#x2F;</a><p>Don&#x27;t get burned. Check your stuff out.

Full-blown AWS console compromise - this sounds similar to what happened to Code Spaces (<a href="https://news.ycombinator.com/item?id=7909791" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=7909791</a>) Is there a new vulnerability?

Any word on how those accounts are getting compromised?<p>Have they been complacent (easy password to guess, keys easy to be compromised (maybe in a public github repo)), or could there be some whole in the AWS secutiy model?

This brought my app down. <a href="http://jrdevjobs.com" rel="nofollow">http:&#x2F;&#x2F;jrdevjobs.com</a>. Our shards were all missing from Bonsai. We looped through each model and saved it.<p>We&#x27;re back up.

AWS needs to improve usability of IAM so that it gets broader adoption. The learning curve is non-trivial.

This sucks... I am happy we just put our search cluster on elasticbeanstalk atm, but I wish we had more services like this running.. good news is new security practices will hop up everywhere because of this.

Not to focus on this when they are experiencing downtime, but Bonsai has been one of the least reliable service providers I&#x27;ve ever used.

our site <a href="http://www.violetgrey.com" rel="nofollow">http:&#x2F;&#x2F;www.violetgrey.com</a> went down because of this. Luckily we were able to reindex pretty fast before their backups kicked in. Any ideas on how to have fallbacks in such cases?