LogoLogo
Release notesAPI docsDocs homeEphemeral CloudTonic.ai
  • Tonic Ephemeral guide
  • About Tonic Ephemeral
  • Getting started with the Ephemeral free trial
  • Managing your Ephemeral account
  • Managing Databases
    • Viewing the list of databases
    • Starting a database
    • Changing the database configuration
    • Database configuration settings
      • Setting the required resources for a database
      • Setting the database expiration
      • Providing a custom configuration file
    • Connecting to a database
    • Resetting a database
    • Deactivating and reactivating databases
    • Managing auto snapshots
    • Tracking database activity
    • Deleting a database
  • Managing user snapshots
    • About user snapshots
    • Viewing the user snapshot list
    • Creating a user snapshot from an Ephemeral database
    • Creating a user snapshot from imported data
    • Editing a user snapshot
    • Creating a database from a user snapshot
    • Deleting a user snapshot
  • Installing and configuring Ephemeral
    • Ephemeral architecture
    • Configuring an allowlist for Ephemeral Cloud database connections
    • Installing a self-hosted instance of Ephemeral
      • System requirements
      • Deploying Ephemeral with Helm
    • Configuring database access on a self-hosted instance
    • Configuring tolerations and node selectors
    • Managing access to Ephemeral
      • Managing Ephemeral users
      • Enabling SSO on a self-hosted instance
        • Google
        • Okta
    • Setting the registry location for data volumes
    • Managing custom images
      • Creating, editing, and deleting custom images
      • Oracle image configuration
    • Configuring automatic deletion of snapshots
  • Monitoring and data collection
    • Monitoring your Ephemeral billed usage
    • Monitoring your disk storage
    • Data that Tonic.ai collects
  • Using the Ephemeral API
    • About the Ephemeral API
    • Configuring Ephemeral
    • Getting information about Ephemeral databases
    • Starting a database
    • Managing databases
    • Managing snapshots
Powered by GitBook
On this page
  • Registry configuration
  • Setting up the registry location
  • Getting the current registry configuration
  • Updating the registry configuration
  • Storage alert threshold and snapshot deletion
  • Getting the current storage alert threshold and snapshot deletion settings
  • Updating the storage alert threshold and snapshot deletion settings

Was this helpful?

Export as PDF
  1. Using the Ephemeral API

Configuring Ephemeral

Registry configuration

Setting up the registry location

Tonic Ephemeral uses the registry location and access credentials to store data volumes that you can use to create Ephemeral databases.

To set the initial registry configuration, use:

POST /api/registry

The request body contains the configuration, which includes the URL, the authentication type, and the credentials for the specified authentication type.

Getting the current registry configuration

To get the current registry configuration, use:

GET /api/registry

The response includes the registry identifier, which you need to use to update the current registry configuration.

Updating the registry configuration

To update the registry configuration, use:

PUT /api/registry/{registryId}

Storage alert threshold and snapshot deletion

Getting the current storage alert threshold and snapshot deletion settings

You can configure how much Ephemeral storage is used before Ephemeral displays an alert. You can also configure whether to automatically delete snapshots after a specified period of time.

To get the current settings, use:

​​GET /api/organization/disk-storage-settings

Updating the storage alert threshold and snapshot deletion settings

To change the current storage alert threshold and snapshot deletion configuration, use:

PUT /api/organization/disk-storage-settings

PreviousAbout the Ephemeral APINextGetting information about Ephemeral databases

Last updated 1 year ago

Was this helpful?