◆ Amazon DynamoDB

Reduce cost of unused DynamoDB capacity

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 taskI need to identify any 'dev_test_data' tables that haven't been accessed in the last 90 days…+
I need to identify any 'dev_test_data' tables that haven't been accessed in the last 90 days and delete them to reduce costs.
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 the end of the fiscal quarter, I need to review our entire 'staging' environment for…+
Before the end of the fiscal quarter, I need to review our entire 'staging' environment for unused database capacity. Help me identify tables or global secondary indexes that are significantly over-provisioned based on actual usage metrics, and suggest a plan to right-size them to save money.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy manager just asked for a cost-saving report, and I suspect we're paying too much for unused…+
My manager just asked for a cost-saving report, and I suspect we're paying too much for unused capacity in our 'legacy_archive' tables.
My manager just asked for a cost-saving report, and I suspect we're paying too much for unused capacity in our 'legacy_archive' tables. These tables are rarely accessed, but I'm unsure how to prove they're over-provisioned without manually digging through months of metrics, and I need to show concrete savings by Friday. What's the best way to quickly identify and quantify the cost of unused capacity in these low-activity tables, and what's the safest first step to reduce it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly reacting to cost reports showing wasted spend on underutilized database…+
I keep finding myself reacting to cost reports showing wasted spend on underutilized database resources.
I'm constantly reacting to cost reports showing wasted spend on underutilized database resources, especially after projects are completed or features are deprecated. It feels like we're always cleaning up after the fact. What habit should I change to proactively manage and reduce the cost of unused database capacity throughout the lifecycle of our applications, rather than just reacting to budget overruns?
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.