What does WZ-IT operate in Open Telekom Cloud?

For suitable Linux ECS instances, we take over the agreed guest scope including patching, hardening, monitoring, backup management, and documented services. VPC, IAM, CBR, CCE, and other platform services are scoped separately.

Can you configure VPC, VPN, and Direct Connect?

Yes. We plan subnets, routes, security groups, public endpoints, and connections to sites or other clouds. VPN and Direct Connect have different availability, bandwidth, and cost characteristics.

Does an ECS scale automatically?

No. ECS initially describes the virtual instance. Automatic scaling requires rules, suitable images, stateless applications, load balancing, and tests. We do not promise elasticity from the product name alone.

Do you operate Cloud Container Engine (CCE)?

Yes, as a separate Kubernetes scope. Responsibilities for control plane, nodes, add-ons, workloads, registry, observability, backups, and upgrades are documented first; CCE is not included in the price of a single ECS.

Do you use Terraform?

For suitable environments, yes. APIs, OpenStack-compatible tools, and infrastructure as code can make changes reproducible. The toolchain is selected for the existing estate, team, and lifecycle rather than imposed by default.

Can you migrate from AWS or Azure to OTC?

Yes. We map services and dependencies, assess portability, data transfer, identities, and the operating model, and plan test migration, cutover, and rollback. Similar product names do not imply complete one-to-one compatibility.

Does a C5 attestation automatically make our application compliant?

No. Provider attestations cover defined controls and periods of the cloud platform. Configuration, identities, guest operations, applications, data, contracts, and the customer's organizational controls remain separate responsibilities.

Is OTC always the best choice for regulated organizations?

Not automatically. Region, service description, evidence, required services, portability, cost, and the customer's control model must fit the project. We compare these requirements with alternatives.

How is administrative access secured?

The customer retains the account. WZ-IT receives separate, least-privilege IAM access; MFA, roles, keys, logging, and emergency access are defined in the access design.

How do you use Cloud Backup and Recovery?

CBR can protect ECS, EVS, and SFS. We configure vaults, schedules, retention, and where needed Backup Lock or cross-region replication. Application consistency and actual recovery are assessed separately.

Is OBS automatically an offsite backup?

No. OBS can be a suitable target for selected backups or application objects. Account, region, permissions, versioning, encryption, and failure domain determine whether the separation meets the recovery objective.

Do you perform recovery tests?

Yes, where included in the recovery scope. Frequency, depth, target system, and acceptable impact are documented; an enabled backup job alone is not a tested recovery.

Does the environment remain in our OTC account?

Yes. The provider contract, resources, and billing remain with the customer. WZ-IT receives documented technical access and takes over only the agreed operating scope.

What does operations cost?

Monitoring-only starts at €49.90 net per server and month. Operating a suitable Linux ECS starts at €149.90 net per month. CCE, databases, complex networks, and other platform services are scoped separately.

What contract term and notice period apply?

The service can be cancelled monthly, with 30 days' notice to the end of the month.

How quickly does WZ-IT respond?

Response time follows the selected service level. Production and Critical include 24/7 response to qualified P1 incidents; provider response and repair times remain separate.

Does Telekom offer its own managed services?

Yes. Open Telekom Cloud has its own managed-service specifications, including operating systems and CCE. During the audit, we assess whether WZ-IT, a Telekom service, or shared responsibility is the best technical and commercial fit.

Managed T Cloud Public (Open Telekom Cloud) ECS: Linux operations

We take over the agreed operation of Linux ECS and clearly scope VPC, CBR, CCE, and other platform services. Resources and the provider contract remain in your account.

ECS & platform services
Systems remain in your account
Service levels up to 24/7 for P1

Configure OTC operations To server audit

Reviews

IT Beratung Service Consulting Soforthilfe

Companies worldwide trust WZ-IT

Read client reviews

Context

Operate OTC infrastructure with clear ownership

ECS, CCE, databases, and other managed services distribute responsibility differently between provider and customer. We map these boundaries, take over the agreed operations, and document access, maintenance, monitoring, backup, and incident response.

ECS Management (Servers)
We take over the agreed operation of suitable Linux ECS instances, including maintenance, monitoring, and documented services.
VPC & Networking
We plan VPCs, subnets, security groups, VPN or Direct Connect, and ELB as one coherent architecture.
Storage & Backup
We align CBR, EVS, SFS, and OBS with data consistency, RPO, RTO, retention, and failure-domain requirements.

Open Telekom Cloud service areas

Which Open Telekom Cloud services we design and operate

