◆ Amazon DynamoDB

Perform CRUD operations with Step Functions

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 taskUpdate the 'order_status' attribute to 'shipped' for order ID 'A1B2C3D4' in the 'Orders' table.…+
Update the 'order_status' attribute to 'shipped' for order ID 'A1B2C3D4' in the 'Orders' table. Then, increment the 'shipped_count' in the 'CustomerMetrics' table for customer ID 'X1Y2Z3'. Confirm both operations complete successfully before marking the Step Functions execution as done.
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 deploy this new order processing workflow, I need to make sure the Step Functions…+
Before we deploy this new order processing workflow, I need to make sure the Step Functions state machine handles concurrent updates to inventory correctly. Design the update operation for the 'Products' table to use optimistic locking to prevent race conditions, and ensure the Step Functions flow correctly retries on a version mismatch. I want to avoid phantom stock issues.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur new user registration service is randomly failing, throwing…+
The new user registration service is failing intermittently, showing 'ConditionalCheckFailedException' errors in the logs, but only for some users.
Our new user registration service is randomly failing, throwing 'ConditionalCheckFailedException' errors when trying to create new user profiles. It's happening to about 5% of new sign-ups, and I can't pinpoint why. We're using a 'PutItem' with a 'ConditionExpression' to ensure the username doesn't already exist. Is it possible that the condition check is too slow or that there's a race condition I'm not seeing with very fast concurrent requests for the same username? What's the best way to diagnose if it's a timing issue or a data modeling problem, and what's the safest next step to stabilize registrations without introducing duplicates?
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 getting paged for 'ProvisionedThroughputExceededException' errors, even on…+
I keep getting paged for 'ProvisionedThroughputExceededException' errors on tables that should have enough capacity.
I'm constantly getting paged for 'ProvisionedThroughputExceededException' errors, even on tables where our metrics say we have sufficient provisioned capacity for read and write units. It feels like I'm always reacting to spikes instead of proactively managing them. What habit should I change to better anticipate and configure capacity, especially for bursty workloads, so I'm not always scrambling to adjust settings after an incident?
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.