This section provides you with a detailed overview of the Lobster Cloud hosting architecture. Every Lobster Cloud system runs on Amazon Web Services (AWS) in a dedicated, isolated environment that is provisioned exclusively for your organization.
The architecture follows a standardized design that cannot be modified on a per-customer basis. This ensures consistent security, reliability, and operational quality across all customer environments. Depending on your edition and selected options, your system may include a DMZ layer, a development environment, or a full High Availability setup with redundant components.
All systems are deployed within a dedicated AWS Virtual Private Cloud (VPC) with private network isolation. The database runs in a protected private subnet with no external access. Only the corresponding Lobster web server can communicate with the database. Outgoing connections from your system to external endpoints are open by default, while incoming connections are controlled via AWS Security Groups (firewall rules) and must be requested via support ticket.
The following pages describe each architecture variant in detail:
Page | Description |
|---|---|
The base architecture for ENTER, SCALE and ACCELERATE editions, including single-server and DMZ configurations. | |
Detailed description of the DMZ server and its role as a security and reverse proxy layer between the internet and your internal Lobster system. | |
The multi-node architecture is included as standard with TRANSFORM and optionally available for SCALE and ACCELERATE. Covers failover, load balancing, database replication, and shared file systems. | |
Available hosting regions, data residency options, and the implications for High Availability systems. |