- Talk to an Expert
Talk to an Expert
' + bio + ''); $(this).closest('.leaders-row').find('.leader-bio').show(200); $(this).closest('.vc_column_container').find('p').css({backgroundColor:"#ececec"}); }); /* $('.leadership-faces .hidden-xs img').on('mouseover', function () { var bio = $(this).closest('.vc_column_container').find('h5').html(); var who = $(this).closest('.vc_column_container').find('p strong').html(); $(this).closest('.leaders-row').find('.leader-bio').html('' + bio + ''); $(this).closest('.leaders-row').find('.leader-bio').show(200); $(this).closest('.vc_column_container').find('p').css({backgroundColor:"#ececec"}); }); $('.leadership-faces .hidden-xs img').on('mouseout', function () { var who = $(this).closest('.leaders-row').find('.leader-bio h6').data('who'), self = this; $(this).closest('.leaders-row').find('.leader-bio').hide(200); setTimeout(function () { var who2 = $(self).closest('.leaders-row').find('.leader-bio h6').data('who'); $(self).closest('.vc_column_container').find('p').css({backgroundColor:"#fff"}); if (who == who2) { $(self).closest('.leaders-row').find('.leader-bio').html(''); } }, 200); });*/ }); // GENERAL LOADSsetTimeout(function () { jQuery('.lw-buttonify').each(function () { var url; if (jQuery('a', this).length < 1) { return; } url = jQuery('a', this).eq(0).attr('href'); jQuery('a', this).on('click', function (e) { e.preventDefault(); }); jQuery(this).on('click', function () { location.href = url; }); }); jQuery('body').on('focus', '.hubspot-form-panel input.hs-input, .hubspot-form-panel select.hs-input, .hubspot-form-panel textarea.hs-input', function () { jQuery(this).closest('.field').addClass('touched'); }); jQuery('.banner-footer-strap p') .append('') .append('') ; jQuery('body').on('click', '.mobile-talk-to-expert-cta span', function () { jQuery('body, html').animate({ scrollTop: jQuery(".hubspot-form-panel").offset().top - 40 }, 200); }); jQuery('.add-arrow').not('.listing-item-more, .no-add-svg').append(' '); }, 250); (function header_when_hubspot_ready () { if (window.hasOwnProperty('hubspot') && jQuery('.hubspot-form-panel input.hs-input').length > 0) { jQuery('.hubspot-form-panel input.hs-input, .hubspot-form-panel select.hs-input, .hubspot-form-panel textarea.hs-input').not('select').each(function () { if (jQuery(this).val().length > 0) { jQuery(this).closest('.field').addClass('touched'); } }); } else { setTimeout(header_when_hubspot_ready, 250); }}());
0
0
- Cloud Optimization
By Jessica Cowle
Your AWS environment changes constantly. Engineers spin up and down new instances, change security groups, and experiment with new AWS services. So how do you make sure that your cloud doesn’t turn into the Wild West?
AWS recommends you conduct a Well-Architected Review every 12-18 months. The Well-Architected Review is a systematic approach to evaluating AWS architectures and can help you identify and fix potential issues with your environment. It’s based off the AWS Well-Architected Framework, which is a comprehensive set of AWS best practices (described over the course of several hundred pages of AWS whitepapers).
Don’t have time to dig through AWS whitepapers? Good news, we did. Below find out how to start a Well-Architected Review.
A Brief Overview of the Well-Architected Framework
AWS has divided the Well-Architected Framework into five distinct sections or Pillars. Each Pillar is designed to help you tackle a specific aspect of your environment.

