AWS neptune documentation change
Summary
Corrected multiple documentation URLs and fixed a malformed CloudWatch metrics link
Security assessment
Changes focus on fixing broken links and URL formatting. Retry strategy guidance remains unchanged with no security impact.
Diff
diff --git a/neptune/latest/userguide/transactions-exceptions.md b/neptune/latest/userguide/transactions-exceptions.md index 2a120b193..8fff780c2 100644 --- a//neptune/latest/userguide/transactions-exceptions.md +++ b//neptune/latest/userguide/transactions-exceptions.md @@ -32 +32 @@ To build a resilient and efficient application, develop a retry strategy that's - * **Identify retryable errors** – Not all exceptions should be retried. For example, syntax errors, authentication failures, or invalid queries should not trigger a retry. Neptune provides [error codes](https://docs.aws.amazon.com/neptune/latest/userguide/errors-engine-codes.html) and general recommendations for which errors are safe to retry, but you need to implement the logic that fits your use case. + * **Identify retryable errors** – Not all exceptions should be retried. For example, syntax errors, authentication failures, or invalid queries should not trigger a retry. Neptune provides [error codes](https://docs.aws.amazon.com//neptune/latest/userguide/errors-engine-codes.html) and general recommendations for which errors are safe to retry, but you need to implement the logic that fits your use case. @@ -84 +84 @@ This CloudWatch metric tracks the number of requests waiting in Neptune's input -Other [Neptune metrics](https://docs.aws.amazon.com/https://docs.aws.amazon.com/neptune/latest/userguide/cw-metrics.html) like `CPUUtilization`, `TotalRequestsPerSecond`, and query latency provide additional context. For example, high CPU and I/O combined with growing queue lengths might indicate that your cluster is overloaded or that queries are too large or too frequent. [CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) can be set on these metrics to alert you to abnormal behavior and help you correlate spikes in errors or retries with underlying resource constraints. +Other [Neptune metrics](https://docs.aws.amazon.com/neptune/latest/userguide/cw-metrics.html) like `CPUUtilization`, `TotalRequestsPerSecond`, and query latency provide additional context. For example, high CPU and I/O combined with growing queue lengths might indicate that your cluster is overloaded or that queries are too large or too frequent. [CloudWatch alarms](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) can be set on these metrics to alert you to abnormal behavior and help you correlate spikes in errors or retries with underlying resource constraints. @@ -88 +88 @@ Other [Neptune metrics](https://docs.aws.amazon.com/https://docs.aws.amazon.com/ -The Neptune [Status API for Gremlin](https://docs.aws.amazon.com/neptune/latest/userguide/gremlin-api-status.html) and its analogous APIs for [OpenCypher](https://docs.aws.amazon.com/neptune/latest/userguide/access-graph-opencypher-status.html) and [SPARQL](https://docs.aws.amazon.com/neptune/latest/userguide/sparql-api-status.html) give a real-time view of the queries accepted and running on the cluster which is useful for diagnosing bottlenecks or understanding the impact of retry logic in real time. +The Neptune [Status API for Gremlin](https://docs.aws.amazon.com//neptune/latest/userguide/gremlin-api-status.html) and its analogous APIs for [OpenCypher](https://docs.aws.amazon.com//neptune/latest/userguide/access-graph-opencypher-status.html) and [SPARQL](https://docs.aws.amazon.com//neptune/latest/userguide/sparql-api-status.html) give a real-time view of the queries accepted and running on the cluster which is useful for diagnosing bottlenecks or understanding the impact of retry logic in real time.