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
| mTLS connection with client key passphrase | <ul><li>Credentials secret with username and password</li><li>CA Certificate secret (server certificate)</li><li>Client certificate secret</li><li>Client key secret</li><li>Client key passphrase secret</li></ul> |
231
+
232
+
Select a tab to learn how to create the required secret.
233
+
234
+
{{< multitabs id="rdi-cloud-secrets"
235
+
tab1="Credentials secret"
236
+
tab2="CA Certificate secret"
237
+
tab3="Client certificate secret"
238
+
tab4="Client key secret"
239
+
tab5="Client key passphrase secret" >}}
220
240
221
241
In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Security, Identity, and Compliance** > **Secrets Manager**. [Create a secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html) of type **Other type of secret** with the following settings:
222
242
223
243
- **Key/value pairs**: Enter the following key/value pairs.
224
244
225
245
- `username`: Database username
226
246
- `password`: Database password
227
-
- `trust_certificate`: Server certificate in PEM format *(TLS only)*
228
-
- `client_public_key`: [X.509 client certificate](https://en.wikipedia.org/wiki/X.509) or chain in PEM format *(mTLS only)*
229
-
- `client_private_key`: Key for the client certificate or chain in PEM format *(mTLS only)*
230
-
- `client_private_key_passphrase`: Passphrase or password for the client certificate or chain in PEM format *(mTLS only)*
231
-
232
-
{{<note>}}
233
-
If your source database has TLS or mTLS enabled, we recommend that you enter the `trust_certificate`, `client_public_key`, and `client_private_key` into the secret editor using the **Key/Value** input method instead of the **JSON** input method. Pasting directly into the JSON editor may cause an error.
234
-
{{</note>}}
235
-
236
-
- **Encryption key**: Select the [encryption key](#create-encryption-key) you created earlier.
237
-
238
-
- **Resource permissions**: Add the following permissions to your secret to allow the Redis data pipeline to access your secret. Replace `<AWS ACCOUNT ID>` with the AWS account ID for the Redis Cloud cluster that you saved earlier.
In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Security, Identity, and Compliance** > **Secrets Manager**. [Create a secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html) of type **Other type of secret** with the following settings:
253
+
254
+
- **Key/value pairs**: Select **Plaintext** and enter the server certificate.
In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Security, Identity, and Compliance** > **Secrets Manager**. [Create a secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html) of type **Other type of secret** with the following settings:
261
+
262
+
- **Key/value pairs**: Select **Plaintext** and enter the client certificate.
Use the [AWS CLI create-secret command](https://docs.aws.amazon.com/cli/latest/reference/secretsmanager/create-secret.html) or the [AWS CreateSecret API endpoint](https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_CreateSecret.html) to create a binary secret containing the client key.
269
+
270
+
For example, using the AWS CLI, run the following command:
271
+
272
+
```sh
273
+
aws secretsmanager create-secret \
274
+
--name <secret-name> \
275
+
--secret-binary fileb://<path-to-client-key> \
276
+
--kms-key-id <encryption-key-arn>
277
+
```
278
+
279
+
Where:
280
+
- `<secret-name>` - Name of the secret
281
+
- `<path-to-client-key>` - Path to the client key file
282
+
- `<encryption-key-arn>` - ARN of the [encryption key](#create-encryption-key) you created earlier
283
+
284
+
After you create the secret, you need to add permissions to allow the data pipeline to access it. In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Security, Identity, and Compliance** > **Secrets Manager**. Select the private key secret you just created and then select **Edit permissions**. Add the following permissions to your secret:
285
+
286
+
{{< embed-md "rc-rdi-secrets-permissions.md" >}}
287
+
288
+
Replace `<AWS ACCOUNT ID>` with the AWS account ID for the Redis Cloud cluster that you saved earlier.
289
+
290
+
--tab-sep--
291
+
292
+
In the [AWS Management Console](https://console.aws.amazon.com/), use the **Services** menu to locate and select **Security, Identity, and Compliance** > **Secrets Manager**. [Create a secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html) of type **Other type of secret** with the following settings:
293
+
294
+
- **Key/value pairs**: Select **Plaintext** and enter the client key passphrase.
After you store this secret, you can view and copy the [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#iam-resources) of your secret on the secret details page.
0 commit comments