Effectual Achieves Inaugural HashiCorp Infrastructure Competency

Effectual has been awarded the HashiCorp Infrastructure Competency as part of the newly released Partner Technical Competency Program for Systems Integrators. Effectual is one of only six companies globally to be recognized with the HashiCorp Infrastructure Competency as part of the program’s launch.

Effectual Wins 2022 Managed Service Provider Stratus Award

Effectual, a modern, cloud first managed and professional services company, announced today that its public sector arm has earned ISO 9001:2015 certification. ISO 9001 is the world’s most widely recognized quality management standard, developed and published by the International Organization for Standardization (ISO).

Effectual Public Sector Inc. Awarded ISO 9001:2015 Certification

Effectual, a modern, cloud first managed and professional services company, announced today that its public sector arm has earned ISO 9001:2015 certification. ISO 9001 is the world’s most widely recognized quality management standard, developed and published by the International Organization for Standardization (ISO).

Effectual Public Sector Inc. Appraised at CMMI Level 3 (ISACA’s Capability Maturity Model Integration)

Effectual, a modern, cloud first managed and professional services company, announced that its public sector arm has been appraised at level 3 of ISACA’s Capability Maturity Model Integration (CMMI®). Effectual Public Sector Inc. provides mission-critical IT modernization solutions to Federal, State, Local, Education, and Nonprofit organizations. CMMI is a proven, outcome-based performance model and a globally accepted standard committed to helping organizations drive continuous improvement and quality management efforts. The appraisal was performed by Concept Quality Assurance Labs.

Considerations for AWS Control Tower Implementation

AWS Control Tower is a recently announced, console-based service that allows you to govern, secure, and maintain multiple AWS accounts based on best practices established AWS.

What resources do I need?

The first thing to understand about Control Tower is that all the resources you need will be allocated to you by AWS. We will need AWS Organizations established, an account factory to create accounts per LOB, and Single Sign On (SSO) to name a few. Based on the size of your entity or organization, those costs may vary. In the Control Tower precursor, AWS Landing Zones, we found that costs for this collection of services could range near $500-$700 monthly for large customers (50+ accounts), as deployed. Control Tower will probably be a similar cost, possibly higher depending on the size of your organization. I will address later in this post on how to go and use Control Tower once you have an account set up a Brownfield situation. In a perfect world, it would be nice to set up the Control Tower and in a Greenfield scenario, but sadly, 99% of the time, that’s not the case.

If you’re a part of an organization that has multiple accounts in different lines of business, this service is for you.

What choices do I need to make?

In order to establish a Cloud Enablement Team to manage Control Tower, you need to incorporate multiple stakeholders. In a large organization, that might entail different people for roles such as:

  1. Platform Owner
  2. Product Owner
  3. AWS Solution Architect
  4. Cloud Engineer (Automation)
  5. Developer
  6. DevOps
  7. Cloud Security

You want to be as inclusive as possible in order to get the most breadth of knowledge. These are the people that will be making the decisions you need to migrate to the cloud and then most importantly, thrive once present and remain engaged. We have the team, so now what can we do to make Control Tower work the best for us?

Decisions for the Team

1. Develop a RACI

This is one of the most crucial aspects of Operations. If you do not have accountability or responsibility, then you don’t have management. Everyone must be able to delineate their tasks from the rest of the team. Finalizing everyone’s role in the workflow then will solve a lot of issues before they happen.

2. Shared Services

In the shared services model, we need to understand what resources are going to the cloud and what will stay. Anything from Active Directory to DNS to one-off internal applications will have to be figured out in a way to accommodate functionality and keep the charge back model healthy. One of Control Tower’s most redeeming and worthy qualities is knowing what each LOB is costing and how they are helping the organization overall.

3. Charge Backs

Since the account factory (previously called Account Vending Machine) is established, each LOB will have its own account. In order to see what the LOB costs are, you must have an account. AWS does not do pricing based on VPC, but by account. Leveraging Control Tower, tagging, and third-party cost management resources all can combine to give an accurate depiction of the costs incurred by a specific line of business.

4. Security

Security will have all logs dumped from each account into a centralized log bucket that can be pointed to the tool of choice to analyze those logs. Other parties may perform audits to read your logs using ready only functions in an account that has nothing else, another feature of Control Tower. The multi-account strategy not only allows for better governance but also now helps in case of compromise. If one account has been compromised, then the blast radius for all the other accounts is minimal. Person X may have accessed a bucket in a specific account, but they did not access it anywhere else. The most important thing to remember is that you cannot treat cloud security like data center security.

There are plenty of choices to make as it relates to Control Tower moving forward for an organization, but if you plan correctly and make wise decisions, then you can secure your environment and keep your billing department happy. Hopefully, this has helped you see what it takes in the real world to prepare. Good luck out there!