b2KIT

ACL / Permission Calculator

Calculate Unix file permissions (chmod), AWS IAM policies, and Kubernetes RBAC rules. Visualize access matrices.

Tested tool guide Tested browser tools Checked August 15, 2026

What ACL / Permission Calculator does, with a checked example

This tool converts Unix file permissions between numeric form (e.g. 750) and symbolic form (e.g. rwxr-x---), and separately helps assemble AWS IAM policy statements and Kubernetes RBAC Role/RoleBinding rules, displaying each as a visual matrix of subjects against their granted permissions. The three modes are distinct calculators sharing one interface, not a unified cross-platform permission translator. The most common mistake is treating the generated IAM or RBAC output as final: it reflects only the actions, resources, or verbs you entered and still needs review against real resource ARNs, namespaces, and least-privilege requirements before it goes into a policy file.

Worked example

A concrete input and expected output from the current implementation.

Input

640

Expected output

rw-r-----

The digit 6 (owner) decomposes to read(4)+write(2); 4 (group) is read only; 0 (other) is no access, giving the nine-character string rw-r-----.

How the result is produced

1

Numeric-symbolic chmod conversion

Each octal digit from 0-7 represents a permission set as the sum of read(4), write(2), and execute(1). The tool decomposes the owner, group, and other digits into their component bits and renders the nine-character rwx string, or runs the process in reverse when you type symbolic notation instead.

2

Policy and matrix scaffolding

For IAM and RBAC modes you pick actions or verbs and target resources, and the tool assembles the corresponding JSON policy statement or YAML Role/RoleBinding skeleton. It also renders a grid of subjects against permissions so you can visually scan coverage and gaps before copying the output into your actual policy or manifest file.

Good uses

  • Working out the exact chmod digits before running chmod on a web server directory, e.g. group-readable but no access for others
  • Drafting a first-pass least-privilege AWS IAM policy JSON for a new service role before tightening resource scope further
  • Generating a starting Kubernetes Role/RoleBinding YAML for a namespace-scoped service account instead of hand-writing the verb list

Limits and checks

  • It computes the permissions you explicitly set, not what a new file or directory would inherit by default under your shell's umask
  • It is not clear from the tool whether special bits (setuid, setgid, sticky) are represented; if you need a 4-digit mode, verify the output digit count before applying it to a shared directory
  • Generated IAM and RBAC output is not validated against AWS's policy simulator or a live cluster, so an invalid ARN, overly broad wildcard, or nonexistent verb will not be caught here

Common questions

Will the generated IAM policy work as-is in AWS?

It gives you syntactically structured JSON based on what you selected, but it is not checked against AWS's policy simulator or your account's actual resources. Review resource ARNs, conditions, and explicit Allow/Deny effects before attaching it to a role or user.

Does using this tool actually change permissions on my files or cluster?

No. It only calculates and displays the chmod notation, IAM policy, or RBAC YAML locally; you still have to run chmod yourself, or apply the generated policy with the AWS console/CLI or kubectl.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools