> For the complete documentation index, see [llms.txt](https://docs.feast.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feast.dev/v0.24-branch/how-to-guides/feast-snowflake-gcp-aws/deploy-a-feature-store.md).

# Deploy a feature store

The Feast CLI can be used to deploy a feature store to your infrastructure, spinning up any necessary persistent resources like buckets or tables in data stores. The deployment target and effects depend on the `provider` that has been configured in your [feature\_store.yaml](/v0.24-branch/reference/feature-repository/feature-store-yaml.md) file, as well as the feature definitions found in your feature repository.

{% hint style="info" %}
Here we'll be using the example repository we created in the previous guide, [Create a feature store](/v0.24-branch/how-to-guides/feast-snowflake-gcp-aws/create-a-feature-repository.md). You can re-create it by running `feast init` in a new directory.
{% endhint %}

## Deploying

To have Feast deploy your infrastructure, run `feast apply` from your command line while inside a feature repository:

```bash
feast apply

# Processing example.py as example
# Done!
```

Depending on whether the feature repository is configured to use a `local` provider or one of the cloud providers like `GCP` or `AWS`, it may take from a couple of seconds to a minute to run to completion.

{% hint style="warning" %}
At this point, no data has been materialized to your online store. Feast apply simply registers the feature definitions with Feast and spins up any necessary infrastructure such as tables. To load data into the online store, run `feast materialize`. See [Load data into the online store](/v0.24-branch/how-to-guides/feast-snowflake-gcp-aws/load-data-into-the-online-store.md) for more details.
{% endhint %}

## Cleaning up

If you need to clean up the infrastructure created by `feast apply`, use the `teardown` command.

{% hint style="danger" %}
Warning: `teardown` is an irreversible command and will remove all feature store infrastructure. Proceed with caution!
{% endhint %}

```
feast teardown
```

\*\*\*\*


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.feast.dev/v0.24-branch/how-to-guides/feast-snowflake-gcp-aws/deploy-a-feature-store.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.