Corporate Cloud Foundation (AWS / Azure / GCP Essentials) for the Healthcare & Pharmaceuticals Sector
Hospitals and health networks modernize SIMRS, BPJS integration hubs, and clinical analytics in the cloud. Patient data is classified as specific personal data under UU PDP, requiring stricter controls. Hospital IT teams need cloud basics, hybrid patterns (on-prem medical devices + cloud), and cost discipline because clinical analytics can become large.
- format
- In-house / online / hybrid
- duration
- 3–5 intensive days or 2–4 month phased program
- participants
- 10–25 per cohort
- language
- Indonesian / English
Why Corporate Cloud Foundation (AWS / Azure / GCP Essentials) is different in Healthcare & Pharmaceuticals
Hospitals and health networks modernize SIMRS, BPJS integration hubs, and clinical analytics in the cloud. Patient data is classified as specific personal data under UU PDP, requiring stricter controls. Hospital IT teams need cloud basics, hybrid patterns (on-prem medical devices + cloud), and cost discipline because clinical analytics can become large.
- Hospital IT training coverageNearly all hospital IT staff
- Patient data breaches in cloud environmentZero in the next period
- Information governance evidence for KARS accreditationComplete at accreditation/reaccreditation
- UU No. 17/2023 Health Law
- UU PDP No. 27/2022 — health data = specific personal data
- KARS Hospital Accreditation Standards — information governance
- PMK on SIMRS and electronic medical records
- ISO/IEC 27001:2022 + ISO 27799 information security in healthcare
- CIS AWS / Azure / GCP Benchmarks
- Hospital Director / Vice Director of Services
- Head of SIMRS / Hospital IT
- Medical Records Manager
- Quality & Patient Safety Committee
- Head of HR / Hospital Training
- Head of Hospital Finance
- Hospital IT teams master cloud basics relevant to SIMRS and clinical analytics
- Patient-data classification & protection documented across cloud controls
- Hybrid patterns (medical devices + cloud) designed with clear security boundaries
- FinOps discipline in place for clinical analytics & medical record archives
- Information governance evidence ready for KARS accreditation
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.
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).
Cloud Foundation (AWS / Azure / GCP Essentials)
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.
Measurable Outcomes
Expected Outcomes
Indicators mapped to Kirkpatrick levels and Well-Architected pillars — qualitative targets, set jointly during TNA against your baseline.
- Cloud concept mastery (Kirkpatrick L2 — Learning)
- Most participants pass knowledge assessment on service models (IaaS/PaaS/SaaS per NIST 800-145), VPC/VNet networking, IAM, and storage tiers
- Well-Architected practice (L3 — Behavior)
- Participants complete a Well-Architected review on one internal workload across 6 pillars (Operational Excellence, Security, Reliability, Performance, Cost, Sustainability)
- Baseline hardening (L3 — Behavior)
- Baseline guardrails confirmed (root account protection, MFA, CIS Benchmarks baseline, encryption-at-rest enabled) on lab accounts
- Cost discipline (FinOps Inform phase)
- Tagging strategy, budgets, and per-team/product cost dashboards defined; participants can read cost & usage reports
- Landing zone readiness (CAF)
- Team has a draft landing zone (account/subscription/project structure, identity, network, logging) aligned to the Cloud Adoption Framework
- Monetized ROI (Phillips L5 — optional)
- Estimated savings from rightsizing, savings plans, and idle-resource elimination, with isolated training effect when finance requests numbers
Program Format
Program Format Options
Chosen by your cloud-adoption stage — finalized after TNA.
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.
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.
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.
Recurring FinOps Enablement
Recurring program (monthly/quarterly): reading cost & usage reports, rightsizing sessions, savings plan/commitments review, and a cross-team FinOps cadence.
Free Consultation
Discuss your team's cloud adoption plan
Start with a free training needs analysis: we map vendors, roles, cloud adoption stage, and your regulatory obligations, then build a proposal and budget based on real needs.
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.
Comparison
Choosing Vendor & Training Format
Concise decision matrix — final recommendation set after training needs analysis.
| Aspect | Cloud Essentials Bootcamp | Well-Architected Review Workshop | Landing Zone & Guardrail Design | Recurring FinOps Enablement |
|---|---|---|---|---|
| Primary goal | Build concept foundation + labs | Mature an existing workload | Standardize accounts & guardrails | Cost discipline & accountability |
| Ideal participants | Teams new to / expanding cloud | Teams already running, need review | Pre-migration or multi-team | Cloud spend already significant |
| Typical duration | 3–5 intensive days | 2–3 day workshop | 1–2 week consulting | Monthly / quarterly |
| Main output | Concept mastery + certificate | Prioritized 6-pillar recommendations | Landing zone reference + guardrails | Tagging, dashboard, FinOps cadence |
| Core framework used | NIST 800-145 + Well-Architected basics | Full Well-Architected 6 pillars | Cloud Adoption Framework + CIS | FinOps 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.
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.
See in Banking & Financial Services context →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 →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 →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 →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 →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.
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.
Engagement Flow
Engagement Path
Follows ADDIE + Cloud Adoption Framework — qualitative durations, scaled to your size & target vendor.
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 stageProgram 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-deliveryCloud 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 weekWell-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-bootcampLanding 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 teamFinOps 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 & continuousCase 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.
Indonesian PT under the Selestia ecosystem (Eduprima group); complete NPWP & legal documents; ready for PKS/contracts and vendor onboarding.
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.
TNA-based — flat per program, per session, per participant, tiered, or custom. No standard numbers without needs analysis; estimates issued after TNA is agreed.
Flexible terms (DP + balance / per-batch installments); tax invoice (PPN) and PO documentation supported.
Familiar with BUMN/government procurement: vendor documentation, e-procurement / SPSE, HPS/offers, and compliance clauses.
Kirkpatrick L1–L3 evaluation reports (attendance, knowledge assessment, lab & Well-Architected review behaviors); Phillips ROI L5 on finance/risk request (FinOps savings estimates).
NDA signing, confidentiality of participant data & internal workloads brought into Well-Architected reviews, and practices aligned with UU PDP and your internal security policy.
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
Next Step
Discuss your team's cloud adoption plan
Start with a free training needs analysis: we map vendors, roles, cloud adoption stage, and your regulatory obligations, then build a proposal and budget based on real needs.
- Training needs analysis at no cost — the natural first step
- Proposal, role-based syllabus, and framework map (Well-Architected / FinOps / CAF / CIS) within a few business days
- Labs in sandbox accounts with budget guardrails; internal workload review option
- Procurement-ready documents (company profile, NPWP, NDA, PPN tax invoice)
Corporate Cloud Foundation (AWS / Azure / GCP Essentials) training for your Healthcare & Pharmaceuticals team
Start with a free training needs analysis: we map vendors, roles, cloud adoption stage, and your regulatory obligations, then build a proposal and budget based on real needs.
- Training needs analysis at no cost — the natural first step
- Proposal, role-based syllabus, and framework map (Well-Architected / FinOps / CAF / CIS) within a few business days
- Labs in sandbox accounts with budget guardrails; internal workload review option
- Procurement-ready documents (company profile, NPWP, NDA, PPN tax invoice)