◆ Amazon DynamoDB

Automate DynamoDB scripts

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 taskWrite a Python script using boto3 to insert a new item into the 'UserProfiles' table. The item…+
Write a Python script using boto3 to insert a new item into the 'UserProfiles' table. The item should have 'userId' as 'user123', 'username' as 'Alice', and 'email' as 'alice@example.com'.
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 run this data migration script against the 'LegacyCustomers' table, ensure it handles…+
Before I run this data migration script against the 'LegacyCustomers' table, ensure it handles potential write throttling by implementing exponential backoff and retry logic. Also, add logging for both successful and failed item insertions, so I can provide a clear audit trail to the data governance 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 momentMy script to clean up old session data in the 'UserSessions' table is failing intermittently,…+
My script to clean up old session data is failing intermittently, leaving stale records.
My script to clean up old session data in the 'UserSessions' table is failing intermittently, leaving stale records and causing our storage costs to creep up. It's supposed to delete items older than 30 days, but sometimes it just stops. I can't tell if it's hitting a rate limit, or if the scan operation is timing out due to too many items. The security team is asking about data retention compliance. What's the most likely cause, and what's the best next step to ensure reliable cleanup?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time manually running ad-hoc scripts for data fixes or one-off reports, often…+
I spend too much time manually running ad-hoc scripts for data fixes or one-off reports, often forgetting to clean up temporary resources.
I spend too much time manually running ad-hoc scripts for data fixes or one-off reports, often forgetting to clean up temporary resources or leaving credentials exposed. This leads to security concerns and unnecessary charges. What habit should I change in how I approach these one-off tasks to ensure they are automated, secure, and leave no trace?
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.