Skip to content
Banking & Financial Services Sector

Cloud Basics Training for the Banking & Financial Services Sector

Banks in Indonesia adopt cloud under OJK supervision. POJK 11/POJK.03/2022 and SEOJK 29/SEOJK.03/2022 require IT risk management for cloud computing: vendor assessment, specific data residency, exit strategy, and cyber controls. Technical teams need to master AWS/Azure/GCP basics, an OJK-auditable landing zone, and FinOps discipline because banking workloads (core, internet banking, mobile, analytics) are significant in cost and service-critical.

  • 4.9/5 · 287 reviews
  • 300+ clients nationwide
  • 2,000+ trainers
  • 1 to hundreds of participants
  • Standard · Premium · Private 1-on-1
Request ProposalChat on WhatsApp
format
In-house / online / hybrid
duration
4 intensive days per cohort
participants
10–25 per cohort
language
Indonesian / English

2,000+ trainers and experts

Our group's teaching network, matched to what your team needs.

See class documentation

You see your trainer first

The trainer's profile, track record and field come with the proposal, before you decide.

4.9 out of 5

287 participant reviews.

300+ clients nationwide and 180,000+ private training sessions completed. Among them: MPR RI, Akademi Militer Magelang, DPRD Provinsi Jawa Timur.

One person to hundreds

Private coaching for one participant, a class for one team, or several cohorts at once.

Three budget levels

  • Standard: core class, material fitted to the participants’ work
  • Premium: senior trainer, deeper material design
  • Private 1-on-1: one participant, one trainer, schedule set by the participant
Tell us your budget
Banking & Financial Services Sector Focus

Why Cloud Basics for IT Teams is different in Banking & Financial Services

Banks in Indonesia adopt cloud under OJK supervision. POJK 11/POJK.03/2022 and SEOJK 29/SEOJK.03/2022 require IT risk management for cloud computing: vendor assessment, specific data residency, exit strategy, and cyber controls. Technical teams need to master AWS/Azure/GCP basics, an OJK-auditable landing zone, and FinOps discipline because banking workloads (core, internet banking, mobile, analytics) are significant in cost and service-critical.

Sector KPIs
  • Landing zone & guardrail coverage
    Applied across all production & non-production accounts/subscriptions
  • FinOps discipline (tagged spend ratio)
    Nearly all spend tagged per product/team
  • OJK examination findings on cloud IT
    No material findings in the next cycle
Relevant regulations & standards
  • POJK 11/POJK.03/2022 Commercial Bank IT Risk Management
  • SEOJK 29/SEOJK.03/2022 Commercial Bank Cyber Resilience & Security
  • UU PDP No. 27/2022 — customer data
  • ISO/IEC 27001:2022 — cloud controls
  • CIS AWS / Azure / GCP Benchmarks
  • AWS Well-Architected Financial Services Lens
Target roles in Banking & Financial Services
  • Bank CIO / Head of IT
  • Head of Cloud Center of Excellence
  • Enterprise Architect
  • Head of IT Security / CISO
  • Head of IT Risk
  • Head of FinOps / Cost Governance
Outcomes commonly requested in Banking & Financial Services
  • Bank engineering teams master AWS/Azure/GCP shared responsibility and can map it to POJK controls
  • Bank landing zone designed with account/subscription, identity, network, logging structure that is auditable
  • Baseline CIS Benchmarks hardening applied to production and non-production accounts
  • FinOps discipline in place: cost tags, budgets, monthly per-product/digital-channel reviews
  • Compliance documentation (shared responsibility, residency, exit strategy) ready for OJK examination
Banking & Financial Services-specific questions
How does this module help comply with POJK 11/POJK.03/2022 for cloud adoption?
The module teaches shared-responsibility mapping, an auditable landing zone, residency and exit-strategy documentation, and CIS Benchmarks hardening as IT risk-management components. Working papers produced can be attached to SKAI working papers during OJK examinations.
Does the material cover AWS, Azure, and GCP or just one vendor?
Either multi-vendor or focused on the bank's primary vendor. For banks with a single-cloud strategy we focus on that vendor's Well-Architected framework; for multi-cloud we map equivalent services and landing zone practices across each.
How does the module handle UU PDP for customer data in cloud?
A dedicated module covers residency, data classification, encryption + KMS, least-privilege IAM, and incident-notification obligations, with case exercises on processing customer data in cloud analytics & AI services.