Operational Excellence is the ability to run and monitor systems that deliver business value and continuously improve supporting processes and procedures. AWS outlines best practices in six design principles:
- Perform operations as code
- Annotated documentation
- Make frequent, small, reversible changes
- Refine operations procedures frequently
- Anticipate failure
- Learn from all operational failures
Security is having the ability to protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies. When implementing security on your architecture, Amazon recommends six design principles:
- Implement a strong identity foundation
- Enable traceability
- Apply security at all layers
- Automate security best practices
- Protect data in transit and at rest
- Keep people away from data and prepare for security events
Reliability is making sure the system is capable of recovering from infrastructure or service disruptions, meeting demand for acquiring computing resources, and mitigating disruptions and network issues. To increase reliability, AWS recommends:
- Test recovery procedures
- Automatically recover from failure
- Scale horizontally to increase aggregate system availability
- Stop guessing capacity
- Manage change in automation
Performance efficiency is optimally using resources to meet requirements as demand changes and as technology evolves. In order to achieve performance efficiency, there are five principles of best practices:
- Democratize advanced technologies by pushing difficult technologies into the cloud vendor’s domain
- Go global in minutes
- Use serverless architectures to help you quickly deploy your system in multiple regions and remove the need to traditionally run and maintain servers
- Use the technology approach to create mechanical sympathy
Cost optimization is the ability to run systems to deliver business value at the lowest price point. To optimize for the lowest cost:
- Adopt a consumption model
- Measure overall efficiency by understanding the gains made from increasing output to reduce costs
- Stop spending money on data center operations
- Analyze and attribute expenditure
- Use managed services to reduce the ownership cost
In this video, our CTO Jason McKay talks about the Well-Architected Framework:
What’s the Process for Conducting a Well-Architected Review?

During the Well-Architected Review, a cloud expert will review your workload using the Well-Architected tool against the five pillars. Once the review is completed, your company will receive videos and documentation related to AWS best practices, a report summarizing your workload review, and a dashboard where you can view the results of workload reviews across the organization. You can then use the detailed findings to remediate issues and improve your infrastructure according to AWS best practices.
Why the Well-Architected Framework? Why not ISO or SOC or some other standard?
Unlike other well-established security standards, the Well-Architected Review tackles architectural best practices, cost efficiency, and other principles not traditionally evaluated in formal audits.
Logicworks recommends the Well-Architected Framework because it codifies and consolidates best practices across ITIL, Agile, and DevOps. It covers more than how to build a good AWS architecture. It shows you how you should also operate and maintain it.
How to Perform a Well-Architected Review Today
You can conduct a Well-Architected Review on your own with the Well-Architected Tool, or you can work with an approved Well-Architected partner, like Logicworks, to perform a custom evaluation. By engaging an approved partner, you can often receive funding from AWS to help offset the cost of a Well-Architected Review.

