AWS redshift documentation change
Summary
Updated links to Amazon S3 documentation, changing paths from 'dev' to 'userguide'.
Security assessment
The changes are documentation URL updates without altering security-related content. No evidence of addressing a security vulnerability or adding security features.
Diff
diff --git a/redshift/latest/dg/c-spectrum-troubleshooting.md b/redshift/latest/dg/c-spectrum-troubleshooting.md index 7b2f94d67..b1e4d505b 100644 --- a//redshift/latest/dg/c-spectrum-troubleshooting.md +++ b//redshift/latest/dg/c-spectrum-troubleshooting.md @@ -74 +74 @@ The error context provides more details about the type of throttling. Following, -Amazon S3 might throttle a Redshift Spectrum request if the read request rate on a [prefix](https://docs.aws.amazon.com/glossary/latest/reference/glos-chap.html#keyprefix) is too high. For information about a GET/HEAD request rate that you can achieve in Amazon S3, see [Optimizing Amazon S3 Performance](https://docs.aws.amazon.com/AmazonS3/latest/dev/optimizing-performance.html) in _Amazon Simple Storage Service User Guide._ The Amazon S3 GET/HEAD request rate takes into account all GET/HEAD requests on a prefix so different applications accessing the same prefix share the total requests rate. +Amazon S3 might throttle a Redshift Spectrum request if the read request rate on a [prefix](https://docs.aws.amazon.com/glossary/latest/reference/glos-chap.html#keyprefix) is too high. For information about a GET/HEAD request rate that you can achieve in Amazon S3, see [Optimizing Amazon S3 Performance](https://docs.aws.amazon.com/AmazonS3/latest/userguide/optimizing-performance.html) in _Amazon Simple Storage Service User Guide._ The Amazon S3 GET/HEAD request rate takes into account all GET/HEAD requests on a prefix so different applications accessing the same prefix share the total requests rate. @@ -82 +82 @@ Also consider partitioning your Redshift Spectrum tables to benefit from early f -If you store your data in Amazon S3 using server-side encryption (SSE-S3 or SSE-KMS), Amazon S3 calls an API operation to AWS KMS for each file that Redshift Spectrum accesses. These requests count toward your cryptographic operations quota; for more information, see [AWS KMS Request Quotas](https://docs.aws.amazon.com/kms/latest/developerguide/requests-per-second.html). For more information on SSE-S3 and SSE-KMS, see [Protecting Data Using Server-Side Encryption](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html) and [Protecting Data Using Server-Side Encryption with KMS keys Stored in AWS KMS](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html) in _Amazon Simple Storage Service User Guide._ +If you store your data in Amazon S3 using server-side encryption (SSE-S3 or SSE-KMS), Amazon S3 calls an API operation to AWS KMS for each file that Redshift Spectrum accesses. These requests count toward your cryptographic operations quota; for more information, see [AWS KMS Request Quotas](https://docs.aws.amazon.com/kms/latest/developerguide/requests-per-second.html). For more information on SSE-S3 and SSE-KMS, see [Protecting Data Using Server-Side Encryption](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingServerSideEncryption.html) and [Protecting Data Using Server-Side Encryption with KMS keys Stored in AWS KMS](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html) in _Amazon Simple Storage Service User Guide._