Camp Fire Academy
Learning path
Complete UI/UX Masterclass UI/UX Design Foundations UI/UX Design Intermediate Advanced UX Strategy
Specialisations
Fintech & Banking UI/UX UI/UX with AI Training UX for Leaders Design Thinking Figma Training
Most requested
AI for Workplace Productivity Excel for Business Power BI & Business Intelligence Cybersecurity Awareness PDPA Compliance Data Protection Officer Browse the full catalogue →
For teams
Corporate & In-House Training LMS & Self-Paced Learning Events
Company
About Contact Verify Certificate WhatsApp

Cloud Engineering Foundations (AWS and Azure)

Two days of building rather than watching. Participants stand up a working application environment from an empty account: network, compute, storage, identity, monitoring and backup, then tear it down again without leaving orphaned resources running up a bill. The intent is not to cover every service but to give you the shape of a competent deployment, so the next one you do at work is structured rather than assembled by following a tutorial.

Programme Agenda

Account Structure and Guardrails

Organisations and subscriptions, environment separation, and the guardrails worth setting on day one: budget alerts, region restriction, and blocking public access to storage by default.

Identity and Access

Roles, policies and least privilege in practice. Why long-lived access keys are the wrong answer, instance and workload identity, and the access review that prevents accumulation.

Designing the Network

Virtual network and subnet layout, public and private separation, routing, network address translation, and security group rules that are specific rather than permissive. Building it before deploying anything into it.

Deploying the Workload

Standing up compute, attaching storage, connecting to a managed database, and putting a load balancer in front. Health checks, and what happens when one instance fails.

Scaling and Availability

Auto scaling groups and scale sets, spreading across availability zones, and the difference between a design that survives an instance failure and one that survives a zone failure.

Monitoring, Logging and Alerting

Metrics, logs and traces, retention decisions, and alerts that fire on something actionable. Setting up the dashboard you would actually look at during an incident.

Backup, Recovery and Cost

Snapshot and backup policies, recovery testing, and the archival tier decision. Tagging for cost allocation, and finding the resources nobody remembers creating.

Decommissioning and Review

Tearing the environment down completely, verifying nothing is left running, and reviewing the build against a checklist participants take away.

Learning Outcomes:
Set up account structure and guardrails before any workload is deployed
Apply least privilege identity without falling back on long-lived keys
Design and build a network with proper public and private separation
Deploy a load-balanced workload with storage and a managed database
Configure scaling and multi-zone availability appropriately
Set up monitoring and alerting that supports an actual incident response
Establish backup policies and test a recovery
Decommission an environment cleanly with no orphaned cost

Duration: 2 Days (16 Hours)
Training Hours: 9:00 AM to 5:00 PM
Level: Beginner
Training Mode: Physical, Online, or Hybrid
HRD Corp SBL-KHAS Claimable
Certificate of Completion included

Frequently Asked Questions

System administrators, developers, IT engineers and technical leads who need to build and run workloads on cloud infrastructure. Some of the participants come from on-premises server administration backgrounds.

Comfort with a command line, basic networking concepts such as IP addressing and ports, and familiarity with either Linux or Windows server administration. Cloud experience is not assumed.

The programme is delivered on one platform per session, chosen with the client. Public sessions alternate. The concepts transfer, and the material notes where the two platforms differ meaningfully.

Training accounts are provided with the necessary permissions and a spend cap. For in-house delivery we can run in your own environment if you prefer, subject to your access approvals.

Yes, this programme is HRD Corp SBL-KHAS claimable. Our team can assist your HR department with the documentation required for the grant application.

Yes. Any programme can be booked as a team day. Everyone works the same brief together, so your people come away having built something and knowing each other better.

If you are claiming under HRD Corp, the session has to fall at least 14 days after your HRD Corp approval. If you are not claiming, the date is flexible and we work around your calendar.

Put them on the self-paced e-learning instead. Your team works through the modules on our LMS in their own time, sits the assessment, and earns the same certificate, so nobody has to clear a full day together.

More in Cloud, DevOps and Platform Engineering