Beyond ECS, Open Telekom Cloud provides numerous network, storage, database, container, and security services. We define the remaining customer and WZ-IT scope for each service and distinguish our work from Telekom's own managed services.

Compute & Linux

Operate ECS, EVS, and related compute resources

Elastic Cloud Server (ECS) with images, flavor, Elastic IP, and Elastic Volume Service (EVS)
Auto Scaling and Elastic Load Balancing for suitable multi-instance architectures
Assess Bare Metal Server (BMS) or Dedicated Host as a separate scope
Operate Linux hardening, OS updates, Docker, and agreed applications
Infrastructure as code through Terraform, APIs, or Resource Formation

Scope boundary and notes

The clear entry point is operating suitable Linux systems on Elastic Cloud Servers. Other compute products are mapped to their own responsibility boundary.

Responsibility boundary: Open Telekom Cloud operates the cloud platform. The guest operating system, configuration, data, and applications remain customer responsibilities unless WZ-IT explicitly takes them over.

Outcome: A clear operating scope for ECS and adjacent compute resources.

VPC & connectivity

Design VPC, ELB, and hybrid connectivity together

Virtual Private Cloud, subnets, Security Groups, Elastic IP, and NAT Gateway
Elastic Load Balancing, Domain Name Service, and VPC Endpoint
Virtual Private Network or Direct Connect for site connectivity
Enterprise Router and Private Link Access Service for suitable complex topologies
Cloud Firewall, Anti-DDoS, and Web Application Firewall by protection requirement

Scope boundary and notes

We structure networks and access using the exact OTC services and document which connections are public, private, or cross-site.

Responsibility boundary: Network and security services provide capabilities; topology, rules, approved data flows, and application access still require design and maintenance.

Outcome: A documented OTC network architecture with explicit public and private paths.

CCE & platform

Take over Kubernetes, registry, and platform-service operations

Cloud Container Engine (CCE) with nodes, node pools, upgrades, and autoscaling
Software Repository for Containers for images and deployment access
Ingress, secrets, policies, observability, GitOps, and CI/CD
Distributed Message Service for Kafka or API Gateway after separate assessment
Application recovery and protection of persistent Kubernetes data

Scope boundary and notes

Cloud Container Engine reduces control-plane effort. WZ-IT covers the remaining duties for clusters, nodes, add-ons, workloads, and data by scope.

Responsibility boundary: CCE management does not replace operation of workloads, Kubernetes objects, data, add-ons, and application integrations.

Outcome: A scoped Kubernetes and platform operation on Open Telekom Cloud.

Storage, data & recovery

Combine CBR, OBS, file storage, and databases correctly

Cloud Backup and Recovery (CBR) with vaults, policies, replication, and Backup Lock
Object Storage Service (OBS), Elastic Volume Service, and Scalable File Service
Relational Database Service for PostgreSQL, MySQL, or Microsoft SQL after assessment
Document Database Service, Distributed Cache Service, or TaurusDB under a separate scope
Restore tests, RPO, RTO, and application-aware restart procedures

Scope boundary and notes

We map storage and data services to consistency, access, retention, and recovery objectives.

Responsibility boundary: CBR, database backups, and storage redundancy serve different purposes. Data consistency and complete application restore must be assessed separately.

Outcome: A recovery design for compute, storage, database, and application instead of isolated backup features.

IAM, observability & governance

Control permissions, logs, and cloud operations with traceability

Identity and Access Management (IAM), technical users, and least-privilege roles
Cloud Eye, Cloud Trace Service, Log Tank Service, and Config by scope
Key Management Service and Host Security Service by protection requirement
24/7 monitoring and incident response according to the selected service level
Migration, cost review, and coordination with OTC or Telekom support

Scope boundary and notes

We connect technical resources with roles, monitoring, audit trails, cost, and provider escalation.

Responsibility boundary: Provider attestations and Telekom's own managed services apply only to their documented scope. Customer configuration, applications, data, and WZ-IT services remain separate responsibility areas.

Outcome: An OTC environment with defined roles, auditable changes, and a clear incident path.

One operating model

One operating model for Open Telekom Cloud and additional systems

The provider is only one operating location. WZ-IT connects servers, clouds, and on-premises systems into a documented environment with consistent monitoring, controlled access, and one coordinated service level.

View hybrid and multi-cloud operations

Location and control

Contracts, accounts, and administrative control remain with you. We take over the agreed technical operations without moving the infrastructure into a closed hosting product.

Private connectivity

NetBird, WireGuard, or existing site connections integrate further clouds, Proxmox systems, and on-premises networks through controlled paths.

Operations and response

Monitoring, updates, backups, documentation, and incident response are designed across all participating systems and operated according to the selected service level.