Quick Answer

Corporate Cloud Foundation training is an in-house program that equips technical teams with AWS, Azure, and GCP essentials (networking, identity, compute, storage, security, and cost), guided by AWS Well-Architected 6 pillars, the FinOps Framework, NIST SP 800-145, and CIS Benchmarks, so cloud adoption is fast, safe, and cost-disciplined.

Free Consultation

Guided by industry-recognized cloud frameworks

The material follows AWS Well-Architected (6 pillars), Azure Well-Architected, Google Cloud Architecture Framework, NIST SP 800-145 (the official cloud definition), CIS Benchmarks (hardening), FinOps Framework (cost), and Cloud Adoption Framework (landing zone), the frameworks cloud vendors and independent auditors themselves reference.

Without FinOps, enterprise cloud spend escalates fast

Unmanaged cloud workloads typically carry 20–35% wasted spend (idle resources, over-provisioning, logs without lifecycle, suboptimal savings plans). The FinOps module establishes discipline that can be reported to the CFO before the board blocks new cloud investment.

Adoption pattern: disciplined single-cloud before multi-cloud

For most Indonesian enterprises, single-cloud executed with strong landing zones, FinOps, and Well-Architected is more sensible than premature multi-cloud. Multi-cloud becomes relevant only with strong reason (regulator residency, critical resilience, unique service combinations).

Clients & Documentation

Some of the institutions we have trained

Photos from sessions we have delivered, each one named after the institution it belongs to.

See class documentation (123 photos)

Cloud Basics for IT Teams

Corporate cloud foundation training is an in-house program that equips technical and operations teams with AWS, Microsoft Azure, and Google Cloud essentials (service models, networking, identity, storage, observability, security, and cost), mapped to AWS Well-Architected 6 pillars, Azure Well-Architected, Google Cloud Architecture Framework, NIST SP 800-145, CIS Benchmarks, and the FinOps Framework, with landing zone and guardrail practice aligned to the Cloud Adoption Framework.

1Designed via training needs analysis (TNA) by role: developer, ops/SRE, security, data, architect, technical executive
2Grounded in NIST SP 800-145 (IaaS/PaaS/SaaS + 5 essential characteristics) as the conceptual baseline
3Hands-on with major vendors: AWS (Well-Architected 6 pillars), Azure (Well-Architected + CAF Azure landing zone), GCP (Architecture Framework)
4Cost governance grounded in the FinOps Framework (3 phases: Inform, Optimize, Operate): tagging, budgets, rightsizing, savings plans
5Baseline hardening per CIS Benchmarks AWS/Azure/GCP, with landing zone & guardrail labs (SCP / Azure Policy / Org Policy)
6Measured via Kirkpatrick (L1–L3); upgradable to Phillips ROI L5 when finance or risk requires monetary impact
7References we work from: the six AWS Well-Architected pillars, the FinOps Framework for cost discipline, the NIST SP 800-145 cloud service definitions, and CIS Benchmarks for baseline hardening.

Measurable Outcomes

Expected Outcomes

Indicators mapped to Kirkpatrick levels and Well-Architected pillars: qualitative targets, set jointly during TNA against your baseline.

