◆ Amazon DynamoDB

Add a global secondary index to a table

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 taskAdd a global secondary index named 'EmailIndex' to the 'UserSessions' table. The partition key…+
Add a global secondary index named 'EmailIndex' to the 'UserSessions' table. The partition key should be 'email' and the sort key 'loginTime'. Project only the 'userId' and 'sessionId' attributes. This needs to be done before the end-of-day report runs.
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 add this 'EmailIndex' to the 'UserSessions' table, make sure it's optimized for the…+
Before I add this 'EmailIndex' to the 'UserSessions' table, make sure it's optimized for the new analytics queries we're running. Surface any potential cost implications or read/write capacity concerns, and flag anything that might cause a bottleneck for the new dashboard reporting to the marketing team.
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 marketing team's new analytics queries on 'UserSessions' are timing out consistently, and…+
The new analytics queries on user sessions are timing out without a proper index.
The marketing team's new analytics queries on 'UserSessions' are timing out consistently, and they're pushing hard for a fix by tomorrow. I'm trying to add a global secondary index, but I'm unsure about the best provisioned capacity and attribute projections to avoid overspending or creating another bottleneck. What's the likely diagnosis for the timeouts and the best next move to get this index deployed safely and effectively?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time I need to add a new global secondary index, I spend too much time second-guessing…+
Adding new indexes always feels like a gamble with cost and performance.
Every time I need to add a new global secondary index, I spend too much time second-guessing capacity and projections, leading to either overspending or underperformance. It's a constant source of anxiety, and I keep losing time to rework indexes. What habit should I change to confidently design and deploy indexes that meet query needs without breaking the bank or causing new performance issues?
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.