Documentation Index

Fetch the complete documentation index at: https://docs.lobstersoftware.com/llms.txt

Use this file to discover all available pages before exploring further.

Validation report: AWS European Sovereign Cloud

Prev Next

This report records a one-time validation. Lobster installed and tested the Lobster Data Platform (LDP) on the AWS European Sovereign Cloud (AWS ESC). AWS ESC is a dedicated AWS cloud built for European data sovereignty and compliance.

Validation result: Passed

This report covers Lobster Data Platform 26.2.3 on the AWS European Sovereign Cloud, region eusc-de-east-1.

Executive summary

Lobster validated AWS ESC as a deployment target for the LDP. The validation used the eusc-de-east-1 region. It passed with no blocking issues.

Implementation required several adjustments:

  • Upgrade of the AWS provider and Terraform modules.

  • Updated AMI (Amazon Machine Image) owner and filter values for the sovereign environment.

  • Adapted ARN (Amazon Resource Name) formats and IAM (Identity and Access Management) policies for the sovereign partition.

Operators should note one key point. AWS ESC runs in a separate AWS partition. A partition is an isolated grouping of AWS regions. This partition uses different ARN prefixes and IAM policy ARNs. Any future reference to AWS-managed policies or service endpoints must be adjusted accordingly. The overall architecture is identical to that of any other region.

Scope and objectives

Purpose

This validation confirms that the LDP installs and runs on AWS ESC infrastructure. It covers a single-node installation. It checks basic installability and core feature functionality.

This report is not a performance benchmark. It is not a security audit. It is not a production readiness assessment.

What was validated

  • Installation of the LDP on a Linux VM running Amazon Linux 2023.

  • Connectivity between the application and a PostgreSQL database instance.

  • The execution of a sample end-to-end integration pipeline.

  • Basic platform stability, including service restart behavior.

What was not validated

  • High availability (HA) or multi-node deployments.

  • Performance under load.

  • Disaster recovery or backup behavior.

  • Long-term operational stability.

  • Provider-managed security controls or compliance posture.

Environment details

Provider information

Field

Value

Provider name

AWS European Sovereign Cloud

Region / data center

eusc-de-east-1

Account type

Not specified

Validation period

May 2026

Infrastructure topology

The Validated Deployment Targets program generally uses a RHEL-family Linux distribution (RHEL = Red Hat Enterprise Linux). Options include RHEL, Fedora, CentOS, or AlmaLinux. The database is PostgreSQL.

This validation used only Amazon Linux 2023. See the software version table below.

This validation used the standard Lobster price list sizing. No changes were needed.

Software version

Component

Version

Lobster Data Platform

26.2.3

Java runtime

21

PostgreSQL

16.8

OS distribution and version

Amazon Linux 2023 with Lobster AMI flavor

Installation summary

The Lobster team added eusc-de-east-1 as a new region. The approach mirrored the existing eu-central-1 and eu-central-2 regions. The following Terraform configuration defines the instance sizes used for the test cases:

eusc-de-east-1 = {
  "S"    = { instance_type = "r6g.medium",  disk_size = 200, rds_instance_type = "db.t3.medium",  rds_disk_size = 100 }
  "M"    = { instance_type = "t4g.xlarge",  disk_size = 300, rds_instance_type = "db.t3.xlarge",  rds_disk_size = 250 }
  "L"    = { instance_type = "t4g.2xlarge", disk_size = 400, rds_instance_type = "db.t3.2xlarge", rds_disk_size = 250 }
  "demo" = { instance_type = "r6g.medium",  disk_size = 50,  rds_instance_type = "db.t4g.small",  rds_disk_size = 20 }
  "dev"  = { instance_type = "t4g.small",   disk_size = 20,  rds_instance_type = "db.t3.medium",  rds_disk_size = 50 }
}

Test results

Test execution summary

The installation process did not generate any errors in the log.

#

Test

Result

T1

Platform components are all running and healthy

Pass

T2

LDP UI is reachable, and login is successful

Pass

T3

A sample integration pipeline is executed end-to-end

Pass

T4

Data written to and read from PostgreSQL successfully

Pass

T5

No blocker-level errors in logs after pipeline execution

Pass

T6

Platform restarted cleanly after simulated reboot

Pass

Issues identified

These non-blocking issues apply to customers with existing AWS accounts outside AWS ESC.

#

Severity

Description

Impact

Workaround / resolution

Status

1

Non-blocking

IAM ARN changed due to the new partition

Low

Change ARNs to arn:aws-eusc

Resolved

2

Non-blocking

S3 buckets cannot be shared across AWS partitions

Low

Create a new bucket for the ESC partition

Resolved

3

Non-blocking

AMIs cannot be shared across AWS partitions

Low

Create a new AMI and CI build for the Lobster Linux AMI in the ESC partition

Partially

Known limitations

Customers relying on this report should review this section.

#

Area

Limitation

Impact

Recommended action

1

Customer

Currently only two availability zones (AZ) are available

Medium

HA (High availability) setups are limited. The standard setup is not affected.

Customer relevance

The AWS European Sovereign Cloud is a dedicated AWS environment. It targets customers with the highest requirements for data sovereignty and compliance. Data is stored and processed exclusively in Europe. It remains under European law, with no access from outside the EU.

The Lobster Data Platform is validated for this environment. Customers can use AWS ESC infrastructure to install and run the platform. This works like any standard cloud environment.

AWS ESC is especially relevant for:

  • Companies in regulated industries, such as finance, healthcare, and the public sector.

  • Customers with legal obligations to store data within the EU.

  • Organizations committed to a fully European sovereign cloud strategy.

Revalidation

Lobster recommends revalidation under any of these conditions:

  • A major Lobster Data Platform release with infrastructure-relevant changes is published.

  • AWS ESC changes a core service relevant to this installation, such as network, compute, or database.

  • 12 to 18 months pass from the date of this report, whichever comes first.

References

Disclaimer

Lobster performed a one-time manual installation and functional verification on third-party infrastructure. This validation confirms basic installability and core feature functionality. Lobster does not operate customer infrastructure on these providers. Lobster does not provide infrastructure-level support. Customers are responsible for provisioning, operating, and maintaining their own infrastructure.