Cloud concepts understood across the team
Most participants pass knowledge assessment on service models (IaaS/PaaS/SaaS per NIST 800-145), VPC/VNet networking, IAM, and storage tiers. Judged through a core services assessment at the close of the class (Kirkpatrick L2).
Designs follow good practice
Participants complete a Well-Architected review on one internal workload across 6 pillars (Operational Excellence, Security, Reliability, Performance, Cost, Sustainability). Visible in the architecture designs reviewed together (Kirkpatrick L3).
Baseline hardening is applied
Baseline guardrails confirmed (root account protection, MFA, CIS Benchmarks baseline, encryption-at-rest enabled) on lab accounts. Seen in the account configuration participants tidy up (Kirkpatrick L3).
The cloud bill comes under control
Tagging strategy, budgets, and per-team/product cost dashboards defined; participants can read cost & usage reports. Progress is read on the Inform phase of the FinOps Framework.
A landing zone ready to build
Team has a draft landing zone (account/subscription/project structure, identity, network, logging) aligned to the Cloud Adoption Framework. The design follows the Cloud Adoption Framework (CAF).
Monetary value of the cost savings (optional)
Estimated savings from rightsizing, savings plans, and idle-resource elimination, with isolated training effect when finance requests numbers. Savings translate into rupiah using Phillips L5 for finance.

Program Format

Program Format Options

Chosen by your cloud-adoption stage, finalized after TNA. Enough grounding to start working in the cloud is in place once those four days close. Organizations mid-migration generally attach a two to four month phased programme so the landing zone and cost discipline get built alongside.

1

Cloud Essentials Bootcamp (3–5 days)

Intensive AWS/Azure/GCP essentials bootcamp: NIST 800-145 concepts, networking, IAM, compute, storage, observability, security & cost basics. Hands-on labs in sandbox accounts.

Best for: Teams new to cloud or expanding cloud adoption
2

Well-Architected Review Workshop

Consultative workshop: participants bring a real workload, facilitator guides a Well-Architected review across 6 pillars with prioritized recommendations as output.

Best for: Teams already running cloud and seeking maturity uplift
3

Landing Zone & Guardrail Design

Consultative session designing a landing zone (accounts/subscriptions structure, identity, hub-spoke network, logging, guardrails) aligned to the Cloud Adoption Framework.

Best for: Organizations pre-migration or standardizing multi-team cloud usage
4

Recurring FinOps Enablement

Recurring program (monthly/quarterly): reading cost & usage reports, rightsizing sessions, savings plan/commitments review, and a cross-team FinOps cadence.

Best for: Organizations with significant cloud spend needing sustained discipline

Free Consultation

Discuss your team's cloud adoption plan

We map vendors, roles, cloud adoption stage, and your regulatory obligations, then build a proposal and budget based on real needs.

Request Proposal

Curriculum

Curriculum Framework

Designed via ADDIE; final modules curated by target vendor (AWS / Azure / GCP), role, and maturity level from TNA. Topics below represent the full activatable coverage.

  • NIST SP 800-145 definition: IaaS, PaaS, SaaS + 5 essential characteristics (on-demand, broad network access, resource pooling, rapid elasticity, measured service)
  • Public vs private vs hybrid vs multi-cloud: when each makes sense
  • AWS / Azure / GCP shared responsibility model: what the vendor owns vs what you own
  • Geography: region, availability zone, edge location. Impact on latency & data residency (UU PDP)
  • Introduction to Cloud Adoption Framework (Microsoft CAF + AWS CAF) as an adoption roadmap

  • Virtual networks: AWS VPC, Azure VNet, GCP VPC. Subnets, route tables, peering, transit gateway / Virtual WAN
  • Hybrid connectivity: VPN, AWS Direct Connect, Azure ExpressRoute, GCP Interconnect
  • Identity & access: AWS IAM + IAM Identity Center, Entra ID + Azure RBAC, Google Cloud IAM
  • Least privilege & break-glass principles; mandatory root/owner protection + MFA
  • Service control policies (AWS Organizations), Azure Policy, GCP Organization Policy as guardrails

  • Compute: VMs (EC2 / Azure VM / Compute Engine), containers (ECS/EKS, AKS, GKE), serverless (Lambda, Functions, Cloud Run)
  • Storage: object (S3, Blob, GCS), block (EBS, Managed Disks, Persistent Disk), file (EFS, Files, Filestore). When to use which
  • Storage classes & lifecycle (S3 Standard / IA / Glacier and equivalents) for cost control
  • Managed databases: RDS / Aurora, Azure SQL / Cosmos DB, Cloud SQL / Spanner / BigQuery. Operational vs analytical fit
  • Observability basics: CloudWatch, Azure Monitor + Log Analytics, Cloud Logging + Cloud Monitoring

  • CIS Benchmarks AWS / Azure / GCP as the technical hardening baseline
  • Encryption at rest & in transit; KMS / Key Vault / Cloud KMS; key rotation policies
  • Logging & audit: CloudTrail + Config, Azure Activity Log + Defender for Cloud, Cloud Audit Logs + Security Command Center
  • Posture management: AWS Security Hub, Microsoft Defender for Cloud, Security Command Center Premium
  • Alignment to UU PDP No. 27/2022 (personal data), data residency, and sectoral policies (POJK, BSSN) where relevant

  • FinOps Framework (FinOps Foundation): 3 phases Inform → Optimize → Operate and 6 core principles
  • AWS/Azure/GCP billing anatomy: cost allocation tags/labels, cost & usage report, BigQuery billing export, Cost Management + EA agreement
  • Savings strategies: rightsizing, scheduling (auto stop/start), spot/preemptible, savings plans / reserved instances / committed use discounts
  • Common anti-patterns: idle resources, over-provisioning, single-instance databases, log retention without lifecycle
  • Showback & chargeback per team/product; monthly cost review cadence & FinOps anomaly detection

  • AWS Well-Architected 6 pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability
  • Azure Well-Architected Framework: Reliability, Security, Cost Optimization, Operational Excellence, Performance Efficiency
  • Google Cloud Architecture Framework: 6 perspectives (operational, security & privacy, reliability, cost, performance, system design)
  • Landing zones: AWS Control Tower / Landing Zone Accelerator, Azure landing zone CAF, GCP Cloud Foundation Toolkit
  • Migration patterns: 6 R's (rehost, replatform, repurchase, refactor, retain, retire). When each is appropriate

