--- title: "AWS Container Setup" slug: "aws-container-setup-1" updated: 2025-06-30T16:23:01Z published: 2025-06-30T16:23:01Z --- > ## 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. # AWS Container Setup ## Overview Through its use of Modules, Decisions provides the capability to integrate with many different [**Container**](/v9/docs/containers-overview)****and [**Docker**](https://documentation.decisions.com/docs/docker) based systems. One such common containerized service integration is integration with **Amazon Web Services (AWS)**. Integrating with AWS gives users the ability to leverage Container Orchestration Architecture; this in turn allows users to scale and descale implementations rapidly, allowing for better performance, cost, and efficiency. The following document demonstrates how to configure a Decisions image on an **AWS Container**. --- ## Example Example Prerequisites  - **EC2**instances in AWS with their associated RDS instances; the EC2 instances must be a current **Windows****OS**and the RDS instance is required for **SQL****Express** - Decisions installation on the EC2 instances. (For more info see [Installing on AWS](https://documentation.decisions.com/docs/installation-guide#aws-connection)) - **.NET SDK**installed on the Decisions instance - The current version of .NET SDK can be confirmed by running the following CMD: "dotnet --list-sdks" - To download the **Windows****Installer**for **.NET SDK 6.0**, see [Download .Net Core 6.0.](https://dotnet.microsoft.com/en-us/download/dotnet/6.0/runtime) 1. After installing **Decisions**, navigate to **System > Administration > Features**. 2. Locate the **Docker****Module**, then click DETAILS and then INSTALL. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-23_09h49_57.png) 3. After the Module installs, open **DecisionsServerIntaller.exe** and select RESTART SERVICE. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-30_10h06_05(1).png) 4. Back in **Decisions****Studio**, navigate to **System > Security > Accounts**, select CREATE ACCOUNT, and create a new **User****Account**; for this example, provide the **Username**"docker@decisions.com" and the **Password**"docker". Default Docker AccountThis Docker Account is the **Default****Account**that is used to talk with the **EC2**instance; this can be changed in AWS if the default Account is not desired.  ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-23_09h53_18.png) 5. After creating the Account, create an **AWS Cluster** with the default configurations by navigating to **All Services > Containers >** **Elastic Container Serivcer > Clusters**and selecting **Create Cluster.**![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_15h13_50.png) 6. From the **Select cluster template**panel of the Create Cluster window, select **EC2 Windows + Networking**, then click **Next step**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_16h05_131.png) 7. From the Configure cluster panel, provide the desired **Cluster****name**. Then, leave the rest of the values set to their default options, and click **Create**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_16h07_43.png) 8. Afterward, navigate to**All Services > Containers >** **Elastic Container Servicer > Task Definitions**and click **Create new Task Definition**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_14h38_56.png) 9. Select **EC2**, then click Next step. 10. While maintaining the default configurations for this example set up, declare a **Task Definition Name**then set the **Task** **memory**and **Task****CPU**values. Task Size Flexibility Note that the **Task Size** settings can be adapted at the user's discretion for their environment. This example uses **1VCPU******for **Task****CPU**and **1GB** for **Task memory** respectively. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_16h11_09.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_16h20_41.png) 11. Scroll down to **Container****Definitions**, then click **Add****Container**. 12. Give the Container a Name, add the **Docker****Image**"decisionscore/unstable:latest" in the **Image**box.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_14h49_58.png) 13. Under **Environmental****Variables**, provide the **Keys**and **Values**listed on the chart below, then click **Add**. Default Username and Password Keys/ValuesBoth**SETTING_USERNAME** and **SETTING_PASSWORD** keys and their respective **Values**are optional. If these values are not used in the configuration, **Decisions** and the **EC2**instance will use the default values of the used **Account**.  | Key | Value | | --- | --- | | SETTING_DATABASE_CONNECTION | RDSConnectionString | | SETTING_PORTAL_BASE_URL | http://decisionsIPorDNSname/decisions | | SETTING_SHM_BASE_URL | http://decisionsIPorDNSname/decisions/Primary/REST | | SETTING_USERNAME | AdminEmail | | SETTING_PASSWORD | AdminPassword | | SETTING_TAKE_REQUESTS | true | ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_16h23_26.png) 14. After the Container has been added, scroll to the bottom of the page and click **Create**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_15h07_59.png) 15. Navigate back to the **Clusters**window, select the previously created **Cluster**. 16. Under the **Tasks**tab, select **Run new Task**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_15h25_40(1)(1).png) 17. From the **Run****Task**window select the Task from the **Task Definition > Family**dropdown. 18. Under **VPC and security groups**, select the desired **Subnet**,****then scroll to the bottom of the page and select **Run****Task**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2021-08-19_15h40_06(2).png) 19. Navigate to the **Logs**tab by selecting the Task and clicking Logs; periodically click the **Refresh**button on the right-side of the page until the Logs populate with the **Container****Status**. Log Population Behavior Depending on the type of **EC2****instance**created, it may take a bit for the **Logs**to populate with the **Container****Status**. The population of these Logs is an indication that the application has started.  ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2020-07-24_15h45_47(1).png) 20. Once the Task begins to run, ensure that the **EC2 Instance** is active and that the Container is displayed under**System > Administration > Containers** in the Decisions Studio. 21. Access the Docker Image by inputting the URL at [Internal IP Swagger.](https://documentation.decisions.com/docs/openapi-integration?highlight=swagger)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-324(1).png)