An OpenSearch Vector Search Edition instance runs inside a virtual private cloud (VPC). The API endpoint is not reachable from on-premises networks or the Internet by default. To access the instance from outside the VPC, add your device's public IP address to the public access whitelist.
Prerequisites
An OpenSearch Vector Search Edition instance is created.
The public IP address of the device that will access the instance is available. You can look up your IP address through any IP address query service on the Internet.
Procedure
Open the
Instance Details page in the OpenSearch console.In the
Network Information section, check thePublic Access status. By default,Public Access is turned off.Turn on
Public Access . After you turn onPublic Access , a public endpoint is automatically generated for the instance. Use this endpoint to access the instance from on-premises networks or the Internet.Click
Public Access Whitelist . TheModify Public Access Whitelist panel opens.Click
Edit to enable editing, and then enter one or more IP addresses or CIDR blocks. Separate multiple entries with commas (,).ImportantThe whitelist takes effect one minute after you save it. If you close the panel without clicking
Save , a confirmation message appears. After you confirm, the panel closes and all unsaved edits are discarded.Click
Save .
Verification
Verify that the IP address was added to the whitelist by pinging the public endpoint from the whitelisted device.
In the
Network Information section, copy the public endpoint.Remove the
http://prefix from the endpoint.Run the following command from your device:
ping <public-endpoint-domain>A successful ping response confirms the IP address is whitelisted.
Troubleshooting
When you access an OpenSearch Vector Search Edition instance through the SDK with the public endpoint, the following error may occur:
Error: 403 Forbidden Response: {'errors': {'code': '403', 'message': 'Forbidden'}}This error typically indicates an incorrect IP address in the whitelist. To confirm the cause, temporarily add 0.0.0.0/0 to the whitelist and retry the request. If the error resolves, update the whitelist with the correct IP address and remove 0.0.0.0/0.
The entry 0.0.0.0/0 allows access from all IP addresses, which poses a security risk. Use it only for temporary troubleshooting. Remove it immediately after you identify the correct IP address.