Comparison

Choosing Vendor & Training Format

Concise decision matrix. Final recommendation set after training needs analysis.

AspectCloud Essentials BootcampWell-Architected Review WorkshopLanding Zone & Guardrail DesignRecurring FinOps Enablement
Primary goalBuild concept foundation + labsMature an existing workloadStandardize accounts & guardrailsCost discipline & accountability
Ideal participantsTeams new to / expanding cloudTeams already running, need reviewPre-migration or multi-teamCloud spend already significant
Typical duration3–5 intensive days2–3 day workshop1–2 week consultingMonthly / quarterly
Main outputConcept mastery + certificatePrioritized 6-pillar recommendationsLanding zone reference + guardrailsTagging, dashboard, FinOps cadence
Core framework usedNIST 800-145 + Well-Architected basicsFull Well-Architected 6 pillarsCloud Adoption Framework + CISFinOps Framework 3 phases

For Whom

Who This Program Is For

Designed by role because cloud adoption challenges differ across functions.

Application developers & engineers

Teams building services on cloud (web, API, mobile backend, data pipelines).

Common challenges

  • Unclear which compute to pick (VM vs container vs serverless) for real workloads
  • Not yet fluent with cloud-safe network, IAM, and secret management patterns
  • Costs balloon from idle resources, logs without lifecycle, and over-provisioned databases

Operations / SRE / Platform engineers

Teams running, monitoring, and securing the platform for all application teams.

Common challenges

  • Hard to standardize landing zones & guardrails across teams (each team rolls its own)
  • Fragmented observability: logs, metrics, traces not connected
  • Patching, scaling, disaster recovery lack consistent repeatable patterns

Security & Compliance

Teams ensuring cloud adoption aligns with regulations & internal controls.

Common challenges

  • Shared responsibility not yet mapped to internal controls (ISO 27001, POJK, UU PDP)
  • CIS Benchmarks not applied consistently across accounts/subscriptions/projects
  • Audit logs scattered across accounts and missing centralization for forensics / examinations

Architects & Tech Leads

Owners of system design and the patterns used by many teams.

Common challenges

  • No shared Well-Architected vocabulary for trade-off discussions
  • Hard to decide single vs multi-cloud appropriate for Indonesian context
  • 6 R's migration not yet used as a workload-by-workload decision framework

Technical executives (CIO / CTO / Head of Eng)

