aws well architected review

1. AWS Well-Architected Framework
2. AWS re:Invent 2021 – Customize your AWS Well-Architected reviews
3. AWS Well-Architected for Startups – 5 Minute Overview
4. Are you Well Architected?
5. AWS Well Architected Framework Explained | How does AWS Well Architected Tool work?
6. Best practices to architect a reliable infrastructure II AWS Well Architected – Reliability Pillar
7. How to Prepare for an AWS Well Architected Review

AWS Well-Architected Framework

[Music],hi guys,in this lesson well go into the five,pillars of the well architected,framework,so again what is this well its there to,help you,understand the pros and cons of,decisions you make building,on aws there are five pillars lets go,into each of these,in some detail firstly we have the,operational excellence pillar,this is about supporting the development,of workloads on aws,its about gaining insight into your,workload operations,and improving your processes and,procedures to make sure youre,delivering,value to your business now the best,practices,are where you really need to take notice,these are the things that come up,in exam questions so you very well might,see these phrases,in the answers perform operations,as code so dont perform operations,manually,use tools like cloud formation to,automatically build your infrastructure,make frequent small and reversible,changes,rather than big changes that are,difficult to roll back,this helps you if something goes wrong,you can quickly roll back and try again,refine operations procedures frequently,constantly re-evaluate how youre doing,things,is there a better way and anticipate,failure,big one that comes up a lot make sure,you always,anticipate what could go wrong thats,how you can prevent it from happening,and also make sure that youre able to,recover from failure when it does happen,so learn from all operational failures,make sure that you update your processes,work out,why did it happen and what can i do next,time then we have the security pillar,this is about protecting your data,systems and assets and taking advantage,of the cloud technologies that are,available for you to secure,your data best practices are,implement a strong identity foundation,so make sure that your identity,management systems,systems like iam like your identity,federation,like your mobile and web application,authentication systems,youve got to get those right so that,your identities are properly secured,and users get access to what they need,enable traceability so,you can trace whats happening where did,things go wrong,whats happening here and whats,happening there apply security at all,layers,dont just apply security at the,perimeter make sure that every layer,of your application and infrastructure,has security applied,automate security best practices,automate as much as you can the more you,automate,the less human error youre likely to,have protect data,in transit and at rest so think about,encryption here,remember its up to you to encrypt your,data on aws,you want to encrypt it as its moving,across a network in transit,and at rest when its stored in a,storage system or in a database,keep people away from data have the,right access controls,in place to secure your data access,prepare for security events,so make sure that youre prepared in,case anything happens like malicious,attacks like,distributed denial of service attacks,next we have the,reliability pillar this is about,ensuring your workloads perform,correctly and consistently as theyre,expected to for whatever they do,this includes the ability to operate and,test the workload for its entire,life cycle best practices are automate,recover from failure,so make sure that when something goes,wrong like a system fails,you can automatically recover you dont,need manual involvement,think about amazon ec2 auto scaling,if a system fails an instance fails then,it will be automatically replaced,by auto scaling and your load balancer,will start distributing traffic to it,thats automatic recovery test recovery,procedures,you always have to test in the cloud,its really easy to test your recovery,procedures including doing full,disaster recovery testing lots of,companies dont test their procedures,until they really need to do it and then,they find they dont work,its too late at that point scale,horizontally to increase,aggregate workload availability wherever,possible,scale horizontally though some services,require you to scale vertically,like for example when you have an rds,database and you need to increase,the right throughput you have to use a,larger instance size,but as you go up to larger instance,sizes and youve got more traffic coming,into that database what happens if that,one instance fails,you have a big problem so of course in,that regard you could have something,like a multi-az failover,but even better where possible like for,example with dynamodb,or with ez2 instances you can scale,horizontally,and that means the failure of an,individual component or system,does not affect the overall application,stop guessing capacity,another one that the cloud makes easy,because we can dynamically and,automatically,change the amount of resources,associated with the services we use,so we dont have to guess how much,resource we need and then find out later,on that we were wrong,if we are wrong it doesnt matter so,much in the cloud because we can adjust,very easily manage change in automation,so implement change management,procedures and,automate as much as possible next we,have the performance efficiency pillar,this is about ensuring our resources are,working to,meet the requirements and changing as,demand,and as technologies evolve as well best,practices,are democratize advanced technologies,aws wants you to leverage the,technologies and services that they,provide they provide lots of amazing,tools,manage services event driven,architectures,serverless services all of these kind of,things can be built,on aws and utilized on aws and so,use as much of that as possible because,it delivers value to your business,go global in minutes this is one that,again is very much,a feature of the cloud the ability to,deploy your applications,all over the world very easily use,serverless architectures,wherever possible use serverless it,means youre not managing the,underlying layer of infrastructure,managing patches managing systems,and you are leveraging a higher level of,service and youre able to scale more,easily as well,experiment more often this is all about,just experimenting and seeing what we,can do we can learn a lot by,testing out different things and its,easy to do in the cloud so we can learn,from,what we do and then improve our,processes,improve our performance and our,operations consider,mechanical sympathy its one of those,strange phrases that aws has,essentially it means that you need to,understand the systems and the purpose,of those systems that are available to,you,so that you can utilize them to their,best effect lastly we have the cost,optimization pillar this is all about,making sure youre delivering value to,your business,at the lowest price point best practices,are,implement cloud financial management,adopt a consumption model mostly were,using a consumption model in aws,measure efficiency so you can constantly,measure,see if you are optimizing your systems,for cost,are you using the right pricing models,have you over allocated resources and so,on,stop spending money on undifferentiated,heavy lifting,so if youre building your own data,center implementing your own,infrastructure and managing it,well thats not really differentiated,thats,stuff which is not delivering value to,your business,aws would prefer that you dont waste,your time and your money on that,and instead you concentrate on higher,value things like developing,better features and applications for,your customers to differentiate your,business,and lastly analyze and attribute,expenditure,so this is about being able to look at,your itemized billing,and understand what your costs are and,where exactly theyre coming from,and thats it for the five pillars of,the well architected framework and do,make sure that you remember the best,practices,associated with each of these pillars,[Music],you

