Because you’re building systems on top of the AWS cloud infrastructure, the security responsibilities will be shared: AWS manages the underlying infrastructure, and you secure anything you put on the infrastructure or connect to the infrastructure.

homepage_global-infrastructure-map

AWS is responsible for protecting the global infrastructure that runs all of the services offered in the AWS cloud. This infrastructure is comprised of the hardware, software, networking, and facilities that develop and run AWS services.

Protecting this infrastructure is AWS’s number one priority, and while you can’t visit our data centers or offices to see this protection firsthand, we provide several reports from third-party auditors who have verified our compliance with a variety of computer security standards and regulations (for more information, visit the AWS Compliance page).

For a description of the security measures built into the AWS cloud infrastructure, please see our Overview of Security Processes whitepaper.

ha_ed_mobile_database_orange

The amount of security configuration work you have to do varies depending on how sensitive your data is and which services you select.

For IaaS services like Amazon EC2 and Amazon S3, you have more control and therefore more configuration work to do. For EC2 instances, you’re responsible for patching the guest OS on the instances as well as any software you install on them, configuring the security group (firewall) that allows outside access to your instances, and setting up any VPC subnets that the instances reside within, etc. For Amazon S3, you must set the access control policies for each of your storage buckets, set up encryption options for the stored data, and specify backup and archiving preferences.

For PaaS services like Amazon RDS or RedShift or WorkSpaces, you have less security configuring to do. For these services, you don’t have to worry about launching and maintaining instances or patching the guest OS or applications—AWS handles that for you. For these managed services, backups are performed automatically, firewalls are configured, and databases are replicated.

However, there are certain security features—such as individual IAM user accounts and credentials, HTTPS for data transmissions, and user activity logging—that you should configure no matter which AWS services you use.

To see a list of the features and services that AWS provides to help you keep your data and services secure in the cloud, see our AWS Security Features page. For information on how to configure a particular AWS service, see the documentation for that service. For more tips on security best practices, see the list of security-related whitepapers, tutorials, and articles on our Security Resources page.