Skip to content

Conversation

@cassiodias
Copy link

Description

Adds implementation clarification that LocalStack uses the Cedar engine for Verified Permissions policy evaluation.

Changes

  • Added "Implementation" section stating Cedar engine usage
  • Placed between "Introduction" and "Getting started" sections

Motivation

Current documentation mentions "Cedar policy language" but doesn't state that LocalStack uses the actual Cedar engine (vs a mock or custom parser). This helps developers understand the fidelity of local testing.


Diff:

+## Implementation
+
+LocalStack uses the Cedar engine to evaluate permissions, ensuring authorization testing closely matches AWS Verified Permissions behavior.
+

@quetzalliwrites
Copy link
Collaborator

@bentsku is this technically accurate? i would like an engineer approval to be safe :)

Copy link
Contributor

@bentsku bentsku left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@quetzalliwrites It is technically correct, but I'm not sure having it so forefront makes sense? Does it follow how the other services are structured?

@cassiodias thanks a lot for the contribution! I was wondering if this should be part of the introduction, I'm not sure having a whole section for this follows how the other services pages are structured?

@cassiodias
Copy link
Author

Up to you guys, my intention was to make that clear. But I can change if there is another place

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants