mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
17ed51f8aa
- Merge upstream/main with -X ours strategy to preserve Hanzo customizations - Strip all backend/src/ee/ files reintroduced by upstream (PAM, discovery, sub-org, permissions, etc.) - Create minimal group-dal stub for new upstream service dependency - Preserve MIT-licensed permission, audit-log, rate-limit, license stubs - Keep Hanzo branding, per-org encryption keys, Insights telemetry - Remove backend/package-lock.json (we use npm/pnpm)
62 lines
3.1 KiB
Plaintext
62 lines
3.1 KiB
Plaintext
---
|
|
title: "PAM Resource"
|
|
sidebarTitle: "Overview"
|
|
description: "Learn how to add and configure resources like databases and servers, and set up automated credential rotation."
|
|
---
|
|
|
|
A resource represents a target system, such as a database, server, or application, that you want to manage access to. Some examples of resources are:
|
|
- PostgreSQL Database
|
|
- MCP Server
|
|
- Linux Server
|
|
- Web Application
|
|
|
|
## Prerequisites
|
|
|
|
Before you can create a resource, you must have an **KMS Gateway** deployed that is able to reach the target resource over the network.
|
|
|
|
The Gateway acts as a secure bridge, allowing KMS to reach your private infrastructure without exposing it to the public internet. When creating a resource, you will be asked to specify which Gateway should be used to connect to it.
|
|
|
|
[Read the Gateway Deployment Guide](/documentation/platform/gateways/gateway-deployment)
|
|
|
|
## Creating a Resource
|
|
|
|
To add a resource, navigate to the **Resources** tab in your PAM project and click **Add Resource**.
|
|
|
|
|
|
|
|
Next, select the type of resource you want to add.
|
|
|
|
|
|
|
|
After selecting a resource type, provide the necessary connection details. The required fields vary depending on the resource type.
|
|
|
|
**Important**: You must select the **Gateway** that has network access to this resource.
|
|
|
|
In this PostgreSQL example, you provide details such as host, port, gateway, and database name.
|
|
|
|
|
|
|
|
Clicking **Create Resource** will trigger a connection test from the selected Gateway to your target resource. If the connection fails, an error message will be displayed to help you troubleshoot (usually indicating a network firewall issue between the Gateway and the Resource).
|
|
|
|
## Resource Metadata
|
|
|
|
Resources support custom key-value metadata that can be used to organize and classify your infrastructure. Common use cases include environment labels, cost centers, compliance tags, and team ownership.
|
|
|
|
- **At creation**: You can attach metadata key-value pairs when creating a resource through the creation modal.
|
|
|
|
|
|
|
|
- **On the details page**: After creation, resource metadata can be viewed and edited from the resource details page.
|
|
|
|
|
|
|
|
- **Filtering**: You can filter the resources list view by metadata key-value pairs.
|
|
|
|
|
|
|
|
## Automated Credential Rotation
|
|
|
|
Some resources, such as PostgreSQL, support automated credential rotation to enhance your security posture. This feature requires configuring a privileged "Rotation Account" on the resource.
|
|
|
|
To learn more about how to configure this, please refer to the [Credential Rotation guide](/documentation/platform/pam/product-reference/credential-rotation).
|