> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/release-instant-datasets/quickstart.md). # Quickstart This is a short guide to getting your first dataset set up and using one of the databases. 1. Create a Release Instant Datasets account. 2. Create a cloud integration. 3. Create a dataset. 4. Check out a database. 5. Integration with our APIs. ## Create a Release Instant Datasets account Visit the [Release Instant Datasets registration](https://beta.release.com/instantdatasets/register) page and sign up with your email address or using Google OAuth. Verify your email by clicking on the link in the email Release sends you. ## Create a cloud integration Navigate to the Cloud Integrations page and click on **Create Cloud Integration**.

The cloud integration connects Release to your cloud account to orchestrate Instant Dataset activities there. Give the cloud integration a name and select your cloud provider where your database snapshots are located. Click **Create Cloud Integration**.

Give your cloud integration a recognizable name

Now you can configure your cloud integration. If AWS is your cloud provider, you can click the **Configure on AWS** button to be redirected to AWS where you can set up a CloudFormation stack with a minimal IAM role allowing Release to manage your datasets.

Configuring an AWS Cloud Integration will redirect you to AWS

Launch the stack, give it 2-3 minutes to create, and your new cloud integration should update. ## Create a dataset When your cloud integration is configured, you can create a dataset. Click the **Create Dataset** button to get started.

Create a dataset with your cloud integration

Give the dataset a name. In "Cloud Settings", select the appropriate cloud integration, the snapshot you want to use, and the instance type. In "Database Settings", add the database name, a user password, and the target number of available databases.

Click **Create Dataset**. It may take up to a minute for the dataset to be initialized after which the target number of databases will be created. How long this takes depends on the size of your database, the instance type, and even the time of day, depending on the cloud provider and region, but it usually takes between ten minutes and an hour to create instances.

## Check out a database Once your dataset and its databases are ready, you can check out one of the databases to use.

The dataset and its databases are available to be checked out

Click into the dataset you created. Click **Check Out** to associate yourself with a database in the dataset. After checking out the database, click the **Connect** button to view different connection options.

## Integration with our APIs We've made all our Instant Dataset functionality available via REST APIs so that it is easy to integrate into your tooling. Documentation of all the endpoints can be found [here](https://api.release.com/api-docs/). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.release.com/release-instant-datasets/quickstart.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.