AWS re:Invent 2021 – Customize your AWS Well-Architected reviews

Right, thank you so much for coming everybody.,Appreciate you taking the time,,Today, we are going to be talking about customizing,your Well-Architected Review.,Im Samir Kopal, I lead the product and engineering teams,for Well-Architected.,And Im Ilana Greenberg,,the product manager for Well-Architected.,Just to understand the crowd,,how many of you are aware of Well-Architected,as a framework or the tool or have used it?,Thats great, thats a great mix here.,So today we are going to cover,,well talk about a little bit about a history,of Well-Architected, how its evolved, where it is today.,And then were going to talk about this really cool feature,that we launched yesterday called custom lenses.,And we want to talk about what is the problem,that we are addressing with that.,Were going to talk about an overview,of what the feature is,,and then we are going to go do a deep dive,on how to actually use it in the tool.,And we have a customer use case, well go through that,,and I promise Ill leave time in the end,for any questions you guys have.,All right, so what is Well-Architected?,A little bit of a lesson in history.,So Well-Architected started when we had a popular service,,have an outage back in 2012,,and a lot of our customers were impacted.,And we recognize that theres some customers,who didnt get impacted.,And the reason for that was they built in,resiliency, reliability into their architecture.,And the thinking then was how do we take this learning,and share it with everybody?,How do you make sure that we have customers,that work with us follow the same best practices?,And fast forward a few years,,we had the Well-Architected Framework with four pillars,,security, performance, reliability, and cost optimization.,And we continued to evolve on that.,So we use that internally, we use that with our customers,,we got feedback,,we did tens and thousands of reviews to figure out,what works, what doesnt.,And when we realized that,,we recognized one aspect was is we need a process,that weaves architecture into your organizational structure.,And that was the birth of the fifth pillar,,which was operational excellence.,Operational excellence brings together,the process that allows you to follow these best practices.,So the three elements to Well-Architected,,one is the Well-Architected Framework.,Its available as a white paper.,The Well-Architected Tool that revolves,around the Well-Architected Framework.,So it adds the pillars, the questions, the best practices,,all of that is in the Well-Architected Tool.,And that allows you to measure and improve,your workload health in a very structured, consistent way,across all your workloads.,When I say, workloads,,a workload is just a collection of resources.,It could be an application, it could be a platform,,it could be a service,,it could be a single Redshift Cluster,,whatever you wanna call it.,But a workload is what youre evaluating.,And then there is the improvement plan.,The improvement plan is, well, I know what my risks are,,how do I mitigate them?,What do I do?,Where do I go?,Whats the best practice?,So thats the improvement plan around Well-Architected.,So these are the three elements.,Now lets talk a little bit about,why it is important to do a review.,Ill give you an example of when,we launched the Well-Architected Tool back in 2018,at re:Invent exactly three years ago.,And I was the software engineering manager back then,,running the service.,I read the white paper,,I was aware we had subject matter experts on the team.,So I was well aware of what Well-Architected is,,and best practices, recommendations, things like that.,But when I formally sat down and did the review,for the service itself,,one of the things I realized is its a conversation starter,,there are things that you dont think of upfront, right?,And when you start doing the review,,thats where you start having those conversations.,An example would be,,how are we going to manage if there is an incident,running on game day?,How are we going to know whats going to happen?,Are we gonna update our runbooks?,Weve not launched, its not in production.,So how do we do that?,So those things that you start thinking of.,Typically, the world was where,,hey, its post production, if you have an incident,,we have someone whos on call, theyll take care of it.,But how can you optimize those things?,And that is what I learned is where you can,identify these risks early.,It has that conversation,,you can identify those risks early,,you can start planning for those risks.,The other thing, how many of you here have been,in a situation where youre looking at an architecture,or youre looking at a design or code and say,,well, why did we make this decision?,It happens all the time.,And then you look back and say,,well, I need to go back to some Wiki pages,or some internal documentation,,or I need to go in and follow some email threads.,Or the person who did this,is no longer with the organization.,Very common, right?,And there is no structured way to document.,Its scattered, its hard to find,,but with Well-Architected,,the tool gives you the ability to document those decisions.,It gives you the ability to write,why you made that trade off, cost and performance.,Hey, we made this decision at this point,for this very reason and thats in there,.,So its there, you can go look at the workload,,you can go look at why it is.,So it gives you that document,,the decisions and the trade-offs.,And then comes the part where you start,addressing those risks that youve identified.,So youre going to start looking at,,well, now we know we have five security risks,,three operational excellence risks,,and you start improving the health of your workload.,Now you might prioritize some things differently.,You might look at it and say,,well, this is an internal tool, cost is more important,,its behind a firewall.,Security is probably less important to me.,Or it could be the other way where its like,,I dont care about cost, I need extremely high availability,,high performance systems.,So you can start prioritizing,and improving the health of your workload.,Its very critical to keep doing that.,And then the last part of this is,how do you actually go ahead and implement,continuous improvement into your processes?,A lot of times when we do code deploys,,we look at it and say, did I run my integration test?,Did I on the unit test?,Whats that coverage looking like?,So youre looking at your code consistently,to look for improving your code quality.,A lot of times we miss out on looking at,architectural risks.,I went from being multi-AZ To Single-AZ,in this deployment.,Its a massive risk for reliability.,So you started looking at that and it helps you do that.,Because now when you make a change, you can say,,run a Well-Architected review,,lets see whether we increase the number of risks we had,,or did we decrease the number of risks that we had.,So thats why it becomes critical to have those reviews.,And it becomes a continuous improvement process,for you to do.,Now why we need to customize it.,So we understand with Well-Architected,,that Well-Architected is a general framework,,its a generic framework that allows you to learn measures,,improve your workload,,but it doesnt tailor it to your specific needs.,Youre looking for compliance best practices in there.,Youre looking for finance best practices in there.,A lot of big enterprises,have Cloud Center of Excellence teams that will go ahead,and have a whole lot of best practices,that theyve built over years of experience.,Customizing the review will allow you to do that.,So custom lenses, which was launched yesterday,,allows you to go ahead and add your own best practices.,And well get into details of how that looks,,but it allows you to incorporate those organizational,best practices into a single place.,That brings me to my next point.,Today, a lot of these best practices are scattered.,There are tools that will do security best practices,,th

