◆ Amazon DynamoDB

Clean up stale data from DynamoDB tables

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 taskRun the daily cleanup script for the 'session_data' table to remove all items older than 24…+
Run the daily cleanup script for the 'session_data' table to remove all items older than 24 hours. Verify that the script completes without errors and logs the number of items deleted.
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-month reporting, clean up the 'event_logs' table. Instead of just deleting…+
Before the end-of-month reporting, clean up the 'event_logs' table. Instead of just deleting items older than 90 days, archive them to S3 first for compliance and then delete them. Make sure the archiving process is robust and doesn't impact the live application's performance.
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 'shopping_cart' table is growing much faster than expected, and I'm worried about storage…+
The 'shopping_cart' table is growing much faster than expected, and I'm worried about storage costs and query performance.
The 'shopping_cart' table is growing much faster than expected, and I'm worried about storage costs and query performance for active carts. We're deleting items older than 7 days, but it's not enough. I'm afraid of accidentally deleting active carts or impacting user experience by being too aggressive. What's the best next move to manage this growth without disrupting users or incurring massive bills?
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 finding myself reacting to unexpected table growth and needing to scramble to implement…+
I keep finding myself reacting to unexpected table growth and needing to scramble to implement data retention policies.
I keep finding myself reacting to unexpected table growth and needing to scramble to implement data retention policies and cleanup jobs for DynamoDB tables. This always happens when a new service goes live without a clear data lifecycle plan. How can I change my habit to proactively define and implement data cleanup strategies as part of the initial design phase for all new tables, avoiding reactive crises?
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.