Securing UI Access with IP-Based Controls
This topic explains how to configure trusted IP addresses for UI and API access, allowing administrators to define which IP address can interact with specific user interface and API components. By implementing IP-based access controls, you can add an extra layer of protection, ensuring that only traffic from approved IP ranges can access watsonx.data. For more information, see What are context-based restrictions?.
Before you begin
To configure trusted IP addresses for UI access, you must have Administrator privileges for the account.
Configuring trusted IP access
-
Sign in to IBM Cloud. Log in to your IBM Cloud account.
-
From the IBM Cloud Console, navigate to Manage > Context-based restrictions.
Access CBR -
From the Navigation pane, click Rules.
-
Click Create+. The New rule page opens. Select watsonx.data service from the list.
Create rule
New rule -
Click Next. Select all APIs. Define the APIs that you want to protect to narrow the scope of a rule's restrictions. See Defining the scope of a rule.
Specify APIs -
Click Next. From Resources, select Specific resource option and choose watsonx.data. You can review the selection.
-
Click Continue. Specify the contexts from where your resource can be accessed. See Contexts.
Turn On the Endpoints to specify the endpoint that receives the connection. Only Public endpoints are supported.
Endpoints From the Network zones, click Create and list the IP addresses that needs to be allowed in the Allowed IP addresses field. You can also list the IP addressed that needs to be denied access in the Denied IP addresses field. See Network zone.
Network -
From the Reference a service section, select watsonx.data as the service. Click Continue.
Network -
You can decide how you want to enforce a rule upon creation and update the rule enforcement at any time. See Rule enforcement.
Enforcement -
Click Create. The rule is created successfully.
For more information, see Creating context-based restrictions and Enforcing context-based restrictions.
Limitation
Context-based restrictions does not work for account-scoped lite instances.