AWS Security ChangesHomeSearch

AWS neptune-analytics documentation change

Service: neptune-analytics · 2026-03-13 · Documentation low

File: neptune-analytics/latest/userguide/scc.md

Summary

Reorganized example descriptions and fixed grammatical error in MATCH clause warning

Security assessment

Restructuring examples and grammar fixes do not indicate security-related changes. The MATCH clause warning reiterates performance guidance, not security mitigations.

Diff

diff --git a/neptune-analytics/latest/userguide/scc.md b/neptune-analytics/latest/userguide/scc.md
index dcbee539f..b5e829690 100644
--- a//neptune-analytics/latest/userguide/scc.md
+++ b//neptune-analytics/latest/userguide/scc.md
@@ -69 +69 @@ If the input node list is empty, the output is empty.
-This openCypher query has an empty input list, and so will have no output:
+This is a query integration example, where `.scc` follows a `MATCH` clause that generates its input node list:
@@ -77 +77 @@ This openCypher query has an empty input list, and so will have no output:
-This is a query integration example, where `.scc` follows a `MATCH` clause that generates its input node list:
+This is another query integration example:
@@ -87 +87 @@ This is a query integration example, where `.scc` follows a `MATCH` clause that
-It is not good practice to use `MATCH(n)` without restriction in query integrations. Keep in mind that every node returned by the `MATCH(n)` clause invokes the algorithm once, which can result a very long-running query if a large number of nodes is returned. Use `LIMIT` or put conditions on the `MATCH` clause to restrict its output appropriately.
+It is not good practice to use `MATCH(n)` without restriction in query integrations. Keep in mind that every node returned by the `MATCH(n)` clause invokes the algorithm once, which can result in a very long-running query if a large number of nodes is returned. Use `LIMIT` or put conditions on the `MATCH` clause to restrict its output appropriately.
@@ -96 +96 @@ Here is an example of the output returned by .scc when run against the [ sample
-      --query-string "CALL neptune.algo.scc({writeProperty: 'sccid'}) YIELD success RETURN success" \
+      --query-string "MATCH (n) CALL neptune.algo.scc(n) YIELD node, component RETURN node, component LIMIT 2" \