--- title: "Platform | Installation and Upgrade AWS | N3uron KB V1.22" slug: "platform-installation-and-upgrade-aws" description: "N3uron is an Industrial Edge Platform for IIoT and DataOps that enables seamless integration between the industrial plant floor and business applications," updated: 2026-05-14T12:36:22Z published: 2026-05-14T12:36:22Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.n3uron.com/llms.txt > Use this file to discover all available pages before exploring further. # AWS Cloud The**N3uron IIoT & DataOps Platform** is available at the [AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-ts5qknzpiy2nw) as an Amazon Machine Image (AMI), offering a simple, fast, and secure way to deploy N3uron in the AWS Cloud. The **N3uron**AMI is built on Ubuntu 24.04 LTS and uses the ARM64 architecture, suitable for EC2 instances powered by [AWS Graviton](https://aws.amazon.com/ec2/graviton/) processors. > [!NOTE] > Note: > > N3uron on AWS uses the same licensing model as the on-premise version of N3uron. For more details, see [Licensing](/v122/docs/platform-licensing). ## Launch an EC2 instance from the Marketplace #### Configure and launch **Step 1:** Go to the [AWS Marketplace](https://aws.amazon.com/marketplace) website and search for the **N3uron IIoT & DataOps Platform** product or access it directly through this [link](https://aws.amazon.com/marketplace/pp/prodview-ts5qknzpiy2nw). **Step 2:** Click on **View purchase options**. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(50).png) **Step 3:** Review and accept the End User License Agreement (EULA) of N3uron. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(23).png) **Step 4:**Wait for AWS to process your request and click on **Continue to Configuration.** ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(24).png) **Step 5:**Select the desired N3uron version and AWS Region to deploy this solution, then click on **Continue to Launch.** ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(25).png) **Step 6:**You can choose to continue configuring the instance from the Marketplace website or go to EC2. In this case, we select **Launch through EC2** and click on **Launch.** ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(26).png) **Step 7:**In the EC2 console, proceed to configure a name for the instance, a security group to allow **SSH access** and inbound **HTTP to port 8003** (N3uron WebUI). ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(27).png) ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(28).png) Configure the storage capacity and click on **Launch instance.** ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(29).png) #### Access the N3uron WebUI **Step 1:**Once the instance is launched, click on its ID to view the instance details in the EC2 console. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(32).png) **Step 2:**Access the N3uron WebUI using the **public IPv4 address** or **public DNS name** at port 8003. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(33).png) **Step 3:** Login to the N3uron WebUI using the default **admin**username and the **EC2 instance ID** (see the previous screenshot) **as password**. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/firefox_7cdRyBB3Oc.png) You can now access the [N3uron IIoT & DataOps Platform](https://n3uron.com/) running in AWS Cloud. Take a look at our [modules](https://docs.n3uron.com/v122/docs/platform-introduction#n3u). ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/firefox_nhrx7vYRwL.png) #### Access the instance using SSH The N3uron AMI supports [EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-linux-inst-eic.html) to securely access the instance through SSH using the user **ubuntu.**See the [AWS documentation to use Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-methods.html). ## Deploy with Terraform Deploy N3uron on AWS in minutes using [Terraform](https://www.hashicorp.com/en/products/terraform)with our ready-to-use templates. The repository includes six templates for standalone and high-availability deployments, with optional managed database integration for Historian using [MongoDB Atlas](https://www.mongodb.com/products/platform/atlas-database) or [Tiger Data](https://www.tigerdata.com/cloud). Visit our [GitHub repository](https://github.com/n3uron/terraform-templates) to access the templates and usage documentation. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/terraform-deploy-n3uron.gif) ## Deploy with CloudFormation Our [AWS Marketplace solution](https://aws.amazon.com/marketplace/pp/prodview-ts5qknzpiy2nw) provides two [CloudFormation](https://aws.amazon.com/cloudformation/)templates to deploy either a standalone or redundant N3uron setup with a [MongoDB Atlas](https://www.mongodb.com/products/platform/atlas-database) cluster as the [data historian](https://n3uron.com/iiot-platform-modules/historian/) database. ### **Getting Started** Before deploying the architectures outlined below, you need to configure the API keys in [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) to access MongoDB Atlas and enable the MongoDB Atlas resources in [CloudFormation](https://aws.amazon.com/cloudformation/). #### Configure your MongoDB Atlas API Keys **Step 1:**Generate an API key pair (public and private keys) for your Atlas organization and configure them to grant CloudFormation access to your Atlas project. Refer to the [Atlas documentation](https://www.mongodb.com/docs/atlas/configure-api-access/#manage-programmatic-access-to-an-organization) for detailed instructions. **Step 2:** Create a new secret in AWS Secrets Manager (in the same region you want to deploy the solution) to store the Atlas “profile”. The secret should follow this format: ```plaintext SecretName: cfn/atlas/profile/{ProfileName} SecretValue: {"PublicKey": "YourPublicKey", "PrivateKey": "YourPrivateKey"} ``` Example: ```plaintext  ProfileName: default  SecretName: cfn/atlas/profile/default  SecretValue = {"PublicKey": "YourPublicKey", "PrivateKey": "YourPrivateKey"} ``` Alternatively, you can use this simple CloudFormation [template](https://github.com/mongodb/mongodbatlas-cloudformation-resources/blob/master/examples/profile-secret.yaml) to create a “default” profile. #### Create an IAM execution role for Atlas To activate and use the MongoDB Cloudformation resources, you need to [create and configure an IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create.html) in the target region with the following permissions: ```json {    "Version": "2012-10-17",    "Statement": [        {            "Action": [                "secretsmanager:CreateSecret",                "secretsmanager:CreateSecretInput",                "secretsmanager:DescribeSecret",                "secretsmanager:GetSecretValue",                "secretsmanager:PutSecretValue",                "secretsmanager:UpdateSecretVersionStage",                "ec2:CreateVpcEndpoint",                "ec2:DeleteVpcEndpoints",                "cloudformation:CreateResource",                "cloudformation:DeleteResource",                "cloudformation:GetResource",                "cloudformation:GetResourceRequestStatus",                "cloudformation:ListResources",                "cloudformation:UpdateResource",                "iam:AttachRolePolicy",                "iam:CreateRole",                "iam:DeleteRole",                "iam:GetRole",                "iam:GetRolePolicy",                "iam:ListAttachedRolePolicies",                "iam:ListRolePolicies",                "iam:PutRolePolicy"            ],            "Resource": "*",            "Effect": "Allow"        }    ] } ``` And the following trust policy: ```json {    "Version": "2012-10-17",    "Statement": [        {            "Effect": "Allow",            "Principal": {                "Service": [                    "lambda.amazonaws.com",                    "cloudformation.amazonaws.com",                    "resources.cloudformation.amazonaws.com"                ]            },            "Action": "sts:AssumeRole"        }    ] } ``` **Recommendation:**You can use this [Cloudformation template](https://github.com/mongodb/mongodbatlas-cloudformation-resources/blob/master/examples/execution-role.yaml) to automatically create the IAM role in the desired region. #### Activate the MongoDB Atlas resources in CloudFormation To use the deployment templates provided in this solution, you need to enable the following resources in the target region: - MongoDB::Atlas::Project - MongoDB::Atlas::Cluster - MongoDB::Atlas::DatabaseUser - MongoDB::Atlas::PrivateEndpointService - MongoDB::Atlas::PrivateEndpointAWS **Step 1:** In the AWS CloudFormation console of the target region, go to **Registry**and select **Third party.** ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(42).png) **Step 2:** Search for the specific resource by name. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(44).png) **Step 3:**Click on **Activate,**set the ARN identifier of the IAM role created in the previous section and click on **Activate extension**. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(45).png) ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(46).png) Repeat the steps 2-3 to enable all the required resources. ### **Architectures** #### Standalone This template deploys a **standalone N3uron node** and a **MongoDB Atlas cluster** securely connected using an [AWS PrivateLink](https://aws.amazon.com/privatelink/) endpoint. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(40).png) We provide two deployment options: - **Deploy N3uron into a new VPC**: This template creates a new VPC with the subnets, security groups, private endpoints, etc., and deploys N3uron in an EC2 instance. - **Deploy N3uron into an existing VPC**: This template deploys the solution into an existing VPC in your infrastructure. #### Redundant This option template deploys a **redundant pair of N3uron nodes**, each in a different availability zone and a **highly-available MongoDB Atlas cluster** securely connected using an [AWS PrivateLink](https://aws.amazon.com/privatelink/) endpoint. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/image(41).png) We provide two deployment options: - **Deploy N3uron into a new VPC**: This template creates a new VPC with the subnets, security groups, private endpoints, etc., and deploys each N3uron in an EC2 instance in different availability zones. - **Deploy N3uron into an existing VPC**: This template deploys the solution into an existing VPC in your infrastructure.