Set Up the Nexus One UI Search Index

Add a new nexusOne connection block to your IQ Server config.yml.

If you are using a self-managed OpenSearch instance, your block will look like the following:

nexusOne:
  connection:
    type: http
    uri: https://opensearch.example.com:9200
    username: . . .
    password: . . .

If you are using an AWS OpenSearch service, your block will look like the following:

nexusOne:
  connection:
    type: aws
    domain: https://my-domain.us-east-1.es.amazonaws.com:443
    region: us-east-1

AWS credentials are resolved using the standard AWS SDK default credentials chain: environment variables, system properties, ~/.aws/credentials, ECS container credentials, or EC2 instance profiles

IQ Server checks the connection and reports Connected, Failed, or Not tested.

If it fails, verify the connection settings in config.yml, that the network is up, and that authentication succeeds; then, reload the page to run the check again.

If an index was built previously and the connection is later lost, step 2 reports that the existing index cannot be used until the connection is restored.

With steps 1 and 2 passing, Build index becomes available. Building is a resource-intensive process; start it when your instance can absorb the load.

While the build runs, the step shows who started it and when, and offers the option to Cancel build. The classic UI is unaffected and remains available while the build runs.

When the first build finishes, the Nexus One UI is enabled automatically and becomes available to all users. There is no separate activation step.

If the build fails, use the button on step 3 to start it again.