Common Errors

Application stuck in CREATING state

Cause: Usually a missing iam:CreateServiceLinkedRole permission.

Fix: Add this to your IAM policy:

{
  "Effect": "Allow",
  "Action": "iam:CreateServiceLinkedRole",
  "Resource": "arn:aws:iam::*:role/aws-service-role/opensearchservice.amazonaws.com/AWSServiceRoleForAmazonOpenSearchService"
}

Other causes:

Service quota reached — default is 10 applications per account per region. Request an increase via Service Quotas.
Region not supported — OpenSearch UI is available in 14 regions. Check the supported regions .

"No Results Found" in Discover

Fix 1: Expand the time range

The default is Last 15 minutes. Click the date picker and select Last 7 days or Last 30 days.

Fix 2: Check the index pattern

The data source selector (top-left of Discover) must point to the correct index pattern. If the list is empty, go to Manage workspace → Index patterns to create one.

Fix 3: Verify the time field

Your index pattern must have a valid time field. If it doesn't match your data's timestamp field, Discover won't find results.

Dashboard panels show "No results" or errors

Error: Expected exactly 1 result for data_source_name "X" but got 0 results

Cause: The visualization references a data source that doesn't exist in this environment (common after migration).

Fix: Check Manage workspace → Data sources and ensure the referenced data source is accessible.

"Access Denied" when launching the application

Your IAM user/role needs es:GetApplication and data source access permissions (es:ESHttp*, aoss:APIAccessAll).

Can't switch to PPL or SQL in Discover

Click the DQL button next to the search bar
Switch to PPL or SQL in the language selector
For PPL, start queries with source = index-name