1 of 35

Cloud Usage Guides For ReXgen Air Device

Quick Start Guide For AWS S3- ReXgen Air

AWS Bucket Creation

How to Create an Access key and secret key to access the S3 Bucket?

Deploying Lambda Function To AWS

AWS Bucket Creation

The following document lists the simple steps that allow the user to create an AWS bucket for storage.

Note:

The listed steps are as per the current process in the AWS portal.

What are AWS S3?

Amazon Simple Storage Service (S3) is an object storage built to retrieve data anytime and from anywhere. It lets you store, distribute and manage your data in the Cloud. The need for more and more data storage continues to grow, and building your storage is not an option. AWS S3 lets you securely collect, analyse and store your data at a massive scale. It even enables you to distribute and manage your data by running multiple applications, hosting high-traffic websites, using 3rd party software, and delivering content.

Influx ReXgen Air now lets you store your data to AWS S3. This not only reduces cost but has no upfront investments. One can think of it as a paid taxi service, where you own nothing and pay for the service, allowing users to pay only for the storage and data transfer they use. One of the main benefits of using S3 is storing and accessing data from anywhere with an internet connection.

How does AWS work?

Amazon Simple Storage Services, as the name suggests, provides a web interface for storing files. Each file is stored as an object within the 'bucket', which serves as a container for storing objects that need to be accessed by multiple users or devices, such as documents, images, and videos. S3 also offers a range of features that make it easy to manage and organise data, including creating and managing folders, setting access controls, and tracking users' activity. It is not only low cost as it allows you to pay as you go, but it also has multiple advantages like no investment, scalability, flexibility, global availability, reliability, and security, making AWS S3 stand out. Data stored in S3 buckets is stored across multiple devices in multiple facilities across the specified region, making it highly resistant to data loss. S3 is also designed to scale automatically to meet users' needs, making it easy to store and access large amounts of data without worrying about capacity limits. Overall, AWS S3 is a robust and reliable cloud storage service that offers a range of features and pricing options to meet the needs of different users. Whether you are looking to store large amounts of data or need a place to store and share documents, S3 is an excellent solution.

How to create a bucket?

The first step for creating an AWS S3 bucket is to have an Amazon Web Services (AWS) account. Signing up for AWS automatically signs you up for all services in AWS, including Amazon S3.

How to create an Amazon Web Services (AWS) account?

Open https://portal.aws.amazon.com/billing/signup#/start/email

Sign-Up (new user): fill in the email address and an account name, then click 'verify email address'.

Note:

This sends an auto-generated verification code to your mentioned email ID; follow the instructions given in the email for verification.

A sign-up automatically creates a 'root user' account on AWS. The root user can access all AWS services and resources in the account.

Note:

As a security best practice, assign administrative access to an administrative user and use only the root user to perform tasks requiring access.

How to create a bucket?

Sign in to your Amazon Web Services (AWS) account.
Under Services, choose Storage to open the Amazon S3 console.

Choose Create Bucket.

Specify the bucket name in Bucket Name and your desired region in the AWS Region section, for example, Europe (London) eu-west-2.

Note:

The bucket name must satisfy the rules for bucket naming listed by AWS. Refer to 'See rules for bucket naming'.

Fill in all the other required fields as desired.
Click Create bucket.

Once the bucket is created successfully, it is displayed in the Buckets pane.

How to Create an Access key and secret key to access the S3 Bucket?

Sign in to your Amazon Web Services (AWS) account:
Under Services, choose 'All services' and open the 'IAM' (Identity and Access Management) console.

Under 'Access management', click Users and then 'Create user'.

Specify the IAM user name (read the other instructions properly and grant permissions as desired).
Click 'Next'.

The next step involves granting permissions to the user-specified.
- One can add this new user to the existing groups by selecting 'Add user to group' or to copy the policies from an existing user, select 'Copy permissions' options.

You can create a custom policy with the necessary permissions to restrict access to a single Amazon S3 bucket when creating an IAM policy for an IAM user using JSON. Select 'Attach policies directly' and click 'Create policy'.

