LaserData Cloud
Networking

Access Rules

Permit selected IP ranges and protocols to reach deployment endpoints

View as Markdownllms.txt

Access rules permit selected IP addresses and CIDR ranges to reach deployment endpoints. A CIDR range describes a group of IP addresses. Rules apply to Managed, BYOC, and On-Premise deployments on every plan.

Paid deployments need a rule before clients can connect. Managed Free deployments include the global rule 0.0.0.0/0. It permits every IPv4 address on the enabled protocols, including browser access when HTTP is enabled. It does not open the Kafka gateway port. Replace it with trusted source ranges before sending application data.

Network access and Cloud permissions are separate. A rule cannot fix a Console deployment:read denial. If your organization owner account is blocked, use the permission troubleshooting steps.

Why Access Rules

Use rules to control the source addresses, protocols, and duration of client access:

  • Permit known office or VPN address ranges.
  • Open TCP for applications and HTTP for monitoring or Stream UI independently.
  • Grant temporary access that expires automatically, for example during contractor work or debugging.
  • Limit Stream UI access to trusted operators' browser IPs.

Concepts

Protocol Rules

Select the protocols that a rule permits for its CIDR ranges. You can enable any combination from the table. A rule without enabled protocols opens no ports, even when it contains address ranges.

ProtocolAPI FieldWhat It Opens
Iggy HTTPiggy_httpIggy HTTP API endpoint (ports 80 and 443)
Iggy TCPiggy_tcpIggy TCP transport
Iggy WebSocketiggy_websocketIggy WebSocket transport
Iggy UDPiggy_udpIggy QUIC/UDP transport
KafkakafkaKafka gateway on TCP port 9092. Off by default, also on the default rule of a Free deployment

A rule that sets kafka for 0.0.0.0/0 makes Kafka sign-in reachable from the whole internet. Set kafka only for the ranges your Kafka clients connect from. The port opens whether or not the gateway runs, and a running gateway is unreachable without such a rule.

Stream UI loads from the Console and runs in the browser. It connects directly to Warden's HTTP proxy on ports 80 and 443. Enable iggy_http for the browser's IP address. LaserData does not add its own IP to make this connection.

CIDR Blocks

Each rule needs at least one IPv4 CIDR block. Supported forms include these:

  • 203.0.113.5/32 permits one host.
  • 10.0.0.0/16 permits a subnet.
  • 0.0.0.0/0 permits every IPv4 address to use the selected protocols.

Subnet masks must range from /0 to /32.

Data Access Rule

When data access is on for a deployment, LaserData adds one rule of its own. It admits LaserData's fixed outgoing addresses for the region that runs the deployment, each as a single host (/32), on port 443 only. On shared Free infrastructure it opens only the deployment's Warden HTTPS port.

The rule does not appear in the Access Rules tab or the list API, cannot be deleted, and does not count against the plan limit. LaserData removes it when data access is turned off. Turning data access on or off leaves your own rules unchanged. While data access is on, Stream UI reaches Warden through LaserData and needs no browser rule, and the Laser CLI takes the same path with its API key and needs no rule for its address either. With data access off, Stream UI connects from your browser to Warden directly and needs the browser rule above, and the CLI needs a rule for its own address.

Rule Expiry

A rule can have a future expiration date. After that date, the rule no longer permits traffic from its address ranges. For example, use expiry to grant a partner 30 days of access without a separate removal task.

Allow My IP

Allow My IP admits the public IPv4 address that LaserData observes for the caller, so a browser, a script, an agent, or a Laser SDK app reaches the deployment without looking the address up. A signed-in member and an API key can both use it. It creates an ordinary rule:

FieldValue
Namemy-ip-{user_id} for a member, my-ip-key-{api_key_id} for an API key, one each per deployment
CIDR blockThe caller's address as a single host (/32)
ProtocolsThe ones the request chooses: iggy_http, iggy_tcp, iggy_websocket, iggy_udp, kafka. Iggy HTTP when it chooses none
Expiry24 hours after creation

The rule appears in the list, counts against the plan limit, can be deleted like any other rule, and is removed when it expires. Using Allow My IP again replaces your earlier rule, so the 24 hours start again and a changed address is followed.

LaserData creates no rule when:

  • The address is IPv6, or not a public address: private, loopback, link-local, the shared range 100.64.0.0/10, unspecified, or broadcast.
  • The deployment has no public IP address, or runs On-Premise.
  • Another rule already admits the address on every chosen protocol, for example a wider office range or the global rule of a Free deployment. The request answers 409 with ip_address_already_allowed, and a client can connect as it is.
  • The deployment has reached its plan limit.