Monitoring · SLA · Operations

Open Telekom Cloud
Private connectivity
Cloud · Proxmox · On-premises

Compliance

Map provider evidence to your own scope

An attestation for the cloud platform does not replace secure configuration and documented operation of the customer workload.

Operating model

Cloud capabilities in the operating model

Map provider attestations and service descriptions to your own compliance scope
Build ECS, VPC, EVS, and ELB as a documented target architecture
Plan CBR with policies, Backup Lock, and optional cross-region replication
Price CCE and other platform services separately from Linux instance operations
Use APIs and infrastructure as code for reproducible changes where required

View server management and pricing

Shared responsibility

Compliance remains shared responsibility

We review the service description and provider evidence and document controls that remain in the customer and WZ-IT scope.

Takeover

How we take over existing OTC environments

The audit first establishes current state, responsibilities, and required action.

01
Audit
We check current state (security, updates, backups)
02
Hardening
We implement agreed safeguards and technical IAM access
03
Onboarding
We configure monitoring, alert paths, maintenance windows, and documentation
04
Operations
We perform the documented operating duties according to the service level

Service scope

Monitoring or full operations

With Monitoring Only, our team reviews alerts and notifies your team during service hours; incident resolution stays with you. Standard Linux VM operations start at €149.90. Kubernetes, managed databases, multi-account setups, and further cloud services are scoped individually. This also applies to complex ECS instances environments.

Server operationsfrom €149.90Monitoring Only from €49.90

Configure server operations Pricing and service levels

Onboarding typically starts within 1 to 2 business days after signing

Payment

Bank transfer

Other routes

Entry

Server audit

Establish condition, responsibilities and required action before takeover.

To server audit →Operations

Server operations as a service

Patching, backups and response from one team

View →

Frequently Asked Questions

Everything about ECS, VPC, Kubernetes and compliance

TopicsECS & Networking CCE, Automation & Migration Security & Compliance Backup & Recovery Takeover, Cost & Service Level

ECS & Networking

CCE, Automation & Migration

Security & Compliance

Backup & Recovery

Takeover, Cost & Service Level

Knowledge

Further guides

In-depth knowledge from our knowledge base.

Guides

Further entry points

Reviews & projects

Operations that visibly relieve customers

Customer feedback on monitoring, updates, maintenance, support and stable production systems.

Networking & Provisioning

WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.

Steve KirchnerManaging Director, nextGYM GmbH

View project

International

Built in Germany's Ruhr Valley. Running worldwide.

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.

Selected projects

Read client reviews

Enquiry

Discuss Open Telekom Cloud operations

We assess your environment and clearly scope ECS, networking, backup, and platform services.

Straight with Timo and Robin - no sales team, no pitch
A professional assessment of your situation
Concrete next steps for infrastructure, software or AI

The conversation is free and non-binding.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.

Jakob ÖschlbergerInno7 GmbH

Email[email protected]Phone+49 2922 875068

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.

Jakob ÖschlbergerInno7 GmbH

Managed T Cloud Public (Open Telekom Cloud) ECS: Linux operations

ECS Management (Servers)

VPC & Networking

Storage & Backup

Operate ECS, EVS, and related compute resources

Design VPC, ELB, and hybrid connectivity together

Take over Kubernetes, registry, and platform-service operations

Combine CBR, OBS, file storage, and databases correctly

Control permissions, logs, and cloud operations with traceability

Location and control

Private connectivity

Operations and response

Monitoring · SLA · Operations

Cloud capabilities in the operating model

Compliance remains shared responsibility

Audit

Hardening

Onboarding

Operations

Server audit

Server operations as a service

ECS & Networking

What does WZ-IT operate in Open Telekom Cloud?+

Can you configure VPC, VPN, and Direct Connect?+

Does an ECS scale automatically?+

CCE, Automation & Migration

Do you operate Cloud Container Engine (CCE)?+

Do you use Terraform?+

Can you migrate from AWS or Azure to OTC?+

Security & Compliance

Does a C5 attestation automatically make our application compliant?+

Is OTC always the best choice for regulated organizations?+

How is administrative access secured?+

Backup & Recovery

How do you use Cloud Backup and Recovery?+

Is OBS automatically an offsite backup?+

Do you perform recovery tests?+

Takeover, Cost & Service Level

Does the environment remain in our OTC account?+

What does operations cost?+

What contract term and notice period apply?+

How quickly does WZ-IT respond?+

Does Telekom offer its own managed services?+

Guides

Further entry points

Built in Germany's Ruhr Valley. Running worldwide.

Selected projects

Read client reviews

Which OTC service do you need?