AWS Control Plane vs Data Plane

Most cloud services are separated into two logic areas - data planes and control planes.

Think of it as an architectural pattern e.g the control plane defines the instructions , the data plane fulfills the instructions

Control Plane - supply the APIs to create\read\update\delete\list services

e.g Provision a new RDS Instance  - the control plane deals with finding capacity , database provisioning , track the db instance state

Data Plane - providing the services main function. The RDS Instance in our example is where the DB runs 

This is a  link to an AWS resource  with in-depth  discussion of Control Plane & Data Plane 

REL11-BP04 Rely on the data plane and not the control plane during recovery

A key concept is preventative mitigation i.e decrease\eliminate dependencies on the control plance , and instead increase dependency on the data plane , & therefore decreasing the possibility of single points of failure. It's a trade off ,  what  is the RPO\RTO and associated budget ?

An AWS Reading list

https://docs.aws.amazon.com/whitepapers/latest/advanced-multi-az-resilience-patterns/availability-zone-independence.html

• REL11-BP01 Monitor all components of the workload to detect failures
• REL11-BP02 Fail over to healthy resources
• REL11-BP03 Automate healing on all layers
• REL11-BP04 Rely on the data plane and not the control plane during recovery
• REL11-BP05 Use static stability to prevent bimodal behavior
• REL11-BP06 Send notifications when events impact availability
• REL11-BP07 Architect your product to meet availability targets and uptime service level agreements (SLAs)
• https://docs.aws.amazon.com/prescriptive-guidance/latest/resilience-analysis-framework/mitigation-strategies.html
• https://docs.aws.amazon.com/whitepapers/latest/aws-fault-isolation-boundaries/appendix-a---partitional-service-guidance.html