Policies Module
Overview
The Policies Module is used to define and manage authorization policies within Catalog IAM.
A policy is a reusable collection of authorization rules that determines which operations may be performed on catalog resources. Policy rules can target different resource levels, including catalogs, namespaces, and tables.
Policies do not grant access directly to users or groups. They define authorization rules that can later be associated with roles and assigned to principals through bindings.
Policy Management
This page displays all policies defined within Catalog IAM.
From this interface, administrators can perform the following actions:
- View existing policies and their rule summaries.
- Search policies using the centralized search field.
- Filter and sort policy records using the available table controls.
- Switch between list and card views.
- Create a new policy using the Add Policy button.
- Review each policy's resource scope, number of rules, priority, and creation date.
Policy Information
Each policy record contains the following information:
| Field | Description |
|---|---|
| Name | The unique name used to identify the policy within Catalog IAM. |
| Description |
Additional information explaining the purpose or intended use of
the policy. A hyphen (-) is displayed
when no description has been provided.
|
| Rules |
Displays the resource types covered by the policy, such as
Catalog,
Namespace, or
Table. The number displayed next to
each resource type indicates how many rules are defined for that
resource level.
|
| Priority | Determines the evaluation priority of the policy. The priority value is used when multiple policies or rules may apply to the same authorization request. |
| Create Date | The date and time when the policy was created. |
Policy Rules
Each policy may contain one or more rules.
A rule defines the authorization behavior for a specific resource level. Policies may include rules for the following resource types:
- Catalog
- Namespace
- Table
The Rules column summarizes the resource scope of the policy and displays the number of rules defined for each resource type.
For example:
-
Catalog 1indicates that the policy contains one catalog-level rule. -
Namespace 1indicates that the policy contains one namespace-level rule. -
Table 1indicates that the policy contains one table-level rule.
Policy Priority
The Priority value determines the order in which applicable policies are evaluated.
When multiple policies apply to the same resource or authorization request, their priority values help determine the evaluation order. Priority values should therefore be assigned carefully to avoid conflicting or unintended authorization behavior.
Key Considerations
- Policies define authorization rules but do not directly assign permissions to users or groups.
- A policy may contain multiple rules covering different Catalog IAM resource levels.
- Policy rules can target catalogs, namespaces, and tables.
- Policies can be reused through roles and assigned to users or groups through bindings.
- Changes made to a policy may affect every role or binding that references it.
- Policy priorities should be reviewed carefully when multiple policies apply to the same resource.
- Policies that are currently referenced by roles or bindings should be reviewed before they are modified or removed.
Access Requirements
This page is available only to users with Administrator privileges.
Only administrators can view and manage Catalog IAM policies. Non-administrator users cannot access this page.
Users without administrator privileges will receive the following authorization error:
Access Denied
You don't have access to this resource.