More: uline review

AWS Well-Architected for Startups – 5 Minute Overview

hello and welcome to this five-minute,overview of aws while architected,i am mark isaacs senior startup solution,architect at aws,today i will be giving you an overview,of aws while architected,what it is and how it can help you,so why does aws well architectured exist,aws solution architects have years of,experience working with customers,architecting solutions across a wide,variety of workloads and use cases,we have helped design and review,thousands of customers architectures on,aws,from this experience we have helped,customers identify,best practices and core strategies to,help them understand,the pros and cons of decisions they make,while building systems on aws,aws while architected helps cloud,architects build secure,high performing resilient and efficient,infrastructure for their applications,and workloads,it is more than a tool while architected,is a mechanism for your cloud journey,it allows you to learn the strategies,and best practices for architecting in,the cloud,measure your architecture against best,practices using the well architected,tool,and improve architectures by addressing,any high risk issues identified,as a startup you want to minimize the,risk of one-way decisions early in your,design process,it helps you better gauge the state of,your architecture and create improvement,roadmaps,to incorporate into your plans,the well architected framework provides,a set of questions and design principles,across,five pillars the five pillars forms the,foundation for building well architected,solutions or workloads on aws,lets look at what these five pillars,are,when you incorporate these pillars it,will help you produce stable,and efficient systems allowing you to,focus on functional requirements,the operational excellence pillar,focuses on running and monitoring,systems,to deliver business value and continue,improving processes and procedures key,topics include,automating changes responding to events,and defining standards to manage your,daily operations,the security pillar focuses on,protecting information and systems,key topics include confidentiality and,integrity of data,identifying and managing who can do what,with privilege management,protecting systems and establishing,controls to detect security events,the reliability pillar focuses on,ensuring the workload performs,its intended function correctly and,consistently when its expected to,a resilient workload quickly recovers,from failures to meet business,and customer demand key topics include,distributed system design recovery,planning,and how to handle change,the performance efficiency pillar,focuses on using i.t,and computing resources efficiently key,topics include,selecting the right resource types and,sizes based on,workload requirements monitoring,performance,and making informed decisions to,maintain efficiency,as business needs evolve,the cost optimization pillar focuses on,avoiding unnecessary costs,key topics include understanding and,controlling where money has been spent,selecting the most appropriate and right,number of resource types,analyzing spend over time and scaling to,meet business needs without,overspending the aws well architected,lenses,extend the guidance offered by aws while,architected to specific industry and,technology domains,such as serverless applications,foundational technical review,and sas lenses are offered within the,well architected tool,to fully evaluate your workloads use,applicable lenses together with the aws,well architected framework and the five,pillars,we use the well architected tool in the,console when executing the well,architected process on a selected,workload,all details are stored securely in your,aws account,workloads can be shared with your essay,or partner resource for collaboration on,the review,or remediation steps using workload,sharing,the well architecture tool also has an,api for programmatic access,the architecture health needs to be done,in a consistent manner,with a blame free approach that,encourages diving deep,it should be a lightweight process hours,not days,that is a conversation and not an audit,the purpose of reviewing an architecture,is to identify any critical issues that,might need addressing,or areas that could be improved the,outcome of the process is a set of,actions,that should improve the experience of a,customer using the workload,as always the earlier you do this in,your cloud journey the more you improve,your chances of success,and limit technical debt,so when should you do a deep dive into,your architecture health,health checks should be applied at key,milestones in your product or,application life cycle,early on in the design phase to avoid,decisions that are difficult to change,and then before they go live date as a,startup you need a performance secure,reliable product before you go live you,dont want to damage your brand,before you even get a chance to build it,therefore the recommended approach is to,do it early in your product life cycle,and continuously,as key aspects of your architecture,change you want it to become part of,your dna to build well architected,solutions,thank you for listening to this episode,and keep watching this series as we dive,deep into each of the well-architected,pillars

