Spaced Repetition for AWS Exams: A 6-Week Flashcard Plan
Quick answer: Turn every AWS fact you miss or hesitate on into a short scenario flashcard, and review it in a free app like Anki that pushes each card further out as you get it right. Add 10 to 20 new cards a day, review 15 to 25 minutes daily, and let practice-exam mistakes feed the deck.↗ Share on X
Spaced repetition works for AWS certification because most of the exam is recall under pressure: which service fits which job, what the limits are, and which option is cheapest or most resilient. You turn each fact you keep forgetting into a small flashcard, review it just before you would forget it, and push the review further out every time you get it right. Fifteen to twenty-five minutes a day of card review, next to your normal course and practice tests, is usually enough to stop the "I read this last week and it is gone" problem.
Below is the exact setup: what to put on cards, what to leave off, how many new cards per day, and a six-week plan you can copy.
What is spaced repetition, in plain words?
Pick the Right English Tense for Daily Life Easily →
No IT Experience? How to Pick Your First Cloud Cert →
How to Pass the PMP Exam: A Clear Step-by-Step Guide →Your brain drops new facts fast unless you pull them back out. Spaced repetition is a schedule for pulling them back out.
- You see a card today.
- If you remember it, you see it again in a few days.
- If you remember it again, the gap grows to a week, then two weeks, then a month.
- If you forget it, the card goes back to the start and you see it again soon.
The key word is pull. Reading your notes again feels productive, but it is recognition, not recall. The exam does not show you your notes. It shows you a scenario and four answers that all sound reasonable. Cards force you to produce the answer from memory, which is the same skill the exam tests.
You do not need to track the gaps yourself. Free apps do it:
| Tool | Cost | Good for |
|---|---|---|
| Anki | Free on computer and Android, paid app on iPhone | Full control, big decks, custom card types |
| RemNote | Free plan available | Notes and cards in the same place |
| Quizlet | Free plan, paid extras | Quick start, less control over the schedule |
| Paper cards (Leitner boxes) | Almost free | People who study better away from screens |
Anki is the most common choice for tech certifications because you can tune it and it works offline. The rest of this article uses Anki words, but the method is the same in any tool.
Level up — free guides in your inbox
Which AWS facts belong on a flashcard?
This is where most people go wrong. They copy the whole course into cards, end up with a mountain of cards, and quit in week two.
A fact belongs on a card if it passes all three tests:
1. You already understand it. Cards are for keeping knowledge, not for learning it the first time. If you do not understand how a VPC route table works, watch the lesson or build it in the console first.
2. You got it wrong or hesitated. Take a practice test or a quiz at the end of each module. Every question you miss or guess becomes a card source.
3. It is short and has one answer. If the answer needs a paragraph, split it.
Good sources for cards, in order:
1. Questions you missed on practice exams.
2. Service pairs that look alike (these cause a lot of wrong answers).
3. Numbers and limits the exam likes to test.
4. "Which service for this job" matches.
What look-alike pairs should you drill first?
These are the classic traps. Make one card per pair, and one card per side:
| Pair | The question to put on the card |
|---|---|
| Security Group vs Network ACL | Which one is stateful? Which one works at the subnet level? |
| S3 Standard-IA vs S3 One Zone-IA | Which one survives the loss of an Availability Zone? |
| SQS vs SNS | Which one holds messages until a consumer pulls them, which one pushes to many subscribers? |
| CloudWatch vs CloudTrail | Which one records who made an API call? |
| EBS vs EFS vs Instance Store | Which one can many instances share at once? Which one loses data when the instance stops? |
| RDS Multi-AZ vs Read Replica | Which one is mainly for failover, which one is for read scaling? |
| NAT Gateway vs Internet Gateway | Which one lets private subnets reach out without being reachable from outside? |
| Cognito User Pool vs Identity Pool | Which one signs users in, which one hands out AWS credentials? |
If you only make cards from this table and your missed questions, you will already have a sharper deck than most people who copy a full course.
How do you write a card that actually sticks?
Cloud Cert Notes: Cut Them to 1 Page per Domain Before Exam →
Study for AWS or PMP Without Burning Out: A Weekly Plan →
PMP Exam Study Plan: 10 Weeks From Application to Pass →Bad card:
Front: S3 storage classes
Back: Standard, Intelligent-Tiering, Standard-IA, One Zone-IA, Glacier Instant Retrieval, Glacier Flexible Retrieval, Glacier Deep Archive...
You will "sort of" remember this and mark it correct. That is a lie to the app, and the app schedules based on your answers.
Good cards (same topic, split up):
Front: Data is rarely read, must come back in milliseconds when it is, and must survive an AZ failure. Which S3 class?
Back: S3 Standard-IA (or Glacier Instant Retrieval for very rare access).
Front: Cheapest S3 class for data you may read once a year and can wait hours for?
Back: S3 Glacier Deep Archive.
Rules that keep cards useful:
1. One question, one answer. No lists longer than three items.
2. Write the front as a scenario when you can. The exam is scenario-based, so train the same way.
3. Add the "why" on the back in one line. Example: "Stateful = return traffic is allowed automatically."
4. Use cloze cards for keywords. In Anki, a cloze card hides one word: "Security Groups are {{c1::stateful}}; NACLs are {{c2::stateless}}." One sentence becomes two cards.
5. Put a tag on every card with the exam domain (for example, `security`, `resilient`, `cost`). Later you can study only your weak domain.
How many new cards per day, and how long does it take?
The number people get wrong is new cards per day. Each new card creates future reviews. Add too many and a month later you face a wall of reviews every morning.
A setting that works well for people who study around a full-time job:
| Setting | Suggested value | Why |
|---|---|---|
| New cards per day | 10 to 20 | Keeps daily reviews short |
| Maximum reviews per day | 200 (or no limit) | Never let reviews pile up hidden |
| Learning steps | 10 minutes, 1 day | Short first check, then next day |
| Session length | 15 to 25 minutes | Short enough to do every single day |
Daily consistency beats long sessions. Doing 20 minutes seven days in a row is much stronger than 2 hours on Sunday, because the whole method depends on reviewing each card on its due day.
If you miss a day, do not add new cards the next day. Clear the backlog first, then go back to normal.
What does a 6-week AWS study plan with spaced repetition look like?
This plan fits the Solutions Architect Associate level. For Cloud Practitioner, you can squeeze it into three or four weeks by merging weeks. Always check the official exam guide on the AWS Certification site for the current domains, since AWS updates its exams over time.
Week 1: Foundations and setup
1. Download the official exam guide and write the domains as tags in your app.
2. Go through the course sections on IAM, the global infrastructure (Regions, Availability Zones), and billing basics.
3. Take one short quiz per section. Make cards only from misses.
4. Target: roughly 60 to 100 cards by the end of the week.
Week 2: Compute and storage
1. EC2 purchase options, Auto Scaling, load balancers, EBS, EFS, S3.
2. Build one small thing in the console, such as an S3 bucket with a lifecycle rule. Hands-on work makes cards easier to remember.
3. Add the look-alike cards from the table above.
Week 3: Networking and databases
1. VPC, subnets, route tables, gateways, Security Groups, NACLs.
2. RDS, Aurora, DynamoDB, ElastiCache.
3. Draw a simple VPC on paper from memory once. Anything you could not draw becomes a card.
Week 4: Decoupling, monitoring, security services
1. SQS, SNS, EventBridge, Lambda, API Gateway.
2. CloudWatch, CloudTrail, Config, KMS, Secrets Manager.
3. Take your first full practice exam at the end of the week. Expect a mediocre score. That is the point: it shows you the gaps.
Week 5: Practice exams feed the deck
1. One full practice exam every two or three days.
2. After each exam, review every wrong and every guessed question. Make a card for each.
3. Stop adding cards from the course. From now on, practice exams are the only source.
Week 6: Reviews only
1. Set new cards to zero for the last 5 to 7 days.
2. Do all due reviews every day.
3. Use the tags to run an extra review of your weakest domain.
4. Take one last practice exam two or three days before the real one, not the night before.
What mistakes make spaced repetition fail?
1. Making cards before understanding. You memorize words without the idea behind them, and scenario questions still beat you.
2. Downloading a giant shared deck. Other people's decks are full of facts you already know and missing the ones you do not. If you use one, suspend everything and turn on only cards for topics you missed.
3. Pressing "Good" when the answer was fuzzy. Be strict. If you had to guess, press "Again."
4. Skipping days. Reviews pile up, the backlog feels heavy, and people quit. Twenty minutes, every day, no exceptions.
5. Only using cards. Flashcards hold facts. They do not replace practice exams, hands-on labs, or reading the "why" behind an answer. Use them together.
Does this work for other tech certifications?
Yes. The same method fits Azure, Google Cloud, CompTIA, Kubernetes, and project exams like PMP. The only change is the card source. For PMP, your cards will be more about process order and definitions. For Azure and Google Cloud, the look-alike service pairs matter just as much as they do in AWS. If you are still choosing between clouds, pick one, finish it, and reuse the same deck habits for the next.
Your next step today
1. Install Anki (or the tool you prefer) and create a deck named after your exam.
2. Set new cards per day to 15.
3. Take one short free quiz on the topic you are studying right now.
4. Turn every miss into one card, written as a scenario, with a one-line "why" on the back.
5. Review tomorrow at the same time. Then do it again the day after.
Do that for six weeks, let practice exams feed the deck, and the facts you keep losing will be there when you sit the exam.
FAQ
How many flashcards do I need for the AWS Solutions Architect Associate exam?
There is no fixed number. Build cards only from questions you miss or guess and from look-alike services. A few hundred focused cards are far more useful than thousands copied from a course.
Should I use a shared AWS Anki deck?
Only with care. Shared decks include many facts you already know and miss your personal weak spots. If you use one, suspend all cards and turn on only the topics you got wrong.
Can spaced repetition replace practice exams?
No. Flashcards keep facts in memory, but practice exams train you to read long scenarios and pick the best option. Use practice exams to find gaps and flashcards to close them.