AWS neptune-analytics medium security documentation change
Summary
Added multiple entries including a fix for database shutdown when accessing S3 without proper permissions.
Security assessment
The resolved issue where the database shut down due to improper S3 permissions addresses a potential denial of service vulnerability caused by insufficient access controls.
Diff
diff --git a/neptune-analytics/latest/userguide/doc-history.md b/neptune-analytics/latest/userguide/doc-history.md index 910335c54..1df9dee13 100644 --- a//neptune-analytics/latest/userguide/doc-history.md +++ b//neptune-analytics/latest/userguide/doc-history.md @@ -10,0 +11,7 @@ Change| Description| Date +Query update| Resolved an issue where using a `WITH` clause that contained an asterisk (`*`) and aliasing expressions caused incorrect query parsing in OpenCypher. | April 28, 2025 +Graph algorithm updates| Neptune Analytics now offers the Louvain algorithm. Additionally, the `personalization` parameter has been added to the pageRank algorithm. | April 28, 2025 +Graph algorithm bug fix| Resolved an issue in `pg_info` where labelless vertices were being counted incorrectly. | April 28, 2025 +Data operations bug fix| Resolved an issue in the bulk loader that caused `failOnError` to behave incorrectly when parsing embeddings. | April 28, 2025 +Data operations bug fix| The error messages in bulk load are now more user friendly. | April 28, 2025 +Data operations bug fix| Neptune Analytics is now reporting an error message if the csv lines are too long to load. Example error message: [ETL] Could not form a complete line for parsing. Please check if you are loading lines longer than 65535. | April 28, 2025 +Data operations bug fix| An issue was resolved that caused the database to be shut down when users tried to access files in Amazon S3 without the proper permissions. | April 28, 2025