Context Based Restrictions

Introduction With the IBM Cloud® Context-based restrictions Management API, you can create, update, view, and delete context-based restriction rules and contexts, and view account settings. You can define ingress rules for IBM Cloud® resources based on the context of access requests by using context-based restrictions. Contexts and rules are the main components that make up context-based restrictions. Rules are used in access decisions when you call service APIs. Contexts can be made up of one or more endpoint types, which are the connection over which an access request is received, and network zones, which are an allowlist of IP addresses and VPCs. For more information about how restrictions work, see What are context-based restrictions?https://cloud.ibm.com/docs/iam?topic=iam-context-restrictions-whatis. The following shows an example of a context-based restrictions rule: Resource | Contexts ------------ | ------------- All COS buckets in instance XYZ | 1. Zone: A. \n \n 2. Zone: B or C, Type: "private" A context allows access only if all its conditions are satisfied. That is, the request must originate from at least one of the specified network zones if any, and be received over a connection that matches one of the specified endpoint types, if any. If no rules are applicable to the request, access is not restricted based on context, and is determined exclusively by Identity and Access Management IAM access policies. Installing the Java SDK Maven xml

MethodPathSummary
POST/v1/zonesCreate a network zone
GET/v1/zonesList network zones
GET/v1/zones/{zone_id}Get a network zone
PUT/v1/zones/{zone_id}Replace a network zone
DELETE/v1/zones/{zone_id}Delete a network zone
GET/v1/zones/serviceref_targetsList available service reference targets
GET/v1/zones/serviceref_targets/{service_name}Get service reference target for a specified service name
POST/v1/rulesCreate a rule
GET/v1/rulesList rules
GET/v1/rules/{rule_id}Get a rule
PUT/v1/rules/{rule_id}Replace a rule
DELETE/v1/rules/{rule_id}Delete a rule
GET/v1/account_settings/{account_id}Get account settings
GET/v1/operationsList available service operations