1 Answer
- Newest
- Most votes
- Most comments
2
It seems like you are encountering a rate limiting error when trying to start central configuration in Security Hub. A few things to check:
- Make sure AWS Config is enabled in all accounts and regions where you want to centrally manage Security Hub. Central configuration relies on AWS Config for cross-account integration.
- Double check that the account you are using to start central configuration has the necessary IAM permissions. It needs permissions to call Security Hub APIs on your behalf.
- Rate limiting errors generally occur when making too many API requests too quickly. Try waiting a few minutes between attempts to start central configuration.
- As your organization grows, you may eventually hit inherent limits on the number of configuration changes allowed per region. For exact limits, check the AWS documentation or contact support.
For long-term management, consider using configuration policies and the Security Hub SDK/CLI instead of the console. For example:
aws securityhub update-organization-configuration \
--configuration-type CENTRAL \
--no-auto-enable
I'm not sure what it was, but it worked when I tried again now.
Relevant content
- asked 2 years ago
- Accepted Answerasked 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hello,
This error can indicate that you reached the AWS API limits for that specific API. You can search in AWS CloudTrail which is this specific(s) API(s) related to Security Hub in order to find which specific API call it is.
Depending on the AWS API error it can be related also to multiple users accessing the service that could contribute to the error.
This is the reference for AWS Security Hub API operations: https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html