Query Amazon Neptune with both openCypher and Gremlin endpoints and use EXPLAIN to diagnose slow graph traversals

Steps

1. Neptune exposes separate query endpoints: POST https://<cluster>:8182/openCypher for openCypher and POST https://<cluster>:8182/gremlin for Gremlin; both operate on the same property graph
2. Submit an openCypher query via the HTTP API: POST /openCypher with body {'query': 'MATCH (p:Person)-[:KNOWS]->(f:Person) WHERE p.name = $name RETURN f.name', 'parameters': {'name': 'Alice'}}
3. Submit a Gremlin query: POST /gremlin with body {'gremlin': 'g.V().has("Person","name","Alice").out("KNOWS").values("name")'}
4. Use Neptune's EXPLAIN endpoint to retrieve the query plan for openCypher: GET /openCypher/explain?query=<url-encoded-query> — examine the plan for full graph scans vs index lookups
5. Create property indexes to avoid full vertex scans: Neptune uses an index on all vertex/edge property values by default (SPO/OSP index structure); ensure filter predicates match indexed properties
6. Monitor slow queries in CloudWatch Logs by enabling Neptune audit and query logs; filter for queries exceeding a latency threshold