# Quotas for Amazon VPC Lattice
<a name="quotas"></a>

Your AWS account has default quotas, formerly referred to as limits, for each AWS service. Unless otherwise noted, each quota is Region-specific. You can request increases for some quotas, and other quotas can't be increased.

To view the quotas for VPC Lattice, open the [Service Quotas console](https://console.aws.amazon.com/servicequotas/home). In the navigation pane, choose **AWS services** and select **VPC Lattice**.

To request a quota increase, see [Requesting a quota increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html) in the *Service Quotas User Guide*.

Your AWS account has the following quotas related to VPC Lattice.

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/vpc-lattice/latest/ug/quotas.html)

The following Availability Zones aren't supported for VPC Lattice: `use1-az3`, `usw1-az2`, `apne1-az3`, `apne2-az2`, `euw1-az4`, `cac1-az3`, `ilc1-az2`.

The following limits also apply.


| Limit | Value | Description | 
| --- | --- | --- | 
| Bandwidth per service per Availability Zone | 10 Gbps | The default bandwidth allocated per service per Availability Zone. This can be increased, contact your Solutions Architect (SA) or Technical Account Manager (TAM) for further assistance. | 
| Maximum transmission unit (MTU) per connection | 8500 bytes | The size of the largest data packet that a service can accept. | 
| Requests per second per service per Availability Zone | 10,000 | For HTTP services, this is the default number of requests per second per service per Availability Zone. This can be increased, contact your Solutions Architect (SA) or Technical Account Manager (TAM) for further assistance.  | 
| Connection idle time per connection for VPC Lattice services | 1 minute | The default time that a connection can sit idle with no active requests (for HTTP and GRPC), or with no active data transfer (for TLS-PASSTHROUGH) for VPC Lattice services. You can use HTTP and application-level keepalives to extend this idle timeout up to the maximum connection lifetime duration. This can be increased, contact your Solutions Architect (SA) or Technical Account Manager (TAM) for further assistance. | 
| Maximum connection lifetime per connection for VPC Lattice services | 10 minutes | The maximum time that a connection can be open between the client and the server for VPC Lattice services. | 
| Maximum connection lifetime per connection for VPC Lattice resources | NA | VPC Lattice doesn't impose any lifetime connection limits for resources. The client and the server determine the lifetime connection duration while being aware of the idle timeout for VPC Lattice resources, which is 350 seconds. | 
| Connection idle time per connection for VPC Lattice resources | 350 seconds | You can use TCP keepalives to extend this idle timeout. | 
| Service network per VPC | 1 service network | You can connect a VPC to only one service network through an association. To connect a VPC to multiple service networks, you can use VPC endpoints of type service network. |