More: x85j review

Are you Well Architected?

so this session is going to be about,well architected really trying to answer,the question are you well architected,because as we see you know failures,happen all the time and so how do your,systems or your processes respond to,those so just to make this a bit more,interactive because all I can see is a,sea of blue lights from headphones is,who here is building technology,solutions and fills but their teams are,building something that is well,architected its following best,practices hopefully most people theyve,got great teams most people feel,reasonably confident ok now when you ask,that question people feel a little bit,less confident when you ask them well do,you feel confident in that when you,think about all of these different areas,so maybe some of those areas would make,you think hey my team is great but we,want to dive a little bit deeper into,how they thought about security or,reliability one thing that can help you,feeling more confident about whether,youre building well architected systems,is to review your architectures is to,have a conversation about the systems,youve built and work out whether its,been following your best practices of,course doing that in a consistent,fashion can be difficult the person,whos involved when youre viewing the,architecture may have had a bad evening,with their football team and so they,might not be reviewing their all the,architecture the same way that theyve,reviewed other architectures or maybe,theyve got a focus on security so,theyll dive deep on security but maybe,dont feel so confident about asking,about reliability and when I talk to,most customers its rare that they,thought about applying a consistent,process across their whole technology,portfolio how do you make sure that all,of the systems youre building are,following some level of best practice,and so thats why we created AWS well,architected is to help customers,understand if theyre following best,practices and of course then be able to,make informed decisions about how you,might address anything you see in there,that you might want to improve so lets,talk about the history of well,architected so well architected has been,around for a number of years it actually,started in 2012 anywhere solutions,architects started having conversations,with customers asking hey well is this,approach to building this architecture,well architected and weve evolved that,over,of years one of the things Id really,like to emphasize is that well,architected is about AWS listening to,customers and looking at what is working,for them and so the best practices that,we talk about evolve and change over,time so this is not a fixed point in,time this is the best way to build a,system we are looking at whats working,new technologies how things are evolving,patterns and practices and building that,into well architected and in 2018 we,released the AWS well architected tool,which you can use in the AWS console to,review your architectures for free so as,much as possible we try to give you not,just a framework for reviewing,architectures but also the tooling for,doing that process as well so what is,the AWS well architected framework I,like to think about any kind of system,will process in terms of why starting,with why and in this case what kind of,benefits do customers see from using,well architected so when I talk to,customers about the benefits they see,from carrying out well architected,reviews on their architectures they see,these kind of benefits so for example,they can build and deploy faster and,that happens because well architected,emphasizes using automation to build,systems so you spend less time doing,manual processes and have human error,and have more time with systems which,are repeatable evolvable and hopefully,high-quality one way to think about well,architected is a mechanism for your,cloud journey so as you move from,working in an on-premises environment,and youre starting your cloud journey,well architected helps you to learn what,the best practices for building in the,cloud are one of the things that well,architected gives you which as an,engineer Ive always looked for is a way,to measure architectures is this,architecture following best practice is,it any good and so thats one of the key,value offerings from doing well,architect it is it gives you a way of,reviewing an architecture and give you,some sort of measure of how well it is,falling best practices and of course,when youve done that measurement,you then have the opportunity to improve,that architecture so we also provide you,with advice on how you can improve the,architecture based upon those findings,so what is the well architected,framework effectively its a set of,questions and design principles across,five pillars one way to think about that,is to think about when youre building,technology solutions its a lot like,constructing physical buildings if,youre building any kind of physical,constructs such as like the Excel center,you really have to think about the,foundations of that building because if,those foundations are not solid then,its going to be half of that building,to be safe and easy to use but also its,going to find it hard to deliver on what,its intended for so if you dont have,good foundations you might build that,library it wont be safe and it wont be,a great place to read books and the,similar thing when youre building,technology solutions if you neglect the,five pillars that we identified the,world architecture framework security,reliability performance efficiency and,cost optimization and importantly how,youre going to operate that system one,of the things we see is that when people,build systems they dont necessarily,think about on day one am i designing,this for operations so you have to think,about how youre going to also operate,it so if you think about something like,the Excel center its not just enough to,think about its physical construction,you also have to think about how is it,going to be used and as youll see with,most technology solutions youll put a,lot of time and resource into the design,phase but the runtime will actually,dominate your costs and the value of,that system so you really want to put,effort in from day one on thinking about,how that system is going to be used so,how are people applying well architected,one of the things we like to do at a ws,is to create ways of doing things that,customers can choose how they apply them,for themselves and what weve seen as a,reoccurring pattern of success are these,three things firstly people who are,successful using well architected use,as a way to have a conversation about,how do i improve my architecture they,dont use it as an audit process so its,not about blaming someone about the,mistakes theyve made its really about,a consultation on how do I look at this,architecture and how can I make it,better secondly the other thing that we,do is we make sure that well architected,is pragmatic so all of the advising well,architected is based upon experiences of,real customers running real systems on,AWS so this isnt based upon people,thinking in ivory towers about the best,way to run architectures this is really,about,have we seen customers be successful,with this and so hopefully when youre,reading the well architected framework,youll see that the advice is based upon,things that youve also seen being,successful as well and finally I would,say the other thing we see is if you use,well architected as a continuous process,so if youre thinking about a product,lifecycle using it early on in your,design phase and as your product matures,helps you to continue to look at your,architecture and work out how you can,improve it what you dont want to have,is a static architecture which you have,to rebuild every few years because you,havent continued to evolve it and so,the well architected framework allows,you to turn that into more of a process,so how might I go about reviewing an,architecture and here you have choice so,this has evolv

