AWS athena documentation change
Summary
Fixed apostrophe encoding in security advice and query documentation
Security assessment
Typo fixes in existing security recommendations about credential handling. Does not introduce new security content
Diff
diff --git a/athena/latest/ug/connectors-vertica.md b/athena/latest/ug/connectors-vertica.md index 2a1c5b949..652606ae7 100644 --- a//athena/latest/ug/connectors-vertica.md +++ b//athena/latest/ug/connectors-vertica.md @@ -151 +151 @@ To provide a user name and password for your database in your JDBC connection st -As a security best practice, don&t use hardcoded credentials in your environment variables or connection strings. For information about moving your hardcoded secrets to AWS Secrets Manager, see [Move hardcoded secrets to AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/hardcoded.html) in the _AWS Secrets Manager User Guide_. +As a security best practice, don't use hardcoded credentials in your environment variables or connection strings. For information about moving your hardcoded secrets to AWS Secrets Manager, see [Move hardcoded secrets to AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/hardcoded.html) in the _AWS Secrets Manager User Guide_. @@ -208 +208 @@ TimeStamp as Varchar -The Lambda function performs projection pushdown to decrease the data scanned by the query. `LIMIT` clauses reduce the amount of data scanned, but if you don&t provide a predicate, you should expect `SELECT` queries with a `LIMIT` clause to scan at least 16 MB of data. The Vertica connector is resilient to throttling due to concurrency. +The Lambda function performs projection pushdown to decrease the data scanned by the query. `LIMIT` clauses reduce the amount of data scanned, but if you don't provide a predicate, you should expect `SELECT` queries with a `LIMIT` clause to scan at least 16 MB of data. The Vertica connector is resilient to throttling due to concurrency.