We use it based on automation. We can create new customers or entities and automatically apply specific configurations according to predefined rules. This automation is a key feature of Control Tower. Additionally, Control Tower can be scripted to automate these processes further. Although not directly related, the combination of AWS Management and Control Tower simplifies accounts' management and billing structure. One notable advantage is the separation between account structure management and account billing. For instance, it allows us to use a centralized billing system and centralized account management, which is highly beneficial. It has become very central and essential. Without Control Tower, for instance, we couldn't automate the creation of thousands of environments across the company, but with it, we can. You need to be a good AWS architect. It requires more skill than just being a practitioner. Ideally, you should be an architect and have an AWS Certification. Overall, I rate the solution a nine out of ten.
It serves as a valuable tool to streamline governance, ensure compliance across these accounts, and facilitate the establishment of standardized practices in areas like security, monitoring, and logging, which are often referred to as cross-cutting concerns. I would strongly recommend using Control Tower if you have multiple AWS accounts. Overall, I would rate it eight out of ten.
It is a highly commendable product. It significantly enhances the management of multi-account architectures. It stands out as one of the best products AWS has introduced in recent years. I'm confident that AWS will continue to make enhancements, possibly expanding support to additional regions and introducing more managed rules to seamlessly align with evolving business needs. I would rate it eight out of ten.
I highly recommend AWS Control Tower as it is a valuable tool for both first-time and long-term AWS adopters. It helps to manage policies and governance, which are crucial for maintaining security. It would be a beneficial asset for customers who have AWS in their infrastructure. I would rate it nine out of ten.
AWS Cloud Engineer/Cloud Architect at Landmark Technologies
Real User
Top 5
2023-09-15T20:07:35Z
Sep 15, 2023
Before choosing Control Tower, you must know what you want to do. I've noticed that most people who use it leave on-premises to go to the cloud. You shouldn't be in the cloud before thinking of using Control Tower. If you move into the cloud, you need the foundation to start something. You need somewhere to run your resources. When migrating into the cloud, you have to go for Control Tower. It will provide the best practices when setting up a landing zone. All the other solutions, like Account Factory and all of that, start from the foundation. People who have been in the industry for many years want cloud control. AWS Organization and single sign-on come automatically with Control Tower, but you can still create AWS Organization and single sign-on out of Control Tower. You need to know what you want to do with Control Tower. You need to know what to do with the solution's security capabilities. I rate AWS Control Tower a nine out of ten.
I think AWS Control Tower is a good solution, and I am comfortable understanding its functionalities. At the moment, I do not use stack-up solutions in any of my operations in a day, but I understand the channel that they help you to apply applications for the use of customers. I rate the overall product a five out of ten.
I give the solution a seven out of ten. People should not rely on AWS Control Tower alone because it is a portion of the configuration but it's not everything.
AWS Control Tower offers the easiest way to set up and govern a new, secure, multi-account AWS environment. It establishes a landing zone that is based on best-practices blueprints, and enables governance using guardrails you can choose from a pre-packaged list.
We use it based on automation. We can create new customers or entities and automatically apply specific configurations according to predefined rules. This automation is a key feature of Control Tower. Additionally, Control Tower can be scripted to automate these processes further. Although not directly related, the combination of AWS Management and Control Tower simplifies accounts' management and billing structure. One notable advantage is the separation between account structure management and account billing. For instance, it allows us to use a centralized billing system and centralized account management, which is highly beneficial. It has become very central and essential. Without Control Tower, for instance, we couldn't automate the creation of thousands of environments across the company, but with it, we can. You need to be a good AWS architect. It requires more skill than just being a practitioner. Ideally, you should be an architect and have an AWS Certification. Overall, I rate the solution a nine out of ten.
Overall, I rate the solution a nine out of ten.
I rate AWS Control Tower a ten out of ten since it is easy and automated.
It serves as a valuable tool to streamline governance, ensure compliance across these accounts, and facilitate the establishment of standardized practices in areas like security, monitoring, and logging, which are often referred to as cross-cutting concerns. I would strongly recommend using Control Tower if you have multiple AWS accounts. Overall, I would rate it eight out of ten.
It is a highly commendable product. It significantly enhances the management of multi-account architectures. It stands out as one of the best products AWS has introduced in recent years. I'm confident that AWS will continue to make enhancements, possibly expanding support to additional regions and introducing more managed rules to seamlessly align with evolving business needs. I would rate it eight out of ten.
I highly recommend AWS Control Tower as it is a valuable tool for both first-time and long-term AWS adopters. It helps to manage policies and governance, which are crucial for maintaining security. It would be a beneficial asset for customers who have AWS in their infrastructure. I would rate it nine out of ten.
Before choosing Control Tower, you must know what you want to do. I've noticed that most people who use it leave on-premises to go to the cloud. You shouldn't be in the cloud before thinking of using Control Tower. If you move into the cloud, you need the foundation to start something. You need somewhere to run your resources. When migrating into the cloud, you have to go for Control Tower. It will provide the best practices when setting up a landing zone. All the other solutions, like Account Factory and all of that, start from the foundation. People who have been in the industry for many years want cloud control. AWS Organization and single sign-on come automatically with Control Tower, but you can still create AWS Organization and single sign-on out of Control Tower. You need to know what you want to do with Control Tower. You need to know what to do with the solution's security capabilities. I rate AWS Control Tower a nine out of ten.
I rate AWS Control Tower an eight out of ten.
I think AWS Control Tower is a good solution, and I am comfortable understanding its functionalities. At the moment, I do not use stack-up solutions in any of my operations in a day, but I understand the channel that they help you to apply applications for the use of customers. I rate the overall product a five out of ten.
I give the solution a seven out of ten. People should not rely on AWS Control Tower alone because it is a portion of the configuration but it's not everything.