Before your Lobster Cloud environment is provisioned, an onboarding call takes place. This is a structured technical discussion between you and a Lobster technician to clarify all requirements, set expectations, and ensure a smooth installation.
Why the onboarding call is important
The onboarding call ensures that all technical details are clarified upfront and prevents misunderstandings later. During the call, you discuss network requirements, VPN needs, and system preferences. Every topic from the onboarding protocol is reviewed together so there are no surprises during or after installation.
The Lobster Cloud is a standardized solution. The onboarding protocol documents all predefined standards and fixed configurations that cannot be modified after installation.
Onboarding steps
Step | Description | Your Involvement |
|---|---|---|
1. Onboarding scheduling | A Lobster technician will arrange an onboarding appointment with you. | Ensure relevant technical contacts are available. |
2. Onboarding call | All topics from the onboarding protocol are discussed and documented. | Provide all required technical information. See the Preparation Checklist for details. |
3. Onboarding document signing | The completed onboarding protocol (PRE-Call PDF) must be signed by you. Once Lobster has received the protocol back, the installation can be initiated. | Review and sign the document. |
4. System provisioning | Your Lobster Cloud environment is being created. After signing the onboarding agreement, provisioning usually takes two business days. | No action required. |
5. Credential delivery | You receive two separate emails with your login credentials. | Your environment is ready for use. |
6. Installation protocol | You receive a detailed document with all system-specific information. | Distribute to relevant contacts. |
Topics covered in the onboarding call
The onboarding protocol covers the following areas. Each topic is discussed in detail during the call:
Topic | Key Points |
|---|---|
Network range | Selection of one of three available private network ranges. Please note that this cannot be changed after installation. |
Access credentials | How you will receive your login information (two separate emails). |
Platform access | Accessing the Lobster DATA Platform via HTTPS on Port 443. |
Ports and protocols | Default ports, fixed system ports, and how to request additional ports. |
SSL certificates | Let's Encrypt (default) or your own certificates. Specific considerations for AS2. |
DNS configuration | Standard .lobster-cloud.com DNS or your own custom DNS names. |
Internal DNS | Route53 Resolver Endpoints for hybrid environments (optional, additional cost). |
Transport Manager | Private IP connectivity on Port 8020. |
You must provide your own email server with SMTP details (Port 587). | |
Firewall | Security group rules, IP-based only, max 960 rules. |
VPN | Site-to-site VPN setup if required. Requirements and limitations. |
AS2 | Fixed Port 443, certificate considerations. |
SMB/NFS | Shared folder connectivity requires VPN and Port 445. |
SAP Connector | ARM/AArch64 compatible driver is required from your side. |
Fixed OS, database, and software update schedules. | |
Standard automatic updates or optional customer-managed updates. | |
Not permitted in the Lobster Cloud environment. |
After the onboarding
Once the onboarding protocol is signed, Lobster provisions your environment within two business days. You do not need to take any further action until you receive your access credentials.
If you have additional requirements after the onboarding (for example, a VPN connection or additional ports), submit a support ticket to support@lobster.de. These can be configured after installation.