Customers can launch Amazon EC2 Dedicated Instances in several ways Set the

Customers can launch amazon ec2 dedicated instances

This preview shows page 7 - 10 out of 18 pages.

Customers can launch Amazon EC2 Dedicated Instances in several ways: Set the tenancy attribute of an Amazon VPC to “dedicated” so that all instances launched into the Amazon VPC will run as Dedicated Instances Set the placement tenancy attribute of an Auto-Scaling Launch Configuration for instances launched into an Amazon VPC Set the tenancy attribute of an instance launched into an Amazon VPC
Image of page 7
Amazon Web Services – Architecting for HIPAA Security and Compliance Page 4 Amazon Virtual Private Cloud offers a set of network security features well- aligned to architecting for HIPAA compliance. Features such as stateless network access control lists and dynamic reassignment of instances into stateful security groups afford flexibility in protecting the instances from unauthorized network access. Amazon VPC also allows customers to extend their own network address space into AWS, as well as providing a number of ways to connect their data centers to AWS. VPC Flow Logs provide an audit trail of accepted and rejected connections to instances processing, transmitting or storing PHI. For more information on Amazon VPC, see . Amazon Elastic Block Store Amazon EBS encryption at rest is consistent with the Guidance that is in effect at the time of publication of this whitepaper. Because the Guidance might be updated, customers should continue to evaluate and determine whether Amazon EBS encryption satisfies their compliance and regulatory requirements. With Amazon EBS encryption, a unique volume encryption key is generated for each EBS volume; customers have the flexibility to choose which master key from the AWS Key Management Service is used to encrypt each volume key. For more information, see . Amazon Redshift Amazon Redshift provides database encryption for its clusters to help protect data at rest. When customers enable encryption for a cluster, Amazon Redshift encrypts all data, including backups, by using hardware-accelerated Advanced Encryption Standard (AES)-256 symmetric keys. Amazon Redshift uses a four- tier, key-based architecture for encryption. These keys consist of data encryption keys, a database key, a cluster key, and a master key. The cluster key encrypts the database key for the Amazon Redshift cluster. Customers can use either AWS KMS or an AWS CloudHSM (Hardware Security Module) to manage the cluster key. Amazon Redshift encryption at rest is consistent with the Guidance that is in effect at the time of publication of this whitepaper. Because the Guidance might be updated, customers should continue to evaluate and determine whether Amazon Redshift encryption satisfies their compliance and regulatory requirements. For more information see
Image of page 8
Amazon Web Services – Architecting for HIPAA Security and Compliance Page 5 - encryption.html .
Image of page 9
Image of page 10

You've reached the end of your free preview.

Want to read all 18 pages?

  • Spring '16
  • Amazon Web Services, Amazon Elastic Compute Cloud