Skip to content

Commit 216d51b

Browse files
updates
1 parent b8ce09f commit 216d51b

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
title: "Configuring External Secret Management with AWS Secret Manager"
3+
url: /private-mendix-platform/configure-aws-secret-manager/
4+
description: "Documents the configuration of AWS Secret Manager for the Private Mendix Platform."
5+
weight: 40
6+
---
7+
8+
## Introduction
9+
10+
The Private Mendix Platform offers enhanced security and flexibility for credential management by supporting [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) as an external secret management solution, alongside the traditional database storage option. In the legacy database storage approach, the credentials are encrypted and stored directly in the Private Mendix Platform database. With AWS Secrets Manager, credentials are instead stored in AWS Secrets Manager and accessed securely via IAM roles for improved security, centralized management, and compliance with enterprise security policies. This document describes how you can configure AWS Secrets Manager integration for your Private Mendix Platform project.
11+
12+
## Prerequisites
13+
14+
Before configuring AWS Secrets Manager integration, prepare the following:
15+
16+
* An AWS account with appropriate permissions to create and manage secrets
17+
* IAM permissions to create roles and policies for AWS Secrets Manager access
18+
* Access to the PPrivate Mendix Platform project admin panel with administrative privileges
19+
* Basic knowledge of AWS services, IAM roles, and Kubernetes (if using EKS deployment)
20+
* An existing EKS cluster (if your PMP deployment runs on Kubernetes)

0 commit comments

Comments
 (0)