<commit_before>All-in-one Installation
=======================
|st2| provides an all-in-one installer aimed at assisting users with the initial setup and configuration. The installer comes pre-bundled in a number of different provisioning options for convenience, or can also be manually deployed and installed manually on a server.

Pre-Requisites
-------------
Before getting started, it is necessary to do a bit of pre-planning to integrate |st2| into an environment. Below is a checklist of items to prepare before running the installer.

#. A server. See below for the list of pre-bundled options, or bring your own.
#. Hostname of new server setup with DNS.
#. Admin Password.
#. Administrative SSH Public/Private Keys *(Optional)*
#. SSL Certificates *(Optional)*
#. Chat service connection credentials *(Optional)*

The initial setup is designed to configure itself to a freshly deployed server with no additional services running. If you do not have or do not wish to provide SSL and SSH keys during the initial setup, |st2| will generate random new keys automatically.

Sizing the Server
-----------------
A standard all-in-one installation has all of the various components of |st2|, as well as the supporting infrastructure components. While the system can operate with less equipped servers, these are recommended for the best experience while testing or deploying |st2|.

Testing
~~~~~~~
* Single or Dual CPU system
* At least 4GB of RAM
* Recommended EC2: **m4.large**

Production
~~~~~~~~~~
* Quad core CPU system
* >16GB RAM
* Recommended EC2: **m4.xlarge**

Deployment Options
==================

Amazon Web Services (AWS)
-------------------------
|st2| provides pre-built AMI images containing the latest stable release of |st2|. These images come equipped with the *All-in-one installer* to help you get setup quickly and easily. To get started:<commit_msg>bumping down to 2GB<commit_after>All-in-one Installation
=======================
|st2| provides an all-in-one installer aimed at assisting users with the initial setup and configuration. The installer comes pre-bundled in a number of different provisioning options for convenience, or can also be manually deployed and installed manually on a server.

Pre-Requisites
-------------
Before getting started, it is necessary to do a bit of pre-planning to integrate |st2| into an environment. Below is a checklist of items to prepare before running the installer.

#. A server. See below for the list of pre-bundled options, or bring your own.
#. Hostname of new server setup with DNS.
#. Admin Password.
#. Administrative SSH Public/Private Keys *(Optional)*
#. SSL Certificates *(Optional)*
#. Chat service connection credentials *(Optional)*

The initial setup is designed to configure itself to a freshly deployed server with no additional services running. If you do not have or do not wish to provide SSL and SSH keys during the initial setup, |st2| will generate random new keys automatically.

Sizing the Server
-----------------
A standard all-in-one installation has all of the various components of |st2|, as well as the supporting infrastructure components. While the system can operate with less equipped servers, these are recommended for the best experience while testing or deploying |st2|.

Testing
~~~~~~~
* Single or Dual CPU system
* At least 2GB of RAM
* Recommended EC2: **m3.medium**

Production
~~~~~~~~~~
* Quad core CPU system
* >16GB RAM
* Recommended EC2: **m4.xlarge**

Deployment Options
==================

Amazon Web Services (AWS)
-------------------------
|st2| provides pre-built AMI images containing the latest stable release of |st2|. These images come equipped with the *All-in-one installer* to help you get setup quickly and easily. To get started:
{'fraction_non_alphanumeric': 0.11267605633802817, 'fraction_numerical': 0.0077066170608557005, 'mean_word_length': 4.00531914893617, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3378697', 'n_tokens_mistral': 946, 'n_tokens_neox': 879, 'n_words': 516}