This page covers the service quotas, limits, and regional availability for OpenSearch UI (Dashboards) applications.
Quotas & Limits
Service quotas
| Resource | Default limit | Adjustable? |
|---|---|---|
| Applications per account per region | 30 | Contact AWS Support to request an increase |
| Data sources per application | 50 | No |
| Tags per application | 50 | No |
If you need more than 30 applications in a single account and region, you can request a quota increase through the AWS Service Quotas console or by contacting AWS Support.
Regional availability
OpenSearch UI is available in select AWS regions. The list of supported regions is updated as new regions are added.
For the current list of supported regions and service endpoints, see the AWS OpenSearch Service endpoints page in the AWS General Reference.
Not all regions that support OpenSearch Service also support OpenSearch UI. Check the endpoints page for the most up-to-date list.
API endpoints
OpenSearch UI uses the OpenSearch Service API endpoints. The endpoint format is:
https://es.<REGION>.amazonaws.comFor example:
- US East (N. Virginia):
https://es.us-east-1.amazonaws.com - EU (Ireland):
https://es.eu-west-1.amazonaws.com
For the full list of regional endpoints, see the AWS OpenSearch Service endpoints page .
Application URL format
Each OpenSearch UI application gets a unique URL in the format:
https://<APP_ENDPOINT>.aos.us-east-1.on.awsThe exact domain pattern may vary by region. You can find your application's URL in the OpenSearch Service console under the application details page.
Other known limits
| Limit | Details |
|---|---|
| Application name length | 3–40 characters, alphanumeric and hyphens only |
| SigV4 presigned URL expiry | Maximum 300 seconds (5 minutes) |
| Dashboard admin users | Configured via update-application — no hard limit on the number of admin principals |
| Concurrent users | No published hard limit — scales with the underlying OpenSearch resources |
Throttling
API calls to manage OpenSearch UI applications (create, update, delete, list) are subject to the same throttling limits as other OpenSearch Service API operations. If you receive throttling errors (ThrottlingException), implement exponential backoff in your automation.