Season 4: One Company, Two Clouds · Episode 5 of 8
Meet SignalNest
You play: AI Engineering Intern
Included with Core programme and Certification prep
The situation
Code Nexus has acquired SignalNest, a five-person startup that does search and auto-captioning. Their entire stack runs on AWS. Amara has the integration and has pulled you in for the first pass: understand what SignalNest actually has, and propose where the boundary between the two companies' systems should sit — before anyone starts moving things.
What you'll learn
- CLF-C02 cloud concepts and technology: the value of cloud (agility, not rewriting what works), comparing provider terminology without assuming equivalence, AWS global infrastructure (regions, availability zones, edge locations), migration as a deliberate decision, integration boundaries, and Well-Architected thinking.
- The six Well-Architected pillars and how to tell them apart; the AWS Cloud Adoption Framework perspectives and business outcomes; the seven migration strategies (the 7 Rs); and the basics of cloud economics: fixed versus variable cost, economies of scale, rightsizing, automation and BYOL.
Who you work with
Priya Naidoo
Cloud Architect
Amara Okafor
ML and Data Engineer
Scenes
- 1.We bought a company
- 2.Same idea, different service
- 3.What SignalNest actually has
- 4.Which pillar is this?
- 5.Where the seam goes
- 6.Cloud concepts check
What you leave with
SignalNest's stack is read as a four-category inventory rather than a pile of AWS names, the mapping table is treated as orientation not gospel, and the integration note recommends a clean boundary: Code Nexus Search keeps running on AWS under the SignalNest team, captions exposed to Code Nexus through a documented API over a private link, migration deferred to a real decision. 8-BIT's shared-credentials plan was rejected.