Owners of cloud investment decisions and cost accountability to the board.

Common challenges

  • Monthly cloud bills rise without per-team/product visibility
  • No FinOps discipline that can be reported to the CFO
  • Cloud adoption roadmap not yet built using the Cloud Adoption Framework

Industry Context

Industry Applications

One specific use case per industry, naming real workflows, regulations, and architecture patterns.

Banking & Financial Services

Bank cloud adoption with a landing zone meeting POJK 11/POJK.03/2022 (commercial bank IT risk management) and SEOJK 29/SEOJK.03/2022 (cyber security), including shared-responsibility documentation, customer data residency aligned with UU PDP, and exit-strategy readiness for the regulator.

Technology & Startups

Standardizing landing zone & FinOps across product teams at a fast-growing technology company, so cloud costs stay controlled, guardrails are uniform, and onboarding new teams is fast without lowering security posture.

See in Technology & Startups context →
State-Owned Enterprises (BUMN)

Holding-scale cloud foundation across subsidiaries with governance auditable by BPK/SPI, uniform landing zone, and consistent UU PDP compliance documentation across entities.

See in State-Owned Enterprises (BUMN) context →
Manufacturing

Cloud foundation for manufacturing plants & corporate functions with production analytics, IoT/OT data lakes, and ERP integration needs, with FinOps discipline because IoT ingestion costs balloon quickly.

See in Manufacturing context →
Government & Public Sector

Cloud foundation for government agencies running SPBE with landing zones that consider citizen-data residency (UU PDP public sector), BSSN guidance, and SPBE Index audit readiness.

See in Government & Public Sector context →
Healthcare & Pharmaceuticals

Cloud foundation for hospitals & health networks with modern SIMRS, BPJS/insurance integration hubs, and clinical analytics, with patient data protected per UU PDP (specific personal data) and KARS accreditation readiness.

See in Healthcare & Pharmaceuticals context →

Delivery Method

Delivery

Format adapts to your technical team distribution; all formats are hands-on in cloud sandbox accounts.

On-site intensive & workshop

Facilitator comes to your office for a 3–5 day bootcamp; labs in cloud sandbox accounts, Well-Architected review of an internal workload, and landing zone exercises.

Live online + managed labs

Interactive classes via Zoom/Teams for distributed teams; labs run in AWS/Azure/GCP sandbox accounts provided by Neksus or your internal accounts.

Hybrid

On-site for consultative modules (Well-Architected review, landing zone design); online for concepts & labs. Suits multi-location teams.

Scheduling fits your release & on-call calendar
Materials & labs localized to Indonesian context (nearest region, regulations, industry patterns)
Sandbox accounts with budget guardrails provided for labs; alternative is labs in your internal account with limited scope
Participation certificate for every attendee
Evaluation report & prioritized recommendations from Well-Architected review for technical leadership

Engagement Flow

Engagement Path

Follows ADDIE + Cloud Adoption Framework: qualitative durations, scaled to your size & target vendor.

1

Training Needs Analysis & Adoption Position

Mapping primary vendors, roles, cloud adoption stage (greenfield/migration/scale), critical workloads, regulatory obligations, and measurement baseline. Output: needs profile + lab scope.

Initial stage
2

Program Design by Role (ADDIE)

Drafting measurable learning objectives, role-based syllabi (dev/ops/security/architect/executive), lab scenarios, and framework map to Well-Architected, FinOps, CIS.

Pre-delivery
3

Cloud Essentials Bootcamp

Core 3–5 day session: NIST 800-145 foundations, networking, IAM, compute, storage, observability, security & cost basics. Hands-on labs in sandbox accounts.

Core week
4

Well-Architected Review of Internal Workload

Team brings a real workload; facilitator guides a 6-pillar review, producing prioritized recommendations the team can execute themselves.

Post-bootcamp
5

Landing Zone & Guardrail Roll-out

Consultative workshop designing landing zone (accounts/subscriptions/projects, identity, network, logging, guardrails via SCP/Azure Policy/Org Policy) aligned to CAF.

Rolling per team
6

FinOps Cadence & Recurring Evaluation

Monthly/quarterly cadence: per-team/product cost review, rightsizing, savings plans, and Kirkpatrick L1–L4 evaluation (Phillips L5 on request). Institutionalize cloud discipline.

Recurring & continuous

Case Studies

Typical Outcome Patterns

Illustrative patterns based on similar program structures. No named clients or promised numbers. FinOps and Well-Architected practices reference FinOps Foundation and AWS/Azure/GCP as industry sources.

Financial institution with engineering teams across many digital products

Intervention

Cloud essentials bootcamp by role + landing zone workshop per CAF + initial FinOps session

Result

Uniform landing zone in place, baseline CIS Benchmarks posture applied, and FinOps started reporting to the board

Fast-growing technology company with early multi-cloud presence

Intervention

Well-Architected review per workload + IaC paved-road + SaaS FinOps

Result

Uniform patterns across engineering teams, per-unit cost declined, and new team onboarding accelerated

BUMN holding with many subsidiaries at varying cloud adoption

Intervention

Subsidiary CIO/CTO bootcamp + holding landing zone + FinOps dashboards across entities

Result

Consistent cloud governance patterns across subsidiaries and cloud spend reported to the holding

Procurement Info

Information for Procurement & Vendor Management

What procurement, finance, legal, and information security teams need.

Proposal

Structured proposal: measurable learning objectives, role-based syllabus, framework map (NIST SP 800-145 / AWS-Azure-GCP Well-Architected / CIS Benchmarks / FinOps Framework / Cloud Adoption Framework / UU PDP / POJK if relevant), facilitator profile, schedule, and TNA-based cost detail.

Pricing model

TNA-based: flat per program, per session, per participant, tiered, or custom. No standard numbers without needs analysis; estimates issued after TNA is agreed.

Payment & tax

Flexible terms (DP + balance / per-batch installments); tax invoice (PPN) and PO documentation supported.

BUMN/government procurement

Familiar with BUMN/government procurement: vendor documentation, e-procurement / SPSE, HPS/offers, and compliance clauses.

Measurement

Kirkpatrick L1–L3 evaluation reports (attendance, knowledge assessment, lab & Well-Architected review behaviors); Phillips ROI L5 on finance/risk request (FinOps savings estimates).

Confidentiality & data security

NDA signing, confidentiality of participant data & internal workloads brought into Well-Architected reviews, and practices aligned with UU PDP and your internal security policy.

Material ownership

Scenarios, landing zone references, and reports built for your company are yours; usage rights of training materials are agreed in the contract.

FAQ

Frequently Asked Questions

It depends on your contracts & strategy. For teams on AWS Enterprise Agreement, focusing on AWS Well-Architected 6 pillars is more efficient. For Microsoft EA + Entra ID-dominant teams, Azure Well-Architected + Azure landing zone CAF is more relevant. For data-heavy teams already on BigQuery, the Google Cloud Architecture Framework fits. For multi-cloud we map equivalent services and landing zone patterns across each vendor.

AWS Well-Architected is a 6-pillar framework (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability) that has become the standard vocabulary for cloud architecture trade-off discussions. Azure Well-Architected and Google Cloud Architecture Framework have equivalent structures. Used as a foundation because it provides a concrete checklist that every engineering team can apply for consistent workload reviews, replacing per-architect opinion.

Well-Architected Review evaluates 6 architecture pillars (not security alone) as input to technical decisions, producing prioritized recommendations engineering can execute themselves. Security audits typically assess compliance with specific controls (ISO 27001 / SOC 2) with control-fulfillment output. They coexist; Well-Architected is more frequent and lighter than a formal audit.

FinOps is a collaborative discipline among engineering, finance, and business to manage cloud spend accountably. The FinOps Foundation outlines 3 phases (Inform → Optimize → Operate) and 6 core principles. It matters because cloud cost is variable; without FinOps, monthly bills rise without per-team/product visibility and the CFO eventually blocks new cloud investment.

The module teaches mapping of shared responsibility to internal controls: data residency, classification, encryption, least-privilege IAM, audit log, incident-notification obligations, DPA contracts, and exit strategy. For banks we add mapping to POJK 11/POJK.03/2022 and SEOJK 29/SEOJK.03/2022, including OJK examination-readiness documentation.

