◆ Elasticsearch

Create Elasticsearch users

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 Elasticsearch tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a new user, 'reporting_svc', with a strong, auto-generated password, and assign it the…+
Create a new user, 'reporting_svc', with a strong, auto-generated password, and assign it the 'read_only_analyst' role for the 'sales_data' index. Get this done before the BI team's morning dashboard refresh.
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 I finalize these new user accounts for the external analytics team, make sure they…+
Before I finalize these new user accounts for the external analytics team, make sure they adhere to our least privilege policy. Review the 'external_analyst' role and verify it only grants access to the 'marketing_campaigns' index and nothing else. Flag any permissions that seem too broad or could expose other 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 intern just reported they can't access the 'dev_logs' index, but I'm sure I assigned…+
The new intern just reported they can't access the 'dev_logs' index, but I'm sure I assigned them the correct role.
The new intern just reported they can't access the 'dev_logs' index, but I'm sure I assigned them the 'dev_reader' role, which should grant access. I'm worried I might have made a typo in the role definition or that there's an implicit deny somewhere. What's the first thing I should check to diagnose why their access is failing, and how can I quickly verify the effective permissions for their user?
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 get requests to create new users or modify existing user permissions, often under…+
I frequently get requests to create new users or modify existing user permissions, often under pressure.
I frequently get requests to create new users or modify existing user permissions, often under pressure, and I'm worried about making a mistake that grants too much access. It feels like I'm just reacting to each request. What habit could I change to streamline user management, ensure consistent application of least privilege, and reduce the risk of security vulnerabilities when creating new accounts?
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 Elasticsearch'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.