Operational excellence pillar is intended to improve how teams operate, monitor and continually refine workloads because operational excellence focuses on delivering business value through effective operations and continuous learning; in this design the new outcome is to reduce the blast radius and rollback effort of deployments, which calls for Small reversible changes rather than Operational excellence pillar or the earlier Operations as code.

Operations as code primarily supports the earlier need to apply controlled repeatable procedures to infrastructure and operations because machine-readable definitions allow review, versioning and consistent execution of operations, but the new task is to reduce the blast radius and rollback effort of deployments; that is why Small reversible changes is preferable here.

Security pillar is intended to protect information, systems and assets using risk-aware controls because the security pillar addresses identities, detection, infrastructure and data protection, and incident response; in this design the new outcome is to reduce the blast radius and rollback effort of deployments, which calls for Small reversible changes rather than Security pillar or the earlier Operations as code.

Operating expenditure (OpEx) is intended to treat recurring service consumption as a running operational cost because opEx reflects spending as services and computing resources are consumed; in this design the new outcome is to avoid running nonproduction compute unnecessarily, which calls for Automation of shutdown schedules rather than Operating expenditure (OpEx) or the earlier Demand forecasting.

Savings Plans commitment is intended to obtain eligible compute discounts in exchange for a spending commitment because savings Plans provide discounts for qualifying usage during a commitment term; in this design the new outcome is to avoid running nonproduction compute unnecessarily, which calls for Automation of shutdown schedules rather than Savings Plans commitment or the earlier Demand forecasting.

Demand forecasting primarily supports the earlier need to estimate future usage to avoid unplanned commitment or capacity decisions because forecasts help teams plan spend and procurement based on usage trends, but the new task is to avoid running nonproduction compute unnecessarily; that is why Automation of shutdown schedules is preferable here.

Resource pooling addresses the separate need to benefit from provider-managed shared infrastructure without operating a dedicated facility because cloud providers abstract and share large infrastructure fleets while logically isolating customers; it is not as direct as On-demand resource availability for the actual requirement to obtain computing resources when a new workload is ready to launch.

Global reach addresses the separate need to serve customers in distant geographies with regional deployments because AWS Regions allow workloads to run closer to users in multiple geographic markets; it is not as direct as On-demand resource availability for the actual requirement to obtain computing resources when a new workload is ready to launch.

Fault tolerance addresses the separate need to continue operating despite an individual infrastructure component failing because fault-tolerant systems absorb failures using redundancy, isolation and suitable application behavior; it is not as direct as On-demand resource availability for the actual requirement to obtain computing resources when a new workload is ready to launch.

AWS CAF Security perspective is intended to embed protection, risk practices and security capabilities into migration because the Security perspective helps establish security governance and resilient protective controls; in this design the new outcome is to modify an application to exploit cloud-native capabilities more substantially, which calls for Refactor or re-architect rather than AWS CAF Security perspective or the earlier AWS Prescriptive Guidance.

Rehost (lift and shift) is intended to move an application to cloud infrastructure with minimal redesign because rehosting relocates a workload while largely preserving its existing architecture; in this design the new outcome is to modify an application to exploit cloud-native capabilities more substantially, which calls for Refactor or re-architect rather than Rehost (lift and shift) or the earlier AWS Prescriptive Guidance.

AWS Prescriptive Guidance primarily supports the earlier need to find practical AWS migration patterns and implementation guidance because prescriptive Guidance provides proven strategies and technical patterns for cloud adoption, but the new task is to modify an application to exploit cloud-native capabilities more substantially; that is why Refactor or re-architect is preferable here.

Reliability pillar addresses the separate need to help a workload recover from failures and continue functioning correctly because reliability covers recovery, capacity planning and resilience to infrastructure or service disruption; it is not as direct as Operational excellence pillar for the actual requirement to improve how teams operate, monitor and continually refine workloads.

Vertical scaling addresses the separate need to increase the capacity of an existing compute resource because vertical scaling changes the size or power of one instance or server; it is not as direct as Operational excellence pillar for the actual requirement to improve how teams operate, monitor and continually refine workloads.

Design for failure addresses the separate need to plan for individual components or zones becoming unavailable because resilient cloud designs anticipate disruption and use isolation and recovery behavior; it is not as direct as Operational excellence pillar for the actual requirement to improve how teams operate, monitor and continually refine workloads.