The material aligns with entry-level certification competencies (e.g. AWS Certified Cloud Practitioner / Solutions Architect Associate, Microsoft AZ-900 / AZ-104, Google ACE). Our primary focus is enterprise application; single-test prep is a secondary outcome. Teams pursuing certification get a strong conceptual foundation plus official vendor certification path references.

Two options: (1) Neksus provides sandbox accounts with budget guardrails for labs (participants experiment freely without risk); (2) labs in your internal non-production account with limited scope and cost guardrails. Production accounts are not touched except during Well-Architected reviews of real workloads, which are read-only / documentation.

A 3–5 day bootcamp covers fundamentals + core labs per vendor. For deeper transformation, we recommend a 2–4 month phased program: bootcamp → Well-Architected review per workload → landing zone workshop → FinOps cadence. Final scope is set during TNA based on your cloud adoption position.

Yes. A dedicated module discusses single vs multi-cloud trade-offs: operational complexity, identity federation, inter-cloud networking, tooling fragmentation, vs benefits of resilience & vendor bargaining. Multi-cloud makes sense for specific scenarios (regulator residency, critical resilience, best-of-breed combinations like BigQuery + S3). For most enterprises, disciplined single-cloud is more sensible in the early stage.

We use Kirkpatrick: Level 1 (reaction), Level 2 (knowledge via assessment), Level 3 (behavior: lab practice, Well-Architected reviews, hardening), Level 4 (results: cloud cost reduction, resilience, delivery speed). When finance/risk requests monetary numbers, impact can be raised to Phillips ROI Level 5 with FinOps savings estimates and isolated training effect. Baseline is set during TNA.

How many cloud providers are covered moves first, since taking apart one provider is a narrower scope than taking apart all three at once. Participant seniority follows, because operations teams, engineers, and architects need different depth. The lab environment counts as well, since hands-on cloud work requires accounts, quota, and permissions arranged in advance. Headcount, the number of cohorts, how often the class meets, sessions held at your office or online, and the host city round out the total. We share the figure once a no-cost training needs analysis is over.

This lab seats 10 to 25 participants, and twenty-odd people make a single cohort, and four full days already covers theory alongside lab work. What often shifts the schedule is lab preparation: accounts, quota, and permissions inside your environment have to be ready before day one. If your team is genuinely mid-migration, those four days normally open the work, followed by landing zone design sessions in the weeks after.

They can. A cloud class easily feels too fast or too slow depending on where participants start. Speak with the programme coordinator, and a fresh validated cloud trainer takes the remaining days. Lab modules, practice environment configuration, and class progress notes are saved in our operations system, so that the lab never has to be built from scratch again.

Next Step

Discuss your team's cloud adoption plan

We map vendors, roles, cloud adoption stage, and your regulatory obligations, then build a proposal and budget based on real needs.

  • Proposal, role-based syllabus, and framework map (Well-Architected / FinOps / CAF / CIS)
  • Labs in sandbox accounts with budget guardrails; internal workload review option
  • Procurement-ready documents (company profile, NPWP, NDA, PPN tax invoice)
Request a ProposalFree Consultation

Explore More

Related Topics

Pelatihan Docker Dan KubernetesPelatihan Devsecops FoundationsPelatihan Mlops Production Ai EngineeringKeamanan Siber Kesadaran KaryawanTransformasi Digital Eksekutif

Cloud Basics for IT Teams training for your Banking & Financial Services team

We map vendors, roles, cloud adoption stage, and your regulatory obligations, then build a proposal and budget based on real needs.

  • Proposal, role-based syllabus, and framework map (Well-Architected / FinOps / CAF / CIS)
  • Labs in sandbox accounts with budget guardrails; internal workload review option
  • Procurement-ready documents (company profile, NPWP, NDA, PPN tax invoice)

Six fields to get started. Our corporate team reads and answers it.

Additional details (optional)

Add these if you already know them. Every field in this section can be left empty, and our team will cover them during the needs-analysis call.