◆ Elasticsearch

Configure Elasticsearch security

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 taskSet up a new role for the finance team, giving them read-only access to the 'transactions'…+
Set up a new role for the finance team, giving them read-only access to the 'transactions' index and nothing else. Make sure it's ready by Friday for their audit.
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 hand off this new security configuration to the audit team, make sure it's robust. Are…+
Before I hand off this new security configuration to the audit team, make sure it's robust. Are there any implicit permissions or default roles that could accidentally expose sensitive data from the 'transactions' index to non-finance users? Flag anything that looks like a potential leak.
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 finance director just asked for a security report on our new Elasticsearch cluster,…+
The finance director just asked for a security report for the new Elasticsearch cluster, and I'm not sure what to show her.
The finance director just asked for a security report on our new Elasticsearch cluster, specifically how we're isolating sensitive data. I've set up roles, but I'm worried about some of the default permissions or if I missed an edge case with index patterns. What's the most concise way to prove we've locked it down, and what's the first thing I should check for potential vulnerabilities she'd spot?
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 getting pulled into urgent security audits, often for new data sources, and it always…+
I keep getting pulled into urgent security audits for Elasticsearch, often for new data sources.
I keep getting pulled into urgent security audits, often for new data sources, and it always feels like I'm starting from scratch. I lose time figuring out how to quickly verify least privilege for new indices. What habit could I change to make these reviews faster and more reliable, especially when the stakes are high with compliance?
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.