Sample from the Well-Architected Tool
Want a free demo of the Well-Architected Review? Learn more here.
October 11, 2019
-
-
-
Leave A Comment
(Video) How to Prepare for an AWS Well Architected Review Manage Cookie Consent
We use technologies like cookies to store and/or access device information. We do this to improve browsing experience and to show personalized ads. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
FunctionalAlways active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage optionsManage servicesManage vendorsRead more about these purposes
View preferences
{title}{title}{title}
Logicworks Control Tower
AWS Control Tower is a purpose-built management utility for building, organizing, and maintaining multiple AWS Accounts. Control Tower allows you to deploy accounts programmatically by using predetermined templates that assign specific guardrails. Security, identitify management, logging, cost management, and other key business functions can be defined and executed through a successful Control Tower implementation. Control Tower operates across Organizational Units and defines rulesets through Service Control Policies. Control Tower Account Factory automates the deployment and configuration of new accounts.
Sessions & Milestones
Briefing & Discovery
Logicworks will lead a workshop to introduce core concepts including use cases, management, automation, and governance. The requirements for your deployment will be identified and documented, to align our technical resources around your project goals & objectives.
(Video) AWS Cost Optimisation Series: Well Architected Review | Amazon Web ServicesArchitecture Design
Based on your requirements, Logicworks will present the recommended architecture design. Our team will share a diagram of the proposed configuration and review the specifics points of your deployment.
Transfer Knowledge
When your deployment is complete, Logicworks will present the details to your team and provide a guided walkthrough of the environment.
Scope & Details
Scope
- Organization Units
- Governance Requirements
- Security Guardrails Definition
- Service Control Policies.
- AWS Config Rules
- Service Control Policy Definitions
- Guardrail Deployment
Deliverables
- Default Control Tower in Desired Region
- Administer Guardrails
- Configure Account Factory
- Provide Reusable IAC Template for Default VPC
- Standardized Networking & Route Tables
- Administer AWS SSO Configuration (can include integration with Active Directory)
- Document Multi-Account Structure and Governance Strategy
- Deploy Up To 2 Customizations for Control Tower (CfCT)
- Cloud Solution Documentation detailing Control Tower Solution
- Architecture Diagram and Technical Specifications
Logicworks Control Tower
Logicworks Control Tower Accelerator is ideal for AWS users who would benefit from a multi-account management strategy. It includes an out-of-the-box well-architected, secure Landing Zone, that will provide a foundation for your AWS environment.
(Video) AWS re:Invent 2022 - The well-architected way (ARC210)Discovery & Requirements Workshop
Control Tower Discovery & Requirements session covering:
- Organization Units
- Security Guardrails Definition (Service Control Policies, AWS Config Rules)
- Define service control policies.
- Define guardrails based on governance requirements.
Architecture Design Workshop
Presentation and Workshop for Architecture Design, discuss and sign off on recommended solution (workshop)
Cloud Solution Documentation detailing
Control Tower solution with architecture diagram and technical specifications
Control Tower Deployment
- Default Control Tower in the desired Region
- Administering guardrails
- Configuring Account Factory Provide
- Reusable IAC template for a default VPC with standardized networking & route tables Administer
- AWS SSO configuration (can include integration with Active Directory)
- Document multi-account structure and governance strategy
- Deploy up to 2 Customizations for Control Tower (CfCT), per the design workshop
We architect your cloud with a deep understanding of how to enable security, resilience, scale, and efficiency.
(Video) AWS Well Architected Framework Tool Hands on demo- Accelerated Migration to AWS/Azure
- Achieve greater security and governance
- Mitigate Cost and Maximize ROI
- Streamline day-to-day cloud Operations
- Modernize tools and platforms
- Overcome staffing challenges with a stable tenured team
Please complete this form to have a specialist contact you.
Consult with a Sr. AWS Solutions Architect to learn how you can improve cost efficiency, security, performance, and compliance. This session is free with no strings attached.
Identify quick wins to improve performance
Improve cost efficiency by 20-30%
Get ready for a compliance audit
0
0
- Cloud Optimization
By Jessica Cowle
Your AWS environment changes constantly. Engineers spin up and down new instances, change security groups, and experiment with new AWS services. So how do you make sure that your cloud doesn’t turn into the Wild West?
AWS recommends you conduct a Well-Architected Review every 12-18 months. The Well-Architected Review is a systematic approach to evaluating AWS architectures and can help you identify and fix potential issues with your environment. It’s based off the AWS Well-Architected Framework, which is a comprehensive set of AWS best practices (described over the course of several hundred pages of AWS whitepapers).
Don’t have time to dig through AWS whitepapers? Good news, we did. Below find out how to start a Well-Architected Review.
A Brief Overview of the Well-Architected Framework
AWS has divided the Well-Architected Framework into five distinct sections or Pillars. Each Pillar is designed to help you tackle a specific aspect of your environment.
Operational Excellence is the ability to run and monitor systems that deliver business value and continuously improve supporting processes and procedures. AWS outlines best practices in six design principles:
- Perform operations as code
- Annotated documentation
- Make frequent, small, reversible changes
- Refine operations procedures frequently
- Anticipate failure
- Learn from all operational failures
Security is having the ability to protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies. When implementing security on your architecture, Amazon recommends six design principles:
- Implement a strong identity foundation
- Enable traceability
- Apply security at all layers
- Automate security best practices
- Protect data in transit and at rest
- Keep people away from data and prepare for security events
Reliability is making sure the system is capable of recovering from infrastructure or service disruptions, meeting demand for acquiring computing resources, and mitigating disruptions and network issues. To increase reliability, AWS recommends:
- Test recovery procedures
- Automatically recover from failure
- Scale horizontally to increase aggregate system availability
- Stop guessing capacity
- Manage change in automation
Performance efficiency is optimally using resources to meet requirements as demand changes and as technology evolves. In order to achieve performance efficiency, there are five principles of best practices:
- Democratize advanced technologies by pushing difficult technologies into the cloud vendor’s domain
- Go global in minutes
- Use serverless architectures to help you quickly deploy your system in multiple regions and remove the need to traditionally run and maintain servers
- Use the technology approach to create mechanical sympathy
Cost optimization is the ability to run systems to deliver business value at the lowest price point. To optimize for the lowest cost:
- Adopt a consumption model
- Measure overall efficiency by understanding the gains made from increasing output to reduce costs
- Stop spending money on data center operations
- Analyze and attribute expenditure
- Use managed services to reduce the ownership cost
In this video, our CTO Jason McKay talks about the Well-Architected Framework:
What’s the Process for Conducting a Well-Architected Review?
During the Well-Architected Review, a cloud expert will review your workload using the Well-Architected tool against the five pillars. Once the review is completed, your company will receive videos and documentation related to AWS best practices, a report summarizing your workload review, and a dashboard where you can view the results of workload reviews across the organization. You can then use the detailed findings to remediate issues and improve your infrastructure according to AWS best practices.
Why the Well-Architected Framework? Why not ISO or SOC or some other standard?
Unlike other well-established security standards, the Well-Architected Review tackles architectural best practices, cost efficiency, and other principles not traditionally evaluated in formal audits.
Logicworks recommends the Well-Architected Framework because it codifies and consolidates best practices across ITIL, Agile, and DevOps. It covers more than how to build a good AWS architecture. It shows you how you should also operate and maintain it.
How to Perform a Well-Architected Review Today
You can conduct a Well-Architected Review on your own with the Well-Architected Tool, or you can work with an approved Well-Architected partner, like Logicworks, to perform a custom evaluation. By engaging an approved partner, you can often receive funding from AWS to help offset the cost of a Well-Architected Review.
Sample from the Well-Architected Tool
Want a free demo of the Well-Architected Review? Learn more here.
October 11, 2019
Leave A Comment
Manage Cookie Consent
We use technologies like cookies to store and/or access device information. We do this to improve browsing experience and to show personalized ads. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
FunctionalAlways active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage optionsManage servicesManage vendorsRead more about these purposes
View preferences
{title}{title}{title}
Logicworks Control Tower
AWS Control Tower is a purpose-built management utility for building, organizing, and maintaining multiple AWS Accounts. Control Tower allows you to deploy accounts programmatically by using predetermined templates that assign specific guardrails. Security, identitify management, logging, cost management, and other key business functions can be defined and executed through a successful Control Tower implementation. Control Tower operates across Organizational Units and defines rulesets through Service Control Policies. Control Tower Account Factory automates the deployment and configuration of new accounts.
Sessions & Milestones
Briefing & Discovery
Logicworks will lead a workshop to introduce core concepts including use cases, management, automation, and governance. The requirements for your deployment will be identified and documented, to align our technical resources around your project goals & objectives.
Architecture Design
Based on your requirements, Logicworks will present the recommended architecture design. Our team will share a diagram of the proposed configuration and review the specifics points of your deployment.
Transfer Knowledge
When your deployment is complete, Logicworks will present the details to your team and provide a guided walkthrough of the environment.
Scope & Details
Scope
- Organization Units
- Governance Requirements
- Security Guardrails Definition
- Service Control Policies.
- AWS Config Rules
- Service Control Policy Definitions
- Guardrail Deployment
Deliverables
- Default Control Tower in Desired Region
- Administer Guardrails
- Configure Account Factory
- Provide Reusable IAC Template for Default VPC
- Standardized Networking & Route Tables
- Administer AWS SSO Configuration (can include integration with Active Directory)
- Document Multi-Account Structure and Governance Strategy
- Deploy Up To 2 Customizations for Control Tower (CfCT)
- Cloud Solution Documentation detailing Control Tower Solution
- Architecture Diagram and Technical Specifications
Logicworks Control Tower
Logicworks Control Tower Accelerator is ideal for AWS users who would benefit from a multi-account management strategy. It includes an out-of-the-box well-architected, secure Landing Zone, that will provide a foundation for your AWS environment.
Discovery & Requirements Workshop
Control Tower Discovery & Requirements session covering:
- Organization Units
- Security Guardrails Definition (Service Control Policies, AWS Config Rules)
- Define service control policies.
- Define guardrails based on governance requirements.
Architecture Design Workshop
Presentation and Workshop for Architecture Design, discuss and sign off on recommended solution (workshop)
Cloud Solution Documentation detailing
Control Tower solution with architecture diagram and technical specifications
Control Tower Deployment
- Default Control Tower in the desired Region
- Administering guardrails
- Configuring Account Factory Provide
- Reusable IAC template for a default VPC with standardized networking & route tables Administer
- AWS SSO configuration (can include integration with Active Directory)
- Document multi-account structure and governance strategy
- Deploy up to 2 Customizations for Control Tower (CfCT), per the design workshop
We architect your cloud with a deep understanding of how to enable security, resilience, scale, and efficiency.
- Accelerated Migration to AWS/Azure
- Achieve greater security and governance
- Mitigate Cost and Maximize ROI
- Streamline day-to-day cloud Operations
- Modernize tools and platforms
- Overcome staffing challenges with a stable tenured team