--- title: "Lucanet SEA: System Requirements and Network Configuration" source_url: https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea/sea-system-requirements language: en last_updated: 2026-06-15 --- # Lucanet SEA: System Requirements and Network Configuration ## Overview **Lucanet.Script Execution Application** (**SEA** for short) is a Lucanet application that you need if you operate ERP/financial source systems on-premises and want to import data from these systems into the Lucanet CFO Solution Platform using an ETL script. This page provides the technical information that your IT department needs to prepare a SEA installation: the system architecture (topology), the system requirements, and the network and firewall configuration (ports and endpoints to allow). {% info-box %} For the step-by-step installation instruction, see [Installing and Updating Lucanet.Script Execution Application](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md). To generate the required certificates, see [Generating and Downloading SEA Certificates](https://support.lucanet.cloud/en/documentation/administration/platform-management/certificates.md). {% /info-box %} ## System Architecture SEA runs as a system service inside your local network, in the same environment as your source system. It executes ETL scripts locally to extract, transform, and load data from your on-premises ERP/financial systems, and then transfers the results securely to **Lucanet.Financial OLAP Server** or **Lucanet.Financial Warehouse** in Lucanet.Cloud (AWS). Because Lucanet.Cloud cannot initiate connections into your network, SEA establishes all connections **outbound**: it connects to **AWS IoT Core** to receive its tasks and to **Lucanet.Financial OLAP Server** to exchange data. SEA is in turn the only component that accesses your ERP/source system inside your network. Depending on whether your source system offers an interface or only export files, one of the following topologies applies. ### Data Access via Interface If your source system has an interface that allows access to its database or application server, SEA accesses the source system directly, reads the data via an ETL script, and transfers it to **Lucanet.Financial Warehouse**. While doing so, SEA must be connected to **Lucanet.Financial OLAP Server** in **Lucanet.Cloud** via HTTPS (SSL/TLS). Lucanet SEA — data access via interface ### Using Export Files If your source system does not offer such an interface, the data must be extracted from the source system using export files. Because export files cannot be stored in **Lucanet.Cloud**, they must be stored locally in your environment. During the ETL process, SEA must be able to access the export files and be connected to **Lucanet.Financial OLAP Server** in **Lucanet.Cloud** via HTTPS (SSL/TLS). Lucanet SEA — using export files {% info-box %} In both topologies, the connection between SEA and Lucanet.Financial OLAP Server is encrypted with SSL/TLS (1.2 or higher), marked with an asterisk (*) in the diagrams. In addition, SEA connects to AWS IoT Core over **port 8883** (or **port 443** over WebSockets); see the [Network and Firewall Configuration](#network-and-firewall-configuration) section below. {% /info-box %} ## System Requirements ### Prerequisites Before you can install SEA, the following prerequisites must be met: - **Lucanet.Software Manager 11 (2503+4) or higher** must be installed. - A valid certificate must be generated and downloaded from the Lucanet CFO Solution Platform (see [Generating and Downloading SEA Certificates](https://support.lucanet.cloud/en/documentation/administration/platform-management/certificates.md)). ### Hardware Requirements The minimum hardware requirements for each computer running SEA are: | Component | Minimum requirement | |---|---| | CPU | At least 2 CPU cores (4 CPU cores recommended) | | RAM | At least 8 GB | | Internal network connection | At least a 1 Gbit connection (10 Gbit recommended) | | Internet connection | At least a 16 Mbit connection | | Storage/hard drive | 500 MB or more | ### Operating System SEA runs on the following operating systems: - **Microsoft Windows**: all currently supported operating system versions - **Unix/Linux**: all common maintained distributions, especially CentOS, Debian (version 7 and later), and SUSE ## Network and Firewall Configuration SEA and Lucanet.Software Manager (which is used to install and update SEA) only establish **outbound** connections. To install and operate SEA, your IT department must allow the following connections through the firewall and through any proxy or endpoint-security software. ### Connections, Ports, and Endpoints | Connection (outbound) | Target address | Port | Notes | |---|---|---|---| | AWS IoT Core (task queue) | Region-specific AWS IoT Core endpoint on amazonaws.com (see note below) | 8883 (or 443) | MQTT over TLS (port 8883), or MQTT over WebSockets with TLS (port 443). Required: SEA registers with AWS IoT Core over port 8883. | | Lucanet.Financial OLAP Server | platform.lucanet.cloud, lucanet.cloud | 443 | HTTPS (TLS 1.2 or higher). Used during script execution. | | ERP/source system | Customer-internal address (varies) | Depends on source system | SEA connects directly within your network. | | Lucanet.Financial Warehouse | Tunneled through Lucanet.Financial OLAP Server | — | Normally no separate firewall rule required. | | Installation and updates (Lucanet.Software Manager) | youniverse.lucanet.com, cdn.lucanet.com (cdn.lucanet.cn) | 443 | HTTPS (TLS). Used by Lucanet.Software Manager to download and update the SEA program components. Required for installation and updates, not at runtime. | {% warning-box %} The AWS IoT Core endpoint is **not the same for every installation**. It follows this pattern, where `` and `` are placeholders: `-ats.iot..amazonaws.com` - `` is unique per AWS account, for example `a1b2c3d4e5f6g7`. - `` is the AWS region where your environment is hosted, for example `eu-central-1` for Frankfurt. For an environment hosted in Frankfurt, the full endpoint is therefore, for example, `a1b2c3d4e5f6g7-ats.iot.eu-central-1.amazonaws.com`. The prefix and region are specific to your installation. If your firewall cannot allow individual, dynamically generated endpoints, allow the pattern `*-ats.iot..amazonaws.com` instead. {% /warning-box %} Proxy and PAC (auto-configuration) scripts must not block or rewrite the connections listed above. ### Antivirus and Endpoint-Security Exclusions To prevent antivirus or endpoint-security software from interfering with SEA, exclude the following directories: ```text C:\ProgramData\LucaNet C:\Program Files\LucaNet ``` These are the default Lucanet installation directories. ## Security - SEA only executes specific, approved tasks. - A one-time code/session token is used for each ETL script execution. - All communication is encrypted (to AWS IoT Core and to Lucanet.Financial OLAP Server in the cloud). - Data processing takes place entirely within your network. Only the aggregated result data is transferred to Lucanet.Financial OLAP Server.