Creating an Amazon EBS Volume
You can create an Amazon EBS volume that you can then attach to any EC2 instance within the same Availability Zone. You can choose to create an encrypted EBS volume, but encrypted volumes can only be attached to selected instance types. For more information, see Supported Instance Types.
You can also create and attach EBS volumes when you launch instances by specifying a block device mapping. For more information, see Launching an Instance and Block Device Mapping. You can restore volumes from previously created snapshots. For more information, see Restoring an Amazon EBS Volume from a Snapshot.
If you are creating a volume for a high-performance storage scenario, you should make sure to use a Provisioned IOPS (SSD) volume and attach it to an instance with enough bandwidth to support your application, such as an EBS-optimized instance or an instance with 10 Gigabit network connectivity. For more information, see Amazon EC2 Instance Configuration.
When a block of data on a newly created EBS volume is written to for the first time, you might experience longer than normal latency. To avoid the possibility of an increased write latency on a production workload, you should first write to all blocks on the volume to ensure optimal performance; this practice is called pre-warming the volume. For more information, see Pre-Warming Amazon EBS Volumes.
To create an EBS volume using the console
Open the Amazon EC2 console.
From the navigation bar, select the region in which you would like to create your volume. This choice is important because some Amazon EC2 resources can be shared between regions, while others can't. For more information, see Resource Locations.
Click Volumes in the navigation pane.
Above the upper pane, click Create Volume.
In the Create Volume dialog box, in the Volume Type list, select General Purpose (SSD), Provisioned IOPS (SSD) or Magnetic. For more information, see Amazon EBS Volume Types.
Some AWS accounts created before 2012 might have access to Availability Zones in us-east-1, us-west-1, or ap-northeast-1 that do not support Provisioned IOPS (SSD) volumes. If you are unable to create a Provisioned IOPS (SSD) volume (or launch an instance with a Provisioned IOPS (SSD) volume in its block device mapping) in one of these regions, try a different Availability Zone in the region. You can verify that an Availability Zone supports Provisioned IOPS (SSD) volumes by creating a 4 GiB Provisioned IOPS (SSD) volume in that zone.
In the Size box, enter the size of the volume, in GiB.
For Provisioned IOPS (SSD) volumes, in the IOPS box, enter the maximum number of input/output operations per second (IOPS) that the volume should support.
In the Availability Zone list, select the Availability Zone in which to create the volume.
(Optional) To create an encrypted volume, select the Encrypted box and choose the master key you want to use when encrypting the volume. You can choose the default master key for your account, or you can choose any Customer Master Key (CMK) that you have previously created using the AWS Key Management Service. Available keys are visible in the Master Key drop down menu, or you can paste the full ARN of any key that you have access to. For more information, see the AWS Key Management Service Developer Guide.
Encrypted volumes can only be attached to selected instance types. For more information, see Supported Instance Types.
Click Yes, Create.
If you receive one of the following errors, the current volume creation would exceed the default storage limit for your account:
Maximum number of active volumes bytes, 20, exceeded. Maximum number of active gp2 volumes bytes, 20, exceeded. Maximum number of active io1 volumes bytes, 20, exceeded.
To view the default service limits for Amazon EBS, see Amazon Elastic Block Store (Amazon EBS) Limits in the Amazon Web Services General Reference. To request an increase in your storage limits, see Request to Increase the Amazon EBS Volume Limit.