Skip to content

Commit e11c6ae

Browse files
Update pmp-configure-aws-secret.md
1 parent 7b31d2e commit e11c6ae

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/docs/private-platform/configuration/pmp-configure-aws-secret.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ To create a secret in AWS Secret Manager, perform the following steps:
3434
5. Select the **JSON** format for storing secrets.
3535
6. Enter the key-value pairs for your secrets using the Private Mendix Platform [naming convention](#naming-convention).
3636
7. Click **Next**.
37-
8. Enter a descriptive name for your secret, for example, *PMP-Production-Credentials* or *PMP-VCS-Credentials*.
37+
8. Enter a descriptive name for your secret, for example, *PMP-Production-Credentials*.
3838
9. Optional: Add a description and tags for better organization and compliance tracking.
3939
10. Click **Next** to review your secret settings.
4040
11. Review the details and click **Store** to create the secret.
@@ -307,4 +307,4 @@ The following example shows how you can configure Private Mendix Platform to wor
307307
308308
## Storing the Credentials Directly in the Database
309309
310-
Instead of using the AWS Secret Manager, you can still use the legacy option to store the credentials in the Private Mendix Platform database. To do this, you must select **Database** from the storage options dropdown, and then enter the credentials directly in an input field. The credentials are encrypted and stored in the Private Mendix Platform database.
310+
Instead of using the AWS Secret Manager, you can still use the legacy option to store the credentials in the Private Mendix Platform database. To do this, you must select **Database** from the storage options dropdown, and then enter the credentials directly in an input field. The credentials are encrypted and stored in the Private Mendix Platform database.

0 commit comments

Comments
 (0)