AWS Developer Associate Readiness: Build Serverless and Container Apps on AWS
Signature Course No. 413 — A Signature AI Socratic Coaching Course.
No experience needed — your coach starts where you are.
A New Kind of Learning
Socratic coaching, delivered by an agentic AI coach.
Not a course you watch. An AI coach you work with.
The Lighthouse Coach begins by discovering how you think about the subject, teaches what is missing, and gives you realistic practice before asking you to prove that you can use it. You may test out of concepts you already understand, while capstones turn the learning into a practical plan, decision, conversation, or other real-world result.
The curriculum is deliberately authored; the AI delivers it through coaching. It is not an AI randomly generating lessons.
A coach that teaches by asking — not by lecturing
The Lighthouse Coach is an AI Socratic coach built on Cognosco Learning's AWS Developer Associate Readiness: Build Serverless and Container Apps on AWS course, in the Personal Effectiveness & Well-Being category. It does not play videos at you. It holds a conversation: it asks you a question, listens to your answer, names the misconception it hears, affirms what you got right, and asks the next question — the way a great coach works in the room.
Readiness, honestly judged — never a guaranteed result. This course promises readiness, never a pass. It teaches to the published AWS Certified Developer — Associate (DVA) skills outline at the level that outline is published — the task statements and the services they name — and it flags that outline as a document Amazon Web Services revises, which you must verify in its current form before you book. No page claims to know actual exam questions, and no score in this course guarantees an outcome in a testing center. What the capstones certify is the narrower, more useful thing a course honestly can: that you have worked every concept on fresh problems, defended each decision from a deciding fact, and learned to judge your own readiness from evidence.
It starts with the deciding fact. Meet Kinvara Field Services, the running company whose booking application this course builds, ships, and debugs end to end. Almost every hard question — on paper or in production — presents a small situation and four plausible moves, of which one is governed by a fact the situation quietly contains: a timeout, a key, a trigger, a permission, a bill. The skill is not recognizing service names. The skill is finding the deciding fact and letting it choose the move — name it first, in writing, before you name a service.
It works in two movements. First, Module 1 — Build and Connect: The Developer Seat on AWS — work through Concepts 1–9, finishing with The Booking Feature, Built Whole; then, Module 2 — Ship, Secure, and Observe — work through Concepts 10–18, finishing with Ship the Release, Then Prove It in Production.
Both capstones produce real artifacts — a build plan for Kinvara's first customer-facing feature, complete enough that another developer could build from it and a reviewer could examine it: the invocations mapped, the data designed from its access patterns, the door disciplined, the identities least-privilege, and the failure paths confessed in advance; and a ship-and-observe plan for taking that feature to production — the release design, the identity and data-protection decisions, and the debugging method, written completely enough that an on-call developer who has never met you could run the release and work its first incident from your document alone.
The honesty standard is part of the course. This is the developer's seat on AWS, and only that seat. No. 242, AWS Cloud Practitioner, is entry-level orientation, and this course assumes it — or equivalent experience — without repeating it. No. 340, AWS Solutions Architect in Practice, designs whole systems from the architect's seat; this course does not sit in that seat either. The developer's questions are narrower and, in their own way, harder: I have code — how does it run, what invokes it, what does it read and write, how do I ship a new version safely, how do I know what it did at 2 a.m., and how do I prove all of that under exam conditions? And because cloud platforms change their consoles, tools, and defaults constantly, the course teaches at workflow level only — the durable pattern that survives a console redesign.
The course is self-paced and always on — roughly 30 minutes per concept, about 9 hours in full, taken in as many sittings as you like. You can type your answers, or talk out loud: the Voice Coach speaks its questions and listens to your spoken replies. Learners who already know the material can test out concept by concept.
AWS Developer Associate Readiness: Build Serverless and Container Apps on AWS is part of The Lighthouse Signature Series — the online counterpart to the one-day, in-person learning Cognosco Learning has delivered since 2002.
Course Facts
One full concept, coached end to end — free: verify your email and we’ll send you a link to start.
Already enrolled? Enter the course →
Diagnose → Learn & Practice → Prove → Capstone
Every learner moves through the same discipline a Cognosco instructor would insist on in the room.
Diagnose
The Coach starts where the course starts: with the developer seat. Think of the last AWS problem you actually solved and say whether you solved it by recognizing a service, or by finding a deciding fact — and name that fact in one sentence; say which seat you default to under pressure, the architect's redesign or the developer's fix to this invocation, key, or deployment, with one example; and name the domain of the published outline you would least want your score to rest on, with the evidence, not the feeling, that tells you so. Every concept opens with three questions that locate where you actually stand, and your answers shape how deeply the Coach works the concept with you. Everyone begins with Module 1 — no skipping the foundations you only think you have.
Learn & Practice
Work each concept in conversation with the Coach — spoken or written — then practice it against realistic situations until it holds up.
Prove
Every concept ends in proof: answer the check cold and demonstrate the skill. Know it already? Test out and take credit immediately.
Capstone
Finish with two capstones — The Booking Feature, Built Whole for Module 1 and Ship the Release, Then Prove It in Production for Module 2 — that pull the whole course together, and earn the certificate.
What You'll Learn
Find the deciding fact, then let it choose the move. Every skill in this course is the same discipline at a different depth: read the situation for the constraint it quietly contains — a timeout, a key, a trigger, a permission, a bill — name it in writing, and only then choose the service, the shape, or the release. Judgment first, vocabulary second, in the exam's own order.
Module 1 builds and connects. The Developer Seat; Lambda's Execution Model; API Gateway, the Front Door; DynamoDB Design Judgment; S3 From the Developer's Seat; Events, Queues, and Streams; Containers as a Developer Pattern; IAM for Applications; and Configuration and Secrets — the code run, invoked, fed, and identified: functions and containers, the door, the data stores, the middlemen, and roles instead of keys.
Module 2 ships, secures, and observes it. The Deployment Pipeline; Infrastructure as Code, at Workflow Level; Application Identity; Workflow Orchestration and Idempotency; Caching and Performance; CloudWatch; X-Ray and the Debugging Method; Protecting Data in Code; and Refactoring and Readiness — the release made a discipline, the users given an identity, the running system made visible, and readiness itself judged from evidence.
And it holds its boundary throughout. Entry-level cloud orientation — what the cloud is, what the major services are called, how billing and support work — is taught in its own neighboring course, No. 242, AWS Cloud Practitioner, whose orientation this course assumes; whole-system architecture lives in No. 340, AWS Solutions Architect in Practice. This course is the developer's seat alone: invocations, items, keys, and releases, at the depth the published outline examines them.
What you will learn
- Reason from the published Developer Associate outline: name what the developer's seat owns, and answer scenario questions by the deciding move, not by recognition
- Build on Lambda correctly: its execution model, its limits, its concurrency behavior, and the code habits those facts demand
- Put an application behind API Gateway and design DynamoDB access and S3 use from the developer's seat
- Decouple an application with events, queues, and streams, and choose containers on ECS and Fargate when a function is the wrong home
- Give every workload an IAM role, keep secrets and configuration out of code, and give end users an identity with Cognito
- Ship safely: pipelines, infrastructure as code at workflow level, staged releases, and a planned rollback
- Orchestrate multi-step work, cache what is expensive, and debug a running application with logs, metrics, and traces
- Refactor a legacy application toward managed services in stages, and diagnose your own readiness honestly before you book
Everything in the course
- All 18 concepts of AWS Developer Associate Readiness: Build Serverless and Container Apps on AWS, in 2 modules
- A starting-point check first — the Coach finds where you actually stand before teaching
- Learn, Practice, Prove for every concept — no passive video watching
- A test-out on every concept: prove you know it and move on
- The Voice Coach: talk with the Coach out loud — it speaks, listens, and replies
- A personal Learner Record of your work across the course
- Two capstone exercises: The Booking Feature, Built Whole and Ship the Release, Then Prove It in Production
- A printable session summary whenever you pause
- The Lighthouse Coach completion certificate (Signature Series)
- Your progress is saved as you go — stop anytime, resume where you left off
Built for developers who hold the Associate seat
Working developers — who build or maintain applications that run, or will run, on AWS and want the credential that certifies the developer's seat, not the architect's; and backend and full-stack engineers whose daily work is functions, APIs, queues, and data stores, and who need the exam's judgment, not just the platform's vocabulary.
Platform-adjacent engineers — who ship through pipelines they did not design and want to understand, and be examined on, what those pipelines are doing.
Career movers with code in hand — who have the assumed orientation below and are aiming at a first cloud developer role. This course assumes 242-level orientation or equivalent experience: you know what a region is, you can name the major compute, storage, and database services, and you have written code in at least one language an AWS SDK supports. It does not re-teach programming, and it does not re-teach cloud orientation.
Prefer to learn live and in person? The same material anchors Cognosco's one-day programs — browse the in-person catalog.
Start with The Developer Seat
$195 — introductory price. One payment. No subscription, no password to manage.
Here is exactly what happens when you enroll:
- Pay securely with Stripe — you are taken straight into the course
- Create your learner profile and begin the Module 1 starting-point check
- Save the access key you are given — it restores your enrollment on any device
- Learn at your pace; your progress is stored in your browser on your device
For the full voice experience, use Chrome and allow the microphone when asked. Typing your answers works everywhere, all the time. Questions before you enroll? Email hello@cognoscolearning.com.
Before you enroll
What is a Socratic coaching session?
A conversation, not a video. Your coach asks a question; you answer — out loud by voice, or by typing — and the coach responds to what you said: naming the misconception it hears, affirming what you got right, and asking the next question. You advance only when you have mastered each concept, so a finished course means the learning held.
How long does it take — and how long do I have?
About 30 minutes per concept. Learn in sittings of any length; your progress is saved as you go. You have a full year from purchase to finish, and you can revisit and retake within that year.
What does the certificate verify?
That you completed every concept and both capstones of this course. Anyone can confirm a Cognosco certificate online — enter its certificate ID on our verification page.
What if it isn't for me — what are the refunds?
If you have not started, cancel for a full refund within seven days of purchase. Once you have started, there is no cash refund — stop before finishing and we credit the full amount you paid toward any other course in the library (credit valid one year from your original purchase). Once you complete the course, no refund or credit applies.
More Signature Courses are coming
AWS Developer Associate Readiness: Build Serverless and Container Apps on AWS is Signature Course No. 413. Leave your email and we'll send you news of future Signature Courses and Lighthouse updates as they are announced — nothing else.