◆ Amazon DynamoDB

Grant project-based access to DynamoDB items

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 taskGrant the 'AnalyticsTeam' IAM role read-only access to all items in the 'customer_metrics'…+
Grant the 'AnalyticsTeam' IAM role read-only access to all items in the 'customer_metrics' table.
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 acceptThe 'MarketingTeam' IAM role needs to update only the 'email_preference' attribute for users in…+
The 'MarketingTeam' IAM role needs to update only the 'email_preference' attribute for users in the 'user_profiles' table, but only for users in the 'US' region. Design an access policy that grants this specific, fine-grained write access without allowing broader modifications or access to other user 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 'SupportAgent' IAM role is accidentally seeing sensitive customer financial data in the…+
The new 'SupportAgent' IAM role is accidentally seeing sensitive customer financial data in the 'customer_orders' table.
The new 'SupportAgent' IAM role is accidentally seeing sensitive customer financial data in the 'customer_orders' table, which is a major compliance risk. They only need to see 'order_id', 'product_name', and 'status' for their assigned customers. I’m unsure if the existing policy is too broad, or if I need to implement attribute-level or item-level access controls. What’s the fastest and most secure way to restrict their access to only the necessary attributes for their customers, without impacting other roles?
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 creating overly permissive IAM policies for database access, or struggling to get them…+
I keep creating overly permissive IAM policies for DynamoDB, or struggling to get them granular enough.
I keep creating overly permissive IAM policies for database access, or struggling to get them granular enough, leading to security reviews and rework. This often delays project launches and creates potential compliance issues. What habit should I change in how I approach granting access to database items to ensure least privilege is consistently applied from the start, without becoming a bottleneck?
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.