Yes, you have responsibilities. Just because you’re using someones else’s computer doesn’t mean you get to ignore all the boring stuff and hope that someone else takes care of it for you.
Want to know who’s responsible for what? Make sure you read the [AWS Shared Responsibility Model] (http://aws.amazon.com/compliance/shared-responsibility-model/).
Here’s the Coles notes version for those of you who still won’t read it.
AWS is responsible for the security of the cloud; you are responsible for security in the cloud. Pretty easy right?
Are you interested in shifting more responsibility to AWS? I think it’s a great idea and we recommend it often to our customers. To shift more responsibility move ‘up the stack’ - use Managed Services or Serverless solutions, that way the demarcation point moves up the stack.
Our typical approach is like this:
By starting at the top of the stack, we’re able to shift more responsibility to AWS and stay focused on what’s important - building the best solutions for our customers. I suggest you take the same approach. Not sure where to start? Check our AWS JetPack solution.
I hate to be the bearer of bad news, but if you’re running an EC2 instance, you still have to patch it. If you’ve had enough of OS' as I have, you should consider moving ‘up the stack.’ If you can’t - which happens - deploy [AWS Systems Manager] (http://aws.amazon.com/systems-manager/) and stop shirking your responsibilities.
Like what you read? Why not subscribe to the weekly Orbit newsletter and get content before everyone else?