Fast links for AWS, Google Cloud, and Azure

Jump straight to AWS, GCP, and Azure.

the fastest way to your cloud console cld.cat is a tiny shortcut layer for cloud consoles. Type a short path like cld.cat/aws/ec2/us-west-2, cld.cat/gcp/compute/us-central1, or cld.cat/az/vm/eastus and land directly on the destination. It also includes a keyboard-first search UI inspired by Raycast and Spotlight.

Browse the URL map

cld.cat/aws/ec2/us-west-2 Amazon EC2 in Oregon

cld.cat/gcp/bigquery/us BigQuery in US multi-region

cld.cat/az/keyvault/eastus Azure Key Vault in East US

cld.cat/ec2/us-east-1 Alias with explicit region

/logs Default logs destination

Keyboard-first search

Press / or Ctrl/Cmd + K from anywhere on the page to open a fast command palette. Search by service, provider, alias, or region.

Open the shortcut palette

Search for commands like ec2, aws logs us-east-1, bigquery us, or azure key vault eastus.

Fuzzy-ish matching

Search with service names, aliases, provider names, or regions. Results are ranked so exact and close matches rise to the top.

Region-aware routes

Shortcuts can include a region segment like /aws/lambda/us-west-2 or a plain command such as ec2 us-east-1.

Fast actions

Use Enter to open the selected result, arrow keys to move, and one click to copy the path or jump directly to the target URL.

How it works

Every shortcut is a simple redirect. The path stays human-friendly, while your edge redirect layer forwards you to the actual provider console URL underneath.

Canonical paths

Use a predictable structure like /aws/ec2/us-west-2, /gcp/run/us-central1, or /az/aks/eastus.

Short aliases

Common shortcuts such as /ec2, /bq, and /kv save even more typing.

Neutral routes

Generic paths like /logs, /compute, and /billing can point to your default platform.

Built for the big three

The URL system is cloud-agnostic. Keep one clean pattern across providers and only memorize a small set of service names.

AWS

Prefix: /aws

Examples: /aws/ec2/us-west-2, /aws/s3/us-east-1, /aws/lambda/eu-west-1, /aws/logs/ap-southeast-2.

Google Cloud

Prefix: /gcp

Examples: /gcp/compute/us-central1, /gcp/storage/us, /gcp/gke/us-west1, /gcp/bigquery/eu.

Azure

Prefix: /az

Examples: /az/vm/eastus, /az/keyvault/westus2, /az/aks/canadacentral, /az/monitor/eastus2.

URL map

The structure is intentionally simple: canonical routes for clarity, short aliases for speed, neutral routes for defaults, and an optional third segment for region.

Canonical format

/{provider}/{service}/{region?}

/aws/ec2/us-west-2
/gcp/compute/us-central1
/az/vm/eastus

Friendly aliases

/ec2/us-east-1  → /aws/ec2/us-east-1
/bq/us          → /gcp/bigquery/us
/kv/eastus      → /az/keyvault/eastus

Neutral shortcuts

/compute
/storage
/logs
/billing

Provider aliases

/azure/*   → /az/:splat
/google/*  → /gcp/:splat

Popular shortcuts

A small number of routes will cover most daily use. Start here, then expand the map over time.

Quick examples

/aws/ec2/us-west-2 /aws/s3/us-east-1 /aws/lambda/eu-west-1 /gcp/compute/us-central1 /gcp/gke/us-west1 /gcp/bigquery/us /az/vm/eastus /az/aks/canadacentral /az/keyvault/westus2 /ec2/us-east-1 /bq/us /kv/eastus /logs /billing

Example redirect rules for region-aware aliases

/ec2/:region      /aws/ec2/:region 302
/ddb/:region      /aws/dynamodb/:region 302
/eb/:region       /aws/elasticbeanstalk/:region 302
/bq/:region       /gcp/bigquery/:region 302
/kv/:region       /az/keyvault/:region 302
/aws/:service/:region   /go/aws/:service/:region 302