API Gateway domain names should use recommended security policies
Flags API Gateway custom domain names that are configured with the legacy TLS_1_0 security policy. TLS_1_0 is deprecated and exposes client traffic to known protocol-level weaknesses; recommended policies enforce TLS 1.2 or higher.
- service
- APIGateway
- severity
- Medium
- scope
- evaluated in every region
How to fix it
Reconfigure each affected API Gateway custom domain to use a recommended security policy of TLS_1_2 or higher.
- Open the API Gateway console and select Custom domain names.
- Choose the affected domain and edit the configuration.
- Set the minimum TLS version (security policy) to TLS_1_2.
- Save the change and verify clients can still negotiate TLS 1.2.
See which of your accounts this check is failing on.
Book a demo