Season 4: One Company, Two Clouds · Episode 6 of 8
The Other Cloud Console
You play: AI Engineering Intern
Included with Core programme and Certification prep
The situation
The fictional integration keeps Code Nexus Search on AWS. Review SignalNest’s supplied caption-pipeline failures and assemble its represented upload-to-function-to-store/consumer route in the provider-neutral cloud simulator. Then state what a real AWS delivery check still requires.
What you'll learn
- CLF-C02 technology and services: AWS compute (EC2, Lambda, containers), object storage and storage classes (S3), databases (RDS relational, DynamoDB key-value), networking (VPC, DNS, CDN), load distribution, event-driven routes, and distinguishing managed services from learner-owned responsibilities.
- Choosing among EC2, Lambda, Fargate, ECS/EKS, RDS/Aurora, DynamoDB and ElastiCache; recognising the rest of the AWS menu (networking, storage options, messaging, analytics, AI/ML, monitoring and developer tools); and the ways to provision on AWS (console, CLI, SDKs, CloudFormation) plus Local Zones, Wavelength and Outposts.
Who you work with
Priya Naidoo
Cloud Architect
Kabelo Mokoena
Platform and DevOps Engineer
Scenes
- 1.It drops events under load
- 2.Right service for the job
- 3.Wire the route
- 4.Compute and databases, round two
- 5.Networking, storage, analytics, AI and the rest
- 6.Latency, cost, and who patches the OS
- 7.AWS technology check
What you leave with
You assembled the caption route in the simulated console and chose services for the supplied workload. The recommendation evaluates key-value access, media lifecycle transitions and a managed runtime. Real deployment still needs provider-specific permissions, retries, duplicate handling and delivery evidence.