AWS Well-Architected Framework

 Hi there!

Lets talk AWS Well-Architected Framework. The bulb made of recommended strategies which illuminates and increases the value of your beloved business.

So lets get into it!

Lets start with,

1.What is AWS Well-Architected Framework all about?

The AWS Well-Architected Framework helps you learn architectural best practices for designing and operating secure, reliable, efficient, cost-effective, and sustainable workloads in the AWS Cloud. It provides a way for you to consistently measure your architectures against best practices and identify areas for improvement.

2.Who created this framework?

AWS Solution Architects (Well, that was tough to guess wasn't it?, hehe). They have years and years of experience architecting solutions across a wide variety of business verticals and use cases. SA' s have helped design and review thousands of customers’ architectures on AWS. From this experience, AWS has identified best practices and core strategies for architecting systems in the cloud.

3.When should these set of best practices should be considered?

All the time!!. If there is a workload running on AWS and is not reviewed against the framework, go do it, now!, and optimize the infrastructure accordingly. If you are going to deploy business system, do checkout the framework and come up with architecture that aligns with the AWS Well-Architecture Framework/ Best practices.

4. How can the present architecture be reviewed and can be optimized to follow the best practices?

AWS provides a service for reviewing your workloads at no charge. The AWS Well-Architected Tool (AWS WA Tool) is a service in the cloud that provides a consistent process for you to review and measure your architecture using the AWS Well-Architected Framework. The AWS WA Tool provides recommendations for making your workloads more reliable, secure, efficient, and cost-effective.

Now lets touch upon the pillars of the framework.

The pillars of AWS Well-Architected Framework

1. OPERATIONAL EXCELLENCE

Subdivisions:
🠊 Evolve: run workloads effectively.
🠊 Prepare and Operate: gain insight into the operations.
🠊 Organization: continuously improve the process to deliver good business.

  • Improving processes and procedures to deliver business by understanding and settling the priorities of a team, and each role in a team.
  • Understanding the compliance , governance and workflow structure of the client.
  • Mitigate risks, analyze problems and overcome them by continuously gaining insights on workflow and workload.
  • Dedicate time and resources for continuous incremental improvements to evolve the effectiveness and efficiency of your operations.  
2. SECURITY
  • Protect Data.
  • Protect Systems.
  • Protect Assets.
3. RELIABILITY
  • The ability of a workload to perform its intended function correctly and consistently.
  • Automatically recover from failure.
  • Stop guessing capacity, use the power of scalability.
  • Test recovery procedures.
  • Scale horizontally to increase the workload availability.
  • Manage service quotas and constraints.
  • Prepare and test backup and disaster recovery plans by simulating failures.
4. PERFORMANCE EFFICIENCY
  • Ability to use computing resources efficiently.
  • To maintain the efficiency as demand changes and technologies evolve.
  • Providing architecture which includes suitable and right-sized AWS services to run the workload.
  • Optimize and evolve on the run.
  • Monitor to ensure right performance.
5. COST OPTIMIZATION
  • Ability to run systems to deliver business value at the lowest price point.
  • Practice cloud finance management.
  • Manage demand and supply resources.
  • Use cost-effective services and resources.
  • Expenditure and usage awareness.
  • Optimize workload on the run or overtime.
6. SUSTAINABILITY
  • Understand your impact.
  • Establish sustainability goals.
  • Adopt new, more efficient hardware and software offerings.
  • Use managed services.
Conclusion:
This blog talks about what, when, who, and how 's of AWS Well-Architected Framework to give you a good understanding about it.
It also briefly highlights the pillars of the framework.
I have provided references below, check it out.
Hope you found it useful!

References:

                                                                                                                                           - ANKITHA B H

Comments

Post a Comment

Popular posts from this blog

Multi-VPC connectivity, AWS network infrastructure.(Part-1)

Image
  Overview Amazon Web Services (AWS) customers often rely on hundreds of accounts and virtual private clouds (VPCs) to segment their workloads and expand their footprint. When a VPC needs to communicate with another VPC present in the same or different region/account, there should be a connection established. As the number of VPCs inc reases in an account or in a region due to the expansion of workload, the communication between those VPCs and the VPCs present in different accounts or regions becomes cumbersome. There could be various use cases and problems to solve other than mentioned above. AWS provides us choices that we can opt, which best suits our network infrastructure requirements. VPC to VPC connectivity VPC Peering AWS VPC peering is a point-to-point connectivity between VPCs. No transitive connections can be leveraged. Maximum of 125 peering connections per VPC. For hybrid connectivity i.e. peering connection between AWS VPC and on-premises network, VPN or Direct conne...
Read more

Multi-Tier Architecture in AWS with Best Practices.

Image
 Hi! This is my very first blog on Amazon Web Services, the team creating an  ocean of services, to whose beach party; innovation, business transformation and sustainability in technology and many more are most welcomed. I am currently working as an AWS Cloud Engineer and I am glad to say that building business workloads on AWS is one of my passion. Fundamentals are very important for any project to be successful. So, I thought I will take a basic yet very important topic and share my knowledge and opinions about it. Grab a coffee and sit back, you are about to take a multi-informational tour. Multi-Tier Architecture in AWS with Best Practices. In multi-tier architecture, there can be, Two layers comprising of Application tier and Database tier. Three layers comprising of Web tier, Application tier and Database tier. Four layers comprising of Web Tier, Application Tier, Proxy Tier and  Database Tier. I will be talking about the components, end-to-end function and how faul...
Read more

Multi-VPC connectivity, AWS network infrastructure.(Part-2)

Image
 Hi! This blog is the continuation of part-1, which is about the multi-VPC networking infrastructure. If you have not checked it out, click on the link below  Multi-VPC connectivity, AWS network infrastructure.(Part-1) :  https://cloudcentralblogs.blogspot.com/2022/05/multi-vpc-connectivity-aws-network.html So lets get into it, shall we? VPC to VPC connectivity AWS PrivateLink Source of above picture: AWS documentation This service can be used to route traffic between different VPCs and access AWS services on a private network using VPC endpoint, as shown in the above figure. The consumer and the service are not required to be in the same VPC. If the VPC is different, the consumer and service provider VPCs can have overlapping IP address ranges. So this a good option when client and servers in the two VPCs have overlapping IP addresses, as the endpoint configuration in consumer VPC leads to the creation of an ENI in the subnet with a private IP address that...
Read more