AWS transcribe documentation change
Summary
Updated documentation links by adding double slashes after the domain in AWS KMS and Transcribe API references
Security assessment
The changes only modify URL paths (adding '//' after docs.aws.amazon.com) without altering security content, permissions, or encryption practices. No vulnerability fixes or security enhancements are mentioned.
Diff
diff --git a/transcribe/latest/dg/health-scribe-encryption-customer.md b/transcribe/latest/dg/health-scribe-encryption-customer.md index 32c6d1c58..2734b5ed5 100644 --- a//transcribe/latest/dg/health-scribe-encryption-customer.md +++ b//transcribe/latest/dg/health-scribe-encryption-customer.md @@ -9 +9 @@ AWS KMS key policies for AWS HealthScribeIAM policy permissions for access roles -You can create a symmetric customer managed key by using the AWS Management Console, or the AWS KMS APIs. To create a symmetric customer managed key, follow the steps for [Creating symmetric customer managed key](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html#create-symmetric-cmk) in the AWS Key Management Service Developer Guide. +You can create a symmetric customer managed key by using the AWS Management Console, or the AWS KMS APIs. To create a symmetric customer managed key, follow the steps for [Creating symmetric customer managed key](https://docs.aws.amazon.com//kms/latest/developerguide/create-keys.html#create-symmetric-cmk) in the AWS Key Management Service Developer Guide. @@ -11 +11 @@ You can create a symmetric customer managed key by using the AWS Management Cons -Key policies control access to your customer managed key. Every customer managed key must have exactly one key policy, which contains statements that determine who can use the key and how they can use it. When you create your customer managed key, you can specify a key policy. For more information, see [Managing access to customer managed keys](https://docs.aws.amazon.com/kms/latest/developerguide/control-access-overview.html#managing-access) in the AWS Key Management Service Developer Guide. +Key policies control access to your customer managed key. Every customer managed key must have exactly one key policy, which contains statements that determine who can use the key and how they can use it. When you create your customer managed key, you can specify a key policy. For more information, see [Managing access to customer managed keys](https://docs.aws.amazon.com//kms/latest/developerguide/control-access-overview.html#managing-access) in the AWS Key Management Service Developer Guide. @@ -15 +15 @@ Key policies control access to your customer managed key. Every customer managed -If you are using a key in the same account as the IAM role you specify as the `DataAccessRole` in your [StartMedicalScribeJob](https://docs.aws.amazon.com/transcribe/latest/APIReference/API_StartMedicalScribeJob.html) or `ResourceAccessRole` in your [StartMedicalScribeStream](https://docs.aws.amazon.com/transcribe/latest/APIReference/API_streaming_StartMedicalScribeStream.html) request, you don't need to update the Key Policy. To use your customer managed key in a different account as your DataAccessRole (for transcription jobs) or ResourceAccessRole (for streaming), you must trust the respective role in the Key Policy for the following actions: +If you are using a key in the same account as the IAM role you specify as the `DataAccessRole` in your [StartMedicalScribeJob](https://docs.aws.amazon.com//transcribe/latest/APIReference/API_StartMedicalScribeJob.html) or `ResourceAccessRole` in your [StartMedicalScribeStream](https://docs.aws.amazon.com/transcribe/latest/APIReference/API_streaming_StartMedicalScribeStream.html) request, you don't need to update the Key Policy. To use your customer managed key in a different account as your DataAccessRole (for transcription jobs) or ResourceAccessRole (for streaming), you must trust the respective role in the Key Policy for the following actions: @@ -17 +17 @@ If you are using a key in the same account as the IAM role you specify as the `D - * [`kms:Encrypt`](https://docs.aws.amazon.com/kms/latest/APIReference/API_Encrypt.html) — Allows encryption using the customer managed key + * [`kms:Encrypt`](https://docs.aws.amazon.com//kms/latest/APIReference/API_Encrypt.html) — Allows encryption using the customer managed key @@ -19 +19 @@ If you are using a key in the same account as the IAM role you specify as the `D - * [`kms:Decrypt`](https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html) — Allows decryption using the customer managed key + * [`kms:Decrypt`](https://docs.aws.amazon.com//kms/latest/APIReference/API_Decrypt.html) — Allows decryption using the customer managed key @@ -21 +21 @@ If you are using a key in the same account as the IAM role you specify as the `D - * [`kms:DescribeKey`](https://docs.aws.amazon.com/kms/latest/APIReference/API_DescribeKey.html) — Provides the customer managed key details to allow AWS HealthScribe to validate the key + * [`kms:DescribeKey`](https://docs.aws.amazon.com//kms/latest/APIReference/API_DescribeKey.html) — Provides the customer managed key details to allow AWS HealthScribe to validate the key @@ -36 +36 @@ The following is trust policy example for the ResourceAccessRole. For DataAccess -For more information about [specifying permissions in a policy](https://docs.aws.amazon.com/kms/latest/developerguide/control-access-overview.html#overview-policy-elements) or [troubleshooting key access](https://docs.aws.amazon.com/kms/latest/developerguide/policy-evaluation.html#example-no-iam), see the AWS Key Management Service Developer Guide. +For more information about [specifying permissions in a policy](https://docs.aws.amazon.com//kms/latest/developerguide/control-access-overview.html#overview-policy-elements) or [troubleshooting key access](https://docs.aws.amazon.com//kms/latest/developerguide/policy-evaluation.html#example-no-iam), see the AWS Key Management Service Developer Guide.