◆ Amazon DynamoDB

Design DynamoDB schemas

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 'product_reviews' with a primary key of 'review_id' and a…+
Create a new DynamoDB table called 'product_reviews' with a primary key of 'review_id' and a sort key of 'product_id'. Ensure it has on-demand capacity and is encrypted at rest.
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 acceptBefore finalizing the 'order_history' table schema, think about how the customer service team…+
Before finalizing the 'order_history' table schema, think about how the customer service team will query it. They need to quickly find all orders for a specific customer, but also all orders placed within a certain date range, and sometimes all orders for a specific product. Design the primary key and any necessary secondary indexes to support these access patterns efficiently without full table scans.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe're designing a new 'user_activity' table, and I'm torn between using a single global…+
We're designing a new 'user_activity' table, and I'm torn between using a single global secondary index or multiple local secondary indexes.
We're designing a new 'user_activity' table, and I'm torn between using a single global secondary index on 'activity_type' for broad queries or multiple local secondary indexes for more specific, partition-key-bound lookups. I'm afraid of creating an expensive GSI that's rarely used, or LSI's that don't scale well. What's the best approach given we expect varied query patterns but also need strong consistency for user-specific activity streams?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself adding new secondary indexes to existing DynamoDB tables post-launch…+
I frequently find myself adding new secondary indexes to existing tables because I didn't foresee a critical query pattern.
I frequently find myself adding new secondary indexes to existing DynamoDB tables post-launch because I didn't foresee a critical query pattern during initial design. This always causes downtime or complex data migrations. How can I change my habit to more thoroughly anticipate future access patterns and design more resilient schemas from the start, reducing the need for costly retrofits?
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.