docs: add managed vm documentation section (#2437)

Signed-off-by: hagen1778 <roman@victoriametrics.com>

docs/managed_victoriametrics/README.md

@@ -0,0 +1,40 @@
+---
+sort: 22
+---
+
+# Managed VictoriaMetrics
+
+VictoriaMetrics is a fast and easy-to-use monitoring solution and time series database. 
+It integrates well with existing monitoring systems such as Grafana, Prometheus, Graphite, 
+InfluxDB, OpenTSDB and DataDog - see [these docs](https://docs.victoriametrics.com/#how-to-import-time-series-data) for details. 
+
+The most common use cases for VictoriaMetrics are:
+* Long-term remote storage for Prometheus;
+* More efficient drop-in replacement for Prometheus and Graphite
+* Replacement for InfluxDB and OpenTSDB, which uses lower amounts of RAM, CPU and disk;
+* Cost-efficient alternative for DataDog.
+
+We are glad to announce the availability of Managed VictoriaMetrics 
+at AWS Marketplace - [try it right now](https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc)!
+
+Managed VictoriaMetrics allows users running VictoriaMetrics at AWS without the need to perform typical 
+DevOps tasks such as proper configuration, monitoring, logs collection, access protection, software updates, 
+backups, etc.
+
+We run Managed VictoriaMetrics instances in our environment at AWS while providing easy-to-use endpoints 
+for data ingestion and querying. And the VictoriaMetrics team takes care of optimal configuration and software 
+maintenance.
+
+Managed VictoriaMetrics comes with the following features:
+
+* It can be used as a Managed Prometheus - just configure Prometheus or vmagent to write data to Managed VictoriaMetrics and then use the provided endpoint as a Prometheus datasource in Grafana;
+* Every Managed VictoriaMetrics instance runs in an isolated environment, so instances cannot interfere with each other;
+* Managed VictoriaMetrics instance can be scaled up or scaled down in a few clicks;
+* Automated backups;
+* Pay only for the actually used compute resources - instance type, disk and network.
+
+See more about Managed VictoriaMetrics in the following articles:
+* [Managed VictoriaMetrics announcement](https://victoriametrics.com/blog/managed-victoriametrics-announcement)
+* [Pricing comparison for Managed Prometheus](https://victoriametrics.com/blog/managed-prometheus-pricing/)
+* [Monitoring Proxmox VE via Managed VictoriaMetrics and vmagent](https://victoriametrics.com/blog/proxmox-monitoring-with-dbaas/)
+

docs/managed_victoriametrics/quickstart.md

@@ -0,0 +1,65 @@
+# Quick Start
+
+Managed VictoriaMetrics - is a database-as-a-service platform, where users can run the VictoriaMetrics 
+that they know and love on AWS without the need to perform typical DevOps tasks such as proper configuration, 
+monitoring, logs collection, access protection, software updates, backups, etc.
+
+## How to register
+
+Managed VictoriaMetrics id distributed via [AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc).
+To start using the service, one should have already registered AWS account 
+and visit [VictoriaMetrics product page](https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc).
+See more details [here](https://dbaas.victoriametrics.com/howToRegister).
+
+## Creating instance
+
+Instances is a page where user can list and manage VictoriaMetrics single-node instances. 
+To create an instance click on the button `Create`:
+
+<p>
+  <img src="quickstart-instances.png" width="800" alt="">
+</p>
+
+In the opened form, choose parameters of the new instance such as:
+
+* `Instance type` from preset of AWS instances (you always can change the type later);
+* `Region` and `Zone` where instance should run;
+* Desired `disk size` for storing metrics (you always can expand disk size later);
+* `Retention` period for stored metrics.
+
+<p>
+  <img src="quickstart-instance-create.png" width="800" alt="">
+</p>
+
+Once created, instance will remain for a short period of time in `PROVISIONING` status 
+while the hardware spins-up, just wait for a couple of minutes and reload the page. 
+You'll also be notified via email once provisioning is finished:
+
+<p>
+  <img src="quickstart-instance-provisioning.png" width="800" alt="">
+</p>
+
+## Access
+
+After transition from `PROVISIONING` to `RUNNING` state, VictoriaMetrics is fully operational 
+and ready to accept write or read requests. But first, click on instance name to get the access token:
+
+<p>
+  <img src="quickstart-tokens.png" width="800" alt="">
+</p>
+
+Access tokens are used in token-based authentication to allow an application to access the VictoriaMetrics API. 
+Supported token types are `Read-Only`, `Write-Only` and `Read-Write`. Click on token created by default 
+to see usage examples:
+
+<p>
+  <img src="quickstart-tokens-usage.png" width="800" alt="">
+</p>
+
+Follow usage example in order to configure access to VictoriaMetrics for your Prometheus, 
+Grafana or any other software.
+
+## Modifying
+
+Remember, you always can add, remove or modify existing instances by changing their type or increasing the disk space. 
+However, such an update requires an instance restart and may result into a couple of minutes of downtime.