Netcup Unveils EOS Cloud Platform & S3 Object Storage
German cloud provider Netcup has launched the public preview of “EOS”, a new cloud platform that aims to unify their management interfaces and introduces S3-compatible object storage and a modern API.
For years, Netcup users have had to juggle two separate web portals: the Customer Control Panel (CCP) for billing and domains, and the Server Control Panel (SCP) for server management.
The EOS platform is built to fix this split by bringing everything into one dashboard, while also adding tools for developers like object storage and cloud automation.
- AMD EPYC G12
- 2.5G Core Ports
- Live Telemetry
- Nuremberg / VIE
- 100% GDPR Compl.
- Multi-AZ Active
- OpenAPI 3.0
- Terraform Prov.
- eosctl CLI
1. Key Features of Netcup EOS
A. Unified Web Interface
- Single Sign-On (SSO): Removes the need to maintain separate credentials for
customercontrolpanel.deandservercontrolpanel.de. One account provides access to both administrative and server functions. - Updated Dashboard Features:
- Live metrics for CPU utilization, RAM usage, and disk I/O on the server overview;
- Integrated HTML5 VNC rescue terminal with clipboard sync;
- Role-Based Access Control (RBAC) allowing admins to grant technical server permissions without exposing billing details.
B. S3-Compatible Object Storage
Addressing the need for bulk storage without attaching NVMe volumes, EOS introduces object storage:
- AWS S3 Compatibility: Works with standard AWS SDKs,
aws-cli,rclone,Cyberduck, and backup tools likeResticandVelero. - Geo-Replication: Data is replicated between facilities located in Nuremberg (Germany) and Vienna (Austria).
- European Data Sovereignty: Operates under EU jurisdiction for GDPR compliance.
C. RESTful OpenAPI 3.0 & DevOps Tooling
- Replaces legacy SOAP/WSDL and JSON-RPC endpoints with JSON REST APIs using bearer token authentication.
- Includes official Go and Python SDKs and a command-line client (
eosctl). - Terraform Provider: Enables Infrastructure-as-Code (IaC) provisioning for servers, DNS records, and firewall rules in CI/CD workflows.
2. Practical Configuration: Mounting Netcup EOS S3 via Rclone
Connecting Netcup S3 storage to any Linux server requires only a few lines in your rclone.conf:
# ~/.config/rclone/rclone.conf
[netcup-eos]
type = s3
provider = Other
env_auth = false
access_key_id = YOUR_EOS_ACCESS_KEY
secret_access_key = YOUR_EOS_SECRET_KEY
endpoint = s3.eos.netcup.net
region = eu-central-1
acl = private
Execute remote operations seamlessly:
# Verify connectivity and list buckets
rclone lsd netcup-eos:
# Synchronize local application backups to remote S3 bucket
rclone sync /var/backups netcup-eos:production-database-backups --transfers 8 --progress
3. EOS and Existing Systems
Note that EOS is currently a standalone platform designed for new workloads. Existing services like the Generation 12 RS and VPS plans are not migrating to EOS, and remain managed through the traditional CCP and SCP panels.
Voucher Code Compatibility: Because EOS is a separate system in its preview phase, it is currently unverified whether existing promotional vouchers (such as the €5 welcome credits or Root Server free-month vouchers) will work for EOS-specific products. We will update our lists once more information is available.