◆ Amazon DynamoDB

Perform system backups and disaster recovery

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 taskInitiate a full backup of the production user database to S3 Glacier Deep Archive. Verify the…+
Initiate a full backup of the production user database to S3 Glacier Deep Archive. Verify the backup integrity and confirm its completion by 5 PM.
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 the new analytics module, run a full backup of the production database. Ensure…+
Before we deploy the new analytics module, run a full backup of the production database. Ensure the recovery point objective is set to 15 minutes, and verify that we can restore the critical user data tables independently if needed.
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 main database cluster in us-east-1 just went down, and the automated failover to us-west-2…+
Our main database cluster just went down, and the automated failover to the standby region failed unexpectedly.
Our main database cluster in us-east-1 just went down, and the automated failover to us-west-2 failed unexpectedly, leaving us with a full outage. The incident response team is asking for an ETA on recovery. I'm afraid we missed something in our DR plan. What's the most likely reason for the failover failure, and what's the immediate best next step to get the critical services back online?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently struggle with restoring specific database tables quickly during incident response,…+
I frequently struggle with restoring specific database tables quickly during incident response.
I frequently struggle with restoring specific database tables quickly during incident response, especially when it's not a full-scale disaster. This causes delays in getting services back to normal. What habit should I change to improve my efficiency and confidence in performing granular data restores, ensuring I can meet strict recovery time objectives?
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.