◆ Amazon DynamoDB

Reduce DynamoDB monthly cost

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 taskFor the 'customer_profiles' table, set the read capacity to 50 and the write capacity to 20,…+
For the 'customer_profiles' table, set the read capacity to 50 and the write capacity to 20, and enable autoscaling with a target utilization of 70% for both. Ensure this change is live by end of day.
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 we push this new 'order_history' table to production, analyze its access patterns.…+
Before we push this new 'order_history' table to production, analyze its access patterns. Recommend the most cost-effective provisioned capacity settings and suggest if on-demand is a better fit, considering our typical peak loads and quiet periods. Highlight any potential for unexpected cost spikes.
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 'user_sessions' table keeps throttling during peak hours, and I'm worried about user…+
We just got a notification that the 'user_sessions' table exceeded its provisioned write capacity by 300% for the third time this week, causing throttles and user complaints.
The 'user_sessions' table keeps throttling during peak hours, and I'm worried about user experience and the impact on our Black Friday sales. I've tried increasing capacity, but it's either too much or not enough. Is the auto-scaling misconfigured, or is there a fundamental issue with how we're handling session writes? What's the fastest way to stabilize this without breaking the bank before Friday?
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 wrestling with table capacity, either paying too much for idle resources or scrambling…+
We consistently over-provision or under-provision our tables, leading to either wasted spend or performance issues.
I keep wrestling with table capacity, either paying too much for idle resources or scrambling to increase it during unexpected spikes. This reactive approach is costing us money and developer time. What habit should I change to proactively manage table costs and performance, finding the right balance between on-demand and provisioned, especially for our core application tables?
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.