IONOS Cloud Expert
Expert certification for the administrators and solution architects who design and build enterprise-grade solutions on IONOS Cloud. Every unit is either DESIGN or BUILD: design units carry deep architecture and a decision summary; build units add a Data Center Designer walkthrough with common-mistakes guidance. The course opens at the architectural decision level, assumes Foundational-level product familiarity, and threads a single regulated-enterprise scenario, FinCorp, through all eight modules so that each decision accumulates into one coherent architecture by the capstone.
Course Details
| Duration | ~8.3 hrs |
| Units | 39 content units and 8 knowledge checks across 8 modules |
| Certification | IONOS Cloud Expert (Administrator & Architect) |
| Passing Score | 750/1000 |
| Prerequisites | Recommended: IONOS Cloud Foundational certification. Assumes familiarity with all IONOS Cloud products as covered in Foundational. No product introductions are provided. Units open at the architectural decision level; build units then walk through the implementation in the Data Center Designer. Hands-on cloud experience strongly recommended. |
Who This Course Is For
This course is built for senior solutions architects, cloud engineers, cloud administrators, enterprise architects, and technical consultants who are past the introductory stage and now responsible for both the design and the implementation of production systems on IONOS Cloud. It is a design-and-build track: you will reason about trade-offs and compliance constraints like an architect, and you will then build the core architectures hands-on in the Data Center Designer like an administrator. The recurring FinCorp scenario, a German financial-services firm under GDPR and BSI obligations with a large VMware estate to migrate and an AI capability to build, gives every decision a real production and regulatory context.
How to Use This Course
- Start with Module 1: it lays down the whole-system frame (platform map, layered architecture, the native-substitution model, sovereignty) that every later unit fills in.
- For design units, focus on the trade-offs and the decision summary; for build units, first understand WHY, then follow the DCD walkthrough.
- Carry the FinCorp scenario forward: each unit's decision accumulates into one coherent architecture by the capstone.
- Treat the common-mistakes lists as production hard-won advice; they prevent the most frequent console errors.
- Pay special attention to IONOS capability boundaries; each is reframed as a native design pattern.
Module 1: Platform Architecture Overview (8%)
The whole-system picture and the platform's design philosophy before any deep dive. Everything later fills in this frame. All design units: no console walkthroughs.
Duration: ~30 min
| Unit | Topic | Duration | Words |
|---|---|---|---|
| 1.1 | The IONOS Cloud Platform Map | ~5 min | 1,082 |
| 1.2 | The Canonical Layered Architecture | ~7 min | 1,342 |
| 1.3 | Designing Around Platform Boundaries: The Native-Substitution Model | ~6 min | 1,280 |
| 1.4 | Sovereignty and Compliance as Design Inputs | ~7 min | 1,334 |
| 1.5 | Knowledge Check - Platform Architecture Overview | ~5 min | 1,039 |
Topics Covered:
- The product families and how they relate, with the Data Center Designer as the central control surface and the Virtual Data Center as the organising boundary
- The canonical enterprise shape: public Layer 7 load balancer, stateless compute tier, private Layer 4 load balancer, private-only data tier
- The native-substitution model: the platform composes capabilities rather than selling them as single managed features
- EU legal sovereignty as a property of operator jurisdiction, and the two BSI recognitions (C5 attestation and IT-Grundschutz certification) whose scopes differ per service
- The FinCorp scenario introduced and the reference diagram that later modules fill in
Module 2: Governance, Identity, and Cost Foundation (12%)
The commercial, identity, audit, and cost boundaries that govern every later decision, with the console builds that establish them.
Duration: ~39 min
| Unit | Topic | Duration | Words |
|---|---|---|---|
| 2.1 | Resource Model: Contracts, VDCs, and Boundaries | ~8 min | 1,518 |
| 2.2 | Identity, RBAC, and Federation | ~10 min | 1,921 |
| 2.3 | Activity Logs and the Audit Trail | ~6 min | 1,206 |
| 2.4 | Cost Architecture and FinOps | ~11 min | 2,117 |
| 2.5 | Knowledge Check - Governance, Identity, and Cost | ~5 min | 1,034 |
Topics Covered:
- Contract as the commercial, governance, and audit boundary; VDC as the regional segmentation primitive, and when to split each
- Identity model: capability rights vs resource grants, least-privilege by not granting, and federation as authentication only with its manual joiner/mover/leaver runbook
- Activity Logs as per-contract, read-only, 35-day retention exported to Object Storage with object lock for long-term, tamper-evident retention
- Cost architecture and FinOps: the compute contention model, storage tiering, scale-up vs cache-based scale-out economics, and Savings Plans
- The console builds that establish these boundaries: first VDC, groups and grants, scoped API tokens, and a cost alert
Module 3: Networking and Connectivity (18%)
Designing and building IONOS network architectures: VDC topology, security, load balancing, edge HA, hybrid connectivity, and customer-orchestrated DNS failover.
Duration: ~85 min
| Unit | Topic | Duration | Words |
|---|---|---|---|
| 3.1 | VDC Topology and Segmentation | ~10 min | 2,086 |
| 3.2 | Network Security: Firewall and Security Groups | ~13 min | 2,564 |
| 3.3 | Load Balancing - Layer 7 (Application) | ~13 min | 2,626 |
| 3.4 | Load Balancing - Layer 4 (Network) | ~11 min | 2,297 |
| 3.5 | High Availability at the Network Edge | ~12 min | 2,325 |
| 3.6 | Hybrid Connectivity: VPN, NAT, and Cross-Connect | ~12 min | 2,327 |
| 3.7 | DNS and Failover Routing | ~8 min | 1,544 |
| 3.8 | Knowledge Check - Networking and Connectivity | ~6 min | 1,166 |
Topics Covered:
- VDC topology and segmentation: the three-tier layout, addressing, reserved public IPv4, and why NIC firewalls protect server NICs only
- Network security: NIC-level firewall mechanics, Network Security Groups, the boundary that NSGs do not apply to managed load balancers or the cluster, and flow logs
- Layer 7 and Layer 4 load balancing: when content-aware routing earns its place, TLS termination, the API-gateway substitution, and the public-L7-to-private-L4 composition
- High availability at the network edge: IP failover and HA edge constructs, reserved-IP-backed stable endpoints
- Hybrid connectivity (VPN Gateway, NAT Gateway, Private Cross-Connect); health-based steering via load balancer health checks and IP failover groups, with customer-orchestrated low-TTL Cloud DNS re-pointing for cross-zone failover (Cloud DNS is not health-aware)
Module 4: Compute and Elasticity (14%)
Choosing the right compute class and building it: VM class selection, disks and images, elasticity and auto-scaling, and the dedicated VMware Private Cloud (design-only).
Duration: ~51 min
| Unit | Topic | Duration | Words |
|---|---|---|---|
| 4.1 | Compute Class Selection | ~13 min | 2,622 |
| 4.2 | Images, Disks, and Cloud-Init | ~10 min | 1,950 |
| 4.3 | Elasticity and VM Auto Scaling | ~11 min | 2,277 |
| 4.4 | Private Cloud (Dedicated VMware) | ~12 min | 2,323 |
| 4.5 | Knowledge Check - Compute and Elasticity | ~5 min | 1,062 |
Topics Covered:
- The four-way compute decision across core isolation, CPU-family control, block-storage attachment, and operational model
- Dedicated-core, shared-vCPU, and fixed-template instances, with the two common traps
- Images, disks, and cloud-init: block storage tiers and the performance floor, region-locking, first-boot configuration, and post-provisioning immutability
- Elasticity and VM Auto Scaling: horizontal-only replica scaling, replica configuration set at design time, anti-flapping controls, and the stateless-tier precondition
- Private Cloud as dedicated VMware delivered as-a-service, when it wins, the hybrid pattern, and guided-engagement provisioning
Module 5: Data and Storage (18%)
Designing and building data and storage under IONOS's real boundaries: no read replicas, dump/restore migrations, Backup Service scoped to VMs and Block Storage. Each constraint is reframed as a native pattern.
Duration: ~101 min
| Unit | Topic | Duration | Words |
|---|---|---|---|
| 5.1 | Block and File Storage | ~10 min | 2,051 |
| 5.2 | Object Storage | ~12 min | 2,386 |
| 5.3 | Relational Databases (Managed PostgreSQL / MariaDB) | ~18 min | 3,554 |
| 5.4 | NoSQL Databases (Managed MongoDB) | ~12 min | 2,451 |
| 5.5 | In-Memory Database (Cache Tier) | ~15 min | 3,022 |
| 5.6 | Event Streaming (Managed Kafka) | ~15 min | 2,987 |
| 5.7 | Data Protection and Lifecycle | ~11 min | 2,273 |
| 5.8 | Knowledge Check - Data and Storage | ~8 min | 1,566 |
Topics Covered:
- Block and file storage, the storage-zone-vs-compute-zone asymmetry, and Object Storage for tamper-evident retention, archive, and backup targets
- Relational databases: replication-mode decision, no read replicas (scale reads with in-memory cache plus connection pooling), failover, private endpoints, and dump/restore migration
- NoSQL MongoDB and the document model; in-memory cache as the read-scaling and session-externalisation layer
- Event streaming with managed Kafka: partition design, consumer groups, and application-level capture as the change-data-capture substitute
- Data protection: Backup Service scoped to VMs and Block Storage (no DBaaS, no immutable backups), snapshots as VM-level rollback, and one data-continuity plane
Module 6: Containers and AI Platform (14%)
Designing and building container platforms (Managed Kubernetes, Container Registry) and AI services (Model Hub) with honest compliance attribution and capability boundaries.
Duration: ~78 min
| Unit | Topic | Duration | Words |
|---|---|---|---|
| 6.1 | Kubernetes Platform Design | ~14 min | 2,888 |
| 6.2 | Provisioning a Public Cluster | ~8 min | 1,656 |
| 6.3 | Provisioning a Private Cluster | ~8 min | 1,666 |
| 6.4 | Container Registry and Platform Selection | ~15 min | 2,976 |
| 6.5 | AI Inference: Managed Model Hub | ~12 min | 2,374 |
| 6.6 | AI Sovereignty and the EU AI Act | ~12 min | 2,412 |
| 6.7 | Knowledge Check - Containers and AI Platform | ~8 min | 1,667 |
Topics Covered:
- Kubernetes platform design: free managed control plane over paid node pools, the autoscaling floor, and the four cluster boundaries
- Provisioning public and private clusters, managed ingress in front of the cluster, and the network dependencies a private cluster needs first
- Container Registry token-only governance, platform selection across managed and customer-deployed alternatives, and multi-cluster vs namespace isolation
- AI inference on Managed Model Hub, customer-built retrieval-augmented generation, and when self-hosted GPU serving is justified
- AI data-sovereignty boundaries and EU-AI-Act roles for the AI tier
Module 7: Operations, Resilience, and Performance (12%)
Making architectures production-ready: resilience and DR, observability, performance engineering, and the honest mechanics of a large VMware migration.
Duration: ~67 min
| Unit | Topic | Duration | Words |
|---|---|---|---|
| 7.1 | Resilience and Business Continuity | ~16 min | 3,214 |
| 7.2 | Observability and Operations | ~15 min | 3,064 |
| 7.3 | Performance Engineering | ~12 min | 2,409 |
| 7.4 | Migration and Hybrid Cutover | ~16 min | 3,224 |
| 7.5 | Knowledge Check - Operations, Resilience, and Performance | ~7 min | 1,486 |
Topics Covered:
- Resilience and business continuity: RTO/RPO anchors, three recovery strategies on platform primitives, multi-zone placement, load-balancer health checks, and customer-orchestrated low-TTL DNS failover
- Observability: the four telemetry planes and their fixed scopes, the gaps to design around, and fan-in to an external SIEM
- Performance engineering: storage performance floors, connection pooling and caching as throughput levers, and right-sizing trade-offs
- Migration and hybrid cutover: no native OVF/OVA import, the three infrastructure paths, wave planning, and the FinCorp large-VMware-estate plan that anchors the course
Module 8: Putting It All Together: Best-Practice Architecture (4%)
Synthesis: decision frameworks, the full reference enterprise architecture, and the flagship capstone build that assembles the FinCorp core end to end.
Duration: ~47 min
| Unit | Topic | Duration | Words |
|---|---|---|---|
| 8.1 | Architecture Decision Frameworks | ~12 min | 2,341 |
| 8.2 | The Reference Enterprise Architecture | ~13 min | 2,667 |
| 8.3 | Capstone Lab: Build the Enterprise Core End-to-End | ~14 min | 2,808 |
| 8.4 | Knowledge Check - Best-Practice Architecture | ~8 min | 1,527 |
Topics Covered:
- Selection matrices for compute, containers, storage, database engine, and networking primitive, each keyed to differentiating criteria and hard eligibility constraints
- The sovereignty filter applied last over the whole design, and the two common composition errors
- The reference enterprise architecture assembled as one design, with HA, load balancing, security, and connectivity as cross-cutting concerns
- The flagship capstone: building the FinCorp enterprise core end to end in the Data Center Designer, tying together every module walkthrough
Learning Outcomes
By the end of this course, you will be able to:
- Design complete solution architectures by composing IONOS Cloud products under real production and compliance constraints.
- Apply the native-substitution model for capabilities the platform composes rather than sells (API routing, read scaling, failover, change-data-capture, VM import, access control).
- Build core architectures in the Data Center Designer: networking, compute, storage, databases, containers, and operations.
- Architect compliant solutions using sovereignty, service-scoped BSI attestations (C5 / IT-Grundschutz), and GDPR as design inputs.
- Plan and execute large VMware migrations honestly (VCDA, NSX-T L2 VPN, image conversion; no native OVF/OVA import).
- Synthesize design and implementation into one enterprise architecture, built end to end in the capstone.
Next Steps
Pursue Specialized Certifications
- IONOS Kubernetes Deep Dive: container orchestration, workload management, and cloud-native architecture on IONOS Managed Kubernetes.
- IONOS AI Specialty: AI Model Hub and architecting end-to-end ML pipelines on IONOS Cloud.
Advance Your Career
- Senior Solutions Architect: lead enterprise cloud architecture initiatives and mentor technical teams on IONOS Cloud.
- Cloud Consultant: provide strategic advisory services for complex cloud migrations and transformations.
- Enterprise Architect: design organization-wide technology strategies incorporating IONOS Cloud.
Keep Learning
- Stay current with IONOS Cloud new service launches and capability expansions.
- Explore emerging technologies across AI/ML, edge computing, and container-native patterns.
- Obtain complementary certifications (Kubernetes Deep Dive, AI Specialty).
Resources
| Resource | Link |
|---|---|
| IONOS Cloud Architecture Center | https://www.ionos.com/enterprise-cloud/architecture/ |
| IONOS Cloud API Documentation | https://api.ionos.com/docs/ |
| IONOS Enterprise Support | https://www.ionos.com/help/enterprise/ |