# Best practices

{% hint style="warning" %}
This page is "work-in-progress", it will be updated soon
{% endhint %}

* For best possible results, consider running SnowKill every minute.
* For ease of maintenance, you may run SnowKill as basic serverless application (AWS Lambda, Fargate, etc.). One CPU core and a few hundred Mb of RAM should be sufficient.
* For better security, consider using private key authentication method for SnowKill [administration user](https://docs.snowkill.net/implementation-details/administration-user). Try to avoid using password for users with programmatic access.
* Consider using an additional queue (SNS, SQS, Pub/Sub, etc.) for notifications to avoid losing messaged if your notification channel is temporary not available.
* Consider using OLTP database for log storage (e.g. [Postgres table](https://docs.snowkill.net/storage/built-in-storages/postgres-table)) instead of [Snowflake table](https://docs.snowkill.net/storage/built-in-storages/snowflake-table). Snowflake table helps to get you started, but it is not the most efficient setup for production.


---

# Agent Instructions: 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:

```
GET https://docs.snowkill.net/deployment/best-practices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