Select 'JSON" from the displayed options.

This displays the 'Policy editor window' where you can define the policy.
Below is an example of a JSON policy that allows read access to a single S3 bucket named "my-example-bucket" (you can modify it to fit your specific requirements).

Editable Example

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:*",
                "s3-object-lambda:*"
            ],
            "Resource": [
                "arn:aws:s3:::your-bucket",
				"arn:aws:s3:::your-bucket/*"
            ]
        }
    ]
}

Detailed explanation for the example above:

Below is the detailed explanation for the example JSON policy to access a single S3 bucket named "example-bucket" (you can modify it to fit your specific requirements)

This JSON snippet represents an AWS IAM policy statement that grants permissions related to Amazon S3 (Simple Storage Service) and S3 Object Lambda for a specific bucket (your-bucket.

Version

"Version": "2012-10-17"

The version here specifies the version of the policy language being used. This particular version (2012-10-17) is commonly used in AWS IAM policies.

Statement

"Statement": [
    {
        "Effect": "Allow",
        "Action": [
            "s3:*",
            "s3-object-lambda:*"
        ],
        "Resource": [
            "arn:aws:s3:::your-bucket",
            "arn:aws:s3:::your-bucket/*"
        ]
    }
]

Enclosed is the main body of the policy, where permissions are defined.

Effect: Specifies whether the statement allows (Allow) or denies (Deny) access. In this case, it allows access.

Action: Lists the actions that are allowed.

"s3:*": Allows all actions on S3 buckets and objects within the bucket.
"s3-object-lambda:*": Allows all actions on S3 Object Lambda, a feature that lets you run custom code on S3 GET requests.

Resource: Specifies the AWS resources to which the actions apply.

"arn:aws:s3:::your-bucket": Refers to the bucket itself (your-bucket) and allows actions on the bucket metadata.
"arn:aws:s3:::your-bucket/*": Refers to all objects within the bucket (your-bucket/*) and allows actions on all objects stored within the bucket.

Explanation

Permissions: This policy grants full access (s3:*) to all operations on the bucket (your-bucket) and its objects (your-bucket/*). It also grants full access (s3-object-lambda:*) to S3 Object Lambda operations. Permissions include reading, writing, deleting, and performing any other operations permitted by S3 and S3 Object Lambda.

Scope: The policy applies only to the specific bucket (your-bucket) and its contents. It does not apply to other buckets or resources within AWS.

Considerations

Security: Granting s3:* and s3-object-lambda:* Actions allow extensive control over the specified bucket and its objects. Ensure that such permissions are granted only to trusted entities and that potential security risks are carefully considered.

Best Practices: It is generally recommended that permissions be limited to only those actions and resources necessary for the intended use case, minimising the potential impact of accidental or malicious actions.

This policy would typically be attached to an IAM user, group, or role in AWS Identity and Access Management (IAM) to grant the specified permissions to that entity.

To create and attach this policy to an existing IAM user, follow these steps:

Sign in to the AWS Management Console.
Navigate to the IAM service.
Create or select the IAM user to restrict access to.
In the "Permissions" tab for the user, click "Add permissions."
Choose "Attach existing policies directly."
Click the "JSON" tab and paste the JSON policy into the text box.
Review and click "Next: Review" to proceed.
Review the permissions and the policy you attached to the user.
Click "Add permissions" to attach the policy to the user.

You can modify the JSON policy to include additional actions or restrict access according to your requirements.

Once you have defined the permissions accordingly, click 'Next'.
Review the details specified and click 'Create user'.

Once the user is created successfully, identify and click on the name to proceed.

Click Security credentials, and under Access Keys, click 'Create access key'.

This takes you to a screen which prompts you to consider use cases and alternatives.
Click 'Other' (read the best practices for managing the access key).
Click 'Next'.

Specify the description tag value and click 'Create access key'.

This generates your Access and Secure Access keys.

Once the access key and the secret access keys are generated, copy and paste them to a secure location, as you can view the Secret access key only once.

Click 'Done' to complete the process.

Configuring ReXgen AIR

ReXgen AIR AWS And Mobile Settings lets users view and define the AWS and Mobile settings.

Uploading AWS and Mobile Settings

Mobile Settings

New Mobile

Allows the user to create a new mobile setting.

Edit Mobile

Allows the user to edit the newly created mobile settings.

Delete Mobile

Allows the user to delete the created mobile settings, if not required.

Label: This allows the user to define a name for mobile settings.
User: This allows the user to enter the mobile server user name.
Pass: This allows the user to define a password for the mobile settings.
APN: Enter the APN.
PIN: Enter the pin to the defined APN.
No Communication timeout (min): The user can enter the delay interval for communication time out in minutes.
Get Real-Time From Mobile: Users can enable this to get real-time from the server.

AWS Settings

Steps to add new AWS settings using ReXdesk.

Steps to enable AWS configuration in the ReXgen logger.

Steps to add new AWS settings using ReXdesk

Click the ‘Tools’ tab in the Navigation bar and select ‘Cloud Settings’.

In the Cloud Settings window, select the ‘S3 ‘option and then select the ‘New S3’ option.

In the S3 Settings window, specify the Region from the drop-down menu.

Specify the type of storage services - AWS or Compatible (alternate S3 API-supported storage services).

Specify the S3 Connection type from the drop-down menu. Select Plain for HTTP connection and SSL for HTTPS (Certificate must be added to the XML file).

Specify ‘Port’ details: 80 if the connection type is Plain, 443 if the connection type is SSL.

Specify the bucket name for objects stored in Amazon S3.

Specify the ‘Access Key’ and ‘Secret Key’ for the AWS account

Click ‘OK’.

The new AWS S3 setting details have been defined using ReXdesk.

Click on ’x’ to exit the window.

Steps to enable AWS configuration in the ReXgen logger

Prepare the base configuration for the logger.

In the Device Configuration window, Click on the ‘Upload’ tab.

Enable the ‘checkbox’ for ‘Enable Aws’.

For a single setting, details are auto-filled in the subsequent sections.
Users can select the desired setting from the corresponding drop-down menus for multiple settings.

Click the ‘Run’ tab in the Navigation bar.

Save the project:

a) Save project: allows you to save the project with the user-defined name.

b) Continue as “New Project”: saves the configuration labelled ‘New Project.’

Click ‘OK’ once the configuration is uploaded successfully.

Uploading AWS and Mobile settings

Notes:

Before you begin the steps, ensure your logger is connected to the server with an existing configuration.

Make the new configuration.
Enable AWS from the Device Configuration menu.

Notes:

Set your configuration check time in the given section while enabling AWS.

Save the Project with the name you require for the configuration.
Under the ‘Config’ tab, select Export from the drop-down menu.
Select ‘Export ReXgen Configuration (rxc)’ from the listed options.

Save the file with the desired name.
Click ‘Save’.
Once saved, rename the file as ‘config.rxc.’

Notes:

Ensure that you rename the file as 'config.rxc' only.

Add to your configuration folder in your S3 bucket by adding it to the root folder of the logger.

Notes:

Once the USB is removed, only then the logger will connect to the server and upload files.

Deploying Lambda Function To AWS

Influx provides a free, open-source conversion function to convert the native RXD format to formats that the user uses for their analysis automatically.

Note:

Before proceeding, please ensure that you create the function in the same region where you have the S3 Bucket and the Timestream Database.

When used with AWS, ReXgen will utilize the following Services:

Amazon S3 Bucket - Data is being stored from the device.
Amazon Lambda - Serverless Compute Service Run Code Without Provisioning or Managing Infrastructure.

ReXgen Air – Auto Conversion in Cloud

Supports – BLF, MF4 and CSV formats.

Supports DBC Decoding.
Supports writing data to external Time Series Databases.

For Beginners

Login to your AWS portal and go to Lambda Services.
Click on 'Create Function'.

Once in the 'Create Function' window:
- Select 'Author from scratch.
- In Basic information:
  - Define function name.
  - Select Runtime as '.NET 6 (C#/PowerShell) (from the drop-down options).
  - Select Architecture, x86_64 (from the given options).
- In Permissions, Change the default execution role:
  - If you are uploading for the first time, make sure you have created an IAM role with the following permissions; refer to the
  - If you have already created a role, you can continue by selecting the existing role.
    Select 'Use an existing role'.
    Select the Existing role as 'influx_lambda_role' from the drop-down options.
Select 'Create function'.

Once the function is created, click on 'Upload from'.

Click 'Upload'.

Select the function code's zip file, and click 'Open'.

Once the zip file is uploaded, click 'Save'.

Once on the function window, under the 'Code' tab, locate 'Runtime settings' and click 'Edit' if you wish to edit any credentials.

In Runtime settings:
- Add Runtime as .NET 6 (C#/PowerShell).
- Change handler as AWSLambdaFileConvert::AWSLambdaConvert.Function::ConvertFiles
- Chose Architecture.
- Click 'Save'.

To edit the general configuration, click' Configuration' and select' Edit'.
- As desired, edit details such as memory, ephemeral (temporary) storage, and time out.

Note:

These parameters may change depending on the DBC use, for example, the size of the DBC, etc.

For Advanced Users

Before proceeding, make sure you have Visual Studio 2022 Installed, and the supporting components are installed as per the .vsconfig file in the link below

Clone or download the repository

https://github.com/InfluxTechnology/ReXlibrary/tree/master/Demo/AWS_Lambda

Open \Demo\AWS_Lambda\AWSLambdaFileConvert.csproj
Provide your credentials with permission to S3 and Lambda for your AWS SDK (Refer)
Right-click on the project name and select 'Publish to AWS Lambda…'

Select
- 'AWS Credential'
- Choose 'Region' in which you have the S3 Bucket.
- Enter the 'Description' for the function if required.
- Leave everything else to default.

Choose an IAM role that provides the Lambda functions necessary permission to access all S3 Services and all Lambda services.
- If uploading for the first time, ensure you have created an IAM role with the following permissions; refer to the link.
- If you have already created a role, you can continue by selecting the existing role.

Click 'Upload' to Upload the function to AWS.

Continue to Adding S3 Trigger for Lambda

Adding S3 Trigger for Lambda

Click on 'Add trigger'.

Select the following
- Source as S3.
- Select the Bucket to which the logger uploads data.
- Suffix add (.rxd).
- Acknowledge the warning.

Continue to Configuring conversion settings.

Configuring conversion settings

Upload the FileConvert.json file into the root folder of the Bucket.

Enable the required flags.

Editable example:

{
  "InfluxDB": {
    "enabled": false,
    "url": "",
    "token": "",
    "org": "",
    "bucket": ""
  },
  "CSV": {
    "enabled": true,
    "resampling": {
      "enabled": true,
      "rate": 1000
    }
  },
  "AmazonTimestream": {
    "enabled": false,
    "db_name": "rexcloud",
    "table_name": "rxddata",
    "downsampling": false,
    "downsampling_tolerance": 0.1
  },
  "Snapshot": {
    "enabled": false,
    "db_name": "rexcloud",
    "table_name": "snapshot"
  },
  "MDF": {
    "enabled": true
  },
  "BLF": {
    "enabled": true
  }
}

Continue to Adding the DBC file for conversion.

Adding the DBC file for conversion

Load the DBC into the corresponding folder created by the Data Logger.

The DBC name should be as follows

dbc_can0.dbc For CAN 0 Bus
dbc_can1.dbc For CAN 1 Bus
dbc_can2.dbc For CAN 2 Bus
dbc_can3.dbc For CAN 3 Bus

Running ReXcloud Docker Image on a local PC

Install docker:
Download the ReXcloud docker image:
Load the docker image with the following command in Windows power shell or cmd prompt (from the image folder):

Run the docker image with the following command in Windows power shell or cmd prompt (from the image folder):

Access Fleet management by typing http://localhost:1337/ in the browser.

Note:

Docker image V1.0 contains Node.js, Influx Fleet and Grafana.

MinIO with ReXgen Air

This documentation details the steps to use ReXgen Air for the alternate S3 API-supported storage service MinIO in Windows.

Step 1 - Allow traffic on port 9000

Step 2 - Access MinIO console

Step 3 - Create Bucket

Step 4 - Create Access and Security Key

Step 5 - Adding S3 Settings

Step 6 - Load Configuration

Step 1 - Allow traffic on port 9000

Open the 'Windows Security' menu, and click 'Advanced settings'.

Click on 'Inbound Rules' and then click the 'New Rule' option. This opens the 'New Inbound Rule Wizard', where the user needs to define the new rule's properties.

For 'Rule Type', enable 'Port' and click 'Next'.

For 'Protocol and Ports', specify the port details for 'Specific local ports', i.e. 9000 for MinIO.

Leave the following steps as they are and click 'Next' for both 'Action' and 'Profile'.

For 'Name', specify a desired name and click Finish.

Step 2 - Access MinIO console

To begin - access MinIO's website and click Download.

Open the command prompt in the folder (where minio.exe is stored.

Paste the following in the command prompt and press 'Enter'.

SET MINIO_ROOT_USER=username 
SET MINIO_ROOT_PASSWORD=password 
minio.exe server C:\DATA --console-address ":9001"

(Username - type your user's name for logging in to the minIO Console)

(Password- type your password for logging in to the minIO Console)

Open the 'MinIO Console' by typing 'localhost:9001' into your browser.

Once you have access to the login window, enter the username and password you used in the command prompt. And click 'Login'.

Step 3 - Create Bucket

Click the 'Buckets' option and then the 'Create a Bucket' tab.

Specify the Bucket details.

Bucket Name: Name the bucket (as desired) after reading the bucket naming rules.
Versioning: allows multiple versions of the same object to be kept under the same key.

Object Locking: prevents objects from being deleted. Required to support retention and legal hold. It can only be enabled at bucket creation.
Quota: limits the amount of data in the bucket.

Retention imposes rules to temporarily prevent object deletion. Versioning must be enabled to set bucket retention policies.

After entering all the details, click 'Create Bucket'.

Once the bucket is created, its properties can be accessed by simply clicking on its name.

Click on the bucket name to add/upload a file to the bucket.

Click the 'Upload' tab to upload any file/folder to the bucket.

Step 4 - Create Access and Security Key

In the User Object store, click 'Access Keys'.

Once the access keys window opens, click 'Create access key'.

This opens a window with your access and a secret key. If necessary, enter other details such as expiry/name/description/comments and click 'Create'.

Copy and save the access and secret key details before proceeding. Additionally, after clicking 'Create,' min-Io prompts you to download and save the access key and security key details. This can be done by clicking the 'Download for import' tab.

The access key is successfully created.

Step 5 - Adding S3 Settings

Click the 'Tools' tab in the Navigation bar and select 'Cloud Settings'.

In the Cloud Settings window, select the 'S3 'option and then select the 'New S3' option.

Region: updates accordingly once the S3 type is entered.
S3 Type: This allows users to select between AWS and compatible storage services (alternate S3 API-supported storage services).

Endpoint: This allows the user to preview the END point.
S3 Connection Type: Select Plain for HTTP connection and SSL for HTTPS.

Port: 9000 in case of min-Io.
Bucket: Specify the bucket name from Mini-Io.
Access Key: paste the access key for the min-Io account.
Secret Key: paste the secret key for the min-Io account.

*Always format the logger's internal storage after sending a configuration with AWS enabled.

Note:

Before continuing, ensure your logger is connected to the server with an existing configuration.

Make the new configuration.

Connect the logger to the PC via USB. Status Bar will display the logger status and time information.

Step 6 - Load Configuration

Click "Run Configuration," save the project, and provide a name for it. The logger will create files with the project name.

The configuration will be loaded in the data logger, and logging will start immediately.

Setting Grafana Dashboard with Parquet

Before proceeding, please create the function in the region where you have the S3 Bucket.

Click on 'Create Function'.

Once in the 'Create Function' window:

Select 'Author from scratch.
In Basic information:
- Define function name.
- Select Runtime as '.NET 6 (C#/PowerShell) (from the drop-down options).
- Select Architecture, x86_64 (from the given options).
In Permissions, set the default execution role for Lambda functions:
- If you are uploading for the first time, make sure you have created an IAM role with the following permissions; refer to the link
- If you have already created a role, you can continue by selecting the existing role.
  - Select 'Use an existing role'.
  -  Select the Existing role as 'influx_lambda_role' from the drop-down options.

Select 'Create function'.

Once the function is created, click on 'Upload from'.

Click 'Upload'.

Select the function code's zip file, and click 'Open'.

Once the zip file is uploaded, click 'Save'.

Once on the function window, under the 'Code' tab, locate 'Runtime settings' and click 'Edit' if you wish to edit any credentials.

In Runtime settings:

Add Runtime as .NET 6 (C#/PowerShell).
Change handler as AWSLambdaFileConvert::AWSLambdaConvert.Function::ConvertFiles
Chose Architecture.
Click 'Save'.

To edit the general configuration, click' Configuration' and select' Edit'.

Edit details such as memory, ephemeral (temporary) storage, and time out.

Click 'Save'.

Adding S3 Trigger for Lambda

Configuring conversion settings

Configuring AWS Glue settings

Setting a Grafana Dashboard using the Athena plugin

Adding S3 Trigger for Lambda

Click on 'Add trigger'

Note:

These parameters may change depending on the DBC use, such as the size of the DBC.

Select the following

Source as S3.
Select the Bucket to which the logger uploads data.
Suffix add (.rxd).
Acknowledge the warning.

The trigger is successfully added.

Configuring conversion settings

Upload the FileConvert.json file into the root folder of the Bucket.

Enable the required flags.

Editable example:

Configuring AWS Glue settings

Open AWS Glue services.

Create a database.

Name the database and click 'Create database'.

A database with the desired name is created.

Open IAM services and select 'Role'.

Select the desired roles.

Select the trusted entity, choose the use case as 'glue', and select 'Next'.

In Permissions, set the default execution role for the Glue function, and click 'Next'.

Name, review and create:

Name the role.
Add description (if needed/as required).
Click 'Create role'.

Click 'ETL jobs'.

Create a script by clicking the 'Script editor' tab.

Select 'Spark' from the options under Engine (from the drop-down).

Enable 'Upload script' and click 'Choose file'.

Locate the script file on your device, select and open.

View or edit your script code (if required)

Add the basic properties under the 'Job details' tab.

Once the properties are added, click 'Create schedule'.

Add Schedule properties and click 'Create schedule.'

Click on the 'CRON expressions' link to learn more about CRON syntax for assigning a required schedule.

Click the 'Run' tab and then click 'Run job' to manually run the job; the database will be populated if the parquet files are already available in S3.

Note:

The database will be populated only if the parquet files are already available in S3; otherwise, there is no need to run the job manually.

The run screen then displays the active status of the job.

The job is successfully scheduled.

The database details, along with the logger number, are displayed.

Note:

Happens only when the job is run manually after creation it will have to wait until the first run.

Click on the logger serial number to get a detailed report.

Setting a Grafana Dashboard using the Athena plugin

Setting a Grafana Dashboard using the Athena plugin

Visit Grafana.com, click 'data sources' and then click 'Add new data source'.

Get plugin >> Amazon Athena >> Install Plugin

'Amazon Athena' plugin is added,

Return to AWS IAM settings, select the 'Users tab', and click 'Create User. '

Specify the user details and click 'Next'.

To set permissions, select 'Attach policies directly'.

Select from the existing policies.

Click 'Create user'

Create the Access Key.

Select 'Others' and click 'Next.'

Set Description tags if required, and click 'Create access key'.

Once the Access key is created, copy and save both the access and the secret access key, or download them as a .csv file and click 'Done'.

Now go back to Grafana to specify the Athena dashboard's settings and click 'Save and test.' Ensure that the output location is a folder in the S3 bucket.

Once the data source is tested, this message is displayed.

Click 'Dashboards', click 'New' and then click 'New dashboard'.

Click 'Add visualization'.

Select the data source.

This opens the basic dashboard screen.

Add your query and then click 'Run query'.

For example

Editable Format

SELECT
    $__timeGroup(time, $__interval) as Time,
    AVG("$__column") as Alt
FROM
    "$__table"
WHERE
    $__timeFilter(time)
GROUP BY
    $__timeGroup(time, $__interval)
ORDER BY
    Time ASC

The Dashboard is created.

Setting up FileZilla FTPS

Download FileZilla

Complete the installation with default settings.

Click on the server settings icon.

Click on general settings and configure the default port. It is advised to use ports other than 21. Example:54345

Configure the welcome message, optional.

Configure the port range (Starting from the port configured in step 3) and the external IP address to be used for FTP passive mode configuration. Example: 54345 - 54350

If the server is being set up on Azure Virtual Machine or an Amazon EC2 instance, use the static IP address of the Virtual Machine or EC2 instance.
If it is a local server with a static IP address, use that static IP Address.

Ensure the ports are open in the Windows firewall and the Firewall settings in the Azure or AWS portal.

Go to FTP over TLS Settings
Enable the FTPS option
Disallow plain FTP
Generate new certificate
Leave other settings as shown in the image below.

*PROT P is not supported

Click Ok

Adding users and selecting the directory for saving the file.

Click on the user management icon.

Click on Add and create a new user.

Enable the password option and enter a password.

Select the user and click the add folder icon.

Select the folder that you wish to use.

Enable all the permissions.

The server is ready for use.

Configuring ReXgen AIR

ReXgen AIR FTP And Mobile Settings: This lets users view and define the and settings.

Mobile Settings

New Mobile

Allows the user to create a new mobile setting.

Edit Mobile

Allows the user to edit the newly created mobile settings.

Delete Mobile

Allows the user to delete the created mobile settings, if not required.

Label: This allows the user to define a name for mobile settings.
User: This allows the user to enter the mobile server user name.
Pass: This allows the user to define a password for the mobile settings.
APN: Enter the APN.
PIN: Enter the pin to the defined APN.
No Communication timeout (min): The user can enter the delay interval for communication time out in minutes.
Get Real-Time From Mobile: Users can enable this to get real-time from the server.

FTP Settings

Use Server Name: This allows the user to use the server name to execute the FTP process.
Use IP Address: This allows the user to use the IP Address to execute the FTP process.
Protocol: This allows users to select the protocol type between FTP and FTPs.

Mode: This allows users to select the mode type between Active and Passive(recommended).

User: This allows the user to specify himself.
Pass: Allows the user to define a password for the FTP settings.

Uploading FTP and Mobile settings

From Tools, select Encryption Manager

Click Mobile and add SIM settings

Click the FTP Setting tab to add FTP server details.

Click upload in “Device Configuration.”

Select the added Mobile settings and FTP settings.

Store data to FTP using mobile internet: Enable storing the data to FTP using mobile internet.
Mobile: Enter the name defined in the SIM settings.
FTP: Enter the name defined in the server settings.
Check Config Time (min): Checks for new config on the server (at a given delay).
Send status Time (min): Updated the status in the given time (at a given delay).
Check Firmware Update: Checks for new firmware on the server (at a given delay).*
Automatic Firmware Update: Enable updating the firmware automatically.*

*will be enabled with the upcoming versions.

Note:

Once the USB is removed, only then the logger will connect to the server and upload files.

How to Create an Access key and secret key to access the S3 Bucket?

Sign in to your Amazon Web Services (AWS) account:
Under Services, choose 'All services' and open the 'IAM' (Identity and Access Management) console.

Under 'Access management', click Users and then 'Create user'.

Specify the IAM user name (read the other instructions properly and grant permissions as desired).
Click 'Next'.

The next step involves granting permissions to the user-specified.
- One can add this new user to the existing groups by selecting 'Add user to group' or to copy the policies from an existing user, select 'Copy permissions' options.

You can create a custom policy with the necessary permissions to restrict access to a single Amazon S3 bucket when creating an IAM policy for an IAM user using JSON. Select 'Attach policies directly' and click 'Create policy'.

Select 'JSON" from the displayed options.

This displays the 'Policy editor window' where you can define the policy.
Below is an example of a JSON policy that allows read access to a single S3 bucket named "my-example-bucket" (you can modify it to fit your specific requirements).

Editable Example

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:*",
                "s3-object-lambda:*"
            ],
            "Resource": [
                "arn:aws:s3:::your-bucket",
				"arn:aws:s3:::your-bucket/*"
            ]
        }
    ]
}

Detailed explanation for the example above:

Below is the detailed explanation for the example JSON policy to access a single S3 bucket named "example-bucket" (you can modify it to fit your specific requirements)

This JSON snippet represents an AWS IAM policy statement that grants permissions related to Amazon S3 (Simple Storage Service) and S3 Object Lambda for a specific bucket (your-bucket.

Version

"Version": "2012-10-17"

The version here specifies the version of the policy language being used. This particular version (2012-10-17) is commonly used in AWS IAM policies.

Statement

"Statement": [
    {
        "Effect": "Allow",
        "Action": [
            "s3:*",
            "s3-object-lambda:*"
        ],
        "Resource": [
            "arn:aws:s3:::your-bucket",
            "arn:aws:s3:::your-bucket/*"
        ]
    }
]

Enclosed is the main body of the policy, where permissions are defined.

Effect: Specifies whether the statement allows (Allow) or denies (Deny) access. In this case, it allows access.

Action: Lists the actions that are allowed.

"s3:*": Allows all actions on S3 buckets and objects within the bucket.
"s3-object-lambda:*": Allows all actions on S3 Object Lambda, a feature that lets you run custom code on S3 GET requests.

Resource: Specifies the AWS resources to which the actions apply.

"arn:aws:s3:::your-bucket": Refers to the bucket itself (your-bucket) and allows actions on the bucket metadata.
"arn:aws:s3:::your-bucket/*": Refers to all objects within the bucket (your-bucket/*) and allows actions on all objects stored within the bucket.

Explanation

Scope: The policy applies only to the specific bucket (your-bucket) and its contents. It does not apply to other buckets or resources within AWS.

Considerations

This policy would typically be attached to an IAM user, group, or role in AWS Identity and Access Management (IAM) to grant the specified permissions to that entity.

To create and attach this policy to an existing IAM user, follow these steps:

Sign in to the AWS Management Console.
Navigate to the IAM service.
Create or select the IAM user to restrict access to.
In the "Permissions" tab for the user, click "Add permissions."
Choose "Attach existing policies directly."
Click the "JSON" tab and paste the JSON policy into the text box.
Review and click "Next: Review" to proceed.
Review the permissions and the policy you attached to the user.
Click "Add permissions" to attach the policy to the user.

You can modify the JSON policy to include additional actions or restrict access according to your requirements.

Once you have defined the permissions accordingly, click 'Next'.
Review the details specified and click 'Create user'.

Once the user is created successfully, identify and click on the name to proceed.

Click Security credentials, and under Access Keys, click 'Create access key'.

This takes you to a screen which prompts you to consider use cases and alternatives.
Click 'Other' (read the best practices for managing the access key).
Click 'Next'.

Specify the description tag value and click 'Create access key'.

This generates your Access and Secure Access keys.

Once the access key and the secret access keys are generated, copy and paste them to a secure location, as you can view the Secret access key only once.