Elasticsearch permissions are confusing and error-prone

2 posts from 2 people2d activeSteady, +1 this weekunverified

Posts per day2 posts, Oct 17 to Nov 11

The posts behind it

GitHub issuesprowler-cloud/prowler · ahmedhany-cysNov 6

AWS resource policy checks treat wildcard conditions that match any account as restrictive

### Issue search - [x] I have searched the existing issues and this bug has not been reported yet ### Which component is affected? Prowler CLI/SDK ### Cloud Provider (if applicable) AWS ### Steps to Reproduce `is_condition_block_restrictive` in...

GitHub issuesprowler-cloud/prowler · 7-BalaOct 17

Lambda, ECR, Glacier and OpenSearch public access fixers delete the whole resource policy

### Which component is affected? Prowler CLI/SDK ### Cloud Provider AWS ### Steps to Reproduce 1. Give a resource a policy with one public statement plus statements that are not public. For example, an ECR repository with: - `Public`: `Allow` `ecr:*` to `{"AWS": "*"}` (the...

Companies and products named

Elasticsearch

2 posts

GitHub

2 posts

AWS

1 post

Lambda

1 post

DynamoDB

1 post

About this problem

Evidence

2 posts from 2 people in 1 place, about 1 a week over 21 days. Mostly on prowler-cloud/prowler. Tools named alongside: GitHub, AWS, Lambda, DynamoDB.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "permissions" rule about Elasticsearch. First post Oct 17, 2026, latest Nov 6, 2026. Unverified: fewer than 3 posts, or one person or place only. Method

The same problem elsewhere