AWS Well Architected Framework Explained | How does AWS Well Architected Tool work?

hello everyone and welcome back to the,channel a lot of you had requested for a,video,on aws well architected framework and i,was really confused as to how should i,make a topic which is mostly a,documentation interesting,and here it is so lets start off with,aws well architected framework,[Music],this is a very interesting topic but,usually ignored by a lot of students but,we wont do that,because it sets a base for you as a,developer or even an architect,what i have promised myself is that we,will cover each pillar,in depth and well do a very good,hands-on demo on this as well,so make sure that you have subscribed,because we will be dividing each of,these topics to separate videos,and i really dont want you to miss out,on any one of them,so please make sure that you have,subscribed having said this lets listen,to a very important message,during these testing times i request you,to please stay at home,and stay safe if you have to step out,please wear a mask,follow social distancing norms wash your,hands and if you feel sick,stay at home and follow proper,medication by following these rules,we can all be on the winning side this,is my humble request,and before moving forward join me in,congratulating our very own pythonics,hall of fame members sanjeev gaurav,kingshuk and jonathan,they have successfully completed their,solutions architect associate,certification,so please put your wishes in the comment,section below,and if you also want to be a part of the,hall of fame members list,please tag python yd with your,certificates on,linkedin so please tag python yt,with your certificates on linkedin it,really makes me feel very happy and it,gives me the motivation to make these,videos,and it also helps the channel grow,awesome job guys,keep them coming as i already told you,that we will be discussing each topic in,depth,and we will be dividing them into,separate videos,but that should be a starting point,isnt it,so we will first discuss about well,architected framework,and what can it help us with and how we,can make use of it,to make our life easy while designing or,delivering,products to the world yes these things,might feel a bit over the top,but this framework is your handbook if,you want to excel,in delivering and managing products with,aws,for that aws obviously provides us five,pillars,just like a house actually needs pillars,to make it stable,and to withstand any calamity a strong,base and pillar,is needed for a product to excel and the,pillars are security,reliability cost optimization,performance efficiency,and operational excellence and its not,that you can work with only one pillar,or two or,leave others in the background you,cannot do that,you have to use all of these pillars,because you cannot make a house with,only one or two pillars,the house will fall isnt it similarly,for your products,you need security so that it should be,secured,it should be reliable so that users,dont face errors or glitches while,using it,the cost should be optimized,optimization doesnt mean cost cutting,or,being a miser it means you need to make,an optimal use of the budget,so that you have the right balance,between the budget and the resource,allocation,the performance is important for you and,your users if i ask you what is,efficiency you might tell me that,efficiency is the ratio of the useful,work,performed by a machine or in a process,to the total energy expanded or,heat taken in yes in the same way the,way you provision features should be,efficient with the work done by your,developers,and it should not have negative impact,the strategy or the business relations,or operations are a determining factor,for the success of your organization,and that is operational excellence and,thats also very important,so you see all these factors or pillars,are really important,and these terms might be very,overwhelming for you right now,but trust me by the end of these,sessions youll be through,like what they say hot knife through,cold butter isnt it,yes just like that so lets see what aws,tells us about the well architected,framework,so aws well architected helps cloud,architects,build secure high-performing resilient,and efficient infrastructure for their,applications,and workloads so by just reading this,line,you might be getting all kinds of,thoughts for example you might be,thinking,if it helps an architect build secure,high performing efficient,infrastructure for their application and,workload what is this framework,is it a service by aws or is the tool,that we must enable,or is it a code that we must incorporate,so that our,infrastructure becomes top quality and,yes you might be partially right here,its a tool but most importantly its a,tool that is going to,question you and the way you have,designed your product,or youre going to design your product,so if you are an architect,or a developer who is designing an,application and its infrastructure,how are you going to validate that your,application or product,is in the right direction and whether it,will achieve the desired results or not,then aws well architect is your answer,to that,and you might ask how but thats what we,will be discussing in this series of,videos,so make sure that you cover each part,carefully and make sure that you dont,miss out on any of these sessions,for that please make sure that you have,subscribed and you have turned on the,notification bell icon so in order to,make an excellent product,you need to have a strong foundation as,i already told you,and to provide you the strong base for,your design,aws provides us with five pillars this i,have told you,three times right now security,reliability cost optimization,performance efficiency,and operational excellence and you must,know that a product is built in stages,so you have a set of features and you,apply,a software development model like agile,or waterfall,or the kind of software development life,cycle that you have as per your,customers request,similarly aws provides us a consistent,approach for the customers and partners,to evaluate architectures and implement,designs that can scale over time,so with growingdemand you have to keep,making changes but it will surely affect,cost security and the more components,that are being used,it will affect the performance,efficiency as well so you have to keep,these things,in mind so considering these factors aws,decided to provide us with a white paper,for our reading so that we can take,better decisions while scaling or,designing the application,and with growing popularity among,architects,this white paper was modeled into a tool,called aws well architected tool and you,know what,its completely free to use and its an,important aspect of product delivery,so remember its a free tool that you,can make use of,just go ahead to your aws console right,now and type aws well architecture tool,you will get free access to this of,course if you have created your free,tier account,and these pillars that you see here are,on its own right,a domain in itself that has to be,handled very carefully and its not that,you will,value one domain more than others you,have to take each of these pillars,seriously with,utmost importance but how do we validate,that,how do we know we are in the right track,so for that you need to question,yourself,if your product is good enough can it,scale with growing demand,or is that a safe product to use but you,dont have to do that,and the same reason why we have this,framework,its very simple on the aws framework,tool,you just need to answer a set of,foundational questions about your,application,and operation based on the outcome of,your answers,you learn how well your architecture,aligns with cloud best practices,and not just that you will also be,provided guidance for making,improvements isnt that awesome yes it,is,now that we know why and how we can make,use of the aws well architected,framework,lets talk in brief about each of these,pillars,so the first pillar is operational,excellence in th