The address is the one LaserData sees. Behind a VPN with split routing, it can differ from the address your browser uses to reach the deployment. The rule then does not help that connection. If your browser reaches LaserData over IPv6, Allow My IP refuses the request, even when the deployment is reachable over IPv4.

Allow My IP needs deployment:access:manage. A key's role already able to manage access rules can admit any address, so Allow My IP gives it nothing more. For a server with a fixed address, an ordinary rule with an explicit CIDR block lasts beyond 24 hours. The Laser CLI runs it with laser deployment connect access-rule allow-my-ip --protocol tcp.

Creating an Access Rule

From the Console

  1. Open your deployment's Access Rules tab.
  2. Click Add Rule.
  3. Enter a name that is unique within the deployment.
  4. Add at least one CIDR range.
  5. Select Iggy TCP, HTTP, WebSocket, UDP, Kafka, or a combination.
  6. If access is temporary, set an expiration date.
  7. Add remarks if you need to explain the rule.
  8. Click Create.

LaserData applies the rule through AWS security groups or GCP firewall rules.

Validation

A new rule must meet these requirements:

  • Its name is unique within the deployment, without regard to letter case.
  • It contains at least one valid IPv4 CIDR block.
  • An expiry date, when supplied, is in the future.
  • The deployment remains within its plan's access-rule limit.

Managing Access Rules

The Access Rules tab lists address ranges, enabled protocols, expiry status, and creation times. Delete a rule to remove it and its corresponding cloud infrastructure configuration. Other active rules retain their permissions.

Plan Limits

ResourceStandardPerformanceEnterprise
Access rules per deployment31020

Rules that LaserData creates for VPC peering do not appear in the list but count toward the limit, so a deployment can reach it with fewer rules in the list. The data access rule does not count.

Audit

The audit log records rule creation, updates, and deletion. Creation records identify the requester, CIDRs, and protocols. Update records preserve previous values. Deletion records identify who removed the rule and when.

API Reference

Use API keys for programmatic access. Creating and deleting rules require deployment:access:manage. Listing rules requires deployment:access:read.

Create a Rule

curl -X POST {supervisor_url}/deployments/{deployment_id}/access_rules \
  -H "ld-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "production-api-access",
    "cidr_blocks": ["10.0.0.0/16", "172.16.0.0/12"],
    "rules": {
      "iggy_tcp": true,
      "iggy_http": true
    },
    "valid_to": "2026-12-31T23:59:59Z",
    "remarks": "Production API servers"
  }'

List Rules

curl {supervisor_url}/deployments/{deployment_id}/access_rules \
  -H "ld-api-key: YOUR_API_KEY"
[
  {
    "id": 1,
    "name": "production-api-access",
    "remarks": "Production API servers",
    "rules": {
      "iggy_http": true,
      "iggy_tcp": true,
      "iggy_websocket": false,
      "iggy_udp": false,
      "kafka": false
    },
    "cidr_blocks": ["10.0.0.0/16", "172.16.0.0/12"],
    "valid_to": "2026-12-31T23:59:59Z",
    "created_at": "2025-01-15T10:30:00Z"
  }
]

Delete a Rule

curl -X DELETE {supervisor_url}/deployments/{deployment_id}/access_rules/{rule_id} \
  -H "ld-api-key: YOUR_API_KEY"

Allow My IP Requests

Both requests take a signed-in session or an API key. GET {supervisor_url}/deployments/{deployment_id}/access_rules/my_ip reports the address LaserData sees and whether Allow My IP can admit it. It needs deployment:access:read.

{
  "ip_address": "203.0.113.7",
  "refusal": null,
  "covered_by": {
    "id": 1,
    "name": "office",
    "cidr_blocks": ["203.0.113.0/24"],
    "valid_to": null
  }
}

refusal is ipv6, not_public or missing when the address cannot be admitted, and null otherwise. covered_by is the rule in the list that already admits the address on Iggy HTTP, other than the caller's own Allow My IP rule, or null.

POST {supervisor_url}/deployments/{deployment_id}/access_rules/my_ip needs deployment:access:manage and answers 201 with the created rule in the list format. An optional JSON body chooses the protocols, for example {"iggy_tcp": true} before a Laser SDK app connects. No body, or a body choosing none, admits Iggy HTTP.

StatusCodeWhen
400ip_address_not_allowedThe address is missing, IPv6, or not public
400deployment_has_no_public_ipThe deployment has no public IP address or runs On-Premise
409ip_address_already_allowedAnother rule already admits the address on every chosen protocol. The client can connect as it is
409deployments_access_rules_limit_reachedThe deployment has reached its plan limit
409deployment_operation_in_progressAnother rule change on the deployment is running. Retry shortly

On this page