◆ Amazon DynamoDB

Ensure software security and data protection

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 taskUpdate the security group for the production DynamoDB table 'customer_profiles' to only allow…+
Update the security group for the production DynamoDB table 'customer_profiles' to only allow inbound traffic from the 'backend_service_vpc' security group, and revoke all other inbound rules. Confirm this change is live before I leave for the day.
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 deploying the new 'order_history' table to production, review its IAM policy. Ensure it…+
Before deploying the new 'order_history' table to production, review its IAM policy. Ensure it follows least privilege, allowing only the 'order_processing_service' role to perform read and write operations, and flag any permissions that look too broad or could expose sensitive data.
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 new analytics service is failing to read from the 'user_sessions' table, but the logs show…+
The new analytics service is failing to read from the 'user_sessions' table, but the logs show successful connection.
The new analytics service is failing to read from the 'user_sessions' table, but the logs show successful connection. I'm afraid we missed an IAM permission, and I can't tell if it's the service role or the table policy. What's the most likely misconfiguration, and what's the quickest way to diagnose this without impacting live traffic?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep finding myself patching security holes in production tables after deployment. The…+
I keep finding myself patching security holes in production tables after deployment.
I keep finding myself patching security holes in production tables after deployment. The pressure to ship often means security reviews are rushed. What habit should I change to ensure every new DynamoDB table has a robust and secure access policy from the start, without becoming a bottleneck for the team?
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.