Best practices to architect a reliable infrastructure II AWS Well Architected – Reliability Pillar

welcome cloud enthusiasts,if you learned something new from this,video share it with your friends,dont forget to subscribe to the cloud,enthusiast channel,and hit the bell icon never to miss new,videos,in this video we will explore the,reliability pillar,of aws well architected framework,after this video you will learn design,techniques and best practices,to architect a reliable environment,capable of enduring resource failures,let us understand reliability using a,car analogy,a reliable car breaks down less often,and it can alert you of any upcoming,problems,so that you can get it fixed before the,car stops working,similarly a systems reliability,can be assessed by its ability to avoid,failures,and to recover quickly from a failure,event,in the cloud reliability is dependent,on the resources used to build the,architecture,from the application users perspective,an application is considered reliable,if it is available when needed and is,working as expected,therefore reliability of an application,can be measured in terms of its uptime,so if you are building an application,with an uptime,of 99.9 percent,that means it will be unavailable for 8,hours,and 45 minutes each year,similarly uptime of 99.95,will be unavailable for four hours and,22 minutes each year,an uptime of 99.99,will be unavailable for 52 minutes each,year,and uptime of 99.999,will be unavailable for five minutes,each year,architecting a reliable solution is,difficult,and expensive especially in traditional,data centers,however the cloud provides the ability,to spin up resources when needed,by treating them as code,therefore achieving the desired,reliability,is much easier especially when,automation techniques are used,this makes it one of the driving factors,for organizations,to embrace the cloud,let us review some of the traits of a,reliable architecture,define before you start working on the,design,you need to understand the applications,reliability requirements,based on the business objectives,reliability is often at odds with the,cost,therefore you have to find a balanced,approach when architecting,during this phase architects need to,determine,recovery time objective or rto,which is the maximum acceptable time it,takes to recover from a failure,in other words it is an acceptable,downtime,and recovery point objective rpo,which is the maximum acceptable time,duration,since the last data recovery point,this determines what is considered an,acceptable loss of data,between failure and recovery,reduce impact once you understand,the business requirements you have to,architect the solution,to minimize the impact of failure,suppose you are running a web server,that requires 8 cores of cpu,instead of using a single ec2 instance,with 8 cores,use 2 ec2 instances with 4 cores each,and divide the workload amongst,this strategy can help avoid the single,point of failure,in case one instance fails the other can,keep the application running,until the system recovers to full,capacity,to protect against availability zone,failures,you can provision each of these,instances,in a separate availability zone,and to protect against the entire region,failure,you can set up multi-region deployments,this is especially useful for mission,critical applications,elasticity using cloud services like,auto scaling,you can build elastic architectures that,can withstand,varying loads by automatically scaling,up,and down when needed this way,you do not have to over provision or,under provision the resources,monitor the most critical step,in creating a reliable system is,monitoring anomalies,and triggering an alert if a problem is,detected,therefore having adequate monitoring and,alerting mechanism,is an essential part of any reliable,architecture,cloudwatch is an aws service that,provides,comprehensive tools for monitoring and,alerting purposes,recovery monitoring and alerting coupled,with automation,can enable a system to recover from,failures without human intervention,for example cloud watch and auto scaling,can be used together to recover from,failed ec2 instances,similarly rds can be used with,cloudwatch,to trigger a failure event if the master,database fails,and shifts traffic to the secondary,database automatically,backup backing up data is essential for,the continuation of any business,in an unforeseen event of losing the,master copy of your valuable data,you can always restore it using the,backup copy,therefore backup your data periodically,using services like,amazon s3 which provides 11,nines of durability by replicating your,data across multiple availability zones,your recovery point objective defines,how often you should back up your data,testing traditionally testing a system,was limited,to the extent of verifying its ability,to work under normal conditions in,contrast,you can simulate various failure,scenarios,using the cloud tools and services and,validate the recovery process,for example you can stop an ec2 instance,and verify that the auto scaling event,launches a new ec2 instance,change management changes to the,production environment,need to be automated so that the system,can be rolled back easily,in order to restore functionality if the,deployment is unsuccessful,cloud formation aws config and code,deploy are some of the tools you can use,for change management limits,resources are available in the cloud,when you need them,however certain limits are imposed on,the services,that you need to account for while,architecting,some are soft limits and can be easily,increased by contacting aws customer,service,while others are hard limits that need,to be considered during the design phase,aws trusted advisor can be used to,review the service limits,that apply to your account,you can also set up notifications via,cloud watch alarms,when youre about to hit the limit,following these principles will help you,design reliable architectures,managed services like s3 dynamodb,and aurora offer built-in resiliency,and should be preferred comment below,to share how you made your applications,reliable