Reduced undifferentiated heavy lifting addresses the separate need to spend less staff effort maintaining generic infrastructure components because managed AWS services take over selected operational tasks such as platform maintenance; it is not as direct as Scalability for the actual requirement to support larger workloads by adding capacity as requirements grow.

Global reach addresses the separate need to serve customers in distant geographies with regional deployments because AWS Regions allow workloads to run closer to users in multiple geographic markets; it is not as direct as Scalability for the actual requirement to support larger workloads by adding capacity as requirements grow.

Automation consistency addresses the separate need to repeat routine resource provisioning with fewer manual variations because automation applies repeatable processes rather than relying on individual manual changes; it is not as direct as Scalability for the actual requirement to support larger workloads by adding capacity as requirements grow.

Return on investment (ROI) addresses the separate need to evaluate expected financial benefit relative to an investment because rOI compares gains with associated investment costs for a business decision; it is not as direct as Demand forecasting for the actual requirement to estimate future usage to avoid unplanned commitment or capacity decisions.

Bring Your Own License (BYOL) addresses the separate need to reuse eligible existing software licenses under applicable provider terms because bYOL can let a customer apply eligible licenses to suitable cloud deployments; it is not as direct as Demand forecasting for the actual requirement to estimate future usage to avoid unplanned commitment or capacity decisions.

Economies of scale addresses the separate need to benefit from infrastructure purchasing and operations at provider scale because large cloud providers can spread infrastructure costs across broad demand and procurement volumes; it is not as direct as Demand forecasting for the actual requirement to estimate future usage to avoid unplanned commitment or capacity decisions.

Avoided data-center costs addresses the separate need to reduce expenses for facility space, power, cooling and physical maintenance because migrating suitable workloads can shift responsibility for physical facility operation to AWS; it is not as direct as Demand forecasting for the actual requirement to estimate future usage to avoid unplanned commitment or capacity decisions.

Migration dependency mapping addresses the separate need to identify which applications and infrastructure components rely on one another because dependency discovery helps group and sequence migrations to avoid broken integrations; it is not as direct as AWS Migration Hub for the actual requirement to track migration progress across applications and migration tools.

AWS Application Migration Service addresses the separate need to replicate source servers for a largely lift-and-shift migration because application Migration Service supports server migration with continuous replication and automated conversion to run on AWS; it is not as direct as AWS Migration Hub for the actual requirement to track migration progress across applications and migration tools.

AWS CAF Security perspective addresses the separate need to embed protection, risk practices and security capabilities into migration because the Security perspective helps establish security governance and resilient protective controls; it is not as direct as AWS Migration Hub for the actual requirement to track migration progress across applications and migration tools.

AWS Migration Hub is intended to track migration progress across applications and migration tools because migration Hub helps provide visibility across a portfolio's migration activity; in this design the new outcome is to collect information about on-premises servers and dependencies for migration planning, which calls for AWS Application Discovery Service rather than AWS Migration Hub or the earlier AWS Application Migration Service.

AWS Application Migration Service primarily supports the earlier need to replicate source servers for a largely lift-and-shift migration because application Migration Service supports server migration with continuous replication and automated conversion to run on AWS, but the new task is to collect information about on-premises servers and dependencies for migration planning; that is why AWS Application Discovery Service is preferable here.

AWS Schema Conversion Tool (AWS SCT) is intended to convert database schema and code for a heterogeneous database migration because AWS SCT helps transform schema objects and certain database code between supported engines; in this design the new outcome is to collect information about on-premises servers and dependencies for migration planning, which calls for AWS Application Discovery Service rather than AWS Schema Conversion Tool (AWS SCT) or the earlier AWS Application Migration Service.

Resource pooling addresses the separate need to benefit from provider-managed shared infrastructure without operating a dedicated facility because cloud providers abstract and share large infrastructure fleets while logically isolating customers; it is not as direct as Self-service provisioning for the actual requirement to create an environment without waiting for physical equipment installation.

Global reach addresses the separate need to serve customers in distant geographies with regional deployments because AWS Regions allow workloads to run closer to users in multiple geographic markets; it is not as direct as Self-service provisioning for the actual requirement to create an environment without waiting for physical equipment installation.

Managed-service operational relief addresses the separate need to avoid administering an underlying platform for a common workload because managed services move specific tasks such as database engine patching to AWS; it is not as direct as Self-service provisioning for the actual requirement to create an environment without waiting for physical equipment installation.