◆ Amazon DynamoDB

Delete a large number of items

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 taskDelete all items from the 'TestData' table where 'status' is 'expired' and the…+
Delete all items from the 'TestData' table where 'status' is 'expired' and the 'expiration_date' is before '2023-01-01'.
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 acceptI need to delete millions of old log entries from the 'ApplicationLogs' table that are older…+
I need to delete millions of old log entries from the 'ApplicationLogs' table that are older than 90 days. Before I start, help me plan this operation to minimize impact on the live application and avoid exceeding our daily budget. Suggest a phased approach, perhaps using batch deletes or a time-based strategy, to ensure a smooth cleanup.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe have a critical GDPR compliance deadline on Monday to delete sensitive customer data from…+
We need to delete sensitive customer data from 'UserProfiles' for GDPR compliance, but the table is actively used.
We have a critical GDPR compliance deadline on Monday to delete sensitive customer data from the 'UserProfiles' table for users who have requested it. There are hundreds of thousands of items to delete, and the table is under heavy write load from the live application. I'm afraid of impacting performance or accidentally deleting wrong data. What's the safest and most efficient way to perform this large-scale deletion without disrupting the production service or missing the deadline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently dread large-scale data deletion tasks in our NoSQL database because they always…+
I consistently dread large-scale data deletions because they always feel risky and impactful.
I consistently dread large-scale data deletion tasks in our NoSQL database because they always feel risky, time-consuming, and have the potential to impact production or incur high costs. This makes me procrastinate until deadlines are tight. What habit or preparatory step should I change in my approach to large deletions to make them less stressful, safer, and more predictable?
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.