In this video, discover what you should know before taking this course.
- [Instructor] If you've looked at any of the introductions to any of the modules of the Well-Architected Framework, the different pillars that we talk about, and you're interested in looking at the Well-Architected Framework some detail, then here's what you should know. First of all, what your job type? Are you a system administrator, a cloud architect, maybe a project manager managing a system administrator, or a cloud architect. If you're the cloud architect, are you interested in architecting solutions at AWS? If you're the system administrator, are you part of the team that's deploying applications at AWS? Perhaps you're a developer interested in moving applications to AWS, or maybe you're actually moving applications to AWS right now and you want some guidance. Maybe the boss has said, "We're all in," for moving to the cloud. I don't know what that means, but I hear that phrase quite a few times. If you know your company's getting ready for the cloud, I highly recommend looking at the Well-Architected Framework in detail. It will help you work as an effective team. It will help you lay out responsibilities, and it will help you being very successful in deploying your applications at AWS. So I hope you join me in all aspects and all pillars of the Well-Architected Framework.
- Design principals
- Key operational areas
- Key AWS services
- Designing workloads with key managed services
- Using Lambda for operational readiness
- Managing operational health
- Responding to health events