ExamFinch.com My Study

Study guide

3.4 Shared Storage (EFS/FSx) & Database Performance

Practice this exam

AWS Certified CloudOps Engineer – Associate SOA-C03

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Monitoring & Observability Infrastructure

1.1 Configuring Workload Observability 1.2 CloudWatch Agent Architecture & Deployment 1.3 Metric Alarms, Anomaly Detection & Composite Alarms

2 Chapter 2: Alarms, Dashboards & Event-Driven Remediation

2.1 CloudWatch Dashboards & Multi-Account Visibility 2.2 Notification Architecture & Alarm Invocation 2.3 Amazon EventBridge Rules, Event Buses & Troubleshooting 2.4 Automated Remediation with Systems Manager & Lambda

3 Chapter 3: Performance Optimization for Compute, Storage & Databases

3.1 EC2 & Compute Performance Optimization 3.2 Amazon EBS Performance Metrics & Volume Tuning 3.3 S3 Performance Strategies & Data Transfer 3.4 Shared Storage (EFS/FSx) & Database Performance

4 Chapter 4: Compute & Database Scalability and Elasticity

4.1 EC2 Auto Scaling Policies & Elasticity 4.2 Auto Scaling Advanced Operations: Warm Pools & Lifecycle Hooks 4.3 Dynamic Scalability Through Caching 4.4 Managed Database Scaling: RDS, Aurora & DynamoDB

5 Chapter 5: High Availability, Fault Tolerance & Load Balancing

5.1 Elastic Load Balancing (ALB/NLB) Configuration & Troubleshooting 5.2 Route 53 Health Checks & DNS Failover 5.3 Multi-AZ Architecture & Fault-Tolerant Deployments

6 Chapter 6: Backup, Data Protection & Disaster Recovery

6.1 Centralized Backup Automation & AWS Backup 6.2 Database Restore Strategies & RTO/RPO Management 6.3 Storage Versioning, Replication & Immutability 6.4 Disaster Recovery Patterns & Multi-Region Resilience

7 Chapter 7: Infrastructure as Code with CloudFormation & AWS CDK

7.1 CloudFormation Foundations & Resource Modeling 7.2 Managing Stacks, Drift Detection & Change Sets 7.3 Infrastructure as Code with AWS CDK 7.4 Identifying & Remediating Deployment Failures

8 Chapter 8: Multi-Account Provisioning, Containers & Third-Party IaC

8.1 Golden Images with EC2 Image Builder & Amazon ECR 8.2 Multi-Account & Multi-Region Resource Sharing 8.3 Deployment Strategies & Container Deployments 8.4 Third-Party Automation with Terraform & Git Workflows

9 Chapter 9: Systems Manager & Event-Driven Operations Automation

9.1 AWS Systems Manager Core Management & Run Command 9.2 Systems Manager Patch Manager & Session Manager 9.3 Event-Driven Operations Automation

10 Chapter 10: Identity, Access Management & Governance

10.1 Advanced IAM Policies, Roles & Policy Conditions 10.2 Auditing Access with CloudTrail Lake & IAM Access Analyzer 10.3 Multi-Account Security: Organizations, SCPs & Identity Center 10.4 Compliance Enforcement with AWS Config & Conformance Packs

11 Chapter 11: Data Security, Encryption & Vulnerability Management

11.1 Data Classification & Amazon S3 Security 11.2 Encryption at Rest with AWS Key Management Service (KMS) 11.3 Encryption in Transit with AWS Certificate Manager (ACM) 11.4 Secrets Management & Centralized Security Findings

12 Chapter 12: VPC Architecture, Endpoints & Network Protection

12.1 VPC Core Architecture, Subnetting & High Availability NAT 12.2 Private Network Connectivity: VPC Endpoints & Peering 12.3 Network Protection & Edge Security Auditing

13 Chapter 13: DNS, Route 53 Routing & Content Delivery

