AWS prescriptive-guidance documentation change
Summary
Added FAQ section addressing applicability of recommendations to monolithic mainframe databases
Security assessment
The change adds guidance about decomposing mainframe databases but does not mention security controls, vulnerabilities, or security-related configurations. The focus is on methodology applicability rather than security aspects.
Diff
diff --git a/prescriptive-guidance/latest/database-decomposition/faq-scope.md b/prescriptive-guidance/latest/database-decomposition/faq-scope.md index c8d1cbcfa..f65337b7a 100644 --- a//prescriptive-guidance/latest/database-decomposition/faq-scope.md +++ b//prescriptive-guidance/latest/database-decomposition/faq-scope.md @@ -5 +5 @@ -How detailed should the initial scope definition be?What if I discover additional dependencies after starting the project?How do I handle stakeholders from different departments who have conflicting requirements?What's the best way to assess technical constraints when documentation is poor or outdated?How do I balance immediate business needs with long-term technical goals?How do I make sure that I'm not missing critical requirements from silent stakeholders? +How detailed should the initial scope definition be?What if I discover additional dependencies after starting the project?How do I handle stakeholders from different departments who have conflicting requirements?What's the best way to assess technical constraints when documentation is poor or outdated?How do I balance immediate business needs with long-term technical goals?How do I make sure that I'm not missing critical requirements from silent stakeholders?Do these recommendations apply for monolithic mainframe databases? @@ -24,0 +25,2 @@ The [Defining the scope and requirements for database decomposition](./scope.htm + * Do these recommendations apply for monolithic mainframe databases? + @@ -57,0 +60,4 @@ Conduct regular validation sessions with both vocal and quiet stakeholders, and +## Do these recommendations apply for monolithic mainframe databases? + +The methodology described in this guide also applies to decomposing monolithic mainframe databases. The primary challenges with these databases are managing requirements from the various stakeholders. The technology recommendations in this guide might apply to monolithic mainframe databases. If the mainframe has a relational database, such as an online transaction processing (OLTP) database, then many of the recommendations apply. For online analytical processing (OLAP) databases, such as those used to generate business reports, then only some of the recommendations apply. +