AWS prescriptive-guidance documentation change
Summary
Updated navigation link, fixed apostrophe formatting, emphasized security constraints, and changed image path
Security assessment
Changes are cosmetic (link update, apostrophe correction) and formatting (emphasis). No security vulnerability or weakness is addressed. Image path change doesn't impact security content.
Diff
diff --git a/prescriptive-guidance/latest/saas-multitenant-managed-postgresql/silo.md b/prescriptive-guidance/latest/saas-multitenant-managed-postgresql/silo.md index 98bb76c16..2fb73003c 100644 --- a//prescriptive-guidance/latest/saas-multitenant-managed-postgresql/silo.md +++ b//prescriptive-guidance/latest/saas-multitenant-managed-postgresql/silo.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 silo model is implemented by provisioning a PostgreSQL instance for each tenant in an application. The silo model excels at tenant performance and security isolation, and completely eliminates the _noisy neighbor_ phenomenon. The noisy neighbor phenomenon occurs when one tenant’s usage of a system affects the performance of another tenant. The silo model lets you tailor performance specifically to each tenant and potentially limit outages to a specific tenant’s silo. However, what generally drives adoption of a silo model is strict security and regulatory constraints. These constraints can be motivated by SaaS customers. For example, SaaS customers might demand that their data be isolated due to internal constraints, and SaaS providers might offer such a service for an additional fee. +The silo model is implemented by provisioning a PostgreSQL instance for each tenant in an application. The silo model excels at tenant performance and security isolation, and completely eliminates the _noisy neighbor_ phenomenon. The noisy neighbor phenomenon occurs when one tenant's usage of a system affects the performance of another tenant. The silo model lets you tailor performance specifically to each tenant and potentially limit outages to a specific tenant's silo. However, what generally drives adoption of a silo model is _strict security and regulatory constraints_. These constraints can be motivated by SaaS customers. For example, SaaS customers might demand that their data be isolated due to internal constraints, and SaaS providers might offer such a service for an additional fee. @@ -11 +11 @@ The silo model is implemented by provisioning a PostgreSQL instance for each ten - +