13.1 DNS Architecture & Route 53 Resolver for Hybrid Clouds 13.2 Route 53 Advanced Routing Policies & Query Logging 13.3 Global Content & Service Distribution: CloudFront & Global Accelerator

14 Chapter 14: Network Troubleshooting, Traffic Analysis & Hybrid Connectivity

14.1 VPC Configuration Troubleshooting & Analysis Tools 14.2 Network Traffic Analysis: VPC Flow Logs & Log Analytics 14.3 CloudFront Caching & Hybrid Connectivity Troubleshooting

3.4 Shared Storage (EFS/FSx) & Database Performance

Key Takeaways Explain This Topic AI

Amazon EFS provides serverless, POSIX-compliant shared file storage supporting Elastic, Provisioned, and Bursting throughput modes, alongside General Purpose (low latency) and Max I/O (high concurrent scale) performance modes.

Amazon FSx provides purpose-built managed file storage, including FSx for Windows File Server (native SMB, Active Directory, DFS namespaces) and FSx for Lustre (ultra-high throughput and POSIX for HPC/ML integrated with S3).

Critical Amazon RDS CloudWatch metrics include CPUUtilization, DatabaseConnections, FreeableMemory, DiskQueueDepth, and read/write latency; persistent disk queue depth combined with elevated latency indicates storage subsystem bottlenecks.

RDS Performance Insights visualizes database load using Average Active Sessions (AAS) against the vCPU threshold line, categorizing bottlenecks into CPU, Lock, IO, and Network wait events.

Amazon RDS Proxy pools and multiplexes database connections from serverless applications (AWS Lambda), preventing database memory exhaustion and reducing Multi-AZ failover times by up to 66%.

Last updated: September 2026

3.4 Shared Storage (EFS/FSx) & Database Performance

CloudOps Blueprint Focus: The AWS Certified CloudOps Engineer – Associate (SOA-C03) exam tests operational mastery of shared file systems and database infrastructure: EFS and FSx tuning, RDS CloudWatch metrics, Performance Insights diagnostics, and Amazon RDS Proxy connection pooling.

Shared File Storage: Cloud Architectures & Operational Tuning

Workloads spanning multiple compute instances often require shared file systems, enabling hundreds of instances, containers, and Lambda functions to mount a common POSIX or SMB filesystem concurrently.

Amazon EFS: Serverless Elastic File System

Amazon Elastic File System (EFS) provides a serverless NFSv4.0/NFSv4.1 file system where capacity scales automatically as files are added or deleted.

Throughput Modes

A file system's throughput determines its data transfer speed:

Bursting (Default Legacy): Scales at 50 KiB/s per GiB (100 MiB/s per TiB), bursting to 100 MiB/s using credits. Small systems (e.g., 20 GB) provide a minuscule baseline (1 MiB/s) and quickly exhaust credits, causing severe throttling.

Provisioned Throughput: Decouples throughput from storage size, allocating dedicated throughput (e.g., 100 MiB/s) for small datasets.

Elastic Throughput (Recommended): Automatically scales based on real-time activity with zero provisioning, paying only for data read or written.

Performance Modes

EFS performance modes are selected at creation and cannot be changed afterward:

General Purpose: Lowest latency per operation (sub-millisecond). Ideal for web serving, content management systems (WordPress), container storage, and home directories.

Max I/O: Scales to thousands of concurrent instances and millions of aggregate IOPS with slightly higher per-operation latency. Designed for big data analytics, genomics, and media rendering.

Lifecycle Management

EFS Lifecycle Management transitions files unaccessed for a specified policy window (e.g., 30, 60, or 90 days) to EFS Infrequent Access (IA) or EFS Archive , cutting storage costs by up to 90% while preserving client access.

Amazon FSx: Purpose-Built Specialized File Systems

When applications require enterprise file protocols or extreme throughput, AWS provides Amazon FSx:

1. Amazon FSx for Windows File Server

Protocol & Integration: Native Windows Server SMB file system (SMB 2.0 through 3.1.1).

