◆ Amazon DynamoDB

Troubleshoot website issues

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 taskInvestigate why the 'UserPreferences' service is returning 500 errors to the frontend. Check…+
Investigate why the 'UserPreferences' service is returning 500 errors to the frontend. Check the DynamoDB table 'UserConfig' for recent changes and review the service logs for any exceptions. Get a preliminary diagnosis by 10 AM.
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 acceptWhen troubleshooting the 'UserPreferences' service, don't just find the error. Analyze the data…+
When troubleshooting the 'UserPreferences' service, don't just find the error. Analyze the data access patterns for the affected users, look for any recent schema changes, and identify potential root causes that could lead to similar issues in other services.
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 'ProductAvailability' feature on the website is down, showing incorrect stock levels for…+
The website's 'ProductAvailability' feature is failing, and the DynamoDB table 'Inventory' shows correct data, but the service logs are unhelpful.
The 'ProductAvailability' feature on the website is down, showing incorrect stock levels for all products. The 'Inventory' DynamoDB table looks perfectly fine, and the service logs are just showing generic 'database error' messages without specifics. The product manager is asking for an ETA, and I'm afraid I'm missing something obvious in how the service interacts with DynamoDB. What's the likely diagnosis, and what's the best next move to pinpoint the actual failure point?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWhen troubleshooting website issues that touch our database, I often get lost in logs or…+
I often spend too much time chasing red herrings when troubleshooting website issues involving DynamoDB.
When troubleshooting website issues that touch our database, I often get lost in logs or misinterpret metrics, wasting hours on red herrings before finding the actual problem. I find myself reacting to symptoms instead of quickly identifying root causes. What habit can I change in my diagnostic process to more efficiently and accurately pinpoint the source of these database-related issues?
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.