AWS medialive documentation change
Summary
Updated passphrase storage instructions with direct Secrets Manager documentation link and secret type specification
Security assessment
Improved documentation for security practice (secret management) but no evidence of addressing specific security vulnerability. Adds clarity to existing security feature implementation.
Diff
diff --git a/medialive/latest/ug/input-caller-srt-prereqs.md b/medialive/latest/ug/input-caller-srt-prereqs.md index 66e0add7f..33ba68d9c 100644 --- a//medialive/latest/ug/input-caller-srt-prereqs.md +++ b//medialive/latest/ug/input-caller-srt-prereqs.md @@ -21 +21 @@ Obtain the passphrase from the operator of the upstream system. - 2. If the content is encrypted, you must store the passphrase that the operator gave you. Someone in your organization must store the passphrase in a secret in AWS Secrets Manager. For more information, see [Storing an encryption or decryption passphrase ](./encryption-srt-password.html). The result of creating the secret is an ARN that looks like this: + 2. If the content is encrypted, you must store the passphrase that the operator gave you. Someone in your organization must store the passphrase in a secret in AWS Secrets Manager. For more information, see [Create an AWS Secrets Manager secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html). Create a secret of type **Other type of secret**. The result of creating the secret is an ARN that looks like this: