Summary of Solutions Architect Associate Learning Path
Summary of the content covered in the solutions architect associate learning path and tips for how to prepare for the exam.
References / Acknowledgements
Cloudwatch Developer Guide
Simple Queue Service FAQ
Building Fault Toerant Applications in the Cloud
High Availability and Scalability
Solutions Architect Associate - Monitoring with Cloudwatch
Solution Architect Associate - IAM
AWS Back up and recovery
Hi and welcome back. We've covered a good body of knowledge in this Solutions Architect Associate Learning Path. We learnt how elasticity and scalability help us design cloud services. And how AWS provides the ability to scale up and down to meet demand rather than having to provision systems on estimated usage. And how that ability increases our agility and reduces our costs as we only pay for what we use. We saw how the four pillars of the AWS well architected framework can be a guide for designing with best practices. In Security, we designed to protect information, systems and assets while delivering business value through risk assessments and medication strategies. In Reliability, we aimed to deliver systems that can recover from infrastructure or service failures and that can dynamically acquire computing resources to meet demand. In Performance Efficiency, AWS enables us to use computing resources efficiently to meet system requirements and to maintain that efficiency as demand changes and evolves. So, we need to be always looking for better ways to use services together and to look for ways to break monolithic stacks down to smallest dependent services. And then Cost Optimization, our goal is to create the best possible outcome for our in customer. We need to avoid or eliminate unneeded cost or sub-optimal resources. Now, that may mean using smaller, more loosely coupled services rather than going straight for biggest invest available. We need to always be looking for ways to reduce single points of failure into reduced costs. AWS has a global footprint but we may not need to use the biggest instances in multiple regions. And it maybe that by using multiple availability zones within one region and by using a blend of On Demand and Reserved Instances, we can create a highly available cost efficient solution. We used that design in cost optimization in our Deployment of Acme Widgets. We are running instances behind an elastic load balancer. In three AZ's connected within Aurora Database that replicates our data across three availability zones with automated fail over could scale and meet burst activity requirements while remaining a highly available cost-efficient solution. So on exam questions, look for clues to help you determine the business requirements and constraints in any of the scenarios you get. Look for the Recovery Time Objective and the Recovery Point Objective. The Recovery Time Objective is the maximum amount of time the customer can be without the system in the event of a disaster. The Recovery Point Objective is the last possible point in time that the business data must be recoverable to. Now, remember that Recovery Point Objective is generally time value as well. There are four design patterns we can deploy in AWS to meet RPO and RTO ojectives. The first is Back up and Restore which is like using AWS as a virtual tape library. It's generally gonna have relatively high recovery time objective since we're going to have to bring back archives to restore at first which could take four to eight hours or longer. We're gonna have a generally high Recovery Point Objective as well simply because our point in time will be our last back up. And then for example, we're using daily back ups only then it could be 24 hours. Cost wise, Back up and Restore is very low and easy to implement. The second option is Pilot Light and that's where we have a minimal version of our environment running around AWS which can be lit up and expanded to production size from the Pilot Light. Our Recovery Time Objective is likely to be lower than Back up and Restore as we have some services to install really and our Recovery Point Objective will be since our last data snapshot. And the third option is Warm stand by where we have a scaled down version of a fully functional environment always running an AWS. Now, that's gonna give us a lower Recovery Time Objective than perhaps Pilot Light as some services are always running and it's likely that their Recovery Point Objective will be lower as well since it will be since their last data write if we're using asynchronous databases with the master-slave multi-AZ database service. The cost of running Warm stand by is negotiably higher than the Pilot Light with Back up and Restores. The benefit of Warm stand by is that we can use the environment for dev test or for skunk works to offset the cost. And the fourth option is Multi site where we have a fully operational version of our environment running in AWS or in another region. And that's likely to give a lowest RTO simply because it could be matter of seconds if we're using active-active fail over throughout 53. Our Recovery Point Objective likewise will be significantly lower than other options. If we're using synchronous databases then yes it'll be a matter of seconds. If we're still using asynchronous databases, then we're gonna be at up here over last data write. So, the cost and maintenance over here to running a multi sites environment needs to be factored in and considered. The benefit is that you have a regular environment for testing DR processes. And just a couple of last points and exam preparation. First of all, I think it's well worth doing or setting a goal of doing 500 minimum quiz questions if you can do 1000. Quiz questions are really good way of sharpening up your subject matter expertise and ensuring that you remember all those key facts. Also, well worth doing all the labs, as tempting to skip over them I'm sure, but remember it's the hands-on freshness when you are presented with a scenario and the scenarios will make you think and you'll be scratching your head trying to remember certain things. They're gonna test your knowledge. So the more that you can come back as active recall, the more time you have to solve some of that more challenging questions. Now, do manage your time in the exam. If you come across some really hard question, mark it and move on. So, you probably better off going through and getting as many of the simple answers that you can get and then coming back and with the time left, try to problem solve these ones that you don't quite get. Do check out the CloudAcademy e-books, they are good guide for helping with your grip. And when you pass, come back and let us know. Email us at firstname.lastname@example.org. We'd love to hear your comments and your feedback. And look, good luck, okay? You can do it, you can nail this exam. So, go knock it over, good luck!.
About the Author
Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe. His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups.