# Amazon Elastic Block Store endpoints and quotas
<a name="ebs-service"></a>

To connect programmatically to an AWS service, you use an endpoint. AWS services offer the following endpoint types in some or all of the AWS Regions that the service supports: IPv4 endpoints, dual-stack endpoints, and FIPS endpoints. Some services provide global endpoints. For more information, see [AWS service endpoints](rande.md).

Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see [AWS service quotas](aws_service_limits.md).

The following are the service endpoints and service quotas for this service.

## Service endpoints
<a name="ebs_region"></a>

**Topics**
+ [Endpoints for Amazon EBS in Amazon EC2](#ebs_in_ec2)
+ [Endpoints for the EBS direct APIs](#ebs_direct_apis)

### Endpoints for Amazon EBS in Amazon EC2
<a name="ebs_in_ec2"></a>

The API actions to manage EBS volumes, snapshots, and encryption are part of the Amazon EC2 API. For more information, see [Amazon EBS actions](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/OperationList-query-ebs.html) in the *Amazon EC2 API Reference*.

For the service endpoints for Amazon EC2, see [Amazon EC2 endpoints and quotas](ec2-service.md).

### Endpoints for the EBS direct APIs
<a name="ebs_direct_apis"></a>

Use the EBS direct APIs endpoints to directly read the data on your Amazon EBS snapshots, and identify the difference between two snapshots. For more information, see [Use EBS direct APIs to access the contents of an Amazon EBS snapshot](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-accessing-snapshot.html) in the *Amazon Elastic Compute Cloud User Guide*.

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/general/latest/gr/ebs-service.html)

## Service quotas
<a name="limits_ebs"></a>

Your quotas can change over time. Amazon EBS constantly monitors your provisioned storage and IOPS usage within each Region and might automatically increase your quotas, on a per-Region basis, based on your usage.

Even though Amazon EBS automatically increases your quotas based on your usage, you can request a quota increase if needed. For example, if you intend to use more `gp3` storage in US East (N. Virginia) than your current quota allows, you can request a quota increase for that volume type in that Region. To request a quota increase, use the [AWS Service Quotas console](https://console.aws.amazon.com/servicequotas/).

**Considerations**
+ The quota for **Concurrent snapshot copies per destination Region** is not adjustable using Service Quotas. However, you can request an increase for this quota by contacting AWS Support.
+ The **IOPS modifications and Storage modifications** quotas apply to the aggregated current value (for *size* or *IOPS*, depending on the quota) of volumes that can undergo modifications concurrently. You can make concurrent modification requests for volumes that have combined current value (for *size* or *IOPS*) up to the quota. For example, if your **IOPS modifications for Provisioned IOPS SSD (io1) volumes** quota is `50,000`, you can make concurrent IOPS modifications requests for any number of `io1` volumes as long as their combined current IOPS is equal to or less than `50,000`. If you have three `io1` volumes provisioned with `20,000` IOPS each, you can request IOPS modifications for two volumes concurrently (`20,000 * 2 < 50,000`). If you submit a concurrent IOPS modification request for the third volume, you exceed your quota and that request fails (`20,000 * 3 > 50,000`). 
+ Amazon EBS has the following non-adjustable limits for the number of EBS volumes per instance launch request.
  + `2500` — `us-east-1`, `us-west-2`, `eu-west-1`, and `ap-northeast-1`
  + `500` — all other Regions

  This limit applies to instance launch requests that you make, and to instance launch requests made by AWS services, such as Amazon EMR, on your behalf. If your instance launch request fails as a result of exceeding this limit, we recommend that you adjust the EBS volume configuration in the launch request to ensure the number of volumes is below the limit, or that you work with your technical account manager (TAM) to explore other options for launching your cluster without exceeding the limit.

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/general/latest/gr/ebs-service.html)