AWS prescriptive-guidance documentation change
Summary
Updated navigation link from 'welcome.html' to 'introduction.html', removed backticks from SQL commands, changed apostrophe formatting, and updated image path
Security assessment
Changes are cosmetic (link updates, typography fixes, image path adjustment) with no security implications. No vulnerability fixes or security enhancements were introduced.
Diff
diff --git a/prescriptive-guidance/latest/saas-multitenant-managed-postgresql/pool.md b/prescriptive-guidance/latest/saas-multitenant-managed-postgresql/pool.md index a917e9373..96de478af 100644 --- a//prescriptive-guidance/latest/saas-multitenant-managed-postgresql/pool.md +++ b//prescriptive-guidance/latest/saas-multitenant-managed-postgresql/pool.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Implementing managed PostgreSQL for multi-tenant SaaS applications on AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Implementing managed PostgreSQL for multi-tenant SaaS applications on AWS](introduction.html) @@ -9 +9 @@ -The pool model is implemented by provisioning a single PostgreSQL instance (Amazon RDS or Aurora) and using [row-level security (RLS)](https://aws.amazon.com/blogs/database/multi-tenant-data-isolation-with-postgresql-row-level-security/) to maintain tenant data isolation. RLS policies restrict which rows in a table are returned by `SELECT` queries or which rows are affected by `INSERT`, `UPDATE`, and `DELETE` commands. The pool model centralizes all tenant data in a single PostgreSQL schema, so it is significantly more cost-effective and requires less operational overhead to maintain. Monitoring this solution is also significantly simpler due to its centralization. However, monitoring tenant-specific impacts in the pool model usually requires some additional instrumentation in the application. This is because PostgreSQL by default isn’t aware of which tenant is consuming resources. Tenant onboarding is simplified because no new infrastructure is required. This agility makes it easier to accomplish rapid and automated tenant onboarding workflows. +The pool model is implemented by provisioning a single PostgreSQL instance (Amazon RDS or Aurora) and using [row-level security (RLS)](https://aws.amazon.com/blogs/database/multi-tenant-data-isolation-with-postgresql-row-level-security/) to maintain tenant data isolation. RLS policies restrict which rows in a table are returned by SELECT queries or which rows are affected by INSERT, UPDATE, and DELETE commands. The pool model centralizes all tenant data in a single PostgreSQL schema, so it is significantly more cost-effective and requires less operational overhead to maintain. Monitoring this solution is also significantly simpler due to its centralization. However, monitoring tenant-specific impacts in the pool model usually requires some additional instrumentation in the application. This is because PostgreSQL by default isn't aware of which tenant is consuming resources. Tenant onboarding is simplified because no new infrastructure is required. This agility makes it easier to accomplish rapid and automated tenant onboarding workflows. @@ -11 +11 @@ The pool model is implemented by provisioning a single PostgreSQL instance (Amaz - +