Enterprise Features: Integrates with Microsoft Active Directory for authentication and granular Windows Access Control Lists (ACLs).

High Availability & Scale: Supports DFS namespaces and Multi-AZ deployments with automatic failover.

2. Amazon FSx for Lustre

High Performance: A POSIX file system engineered for compute-heavy workloads (machine learning, HPC, rendering).

Throughput & Speed: Delivers sub-millisecond latencies, millions of IOPS, and hundreds of gigabytes per second of throughput.

S3 Repository Integration: Directly links to Amazon S3 as a fast scratch cache, loading objects lazily on demand and exporting results back.

  • Feature Amazon EFS FSx for Windows FSx for Lustre
  • Protocol NFSv4.0 / NFSv4.1 SMB 2.0 - 3.1.1 POSIX
  • Client OS Linux, macOS, Lambda Windows, Linux, macOS Linux
  • Latency Low ms (sub-ms General Purpose) Sub-millisecond Sub-millisecond
  • Key Workload Web serving, shared Linux dirs Active Directory, Windows apps HPC, Machine Learning, S3 Cache
  • Amazon RDS Performance Monitoring & CloudWatch Metrics

Proactive management of Amazon Relational Database Service (RDS) instances requires tracking key CloudWatch operational metrics:

CPUUtilization : Host CPU percentage. Sustained utilization above 85% indicates query inefficiency or undersized compute.

DatabaseConnections : Active client sessions. Spikes can exhaust memory and trigger connection errors.

FreeableMemory : Available RAM for buffer pools. When freeable memory nears zero, the host swaps to disk, spiking latency.

ReadLatency & WriteLatency : Elapsed time per storage operation. Values exceeding 20 ms indicate storage saturation.

DiskQueueDepth : Outstanding I/O requests queued for storage. High queue depth with elevated latency confirms a storage bottleneck.

Deep Database Engine Diagnosis: RDS Performance Insights

CloudWatch metrics indicate that RDS is slow, but RDS Performance Insights reveals why by exposing engine wait states: Average Active Sessions (AAS)

  • DB Load |
  • | /---\ [CPU: Active execution]
  • 8 vCPUs + - - -/- - -\- - - Max vCPU Line (Threshold)
  • | / \ [IO: wait/io/table/space]
  • | / \ [Lock: transaction locks]
  • +------------------- Time --->

DB Load (Average Active Sessions - AAS): Measures average sessions actively running queries or waiting on resources.

The Max vCPU Line: A dashed line representing total host vCPU cores. If DB Load exceeds Max vCPU, the database is saturated and queries are queuing.

Wait Event Breakdown: Categorizes bottlenecks into CPU (processing query logic), IO ( wait/io/table/space , db file sequential read waiting on disk reads), Lock (transactions blocked on table/row locks), or Network (waiting on client transmissions).

Top SQL: Identifies specific queries generating the largest share of database load for targeted optimization.

Connection Optimization with Amazon RDS Proxy

Serverless architectures (such as AWS Lambda) scale horizontally into thousands of concurrent executions during traffic surges. Each Lambda instance opens an independent database connection.

The Serverless Connection Storm

Thousands of simultaneous direct TCP connections cause two major failures:

Connection Exhaustion: The database hits its max_connections limit and rejects new client connections.

Memory Starvation: Maintaining thousands of idle connection threads consumes gigabytes of server RAM, starving database buffer pools.

RDS Proxy Architecture & Failover Acceleration

Amazon RDS Proxy is a managed database proxy sitting between applications and RDS/Aurora:

Connection Pooling & Multiplexing: Maintains a persistent pool of established database connections and multiplexes thousands of ephemeral client queries across them.

Failover Acceleration: During Multi-AZ failovers, RDS Proxy retains open client connections, queues traffic, and redirects queries to the promoted primary instance, slashing failover recovery times by up to 66% .

Security: Enforces TLS encryption and integrates with AWS Secrets Manager and IAM database authentication.