The week before your AWS exam: a final checklist
In the last week before an AWS exam you should stop learning new material and switch to consolidation — full-length timed mocks, targeted review of your weak domains, and sorting out the practical logistics before they can become exam-morning surprises. The final seven days are not for becoming a better candidate; they are for making sure the candidate you already are performs at full strength. That reframing matters, because the instinct under pre-exam nerves is to do the opposite: cram new services, start one more course, and stay up late — all of which trade calm, consolidated knowledge for a thin layer of anxiety-driven trivia. This guide lays out how to spend the week: what to review, what to deliberately leave alone, which logistics to confirm days in advance, and how to arrive at the exam rested rather than depleted. (What the exam day itself is like — check-in, proctoring, ID rules — is covered in our exam-day guide; this is about the seven days before it.)
The strategic shift: from acquisition to consolidation
By the final week, the syllabus you know is essentially the syllabus you will sit with. Genuinely new material learned days before an exam is the most fragile knowledge you hold — unconnected to anything, unrehearsed under exam conditions, and most likely to dissolve under pressure. Worse, cramming new services costs the time and rest that would have strengthened the large body of things you already half-know, which is where the real marks are.
So the week has a different job: converting “I have seen this” into “I can answer this under a clock”. That means retrieval, not input — timed questions, mock exams, and reviewing your own past mistakes rather than watching more videos. If a mock reveals a small, well-defined gap, close it; that is repair, not acquisition. What you should not do is open a new course, a new book, or a new domain. The syllabus is closed. The week is for sharpening.
A shape for the seven days
You do not need a rigid hour-by-hour plan, but the week has a natural order — heavy work early, logistics in the middle, and a deliberate wind-down at the end:
- Days 7–6: sit a full-length timed mock under real conditions. Score it, then spend more time reviewing it than you spent sitting it — every wrong answer and every lucky guess.
- Days 5–4: targeted review of the weak domains the mock exposed, weighted by how much of the exam each domain carries. Re-drill those areas with fresh practice questions.
- Day 4: confirm the logistics — ID, booking details, and (if testing online) the OnVUE system check on the actual machine and network you will use.
- Days 3–2: a second full-length timed mock. If the score is comfortably above the pass mark, you have your evidence; review it, then ease off. If it is not, this is the moment to consider rescheduling rather than hoping.
- Day 1 (the day before): light review only — your error log and key comparisons, an hour or two at most. No mocks, no new questions after midday, and an early night.
What to review: weak domains, your error log, and key comparisons
Review time is scarce, so spend it where marks are. Start with your weakest domains, but weight them by the exam blueprint — a shaky performance in a heavily weighted domain matters far more than the same wobble in a small one, and the official exam guide tells you exactly what each domain carries. Fresh practice questions in those domains, with careful reading of the explanations, beat re-reading notes you have already read.
Second, your error log — the record of every practice question you have got wrong and why. In the final week this document is worth more than any course, because it is a syllabus of your specific weaknesses. Re-attempt those questions cold and see which mistakes have actually been fixed. Third, the classic comparison pairs: the storage options against each other, the database options against each other, the places where two services overlap and the exam loves to make you choose. Those side-by-side distinctions are dense in marks and cheap to refresh — a one-page comparison sheet you rewrite from memory is an excellent final-week exercise.
What not to do in the final week
The discipline of the week is as much about what you refuse to do. Do not start a new course, book, or video series — new input this late displaces consolidation and feeds anxiety rather than competence. Do not pull all-night study sessions; the marginal facts gained are worth less than the reasoning speed lost, and sleep is when the week’s consolidation actually settles. Do not spend the week re-sitting the same mock until the score flatters you — a repeated mock measures memory of the mock, not readiness.
And do not let your first-ever full-length mock happen two days before the exam. If timed mocks are new to you at that point, the first one usually delivers a bruising score for reasons of pacing rather than knowledge — which is useful feedback a month out and pure panic fuel two days out. If you are in that situation, sit one anyway, but read the result as a pacing diagnosis, not a verdict, and be honest with yourself about whether rescheduling is the wiser move. The fourteen-day retake wait and a second fee cost more than moving a booking.
Logistics to confirm days in advance, not on the morning
Almost every exam-morning disaster is a logistics failure that was checkable a week earlier. Confirm that the name on your booking exactly matches the name on the government-issued photo ID you will present — a mismatch is one of the few things that can stop an exam before it starts, and fixing it takes longer than a morning. Re-read your confirmation email for the exact date, time, and time zone.
If you are testing online, run the OnVUE system check now, on the actual computer and the actual network you will use on the day — not a work laptop that might have restrictive software, and not a different room. Then plan the room itself: private, clearable desk, a door that closes, and household members warned that nobody can come in. If you are testing at a centre, do the equivalent: know the route, the travel time with margin, and where you will park or which entrance to use. Either way, the goal is an exam morning with no unknowns in it.
The night before: rest is preparation
The strongest thing you can do in the final twenty-four hours is arrive rested. A full night’s sleep improves the exact faculties the exam taxes — careful reading, working memory, and judgement between close options — more than any facts you could cram in the same hours. Close the books by early evening, do something unrelated to AWS, and go to bed at your normal time or earlier. A short glance at your one-page comparison sheet over breakfast is fine; a frantic morning re-read of a whole domain is not, and mostly serves to spike nerves.
By this point the week has done its work: two mocks sat and reviewed, weak domains re-drilled, your error log retired, logistics confirmed, and a rested head. Whatever happens in the room, you will be sitting the exam you prepared for — which is all a final week can honestly promise, and it turns out to be enough for most well-prepared candidates.
Original practice questions, timed mock exams and revision notes. No card, nothing to pay.