Manage service quotas for your portal

When you create your AWS account, we automatically set default service quotas (also referred to as limits) for resource usage with AWS services. Administrators must be aware of two quotas that might need to be increased to support their use case. These two quotas are the number of web portals you can create in each region, and the number of maximum concurrent sessions you can support with each available instance type in each region. You can request an increase for these from the Service Quotas page in the AWS Console.

The following table lists the default service quotas limits.

Default quotas within an AWS Region by account	Value
Web portals	3
Maximum concurrent sessions - standard.regular	25
Maximum concurrent sessions - standard.large	10
Maximum concurrent sessions - standard.xlarge	5

Important

Service quotas affect one AWS Region at a time. You must request service quota increases in each AWS Region where you need more resources. For more information, Amazon WorkSpaces Secure Browser endpoints and quotas.

To request a service quota increase

1. Open the AWS Support dashboard.

2. Choose Service Limit Increase.

   Important

   WorkSpaces Secure Browser service quotas affect one Region at a time. You must request service quota increases in each AWS Region where you need more resources. For more information, see AWS service endpoints.

3. Under Use case description, enter the following information:

   • If you are requesting an increase for the number of web portals, specify this resource type, and include your AWS Account ID, the region where you would like the increase, and the new limit value.

   • If you are requesting an increase for maximum concurrent sessions, specify this resource type, and include your AWS Account ID, the region where you would like the increase, the web portal ARN, and the new limit value.

4. (Optional) To request multiple service quota increases at the same time, complete one quota increase request in the Requests section, and then choose Add another request.

Request a portal increase

A portal is the service’s foundational resource. Each portal is an association between your SAML 2.0 identity provider and your networking connection to the internet and any private web content. Each portal can have a separate portal browser policy and user settings, so administrators will commonly create multiple portals in the same region to address different use cases. For example, you can provide Group A with access to a specific website with restrictive policies (e.g., Clipboard and File transfer disabled), and Group B with access to the general internet without URL filtering. You can create a portal in any supported AWS Region. To view current service availability, see AWS Services by Region.

To request a service quota increase

1. Open the Service Quotas page in your desired region.

2. Choose Number of Web Portals.

3. Choose Request an increase at account level.

4. Under Increase quota value, enter in the total amount that you want the quota to be.

Request a maximum concurrent sessions increase

The maximum concurrent sessions quota is the highest amount of users that can be connected at the same time to a portal. If the service quota limit for maximum concurrent sessions is not set appropriately, users may find that a session is not available when they sign in. In addition to increasing this service quota, customers must also ensure that their VPC and subnets have sufficient IP space to support the maximum concurrent sessions.

To request a maximum concurrent session increase

1. Open the Service Quotas page in your desired region.

2. Choose Number of Maximum Concurrent Sessions per Portal for the instance type you want to increase.

3. Choose Request an increase at account level.

4. Under Increase quota value, enter in the total amount that you want the quota to be.

   Note

   For large or urgent increases, go to your Service Quotas history page, select the link in the status column of your request, link to your support case, and add a reply with details about your use case and/or the urgency. This information helps the service team prioritize requests and ensure sufficient capacity is allocated for your account.

Limit example

For example, assume an administrator is configuring two web portals in US East (N. Virginia) for 125 total users. Before creating the web portal, the administrator identifies the first web portal (Portal A) will support 100 users. When testing the workflow for these users, the administrator determines they will need the XL instance type to support streaming of audio and video during the session. The second web portal (Portal B) needs to be available for up to 25 users to support access to a single static webpage hosted in the customers VPC. When testing this use case, the administrator determines that the standard instance type can support this use case.

For portal A, the administrator must submit a service quota increase request to raise the limit for XL instances from the regions default (i.e., 5) to 100. Once fulfilled, the administrator can allocate the capacity by editing the web portal. For portal B, the administrator can move forward without requesting a quota increase (i.e., since the region has a default quota of 25 for standard instance type).

Manage service quotas

To view the service quotas allocated to your account for each region at any time, see the Service Quotas page.

Other service quotas

You can view and request increases for other quotas listed on the Service Quotas page. In practice, most customers will find it unnecessary to request increases for these limits. These quotas are broadly grouped into two types: Number and Rate.

For Number quotas, when you submit a service quota increase for Number of web portals, you will automatically receive an increase in the number of sub-resources required to create a unique portal. This will be reflected on the Service Quotas page. For example, if you request an increase in portals from 3 to 5, you will automatically receive a service quota increase from 3 to 5 for both browser and user settings. You have the option to re-use or create new sub-resources as desired.

On rare occasion, customers may find a use case for increasing the number or rate of other resource quotas. For example, administrators may want to increase the number of browser settings for testing additional portal configurations. These service quota requests will be reviewed and fulfilled on a case-by-case basis.

For Rate quotas, the rate limits exposed in Service Quotas should not need to be adjusted, regardless of the account portal limit.