--- title: "Installing on AWS" slug: "installing-aws" updated: 2024-12-20T20:31:15Z published: 2024-12-20T20:31:15Z canonical: "documentation.decisions.com/installing-aws" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Installing on AWS ## ## Overview The following document demonstrates how to setup a [**v9** **Installation**](https://documentation.decisions.com/v9/docs/installation-ms-sql) on [**Amazon Web Services**](https://aws.amazon.com/). Installing to AWS gives **Server** **Administrators** the flexibility and scalability of AWS to their Decisions environment. --- ## AWS Specifications PLEASE READ BEFORE CONTINUING - IMPORTANT!!!  Decisions is a robust software with a wide variety of use cases. The deploying organizations' Senior Database Administrator (DBA) should be involved in recommending resources. - **Standard Specifications** - recommended for optimal performance in the average standalone server environment - local development installs may run on reduced system requirements - **Enterprise Specifications** - recommended for data-heavy [clustered](https://documentation.decisions.com/v9/docs/about-clustering) environments and/or organizations with long procurement/change request cycles The specifications outlined in this article are intended for the **Application Server** based on these server types: - **Production Server**: a live environment where created processes are leveraged by end-users (customers) - **Non-Production Server**: non-customer facing environment used for testing and development to assess production readiness - **Repository Server**: non-customer facing environment used to help maintain version control and migrating projects between servers ### Production Server | | **Instance Class** | **VCPU** | **Memory** | **Storage** | | --- | --- | --- | --- | --- | | **Standard** | t3.xlarge | 4-Core | 16 GB RAM | 100 GB | | **Enterprise** | t3.2xlarge | 8-Core | 32 GB RAM | 100 GB | ### Non-Production Server | | **Instance Class** | **VCPU** | **Memory** | **Storage** | | --- | --- | --- | --- | --- | | **Standard** | t3.xlarge | 4-Core | 16 GB RAM | 100 GB | ### Repository Server | | **Instance Class** | **VCPU** | **Memory** | **Storage** | | --- | --- | --- | --- | --- | | **Standard** | t3.xlarge | 4-Core | 16 GB RAM | 100 GB | --- ## Start an AWS Database (RDS) Time-Zone Compatibility The **Application** **Server** and **Database** **Server** must be set to the same Time-Zone. 1. From AWS, navigate to **Services > Database > RDS**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-22_16h15_09.png) 2. From the **Amazon** **RDS** **Databases** page, click **Create database**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-22_16h19_59.png) 3. From the **Select** **Engine** window, **Select** **Microsoft** **SQL Server**. Then, choose the specific type of SQL based on the environment's needs (for most deployments **SQL** **Server** **SE** is used).![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/selectSQLServer(1).png) 4. Configure the **DB** **Details** as is needed, then click **Next** **Step**. For most **Production** applications **4 CPU, 15 GB RAM** works well.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/02_22_2022_16h_29m.png) 5. From **Configure** **Advanced** **Settings**, under **Network & Security > VPC Security Group (s)** select **Create new Security Group** unless there is one already configured. --- ## **Start an EC2 Instance** Launch a new **Windows** **Server** **Instance** and choose the **size** and **OS** **Version** in accordance with the [**Amazon Web Services (AWS) Specifications**](https://documentation.decisions.com/v9/docs/installation-requirements#amazon-web-services-aws-specifications:~:text=100%20GB-,Amazon%20Web%20Services%20(AWS)%20Specifications,-Server%20Type). After the **Instance** starts, configure any software requirements that are missing from the image. --- ## **Install Decisions on an EC2 Instance** 1. **Remote** **Desktop** into the **Instance** and run **DecisionsServerInstaller.exe**. Proceed with [installation](https://documentation.decisions.com/v9/docs/installation-ms-sql) until the **D****atabase Setup** screen is reached. In the **Database** **Setup** dialog, select **MS SQL** for the **Database Type.** Then, locate the **Endpoint** address for the **RDS** **Instance**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-23_16h_16.png) 2. Enter this **Endpoint** address in the **DB Server** field**.**Required ConfigurationsFor the **Decisions** **Server** to be allowed to connect to the **RDS** **Instance**, the **RDS** **Security** **Groups** and/or **VPC** must be configured to allow communication from the **EC2** **Instance**. For more information see **Amazon's** articles on [**Security Groups**](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.RDSSecurityGroups.html) and [**RDS in VPC**](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.html).![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-22_16h48m.png) 3. Back in the **RDS** **Dashboard**, edit the **RDS** **Security** **Group** to allow **SQL** **Connections** from the **Internal** **IP** **Address** of the **EC2** **Application** **Server**; find and select the Security Group for the **RDS** **Instance**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-23_16h_15.png) 4. Unde**r Security Group > Inbound**, click **Edit**. From the **Edit** **inbound** **rules** window, add a **Rule** that allows MS SQL from the **Internal** **IP** **Address** of **EC2** **Instance**. Then, click **Save**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-23_16h_25.png) 5. Select **T****est** on the **Database Setup** screen to ensure that there is successful communication between these two servers. Continue the [Decisions Installation](https://documentation.decisions.com/v9/docs/installation-ms-sql#installing-decisions-part-2-database-setup-and-hosting-options-). ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-02-23_16h34(1).png) --- For more information regarding **Installation**/**Setup**, see [Decisions Forum Installation/Setup](https://support.decisions.com/forum/forum2-installation--setup.aspx).