AWS glue documentation change
Summary
Modified Secrets Manager documentation URL formatting with additional slash
Security assessment
Purely a URL syntax change without any modification to security recommendations. The existing security practice of storing credentials in Secrets Manager remains unaffected.
Diff
diff --git a/glue/latest/dg/creating-teradata-connection.md b/glue/latest/dg/creating-teradata-connection.md index 79a5617d5..bd6a70a46 100644 --- a//glue/latest/dg/creating-teradata-connection.md +++ b//glue/latest/dg/creating-teradata-connection.md @@ -24 +24 @@ Based on your network layout, secure VPC connectivity may require changes in Ama - 2. In AWS Secrets Manager, create a secret using your Teradata credentials. To create a secret in Secrets Manager, follow the tutorial available in [ Create an AWS Secrets Manager secret ](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html) in the AWS Secrets Manager documentation. After creating the secret, keep the Secret name, `secretName` for the next step. + 2. In AWS Secrets Manager, create a secret using your Teradata credentials. To create a secret in Secrets Manager, follow the tutorial available in [ Create an AWS Secrets Manager secret ](https://docs.aws.amazon.com//secretsmanager/latest/userguide/create_secret.html) in the AWS Secrets Manager documentation. After creating the secret, keep the Secret name, `secretName` for the next step.