AWS development, operations, and DevOps certifications form a useful progression, but the path is changing in late 2026. AWS Certified Developer \u2013 Associate is moving from DVA-C02 to DVA-C03, AWS Certified CloudOps Engineer \u2013 Associate is already on SOA-C03, and AWS Certified DevOps Engineer \u2013 Professional remains DOP-C02.<\/p>\n
As of October 7, 2026, DVA-C02<\/a> is still the current Developer Associate exam. AWS has announced that registration for DVA-C03 opens October 27, the final day for DVA-C02 is November 30, and DVA-C03 begins general delivery December 1. That makes timing part of the certification decision for anyone studying now.<\/p>\n The larger question, however, is not which code appears on the badge. It is whether your work is primarily application development, cloud operations, or end-to-end delivery and reliability.<\/p>\n The current DVA-C02 blueprint focuses on Development with AWS Services, Security, Deployment, and Troubleshooting and Optimization. It is designed for developers who build, test, deploy, and debug AWS applications.<\/p>\n The exam expects application-level understanding of services and patterns: Lambda, APIs, event-driven integration, data stores, authentication and authorization, encryption, secrets, deployment workflows, testing, observability, and optimization. It explicitly does not make deep infrastructure administration or network architecture the center of the role.<\/p>\n A practical DVA-C02 application development<\/a> is useful if you intend to test before the November 30 cutoff.<\/p>\n AWS says the updated DVA-C03 reflects how developer work now includes AI-assisted development, managed AI integrations, and security for AI agent interactions. The four broad domains remain development, security, testing\/deployment, and troubleshooting\/optimization, although the weights and detailed skills are being updated.<\/p>\n That does not mean the certification turns into a machine-learning exam. AWS has specifically said areas such as prompt engineering, RAG design, model selection, SageMaker AI, and AI-governance framework design are outside the announced DVA-C03 scope. The emphasis is on modern application-development workflows that may use AI-assisted tools and managed AI services.<\/p>\n If you are already ready for DVA-C02, AWS explicitly recommends taking it before the cutoff rather than restarting preparation only to chase the new code. If you are early in study, waiting for the DVA-C03 guide may be sensible.<\/p>\n The current SOA-C03 exam<\/a> validates deployment, management, and operation of AWS workloads. AWS renamed the certification from SysOps Administrator to CloudOps Engineer when SOA-C03 launched, reflecting a broader operating model.<\/p>\n The blueprint covers monitoring and logging, remediation, performance optimization, reliability and business continuity, deployment and provisioning, automation, security and compliance, networking, and content delivery. Containers, multi-account design, multi-Region architectures, and infrastructure as code have a more visible role than in the older SOA-C02 program.<\/p>\n The SOA-C03 CloudOps<\/a> makes sense for engineers responsible for keeping production environments healthy.<\/p>\n Modern teams rarely have a perfect wall between development and operations. Developers need observability, deployment, security, and performance knowledge. CloudOps engineers need to understand application behavior, automation, containers, and delivery systems.<\/p>\n The difference is the center of gravity. Developer Associate asks whether you can build and debug cloud applications. CloudOps Engineer asks whether you can deploy, monitor, secure, recover, and operate workloads reliably.<\/p>\n If your job is full-stack or platform-oriented, studying both domains can be useful even if you take only one exam. The overlap creates the foundation for professional DevOps work.<\/p>\n The current DOP-C02 exam<\/a> validates advanced ability to provision, operate, and manage distributed systems and services on AWS. Its six domains cover SDLC automation, configuration management and infrastructure as code, resilient cloud solutions, monitoring and logging, incident and event response, and security and compliance.<\/p>\n Professional-level questions require wider context. A deployment strategy is not only about releasing code; it is about rollback, blast radius, observability, governance, and reliability. An infrastructure-as-code choice is not only a template; it is about repeatability, drift, organizational controls, and multi-account operation.<\/p>\n The DOP-C02 resilience and monitoring<\/a> illustrates that broader systems perspective.<\/p>\n Developers use automation to package and deploy applications. CloudOps engineers use it to provision repeatable environments. DevOps engineers use it at scale to control change across systems and accounts. That makes infrastructure as code one of the strongest connecting skills across the path.<\/p>\n Understand declarative provisioning, reusable modules, state where relevant, drift, change review, rollback, and safe promotion between environments. The infrastructure-as-code fundamentals<\/a> matter well beyond any single AWS exam.<\/p>\n Do not treat automation as a set of commands. The purpose is to make change reproducible, reviewable, and less dependent on manual memory.<\/p>\n A CI\/CD pipeline is not a complete DevOps operating model. Teams also need to know whether the release worked, how user experience changed, what failed, and how to recover. Metrics, logs, traces, dashboards, alarms, deployment health, and event-driven response are central to production work.<\/p>\n The observability model<\/a> helps connect Developer troubleshooting, CloudOps monitoring, and DOP-C02 incident response.<\/p>\n Practice deploying a change and defining the evidence that would prove success. Then simulate a failure and decide whether to roll back, remediate, or route traffic away from the problem.<\/p>\n Developer Associate expects secure application behavior: authentication, authorization, encryption, and sensitive-data handling. CloudOps adds operational security and compliance. DevOps Professional expands the problem to automated controls, identity at scale, auditing, and security monitoring across delivery systems.<\/p>\n This progression mirrors real responsibility. A developer secures code and service interactions. An operator secures workloads and environments. A DevOps engineer helps make secure behavior repeatable across the delivery lifecycle.<\/p>\nDVA-C02 currently validates cloud application development<\/h2>\n
DVA-C03 changes the context without abandoning core developer skills<\/h2>\n
SOA-C03 is for operating workloads, not writing the application<\/h2>\n
Developer and CloudOps skills overlap in production<\/h2>\n
DOP-C02 raises the scope to systems and delivery at scale<\/h2>\n
Infrastructure as code is the bridge across all three roles<\/h2>\n
Observability and incident response separate DevOps from deployment automation<\/h2>\n
Security should become more automated as you progress<\/h2>\n