The official AWS Certified CloudOps Engineer - Associate syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
Implement metrics, alarms, and filters by using AWS monitoring and logging services
Each workload has its tool: Lambda Insights gives Lambda system metrics and cold starts, Bedrock model invocation logging stores requests and responses, and Amazon Managed Service for Prometheus managed collectors scrape EKS metrics without agents. CloudTrail does not log data events (such as S3 DeleteObject) unless you turn them on, and metric filters turn log events into metrics you can alarm on.
Lambda Insights ↗Creating metrics from log events using filters ↗
The CloudWatch agent collects in-guest metrics (memory, disk) and logs, using a role with CloudWatchAgentServerPolicy. For fleets, the configuration is stored in Parameter Store and applied with AmazonCloudWatch-ManageAgent; after editing it you must run fetch-config. On ECS with EC2 it runs as a daemon service, and on EKS through the amazon-cloudwatch-observability add-on with EKS Pod Identity.
Install the CloudWatch agent using AWS Systems Manager ↗Troubleshooting the CloudWatch agent ↗
Alarms can notify SNS, invoke Lambda (with a resource policy for lambda.alarms.cloudwatch.amazonaws.com), run EC2 and Auto Scaling actions and create OpsItems; other targets use their state change events in EventBridge. Composite alarms combine states with AND, OR and NOT, cannot trigger Auto Scaling and support suppressor alarms. TreatMissingData decides whether missing data counts as OK or ALARM.
Alarm actions ↗Configuring how CloudWatch alarms treat missing data ↗
CloudWatch dashboards can show metrics and alarms from several accounts and Regions (accountId and region properties) when each account shares its data with the monitoring account. For cross-account logs and alarms within a Region, use cross-account observability. Variables let one dashboard switch, for example, between Lambda functions, and a dashboard can be shared by email, publicly or through SSO.
Cross-account cross-Region CloudWatch console ↗Sharing CloudWatch dashboards ↗
Many services publish to SNS: RDS event subscriptions, Auto Scaling notifications (EC2_INSTANCE_LAUNCH_ERROR), S3 event notifications and the Amazon Managed Service for Prometheus alert manager. The topic needs an access policy that lets the service principal publish and, when encrypted, a customer managed key that grants it kms:GenerateDataKey* and kms:Decrypt.
Managing Amazon SNS encryption keys and costs ↗Granting permissions to publish event notification messages to a destination ↗
Identify and remediate issues by using monitoring and availability metrics
CloudWatch anomaly detection compares a metric with its expected band based on seasonality. EC2 alarm actions reboot an instance on instance status check failures and recover it only with StatusCheckFailed_System. AWS Config fixes resources with Automation runbooks, and EventBridge can start a runbook when its required parameters are set. AWS DevOps Agent investigates incidents and proposes mitigations.
Create alarms that stop, terminate, reboot, or recover an instance ↗Setting Up Auto Remediation for AWS Config ↗
EventBridge routes events with rules per bus; CloudTrail events reach only the default bus, global service events such as IAM only us-east-1, and read-only ones need the ENABLED_WITH_ALL_CLOUDTRAIL_MANAGEMENT_EVENTS state. Input transformers reshape the event, Pipes enriches it by calling API Gateway, Lambda or Step Functions, and cross-account delivery needs a bus policy and an IAM role.
Troubleshooting Amazon EventBridge ↗AWS service events delivered via AWS CloudTrail ↗
Systems Manager Automation runs predefined runbooks (such as AWS-RestartEC2Instance) or custom ones, with tag targets and rate controls (concurrency and error threshold). aws:executeScript runs Python or PowerShell and aws:executeAwsApi calls APIs with automatic retries; aws:approve requests approval through SNS. It can be started from the CLI or SDKs, EventBridge, AWS Config, or across accounts and Regions.
Run automated operations at scale ↗aws:executeScript - Run a script ↗
Implement performance optimization strategies for compute, storage, and database resources
AWS Compute Optimizer analyzes CloudWatch metrics and specifications of EC2, Auto Scaling groups, Lambda, EBS or ECS on Fargate to find under- or over-provisioned resources. Memory requires the CloudWatch agent with the InstanceId dimension, and enhanced metrics extend the lookback period. Recommendations can be filtered by tags; on T instances, a CPUCreditBalance of zero in standard mode caps CPU at baseline.
EC2 instance metrics (AWS Compute Optimizer) ↗Key concepts for burstable performance instances ↗
SSD volumes (gp3, gp2, io2) suit IOPS-bound transactional workloads and HDD volumes (st1, sc1) suit large sequential throughput workloads; gp3 has no bursting and provisions IOPS and throughput separately. Elastic Volumes changes type and performance without stopping the instance. Key metrics: BurstBalance, VolumeQueueLength and the IOPS and throughput exceeded checks; fast snapshot restore avoids first-access latency.
Amazon EBS volume types ↗Amazon CloudWatch metrics for Amazon EBS ↗
S3 Transfer Acceleration uses edge locations for long-distance uploads through the s3-accelerate endpoint; multipart upload sends parts in parallel and retries only failed ones. DataSync moves data from NFS, SMB or other clouds to S3 with integrity validation and bandwidth limits. S3 Lifecycle transitions or expires objects and aborts incomplete uploads; Intelligent-Tiering adapts to unpredictable access.
Configuring fast, secure file transfers using Amazon S3 Transfer Acceleration ↗Performance guidelines for Amazon S3 ↗
Amazon EFS provides shared NFS storage with Elastic, Provisioned or Bursting throughput, and lifecycle policies that move files to IA and Archive and can return them to Standard on first access. FSx for Windows File Server provides SMB with Active Directory, FSx for Lustre gives high-performance POSIX storage linked to S3, and S3 Files mounts a bucket as a synchronized file system.
Managing storage lifecycle (Amazon EFS) ↗Working with Amazon S3 Files ↗
CloudWatch Database Insights measures DB load in average active sessions and breaks it down by SQL, waits, hosts or users; with paid retention it produces proactive recommendations. Enhanced Monitoring shows OS processes. RDS Proxy pools and reuses connections (useful with Lambda) and attaches only to the writer instance. Read replicas offload reads, and ReplicaLag measures their delay.
Monitoring Amazon RDS databases with CloudWatch Database Insights ↗Amazon RDS Proxy ↗
Cluster placement groups pack instances in one AZ for the lowest latency, partition groups separate racks for distributed workloads such as Cassandra, and spread groups isolate a few instances. An instance must be stopped to change its placement group. Enhanced networking with ENA gives higher PPS, and ethtool exposes counters such as pps_allowance_exceeded. Instance store data is lost when the instance stops.
Placement strategies for your placement groups ↗Monitor network performance for ENA settings on your EC2 instance ↗