◆ Amazon DynamoDB

Generate infrastructure code for DynamoDB

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGenerate the CloudFormation template for a new DynamoDB table called 'UserPreferences', with…+
Generate the CloudFormation template for a new DynamoDB table called 'UserPreferences', with 'userId' as the partition key and 'preferenceName' as the sort key. Ensure it has on-demand capacity and point-in-time recovery enabled.
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 I deploy this 'ProductCatalog' DynamoDB table, make sure the CloudFormation template…+
Before I deploy this 'ProductCatalog' DynamoDB table, make sure the CloudFormation template includes global secondary indexes on 'category' and 'brand' to support common query patterns without impacting read performance on the primary key, and set up auto-scaling for both to handle peak loads efficiently.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'OrderHistory' table's read latency spiked during the Black Friday sale, and I'm getting…+
The new 'OrderHistory' table's read latency spiked during the Black Friday sale, and I'm getting alerts.
The 'OrderHistory' table's read latency spiked during the Black Friday sale, and I'm getting alerts from CloudWatch. We thought on-demand capacity would handle it, but it's clearly not. The marketing team is furious about slow page loads. I can't tell if it's a hot partition issue, or if our access patterns are just too inefficient. What's the most likely diagnosis, and what's the fastest way to stabilize performance without overspending?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep having to manually adjust read/write capacity for our DynamoDB tables after new features…+
I keep having to manually adjust read/write capacity for our DynamoDB tables after new features launch, leading to either throttling or wasted spend.
I keep having to manually adjust read/write capacity for our DynamoDB tables after new features launch, leading to either throttling or wasted spend. This takes up too much of my time and causes friction with the product team. What habit should I change in how I approach table provisioning and scaling to ensure we're always right-sized without constant manual intervention?
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.