You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user-guide/creating-application/eso/aws-eso.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,41 +2,41 @@
2
2
3
3
To add secrets from **AWS Secrets Manager**, we need to create a generic Kubernetes secret for AWS authentication.
4
4
5
-
Create a Kubernetes secret in the namespace in which the application is to be deployed using base64 encoded AWS access-key and secret-access-key. You can use devtron generic chart for this.
5
+
Create a Kubernetes secret in the namespace in which the application is to be deployed using base64 encoded AWS access-key and secret-access-key. You can use a Devtron generic chart for it.
6
6
7
-
**Note:** You don't have to create the Kubernetes secret everytime you create External Secret for the respective namespace.
7
+
**Note**: You don't have to create the Kubernetes secret every time you create external secret for the respective namespace.
**3. Create a secret in the application using ESO AWS Secrets Manager:**
62
+
**3. Create a secret in the application using ESO AWS Secrets Manager**
63
63
64
64
Go to the application where you want to create an external secret. Navigate to secrets section under application configuration and create a secret using ESO AWS Secrets Manager.
To incorporate secrets from **HashiCorp Vault**, you need to create a generic Kubernetes secret that will be used for vault authentication. This involves creating a Kubernetes secret in the specific namespace where your application will be deployed.
4
+
The secret should store the base64-encoded password or token obtained from vault. To simplify the process, you can utilize the Devtron generic chart. An example yaml is given below:
5
+
6
+
```yaml
7
+
apiVersion: v1
8
+
kind: Secret
9
+
type: Opaque
10
+
data:
11
+
token: <vault-password>
12
+
metadata:
13
+
name: vault-token
14
+
namespace: <namespace>
15
+
```
16
+
17
+
**Note**: Please note that you don't need to create the Kubernetes secret every time you create an External Secret for the corresponding namespace.
18
+
19
+
Once you have created the generic secret, follow these steps in the application's Secrets section:
20
+
21
+
**1. Create a new secret**
22
+
23
+
To add a new secret to the application, go to the `App Configuration` section of the application. Then, navigate to the left pane and select the `Secrets` option and click the **Add Secret** button.
**2. Select `HashiCorp Vault` as the External Secret Operator**
28
+
29
+
After clicking the **Add Secret** button, select `HashiCorp Vault` from the dropdown menu for the `Data type` option. Provide a name for the secret you are creating, and then proceed to configure the external secret as described in the next step.
To configure the external secret that will be fetched from HashiCorp Vault for your application, you will need to provide specific details using the following key-value pairs:
After configuring the external secret from HashiCorp Vault, proceed to save the secret by clicking the **Save** button.
57
+
58
+
By following the steps mentioned above and configuring these values correctly, you can seamlessly fetch and utilize external secrets from HashiCorp Vault within your application environment by deploying the application.
0 commit comments