Skip to main content

Bucket Explorer Management Endpoints

Note: Utility resources (terminals, bucket explorers, db monitors) share common patterns. See 11-utility-resources.md for a consolidated overview; this file focuses on bucket-explorer specifics.
Bucket explorers are resources that can be connected to storage buckets to browse and explore their contents. Similar to terminals that connect to instances, bucket explorers provide a way to interact with S3 buckets.

Create Bucket Explorer

  • POST /api/:projectSlug/:environmentSlug/bucket-explorers - Create a new bucket explorer resource and S3 storage bucket
Description: The name provided will be used directly as the S3 bucket name. The endpoint will automatically create the S3 bucket and connect it to the bucket explorer. Important:
  • The name must be a valid S3 bucket name (3-63 characters, lowercase, alphanumeric, hyphens, periods)
  • Bucket names must be globally unique across all AWS accounts
  • The endpoint will automatically create the S3 bucket and connect it to the bucket explorer
Request Body:
S3 Bucket Naming Rules:
  • Must be 3 to 63 characters long
  • Must begin and end with a letter or number
  • Can contain lowercase letters (a-z), numbers (0-9), periods (.), and hyphens (-)
  • Cannot contain consecutive periods (..)
  • Cannot be formatted as an IP address (e.g., 192.168.1.1)
  • Cannot start with “xn—” or end with “-s3alias”
  • Must be globally unique across all AWS accounts
Example:
Example Response:
Error Response (Invalid bucket name):
Error Response (Bucket already exists):

List Bucket Explorers

  • GET /api/:projectSlug/:environmentSlug/bucket-explorers - List all bucket explorers for a project environment
Example:
Example Response:

Get Bucket Explorer Details

  • GET /api/:projectSlug/:environmentSlug/bucket-explorers/:explorerId - Get details of a specific bucket explorer
Example:
Example Response:

Update Bucket Explorer

  • PATCH /api/:projectSlug/:environmentSlug/bucket-explorers/:explorerId - Update a bucket explorer
Request Body:
Example:
Example Response:

Delete Bucket Explorer

Bucket explorer deletion is performed only via the unified resources API:
  • DELETE /api/:projectSlug/:environmentSlug/resources/:resourceId
Use the bucket explorer’s database ID. The service removes all resource connections, then soft-deletes the resource. See Resources API — Delete Resource by ID. Example:

Connecting Bucket Explorers to Storage Buckets

Bucket explorers can be connected to storage buckets using the Resource Connections API. This allows the bucket explorer to browse and interact with the contents of the connected storage bucket. Example: Connect bucket explorer to a storage bucket
See the Resource Connections documentation for more details on connecting resources.

Status Values

Bucket explorers have the following status values:
  • inactive - Default status when created
  • active - Explorer is active and connected
  • connecting - Currently establishing connection
  • error - Connection error occurred