AWS prescriptive-guidance documentation change
Summary
Removed blank lines and consolidated paragraphs without altering content. Merged two sections about Neptune version updates and cost considerations into single paragraphs.
Security assessment
The changes are purely formatting/structural with no security-related content modifications. No vulnerabilities, security features, or incidents are mentioned. The content remains focused on general best practices for version updates and cost management.
Diff
diff --git a/prescriptive-guidance/latest/multi-tenancy-amazon-neptune/best-practices.md b/prescriptive-guidance/latest/multi-tenancy-amazon-neptune/best-practices.md index 7b5e42b7c..b4b809ad4 100644 --- a//prescriptive-guidance/latest/multi-tenancy-amazon-neptune/best-practices.md +++ b//prescriptive-guidance/latest/multi-tenancy-amazon-neptune/best-practices.md @@ -15,3 +15 @@ Many of the guidelines in this section are best practices for all customers, but -In the Amazon Neptune [release notes](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html), you can see that every version brings a number of bug fixes, performance improvements, and new features. Keep your Neptune clusters on the latest version as much as possible. - -If you find a previously undiscovered bug in your workload and your cluster is on the latest version, Neptune engineers can create a private patch for your cluster (if warranted and you want it). The patch can bridge until the next release when that fix will be generally available. To help with updating your clusters to the newest version, use the [Neptune Blue/Green solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html). +In the Amazon Neptune [release notes](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html), you can see that every version brings a number of bug fixes, performance improvements, and new features. Keep your Neptune clusters on the latest version as much as possible. If you find a previously undiscovered bug in your workload and your cluster is on the latest version, Neptune engineers can create a private patch for your cluster (if warranted and you want it). The patch can bridge until the next release when that fix will be generally available. To help with updating your clusters to the newest version, use the [Neptune Blue/Green solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html). @@ -31,3 +29 @@ We highly recommend that you develop a way to calculate the true delta of what h -Whether you use a silo, pool, or hybrid model, your cloud costs will scale with your tenants' size. Tenants that require more concurrent connections need larger instances or more read replicas than those with fewer concurrent connections. The same applies to tenants that require more rapid data ingestion. - -The three components of Neptune cluster cost are instance size (and number), data size (GB-months), and I/O operations (per million). While these costs are generally workload specific, they scale with size and data volume, they can be measured by using AWS tools. Track and understand the economies of scale against key indicators of your tenants' sizes, including how their sizes vary over time. If the unpredictability of your I/O charges impacts your margins, consider choosing [Neptune I/O-Optimized](https://docs.aws.amazon.com/neptune/latest/userguide/storage-types.html) storage for a more predictable cost. +Whether you use a silo, pool, or hybrid model, your cloud costs will scale with your tenants' size. Tenants that require more concurrent connections need larger instances or more read replicas than those with fewer concurrent connections. The same applies to tenants that require more rapid data ingestion. The three components of Neptune cluster cost are instance size (and number), data size (GB-months), and I/O operations (per million). While these costs are generally workload specific, they scale with size and data volume, they can be measured by using AWS tools. Track and understand the economies of scale against key indicators of your tenants' sizes, including how their sizes vary over time. If the unpredictability of your I/O charges impacts your margins, consider choosing [Neptune I/O-Optimized](https://docs.aws.amazon.com/neptune/latest/userguide/storage-types.html) storage for a more predictable cost.