Configure required resources
Set the disk space allocation and compute resources for a database
Configure the database expiration
Set whether the database expires, and how to determine when the database expires
Provide a custom configuration file
Enter the content of a custom configuration file for a MySQL or PostgreSQL database
For a Tonic Ephemeral database, you can specify disk space and compute resources. After you set these values for a database, you cannot change them.
In the Disk space allocation field, specify the size in gigabytes to allocate to the database and to each of its snapshots. For a free trial, a database cannot use more than 100 GB.
Ephemeral uses that value to calculate the amount of space being used by the current databases and snapshots, and to determine the amount of disk space that can be used before Ephemeral displays a warning. For information about how to monitor disk space usage and configure the alert threshold, go to Monitoring your disk storage.
From the Compute resources dropdown list, select the option to use for the combination of vCPUs and memory:
Nano - 0.125 vCPU with 0.5 GB RAM
Micro - 0.5 vCPU with 2 GB RAM
Small - 1 vCPU with 4 GB RAM
Medium - 2 vCPU with 8 GB RAM
Large - 4 vCPU with 16 GB RAM
For a MySQL or PostgreSQL database, you can provide a customization file to ensure that the database is configured correctly.
On the Settings tab of the database details panel, to provide the customization file:
Toggle Custom configuration file to the on position.
In the text area, paste the contents of the customization file.
You can configure the database to expire automatically, or to pause outside of business hours. When you start a new database, the default configuration is to expire the database after 8 hours of inactivity.
To set the expiration, on the Settings tab of the details panel, Establish an expiration timer for the database must be in the on position.
When you enable expiration, the options are:
Inactivity - The database expires when it hasn't been used for a specified amount of time. For example, expire the database after it hasn't been used for 3 hours. By default, a database expires after 8 hours of inactivity.
A set duration - The database expires after a specific amount of time. For example, expire the database 3 days after it is created. If the database is in use when it is scheduled to expire, Tonic Ephemeral waits to expire the database until an hour after it is no longer in use.
Business hours - The database is only active during specified business hours, and pauses outside of those hours. The database does not expire. For example, pause the database each weekday at 5:00 PM, and resume it the next weekday at 7:00 AM. If the database is in use when the business hours end, Ephemeral waits to pause the database until an hour after it is no longer in use.
To set the expiration based on inactivity:
Click Inactivity.
Select the length of inactivity after which the database expires.
Ephemeral provides built-in options to expire the database after 3, 8, or 24 hours of inactivity. To configure a custom expiration:
Click Custom.
In the value field, provide the number of hours or days of inactivity after which to expire the database.
Click the unit to use (Hours or Days).
To set the expiration based on a specific time period:
Click Set Duration.
Select the length of time that the database is active.
In the value field, provide the number of hours or days that the database is active.
Click the unit to use for the duration (Hours or Days).
To limit a database to specified business hours:
Click Business Hours.
From the Timezone dropdown, select the time zone to use to determine the business hours.
From the From and To dropdowns, select the start and end days when business hours are in effect. For example, for a traditional 5-day work week, the start day is Monday and the end day is Friday.
From the Start and End dropdowns, select the start and end time for each business day. For example, your business hours might be from 7:00 AM to 6:00 PM.
