- Newest
- Most votes
- Most comments
Hi There
I see you mentioned you ran a few EC2 instances for a while. You do not need to run a paid EC2 instance. Try starting a free tier EC2 instance (Amazon linux ami on a t2.micro is fine), wait about 15 mins, then attempt to launch Control Tower.
If that does not work, you can still open a free support case by choosing Account and Billing in the AWS Support Center Console, and support will be able to assist you further.
Identify the Service Limits: First, identify which AWS services are causing the issue. The error message you received may provide some indication, but you may also need to check your service limits manually.
1)Check Service Limits: Go to the AWS Service Quotas page in the AWS Management Console. This page lists your current service limits for various AWS services.
2)Request Limit Increase: If you find that the limits for certain services are too low to enable AWS Control Tower, you'll need to request a limit increase. Here's how you can do it:
Click on the service for which you need to increase the limit.
Click the "Request quota increase" button.
Fill out the form with the required details, including the reason for the increase and the new limit you're requesting.
Submit the request.
3)Wait for Approval: After you submit the request, AWS Support will review it. Approval times can vary depending on the service and your region. Once approved, the new limits will be applied to your account.
4)Enable AWS Control Tower: Once you have the necessary service limits in place, you should be able to proceed with enabling AWS Control Tower on your account without encountering the previous error.
If you've already tried increasing limits for services that you suspect might be causing the issue and you're still facing problems, you may need to check if there are other services with low limits that are required for Control Tower setup.
Which specific limit is it please? There are none for Control Tower and apart from the EC2 instances I started / stopped, and AWS Organizations the account is unused.
Relevant content
- asked 2 years ago
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 years ago
Ticket raise, and support fixed the issue. Thanks!