How to Prepare for an AWS Well Architected Review

welcome back to the thoughtful techie,Cloud YouTube channel today were going,to jump right in and talk about the AWS,World architected review specifically,what it is and how you prepare for the,review now before we get started let me,give you a little bit of background if,you dont already know I have worked,with AWS for over six years Ive done a,number of AWS World architected reviews,on customer workloads so I know a thing,or two about how to do a World,architected review and what to look for,and what good looks like so pay close,attention because youre going to learn,a lot in this session what can you,expect from this particular session well,first Im going to intro you to the AWS,World architected framework second Im,going to go over the core tenets of what,it means to be well architected the,tenants sometimes referred to as pillars,are as follows there are six of them,theyre very important number one is,security,the second one is reliability third is,performance the fourth is cost,optimization the fifth is operational,excellence and the last but certainly,not least,and the newest member of the world,architecture framework pillars is,sustainability,the third thing were going to take a,look at is which workloads you should,review like I say you couldnt have many,many workloads and you may not have the,time and energy to review every single,one of them so you need to prioritize,Im going to go over what that looks,like to be able to categorize what you,should review,fourth were going to talk about Key,Well architected stakeholders that,should be reviewed that should be a part,of the review process and then five will,close things out and discuss next steps,so what is the world architected,framework,the world architected framework provides,access to knowledge developed over tens,of thousands of architecture reviews,the well architected review started off,many years ago,and AWS Solutions Architects would,review customer workloads and over time,there were patterns that were formed,these patterns were later aligned over,several iterations into a framework that,aligned to these six pillars the world,like protected framework evolves over,time and it continues to get better,as,the AWS Cloud evolves,its designed to help,those who consume AWS and AWS services,to always be able to leverage the best,practices and reduce architectural,issues and minimize risk to your,business,the AWS World architect of framework,is essentially General design principles,that facilitate what a good design looks,like in Cloud,so some of the things at a very high,level that the world architect to review,enables you to do is things like stop,having to guess about capacity it allows,you to test your systems at scale it,allows you to build data-driven,architectures,you can employ automation so now that,you can easily enable experimentation it,allows for the evolution of the,architecture and finally,it allows and ensures that your,architectural,is sustainable and has the Earth in mind,as you build so as I said the AWS World,architecture framework is really a set,of questions that allows you to evaluate,how an architecture is aligned to AWS,best practices and its broken down into,those six pillars as I mentioned earlier,security reliability performance,efficiency cost optimization operational,excellence and sustainability,now were going to dive into each one of,these pillars to dig a little bit deeper,so for the security pillar security is,all about protecting information those,systems that host that information and,the assets while still being able to,deliver business value through risk,assessment and mitigation of those,strategies,the reliability pillar is the ability of,a system to recover from infrastructure,or service disruptions dynamically and,acquiring compute resources to meet the,demand and mitigate any disruptions such,as misconfigurations or transient,network issues,performance efficiency,is the efficient use of computing,resources to meet requirements as well,as maintaining that efficiency as the,demand changes and Technologies evolve,the cost optimization pillar is all,about assessing your ability to avoid,and eliminate it unnecessary costs and,sub-optimal resources that are not,optimized and just wasting money and,cost,and you use those savings,to reinvest back into your business,operational excellence is all about,practicing best operational practices,and procedures used to manage your,production workloads such as run books,and playbooks,sustainability is about understanding,the impacts of the services used,quantifying those impacts through the,entire workload life cycle and applying,design principles and best practices to,reduce these impacts,now lets look at what workloads should,be reviewed this is not an,all-exhaustive list this is just six,overarching areas that you need to think,about the first is,could damage be calls to your business,reputation or revenue streams,given this particular workload number,two is this workload a foundational,business applications,such as benefits payroll,Etc now let me just back up just a,minute in case its not clear when I,refer to a workload this is really,another word for the architecture that,underpins either the application or,service that provides value to your,customers so anytime you hear me say,workload just think of an application or,service and that the particular,architecture which is associated with,that,number three,so it looks like bullets two and three,are duplicates so well just keep on,moving,number four does your application have,an aggressive recovery Point objective,or recovery time objective a recovery,time objective is the time it takes for,you to be able to recover your,application the tighter that window the,more complex the architecture is going,to be and the more critical the business,deems that application same thing for,the recovery Point objective when you,have a failure this is the amount of,data that the business is willing to,lose,based on the time that application uh,fails the smaller that number is uh in,minutes the more complex that,application is the architect and thus,the more critical your business teams,application and the more likely thats,something you want to take a look at in,terms of the review,number five here,data security,are you having to achieve compliance,requirements such as HIPAA or pii or PCI,this is definitely a workload that you,want to submit to the review also the,last number six time bound event driven,workloads that are mapped to big events,could be things like the Super Bowl or,the Oscars or the open enrollment,uh in in a uh in summary,a workload,and whether or not it should be reviewed,is ultimately up to you,and these are just some guidelines of,things you need to look at to consider,now will our protected review needs to,involve a good representation from,several cross-functional teams Ive,indicated just a few here the first I,would suggest is security youre going,to want to have somebody there at the,table sitting with you as you conduct,the review that has good insights on the,security of that application and service,and the architecture you need to have,somebody thats familiar with the,operations knowing what it takes to,operate that particular application and,service,networking what are the ins and outs of,the networking of that particular,application or service you definitely,need to have an app Dev team there or,representation from that team Enterprise,Architects if you have Enterprise,Architects within your organization,definitely you want those Enterprise,Architects to have a seat at the table,and then ideally somebody from business,and financial theyre going to be very,keen on the cost now let me tell you in,out in the field in real life depending,on what size organization you are if,youre an Enterprise customer,sometimes its easy to get these,particular roles to have a seat at the,table however if youre a startup you,may wear several hats thats okay as,long as the