◆ Amazon DynamoDB

Design DynamoDB data models

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Amazon DynamoDB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a new DynamoDB table called 'CustomerPreferences' with 'customer_id' as the primary key…+
Create a new DynamoDB table called 'CustomerPreferences' with 'customer_id' as the primary key and 'preference_type' as a sort key. Ensure it has on-demand capacity and is encrypted with an AWS-managed key.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptI'm designing the data model for our new 'UserActivityLog' feature. Before I finalize the…+
I'm designing the data model for our new 'UserActivityLog' feature. Before I finalize the primary key, help me think through future access patterns. We'll need to query by user, by activity type, and by time range. Suggest a primary key and any necessary secondary indexes that will optimize for these queries while minimizing cost and complexity.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm designing the 'GameScores' table, and the lead developer insists on a single-table design…+
I'm modeling a 'GameScores' table, and the lead developer is pushing for a single-table design using generic attributes.
I'm designing the 'GameScores' table, and the lead developer insists on a single-table design using generic 'PK' and 'SK' attributes for all entities to save on cost. I'm concerned this will make queries complex and hard to maintain for the junior developers, especially when we need to add new entities later. What's the best way to balance cost efficiency with future maintainability and query simplicity here, and how should I present my concerns effectively?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often end up refactoring NoSQL data models months after launch because critical access…+
I frequently find myself refactoring DynamoDB data models because new access patterns weren't considered upfront.
I often end up refactoring NoSQL data models months after launch because critical access patterns or data relationships weren't fully anticipated during the initial design phase. This leads to costly migrations and performance issues. What habit should I change in my design process to more thoroughly vet future access patterns and prevent these late-stage refactorings?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Amazon DynamoDB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.