Split (1)

train · 107k rows

id stringlengths 8 78	source stringclasses 743 values	chunk_id int64 1 5.05k	text stringlengths 593 49.7k
support-ug-032	support-ug.pdf	32	accounts. Note Member accounts don't have access to aggregated recommendations. 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Priority page, make sure that you're on the My Organization tab. 3. Under Closed recommendations, select a recommendation that was Dismissed, and then choose Reopen. 4. In the Reopen recommendation dialog box, describe why you're reopening the recommendation. 5. Choose Reopen. The recommendation status changes to In progress and appears under the Active tab. Tip You can choose the recommendation name and choose View note to ﬁnd the reason for reopening. If your account team reopened the recommendation for you, their name appears next to the note. 6. Follow the steps in the recommendation details. Reopen a recommendation API Version 2025-05-13 95 AWS Support User Guide Example : Reopen a recommendation from Trusted Advisor Priority The following example shows a recommendation that you want to reopen. Download recommendation details You can also download the results of a prioritized recommendation from Trusted Advisor Priority. Note Currently, you can download only one recommendation at a time. To download a recommendation 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Priority page, select the recommendation, and then choose Download. 3. Open the ﬁle to view the recommendation details. Download recommendation details API Version 2025-05-13 96 AWS Support User Guide Register delegated administrators You can add member accounts that are part of your organization as delegated administrators. Delegated administrator accounts can review, acknowledge, resolve, dismiss, and reopen recommendations in Trusted Advisor Priority. After you register an account, you must grant the delegated administrator the required AWS Identity and Access Management permissions to access Trusted Advisor Priority. For more information, see Manage access to AWS Trusted Advisor and AWS managed policies for AWS Trusted Advisor. You can register up to ﬁve member accounts. Only the management account can add delegated administrators for the organization. You must be signed in to the organization's management account to register or deregister a delegated administrator. To register a delegated administrator 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home as the management account. 2. In the navigation pane, under Preferences, choose Your organization. 3. Under Delegated administrator, choose Register new account. 4. 5. In the dialog box, enter the member account ID, and then choose Register. (Optional) To deregister an account, select an account and choose Deregister. In the dialog box, choose Deregister again. Deregister delegated administrators When you deregister a member account, that account no longer has the same access to Trusted Advisor Priority as the management account. Accounts that are no longer delegated administrators won't receive email notiﬁcations from Trusted Advisor Priority. To deregister a delegated administrator 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home as the management account. 2. In the navigation pane, under Preferences, choose Your organization. 3. Under Delegated administrator, select an account and then choose Deregister. Register delegated administrators API Version 2025-05-13 97 AWS Support User Guide 4. In the dialog box, choose Deregister. Manage Trusted Advisor Priority notiﬁcations Trusted Advisor Priority delivers notiﬁcations through email. This email notiﬁcation includes a summary of the recommendations that your account team prioritized for you. You can specify the frequency that you receive updates from Trusted Advisor Priority. If you registered member accounts as delegated administrators, they can also set up their accounts to receive Trusted Advisor Priority email notiﬁcations. Trusted Advisor Priority email notiﬁcations don't include check results for individual accounts and are separate from the weekly notiﬁcation for Trusted Advisor Recommendations. For more information, see Set up notiﬁcation preferences. Note Only the management account or delegated administrator can set up Trusted Advisor Priority email notiﬁcations. To manage your Trusted Advisor Priority notiﬁcations 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home as a management or delegated administrator account. 2. In the navigation pane, under Preferences, choose Notiﬁcations. 3. Under Priority, you can select the following options. a. Daily – Receive an email notiﬁcation daily. b. Weekly – Receive an email notiﬁcation once a week. c. Choose the notiﬁcations to receive: • Summary of prioritized recommendations • Resolution dates 4. For Recipients, select other contacts that you want to receive the email notiﬁcations. You can add and remove contacts from the Account Settings page in the AWS Billing and Cost Management console. Manage Trusted Advisor Priority notiﬁcations API Version 2025-05-13 98 AWS Support User Guide 5. For Language, choose the language for the email notiﬁcation. 6. Choose Save your preferences. Note Trusted Advisor Priority sends email notiﬁcations from the noreply@notiﬁcations.trustedadvisor.us-west-2.amazonaws.com address. You might need to verify that your email client doesn't identify these emails as spam. Disable Trusted Advisor Priority Contact your account team and ask that they disable this feature for you. After this
support-ug-033	support-ug.pdf	33	that you want to receive the email notiﬁcations. You can add and remove contacts from the Account Settings page in the AWS Billing and Cost Management console. Manage Trusted Advisor Priority notiﬁcations API Version 2025-05-13 98 AWS Support User Guide 5. For Language, choose the language for the email notiﬁcation. 6. Choose Save your preferences. Note Trusted Advisor Priority sends email notiﬁcations from the noreply@notiﬁcations.trustedadvisor.us-west-2.amazonaws.com address. You might need to verify that your email client doesn't identify these emails as spam. Disable Trusted Advisor Priority Contact your account team and ask that they disable this feature for you. After this feature is disabled, prioritized recommendations no longer appear in your Trusted Advisor console. If you disable Trusted Advisor Priority and then enable it again later, you can still view the recommendations that your account team sent before you disabled Trusted Advisor Priority. Get started with AWS Trusted Advisor Engage (Preview) Note AWS Trusted Advisor Engage is in preview release and is subject to change. You can see preview service terms here https://aws.amazon.com/service-terms/. You can use AWS Trusted Advisor Engage to get the most out of your AWS Support Plans by making it easy for you to see, request and track all your proactive engagements, and communicate with your AWS account team about ongoing engagements. For example, you can request a “Management Business Review” towards your AWS account team by going into the Engage page within the AWS Trusted Advisor console. Then, an AWS expert will be assigned to your request, and follow through the entire engagement. Topics • Prerequisites Disable Trusted Advisor Priority API Version 2025-05-13 99 AWS Support User Guide • View the Engagements Dashboard • View the Catalog of Engagement Types • Request an Engagement • Edit an Engagement • Submit Attachments and Notes • Change the Engagement Status • Diﬀerentiate Between Recommended and Requested Engagements • Search Engagements Prerequisites You must take necessary action to satisfy the following requirements in order to use Trusted Advisor Engage: • You must have an Enterprise On-Ramp Support plan. • Your account must be part of an organization which has enabled all features in AWS Organizations. For more information, see Enabling all features in your organization in the AWS Organizations User Guide. • Your organization must have enabled trusted access to Trusted Advisor. You can enable trusted access by logging in as the management account and going to the Your organization page in the Trusted Advisor console. • You must have AWS Identity and Access Management (IAM) permissions to access Trusted Advisor Engage. For information about how to control access to Trusted Advisor Engage, see Manage access to AWS Trusted Advisor. Note Any account within an AWS Organization can create an engagement request. If an Engagement-owning account moves to a diﬀerent AWS Organization, the Engagement will only be accessible by the account. To limit controls, see Example Service Control Policies for AWS Trusted Advisor. Prerequisites API Version 2025-05-13 100 AWS Support User Guide View the Engagements Dashboard After you have obtained access rights, you can access the Trusted Advisor Engage page within the Trusted Advisor console to view a dashboard where you can manage engagements with your AWS account team. To manage your Engagements: 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Engage page, you can view the: • Request Engagement Button • Active Engagements Table • Closed Engagements Table • All Available Engagements Catalog Example : Engagements Dashboard View the Engagements Dashboard API Version 2025-05-13 101 AWS Support User Guide View the Catalog of Engagement Types You can view the catalog of engagement types to ﬁnd the latest types of engagements that you can request towards your AWS account team. To view the catalog of engagement types: 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Engage page, you can ﬁnd the catalog of Engagement types. Example : Engagement Types Catalog Request an Engagement You can request engagements to your AWS account team according to the engagement types included in your AWS Support Plan. To request an Engagement: 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Engage page, choose Request Engagement. 3. Fill out the: • Title View the Catalog of Engagement Types API Version 2025-05-13 102 AWS Support User Guide • Select Engagement: the type of Engagement you want to request. • Desired Completion Date: the desired completion date of the Engagement. Each Engagement Type has a diﬀerent lead time which is calculated in the minimum desired completion date. • Request Visibility: • My account: this engagement request is visible only to your account. • My account and Admin accounts: this engagement request is visible to your account, and the Management account and all Delegated Admin
support-ug-034	support-ug.pdf	34	page, choose Request Engagement. 3. Fill out the: • Title View the Catalog of Engagement Types API Version 2025-05-13 102 AWS Support User Guide • Select Engagement: the type of Engagement you want to request. • Desired Completion Date: the desired completion date of the Engagement. Each Engagement Type has a diﬀerent lead time which is calculated in the minimum desired completion date. • Request Visibility: • My account: this engagement request is visible only to your account. • My account and Admin accounts: this engagement request is visible to your account, and the Management account and all Delegated Admin accounts of your AWS Organization. • Organization: This engagement request is visible to all accounts in your AWS Organization. • Engagement Requester Email: the email address that AWS will use as the primary point of contact for this Engagement. • Email notiﬁcation settings: choose if the Engagement Requester Email will receive email notiﬁcations about the engagement. • Point of escalation: the email address that AWS will use when an escalation is required for this Engagement. • Correspondence: a note and an optional ﬁle attachment for you to provide details regarding this Engagement. 4. Choose Send Request. Request an Engagement API Version 2025-05-13 103 AWS Support Example : Request Engagement User Guide Edit an Engagement You can edit details on your engagement request. To edit an Engagement: 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Engage page, select an existing engagement. 3. Select Edit. 4. You can edit the: • Title Edit an Engagement API Version 2025-05-13 104 AWS Support User Guide • Desired Completion Date: the desired completion date of the Engagement. Each Engagement Type has a diﬀerent lead time which is calculated in the minimum desired completion date. • Request Visibility: • My account: this engagement request is visible only to your account. • My account and Admin accounts: this engagement request is visible to your account, and the Management account and all Delegated Admin accounts of your AWS Organization. • Organization: This engagement request is visible to all accounts in your AWS Organization. • Engagement Requester Email: the email address that AWS will use as the primary point of contact for this Engagement. • Email notiﬁcation settings: choose if the Engagement Requester Email will receive email notiﬁcations about the engagement. • Point of escalation: the email address that AWS will use when an escalation is required for this Engagement. 5. Choose Save. Edit an Engagement API Version 2025-05-13 105 AWS Support Example : Edit Engagement User Guide Submit Attachments and Notes You can communicate with your AWS account team on individual engagements by sending notes and ﬁle attachments to support your engagement request. You can include a single attachment and note per communication, you can only attach ﬁles to an engagement with the same AWS account which requested the engagement, and you can not delete attachments or notes after a communication has been sent. To attach ﬁles or add notes to an Active Engagement request: 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Engage page, choose the ID of the active engagement to which you would like to attach ﬁles or add notes. 3. Choose Correspondence to expand the form. 4. Enter a note for your assigned TAM and optionally attach a ﬁle. Don't share any sensitive information in correspondences, such as passwords, credit card data, signed URLs, or personally identiﬁable information. Submit Attachments and Notes API Version 2025-05-13 106 AWS Support 5. Choose Save. User Guide Example : Add Note and Attach File to an Engagement Change the Engagement Status You can change that status of engagements to cancel engagements which are pending response, complete engagements which are in progress, and reopen engagements which have been marked as cancelled or closed. To change the status of an Engagement: 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Engage page, choose the ID of the active engagement of which you would like to change the status. Change the Engagement Status API Version 2025-05-13 107 AWS Support User Guide 3. On the Engagement details page, you can change the status to Cancelled or Complete. • You are able to select Cancel when engagement status is Pending Response. • You are able to select Complete when engagement status is In Progress. • You are able to select Reopen for closed engagements. Cancelled engagements move to Pending Response, while Complete engagements move to In Progress. Example : Change Engagement Status Diﬀerentiate Between Recommended and Requested Engagements You can identify the source of engagements to know whether an engagement was requested by you or recommended by your AWS account team. To view diﬀerent sources of Active Engagements: 1. Sign
support-ug-035	support-ug.pdf	35	can change the status to Cancelled or Complete. • You are able to select Cancel when engagement status is Pending Response. • You are able to select Complete when engagement status is In Progress. • You are able to select Reopen for closed engagements. Cancelled engagements move to Pending Response, while Complete engagements move to In Progress. Example : Change Engagement Status Diﬀerentiate Between Recommended and Requested Engagements You can identify the source of engagements to know whether an engagement was requested by you or recommended by your AWS account team. To view diﬀerent sources of Active Engagements: 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Engage page, view the Eﬀective Date column to distinguish between Recommended and Requested Engagements: • Recommended: Engagement request created by your AWS account teams. • Requested: Engagement request created by the user. Diﬀerentiate Between Recommended and Requested Engagements API Version 2025-05-13 108 AWS Support Search Engagements User Guide You can search your existing active and closed engagements using ﬁlters. To search Engagements: 1. Sign in to the Trusted Advisor console at https://console.aws.amazon.com/trustedadvisor/ home. 2. On the Trusted Advisor Engage page, you can select from the following ﬁlters: • Age (days) • Engagement Type • Request Title • Status • Desired Completion Date • Eﬀective Date Example : Search Engagements AWS Trusted Advisor check reference You can view all Trusted Advisor check names, descriptions, and IDs in the following reference. You can also sign in to the Trusted Advisor console to view more information about the checks, recommended actions, and their statuses. Search Engagements API Version 2025-05-13 109 AWS Support User Guide If you have a Business, Enterprise On-Ramp, or Enterprise Support plan, you can also use the AWS Trusted Advisor API and the AWS Command Line Interface (AWS CLI) to access your checks. For more information, see the following topics: • Get started with the Trusted Advisor API • AWS Trusted Advisor API Reference Note If you have a Basic Support and Developer Support plan, you can use the Trusted Advisor console to access all checks in the Service limits category and the following checks in the security category: • Amazon EBS Public Snapshots • Amazon RDS Public Snapshots • Amazon S3 Bucket Permissions • MFA on Root Account • Security Groups – Speciﬁc Ports Unrestricted Check categories • Cost optimization • Performance • Security • Fault tolerance • Service limits • Operational Excellence Cost optimization You can use the following checks for the cost optimization category. Check names • AWS Account Not Part of AWS Organizations Cost optimization API Version 2025-05-13 110 AWS Support User Guide • Amazon Comprehend Underutilized Endpoints • Amazon EBS over-provisioned volumes • Amazon EC2 instances consolidation for Microsoft SQL Server • Amazon EC2 instances over-provisioned for Microsoft SQL Server • Amazon EC2 Instances Stopped • Amazon EC2 Reserved Instance Lease Expiration • Amazon EC2 Reserved Instance Optimization • Amazon ECR Repository Without Lifecycle Policy Conﬁgured • Amazon ElastiCache Reserved Node Optimization • Amazon OpenSearch Service Reserved Instance Optimization • Amazon RDS Idle DB Instances • Amazon Redshift Reserved Node Optimization • Amazon Relational Database Service (RDS) Reserved Instance Optimization • Amazon Route 53 Latency Resource Record Sets • Amazon S3 Bucket Lifecycle Policy Conﬁgured • Amazon S3 Incomplete Multipart Upload Abort Conﬁguration • Amazon S3 version-enabled buckets without lifecycle policies conﬁgured • AWS Lambda Functions with Excessive Timeouts • AWS Lambda Functions with High Error Rates • AWS Lambda over-provisioned functions for memory size • AWS Well-Architected high risk issues for cost optimization • Idle Load Balancers • Inactive AWS Network Firewall • Inactive VPC interface endpoints • Inactive Gateway Load Balancer endpoints • Inactive NAT Gateways • Low Utilization Amazon EC2 Instances • Savings Plan • Unassociated Elastic IP Addresses Cost optimization API Version 2025-05-13 111 AWS Support User Guide • Underutilized Amazon EBS Volumes • Underutilized Amazon Redshift Clusters AWS Account Not Part of AWS Organizations Description Checks if an AWS account is part of AWS Organizations under the appropriate management account. AWS Organizations is an account management service for consolidating multiple AWS accounts into a centrally-managed organization. This enables you to centrally structure accounts for billing consolidation and implement ownership and security policies as your workloads scale on AWS. You can specify the management account id using the MasterAccountId parameter of the AWS Conﬁg rules. For more information, see What is AWS Organizations? Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz127 Source AWS Config Managed Rule: account-part-of-organizations Alert
support-ug-036	support-ug.pdf	36	and implement ownership and security policies as your workloads scale on AWS. You can specify the management account id using the MasterAccountId parameter of the AWS Conﬁg rules. For more information, see What is AWS Organizations? Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz127 Source AWS Config Managed Rule: account-part-of-organizations Alert Criteria Yellow: This AWS account is not part of AWS Organizations. Cost optimization API Version 2025-05-13 112 AWS Support Recommended Action User Guide Add this AWS account as part of AWS Organizations. For more information, see Tutorial: Creating and conﬁguring an organization. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon Comprehend Underutilized Endpoints Description Checks the throughput conﬁguration of your endpoints. This check alerts you when endpoints are not actively used for real-time inference requests. An endpoint that isn’t used for more than 15 consecutive days is considered underutilized. All endpoints accrue charges based on both the throughput set, and the length of time that the endpoint is active. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Cm24dfsM12 Alert Criteria Yellow: The endpoint is active, but hasn’t been used for real-time inference requests in the past 15 days. Cost optimization API Version 2025-05-13 113 AWS Support Recommended Action User Guide If the endpoint hasn’t been used in the past 15 days, we recommend that you deﬁne a scaling policy for the resource by using Application Autoscaling. If the endpoint has a scaling policy deﬁned and hasn’t been used in the past 30 days, consider deleting the endpoint and using asynchronous inference. For more information, see Deleting an endpoint with Amazon Comprehend. Report columns • Status • Region • Endpoint ARN • Provisioned Inference Unit • AutoScaling Status • Reason • Last Updated Time Amazon EBS over-provisioned volumes Description Checks the Amazon Elastic Block Store (Amazon EBS) volumes that were running at any time during the lookback period. This check alerts you if any EBS volumes were over-provisioned for your workloads. When you have over-provisioned volumes, you’re paying for unused resources. Although some scenarios can result in low optimization by design, you can often lower your costs by changing the conﬁguration of your EBS volumes. Estimated monthly savings are calculated by using the current usage rate for EBS volumes. Actual savings will vary if the volume isn’t present for a full month. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Cost optimization API Version 2025-05-13 114 AWS Support Check ID COr6dfpM03 Alert Criteria User Guide Yellow: An EBS Volume that was over-provisioned during the lookback period. To determine if a volume is over-provisioned, we consider all default CloudWatch metrics (including IOPS and throughput). The algorithm used to identify over-provisioned EBS volumes follows AWS best practices. The algorithm is updated when a new pattern has been identiﬁed. Recommended Action Consider downsizing volumes that have low utilization. For more information, see Opt in AWS Compute Optimizer for Trusted Advisor checks. Report columns • Status • Region • Volume ID • Volume Type • Volume Size (GB) • Volume Baseline IOPS • Volume Burst IOPS • Volume Burst Throughput • Recommended Volume Type • Recommended Volume Size (GB) • Recommended Volume Baseline IOPS • Recommended Volume Burst IOPS • Recommended Volume Baseline Throughput • Recommended Volume Burst Throughput • Lookback Period (days) • Savings Opportunity (%) • Estimated Monthly Savings • Estimated Monthly Savings Currency Cost optimization API Version 2025-05-13 115 AWS Support • Last Updated Time User Guide Amazon EC2 instances consolidation for Microsoft SQL Server Description Checks your Amazon Elastic Compute Cloud (Amazon EC2) instances that are running SQL Server in the past 24 hours. This check alerts you if your instance has less than the minimum number of SQL Server licenses. From the Microsoft SQL Server Licensing Guide, you are paying 4 vCPU licenses even if an instance has only 1 or 2 vCPUs. You can consolidate smaller SQL Server instances to help lower costs.
support-ug-037	support-ug.pdf	37	Monthly Savings • Estimated Monthly Savings Currency Cost optimization API Version 2025-05-13 115 AWS Support • Last Updated Time User Guide Amazon EC2 instances consolidation for Microsoft SQL Server Description Checks your Amazon Elastic Compute Cloud (Amazon EC2) instances that are running SQL Server in the past 24 hours. This check alerts you if your instance has less than the minimum number of SQL Server licenses. From the Microsoft SQL Server Licensing Guide, you are paying 4 vCPU licenses even if an instance has only 1 or 2 vCPUs. You can consolidate smaller SQL Server instances to help lower costs. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Qsdfp3A4L2 Alert Criteria Yellow: An instance with SQL Server has less than 4 vCPUs. Recommended Action Consider consolidating smaller SQL Server workloads into instances with at least 4 vCPUs. Additional Resources • Microsoft SQL Server on AWS • Microsoft Licensing on AWS • Microsoft SQL Server Licensing Guide Report columns • Status • Region Cost optimization API Version 2025-05-13 116 AWS Support User Guide • Instance ID • Instance Type • vCPU • Minimum vCPU • SQL Server Edition • Last Updated Time Amazon EC2 instances over-provisioned for Microsoft SQL Server Description Checks your Amazon Elastic Compute Cloud (Amazon EC2) instances that are running SQL Server in the past 24 hours. An SQL Server database has a compute capacity limit for each instance. An instance with SQL Server Standard edition can use up to 48 vCPUs. An instance with SQL Server Web can use up to 32 vCPUs. This check alerts you if an instance exceeds this vCPU limit. If your instance is over-provisioned, you pay full price without realizing an improvement in performance. You can manage the number and size of your instances to help lower costs. Estimated monthly savings are calculated by using the same instance family with the maximum number of vCPUs that an SQL Server instance can use and the On-Demand pricing. Actual savings will vary if you’re using Reserved Instances (RI) or if the instance isn’t running for a full day. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Qsdfp3A4L1 Cost optimization API Version 2025-05-13 117 AWS Support Alert Criteria User Guide • Red: An instance with SQL Server Standard edition has more than 48 vCPUs. • Red: An instance with SQL Server Web edition has more than 32 vCPUs. Recommended Action For SQL Server Standard edition, consider changing to an instance in the same instance family with 48 vCPUs. For SQL Server Web edition, consider changing to an instance in the same instance family with 32 vCPUs. If it is memory intensive, consider changing to memory optimized R5 instances. For more information, see Best Practices for Deploying Microsoft SQL Server on Amazon EC2. Additional Resources • Microsoft SQL Server on AWS • You can use Launch Wizard to simplify your SQL Server deployment on EC2. Report columns • Status • Region • Instance ID • Instance Type • vCPU • SQL Server Edition • Maximum vCPU • Recommended Instance Type • Estimated Monthly Savings • Last Updated Time Amazon EC2 Instances Stopped Description Checks if there are Amazon EC2 instances that have been stopped for more than 30 days. You can specify the allowed number of days value in the AllowedDays of AWS Conﬁg parameters. Cost optimization API Version 2025-05-13 118 AWS Support User Guide For more information, see Why am I being charged for Amazon EC2 when all my instances were terminated? Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz150 Source AWS Config Managed Rule: ec2-stopped-instance Alert Criteria • Yellow: There are Amazon EC2 instances stopped for more than the allowed number of days. Recommended Action Review the Amazon EC2 instances that have been stopped for 30 days or more. To avoid incuring unnecessary costs, terminate any instances that are no longer needed. For more information, see Terminate your instance. Additional Resources • Amazon EC2 On-Demand Pricing Report columns •
support-ug-038	support-ug.pdf	38	For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz150 Source AWS Config Managed Rule: ec2-stopped-instance Alert Criteria • Yellow: There are Amazon EC2 instances stopped for more than the allowed number of days. Recommended Action Review the Amazon EC2 instances that have been stopped for 30 days or more. To avoid incuring unnecessary costs, terminate any instances that are no longer needed. For more information, see Terminate your instance. Additional Resources • Amazon EC2 On-Demand Pricing Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters Cost optimization API Version 2025-05-13 119 AWS Support • Last Updated Time User Guide Amazon EC2 Reserved Instance Lease Expiration Description Checks for Amazon EC2 Reserved Instances that are scheduled to expire within the next 30 days, or have expired in the preceding 30 days. Reserved Instances don't renew automatically. You can continue using an Amazon EC2 instance covered by the reservation without interruption, but you will be charged On-Demand rates. New Reserved Instances can have the same parameters as the expired ones, or you can purchase Reserved Instances with diﬀerent parameters. The estimated monthly savings is the diﬀerence between the On-Demand and Reserved Instance rates for the same instance type. Check ID 1e93e4c0b5 Alert Criteria • Yellow: The Reserved Instance lease expires in less than 30 days. • Yellow: The Reserved Instance lease expired in the preceding 30 days. Recommended Action Consider purchasing a new Reserved Instance to replace the one that is nearing the end of its term. For more information, see How to Purchase Reserved Instances and Buying Reserved Instances. Additional Resources • Reserved Instances • Instance Types Report columns • Status • Zone • Instance Type Cost optimization API Version 2025-05-13 120 User Guide AWS Support • Platform • Instance Count • Current Monthly Cost • Estimated Monthly Savings • Expiration Date • Reserved Instance ID • Reason Amazon EC2 Reserved Instance Optimization Description An important part of using AWS involves balancing your Reserved Instance (RI) purchase against your On-Demand Instance usage. This check provides recommendations on which RIs will help reduce the costs incurred from using On-Demand Instances. We create these recommendations by analyzing your On-Demand usage for the past 30 days. We then categorizing the usage into eligible categories for reservations. We simulate every combination of reservations in the generated category of usage to identify the recommended number of each type of RI to purchase. This process of simulation and optimization allows us to maximize your cost savings. This check covers recommendations based on Standard Reserved Instances with the partial upfront payment option. This check is not available to accounts linked in consolidated billing. The recommendations for this check are only available for the paying account. Check ID cX3c2R1chu Alert Criteria Yellow: Optimizing the use of partial upfront RIs can help reduce costs. Recommended Action See the Cost Explorer page for more detailed and customized recommendations. Additionally, refer to the buying guide to understand how to purchase RIs and the options available. Cost optimization API Version 2025-05-13 121 AWS Support Additional Resources User Guide • Information on RIs and how they can save you money can be found here. • For more information on this recommendation, see Reserved Instance Optimization Check Questions in the Trusted Advisor FAQs. Report columns • Region • Instance Type • Platform • Recommended Number of RIs to Purchase • Expected Average RI Utilization • Estimated Savings with Recommendations (Monthly) • Upfront Cost of RIs • Estimated costs of RIs (Monthly) • Estimated On-Demand Cost Post Recommended RI Purchase (Monthly) • Estimated Break Even (Months) • Lookback Period (Days) • Term (Years) Amazon ECR Repository Without Lifecycle Policy Conﬁgured Description Checks if a private Amazon ECR repository has at least one lifecycle policy conﬁgured. Lifecycle policies allow you to deﬁne a set of rules to automatically clean up old or unused container images. This gives you control over the lifecycle management of the images, allows Amazon ECR repositories to be better organized, and helps to lower overall storage costs. For more information, see Lifecycle policies. Check ID c18d2gz128 Source AWS Config Managed Rule: ecr-private-lifecycle-policy-configured Cost optimization API Version 2025-05-13 122 AWS Support Alert Criteria User Guide Yellow: An Amazon ECR private repository doesn’t have any lifecycle policies conﬁgured. Recommended Action Consider creating at least one lifecycle policy for your private Amazon ECR repository. For more information, see Creating a lifecycle policy. Additional Resources • Lifecycle policies. • Creating a lifecycle policy. • Examples of lifecycle policies. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon ElastiCache Reserved Node Optimization Description Checks your usage of ElastiCache and provides
support-ug-039	support-ug.pdf	39	Source AWS Config Managed Rule: ecr-private-lifecycle-policy-configured Cost optimization API Version 2025-05-13 122 AWS Support Alert Criteria User Guide Yellow: An Amazon ECR private repository doesn’t have any lifecycle policies conﬁgured. Recommended Action Consider creating at least one lifecycle policy for your private Amazon ECR repository. For more information, see Creating a lifecycle policy. Additional Resources • Lifecycle policies. • Creating a lifecycle policy. • Examples of lifecycle policies. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon ElastiCache Reserved Node Optimization Description Checks your usage of ElastiCache and provides recommendations on purchase of Reserved Nodes. These recommendations are oﬀered to reduce the costs incurred from using ElastiCache On-Demand. We create these recommendations by analyzing your On-Demand usage for the past 30 days. We use this analysis to simulate every combination of reservations in the generated usage category. This allows us to recommend the number of each type of Reserved Node to purchase to maximize your savings. This check covers recommendations based on the partial upfront payment option with a 1-year or 3-year commitment. This check is not available to accounts linked in consolidated billing. The recommendations for this check are only available for the paying account. Cost optimization API Version 2025-05-13 123 AWS Support Check ID h3L1otH3re Alert Criteria User Guide Yellow: Optimizing the purchase of ElastiCache Reserved Nodes can help reduce costs. Recommended Action See the Cost Explorer page for more detailed recommendations, customization options (for exampe, look-back period, payment option, and so on.) and to purchase ElastiCache Reserved Nodes. Additional Resources • Information on ElastiCache Reserved Nodes and how they can save you money can be found here. • For more information on this recommendation, see Reserved Instance Optimization Check Questions in the Trusted Advisor FAQs. • For more detailed description of ﬁelds, see Cost Explorer documentation Report columns • Region • Family • Node Type • Product Description • Recommended number of Reserved Nodes to purchase • Expected Average Reserved Node Utilization • Estimated Savings with Recommendations (monthly) • Upfront Cost of Reserved Nodes • Estimated cost of Reserved Nodes (monthly) • Estimated On-Demand Cost Post Recommended Reserved Nodes Purchase (monthly) • Estimated Break Even (months) • Lookback Period (days) • Term (years) Cost optimization API Version 2025-05-13 124 AWS Support User Guide Amazon OpenSearch Service Reserved Instance Optimization Description Checks your usage of Amazon OpenSearch Service and provides recommendations on purchase of Reserved Instances. These recommendations are oﬀered to reduce the costs incurred from using OpenSearch On-Demand. We create these recommendations by analyzing your On- Demand usage for the past 30 days. We use this analysis to simulate every combination of reservations in the generated usage category. This allows us to recommend the number of each type of Reserved Instance to purchase to maximize your savings. This check covers recommendations based on partial upfront payment option with a 1-year or 3-year commitment. This check is not available to accounts linked in consolidated billing. The recommendations for this check are only available for the paying account. Check ID 7ujm6yhn5t Alert Criteria Yellow: Optimizing the purchase of Amazon OpenSearch Service Reserved Instances can help reduce costs. Recommended Action See the Cost Explorer page for more detailed recommendations, customization options (e.g. look-back period, payment option, etc.) and to purchase Amazon OpenSearch Service Reserved Instances. Additional Resources • Information on Amazon OpenSearch Service Reserved Instances and how they can save you money can be found here. • For more information on this recommendation, see Reserved Instance Optimization Check Questions in the Trusted Advisor FAQs. • For more detailed description of ﬁelds, see Cost Explorer documentation Report columns • Region Cost optimization API Version 2025-05-13 125 AWS Support • Instance Class • Instance Size • Recommended number of Reserved Instances to purchase • Expected Average Reserved Instance Utilization • Estimated Savings with Recommendation (monthly) • Upfront Cost of Reserved Instances • Estimated cost of Reserved Instances (monthly) User Guide • Estimated On-Demand Cost Post Recommended Reserved Instance Purchase (monthly) • Estimated Break Even (months) • Lookback Period (days) • Term (years) Amazon RDS Idle DB Instances Description Checks the conﬁguration of your Amazon Relational Database Service (Amazon RDS) for any database (DB) instances that appear to be idle. If a DB instance has not had a connection for a prolonged period of time, you can delete the instance to reduce costs. A DB instance is considered idle if the instance hasn't had a connection in the past 7 days. If persistent storage is needed for data on the instance, you can use lower- cost options such as taking and retaining a DB snapshot. Manually created DB snapshots are retained until you delete them. Check ID Ti39halfu8 Alert Criteria Yellow: An active DB instance has not had a connection in the
support-ug-040	support-ug.pdf	40	database (DB) instances that appear to be idle. If a DB instance has not had a connection for a prolonged period of time, you can delete the instance to reduce costs. A DB instance is considered idle if the instance hasn't had a connection in the past 7 days. If persistent storage is needed for data on the instance, you can use lower- cost options such as taking and retaining a DB snapshot. Manually created DB snapshots are retained until you delete them. Check ID Ti39halfu8 Alert Criteria Yellow: An active DB instance has not had a connection in the last 7 days. Recommended Action Consider taking a snapshot of the idle DB instance and then either stopping it or deleting it. Stopping the DB instance removes some of the costs for it, but does not remove storage costs. A stopped instance keeps all automated backups based upon the conﬁgured retention period. Cost optimization API Version 2025-05-13 126 AWS Support User Guide Stopping a DB instance usually incurs additional costs when compared to deleting the instance and then retaining only the ﬁnal snapshot. See Stopping an Amazon RDS instance temporarily and Deleting a DB Instance with a Final Snapshot. Additional Resources Back Up and Restore Report columns • Region • DB Instance Name • Multi-AZ • Instance Type • Storage Provisioned (GB) • Days Since Last Connection • Estimated Monthly Savings (On Demand) Amazon Redshift Reserved Node Optimization Description Checks your usage of Amazon Redshift and provides recommendations on purchase of Reserved Nodes to help reduce costs incurred from using Amazon Redshift On-Demand. We generate these recommendations by analyzing your On-Demand usage for the past 30 days. We use this analysis to simulate every combination of reservations in the generated usage category. This allows us to identify the best number of each type of Reserved Nodes to purchase to maximize your savings. This check covers recommendations based on partial upfront payment option with a 1-year or 3-year commitment. This check is not available to accounts linked in consolidated billing. The recommendations for this check are only available for the paying account. Check ID 1qw23er45t Alert Criteria Yellow: Optimizing the purchase of Amazon Redshift Reserved Nodes can help reduce costs. Cost optimization API Version 2025-05-13 127 AWS Support Recommended Action User Guide See the Cost Explorer page for more detailed recommendations, customization options (e.g. look-back period, payment option, etc.) and to purchase Amazon Redshift Reserved Nodes. Additional Resources • Information on Amazon Redshift Reserved Nodes and how they can save you money can be found here. • For more information on this recommendation, see Reserved Instance Optimization Check Questions in the Trusted Advisor FAQs. • For more detailed description of ﬁelds, see Cost Explorer documentation Report columns • Region • Family • Node Type • Recommended number of Reserved Nodes to purchase • Expected Average Reserved Node Utilization • Estimated Savings with Recommendation (monthly) • UpFront Cost of Reserved Nodes • Estimated cost of Reserved Nodes (monthly) • Estimated On-Demand Cost Post Recommended Reserved Nodes Purchase (monthly) • Estimated Break Even (months) • Lookback Period (days) • Term (years) Amazon Relational Database Service (RDS) Reserved Instance Optimization Description Checks your usage of RDS and provides recommendations on purchase of Reserved Instances to help reduce costs incurred from using RDS On-Demand. We generate these recommendations by analyzing your On-Demand usage for the past 30 days. We use this analysis to simulate every combination of reservations in the generated usage category. This allows us to identify the best number of each type of Reserved Instance Cost optimization API Version 2025-05-13 128 AWS Support User Guide to purchase to maximize your savings. This check covers recommendations based on partial upfront payment option with 1-year or 3-year commitment. This check is not available to accounts linked in consolidated billing. The recommendations for this check are only available for the paying account. Check ID 1qazXsw23e Alert Criteria Yellow: Optimizing the purchase of Amazon RDS Reserved Instances can help reduce costs. Recommended Action See the Cost Explorer page for more detailed recommendations, customization options (e.g. look-back period, payment option, etc.) and to purchase Amazon RDS Reserved Instances. Additional Resources • Information on Amazon RDS Reserved Instances and how they can save you money can be found here. • For more information on this recommendation, see Reserved Instance Optimization Check Questions in the Trusted Advisor FAQs. • For more detailed description of ﬁelds, see Cost Explorer documentation Report columns • Region • Family • Instance Type • Licence Model • Database Edition • Database Engine • Deployment Option • Recommended number of Reserved Instances to purchase • Expected Average Reserved Instance Utilization • Estimated Savings with Recommendation (monthly) • Upfront Cost of Reserved Instances Cost optimization API Version 2025-05-13 129 AWS Support User Guide • Estimated cost of
support-ug-041	support-ug.pdf	41	how they can save you money can be found here. • For more information on this recommendation, see Reserved Instance Optimization Check Questions in the Trusted Advisor FAQs. • For more detailed description of ﬁelds, see Cost Explorer documentation Report columns • Region • Family • Instance Type • Licence Model • Database Edition • Database Engine • Deployment Option • Recommended number of Reserved Instances to purchase • Expected Average Reserved Instance Utilization • Estimated Savings with Recommendation (monthly) • Upfront Cost of Reserved Instances Cost optimization API Version 2025-05-13 129 AWS Support User Guide • Estimated cost of Reserved Instances (monthly) • Estimated On-Demand Cost Post Recommended Reserve Instance Purchase (monthly) • Estimated Break Even (months) • Lookback Period (days) • Term (years) Amazon Route 53 Latency Resource Record Sets Description Checks for Amazon Route 53 latency record sets that are conﬁgured ineﬃciently. To allow Amazon Route 53 to route queries to the AWS Region with the lowest network latency, you should create latency resource record sets for a particular domain name (such as example.com) in diﬀerent Regions. If you create only one latency resource record set for a domain name, all queries are routed to one Region, and you pay extra for latency-based routing without getting the beneﬁts. Hosted zones created by AWS services won’t appear in your check results. Check ID 51fC20e7I2 Alert Criteria Yellow: Only one latency resource record set is conﬁgured for a particular domain name. Recommended Action If you have resources in multiple regions, be sure to deﬁne a latency resource record set for each region. See Latency-Based Routing. If you have resources in only one AWS Region, consider creating resources in more than one AWS Region and deﬁne latency resource record sets for each; see Latency-Based Routing. If you don't want to use multiple AWS Regions, you should use a simple resource record set. See Working with Resource Record Sets. Additional Resources • Amazon Route 53 Developer Guide Cost optimization API Version 2025-05-13 130 AWS Support • Amazon Route 53 Pricing Report columns • Hosted Zone Name • Hosted Zone ID • Resource Record Set Name • Resource Record Set Type User Guide Amazon S3 Bucket Lifecycle Policy Conﬁgured Description Checks if an Amazon S3 bucket has a lifecycle policy conﬁgured. An Amazon S3 lifecycle policy ensures that Amazon S3 objects inside the bucket are stored cost-eﬀectively throughout their lifecycle. This is important for meeting regulatory requirements for data retention and storage. The policy conﬁguration is a set of rules that deﬁne actions applied by the Amazon S3 service to a group of objects. A lifecycle policy allows you to automate transitioning objects to lower- cost storage classes or deleting them as they age. For example, you can transition an object to Amazon S3 Standard-IA storage 30 days after creation, or to Amazon S3 Glacier after 1 year. You can also deﬁne object expiration so that Amazon S3 deletes the object on your behalf after a certain period of time. You can adjust the check conﬁguration using the parameters in your AWS Conﬁg rules For more information, see Managing your storage lifecycle. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz100 Cost optimization API Version 2025-05-13 131 AWS Support Source User Guide AWS Config Managed Rule: s3-lifecycle-policy-check Alert Criteria Yellow: Amazon S3 bucket has no lifecycle policy conﬁgured. Recommended Action Make sure that you have a lifecycle policy conﬁgured in your Amazon S3 bucket. If your organization does not have a retention policy in place, consider using Amazon S3 Intelligent-Tiering to optimize cost. For information on how to deﬁne your Amazon S3 lifecycle policy, see Setting lifecycle conﬁguration on a bucket. For information on Amazon S3 Intelligent-Tiering, see Amazon S3 Intelligent-Tiering storage class Additional Resources Setting lifecycle conﬁguration on a bucket Examples of S3 Lifecycle conﬁguration Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameteres Amazon S3 Incomplete Multipart Upload Abort Conﬁguration Description Checks that each Amazon S3 bucket is conﬁgured with a lifecycle rule to abort multipart uploads that remain incomplete after 7 days. Using a lifecycle rule to abort these incomplete uploads and delete the associated storage is recommended. Cost optimization API Version 2025-05-13 132 AWS Support Note User Guide Results for this check are automatically refreshed one or more times each day, and refresh requests are not allowed. It might take a few hours for changes to appear. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support
support-ug-042	support-ug.pdf	42	Multipart Upload Abort Conﬁguration Description Checks that each Amazon S3 bucket is conﬁgured with a lifecycle rule to abort multipart uploads that remain incomplete after 7 days. Using a lifecycle rule to abort these incomplete uploads and delete the associated storage is recommended. Cost optimization API Version 2025-05-13 132 AWS Support Note User Guide Results for this check are automatically refreshed one or more times each day, and refresh requests are not allowed. It might take a few hours for changes to appear. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1cj39rr6v Alert Criteria Yellow: The lifecycle conﬁguration bucket does not contain a lifecycle rule to abort all multipart uploads that remain incomplete after 7 days. Recommended Action Review lifecycle conﬁguration for buckets without a lifecycle rule that would cleanup all incomplete multipart uploads. Uploads that are not completed after 24 hours are unlikely to be completed. Click here to follow instructions to create a lifecycle rule. It is recommended that this is applied to all objects in your bucket. If you have a need to apply other lifecycle actions to selected objects in your bucket, you can have multiple rules with diﬀerent ﬁlters. Check the storage lens dashboard or call the ListMultipartUpload API for more information. Additional Resources Creating a lifecycle conﬁguration Discovering and Deleting Incomplete Multipart Uploads to Lower Amazon S3 Costs Uploading and copying objects using multipart upload Lifecycle conﬁguration elements Elements to describe lifecycle actions Lifecycle conﬁguration to abort multipart uploads Cost optimization API Version 2025-05-13 133 User Guide AWS Support Report columns • Status • Region • Bucket Name • Bucket ARN • Lifecycle rule for deleting incomplete MPU • Days After Initiation • Last Updated Time Amazon S3 version-enabled buckets without lifecycle policies conﬁgured Description Checks if Amazon S3 version-enabled buckets have a lifecycle policy conﬁgured.. For more information, see Managing your storage lifecycle. You can specify the bucket names that you want to check using the bucketNames parameters in your AWS Conﬁg rules. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz171 Source AWS Config Managed Rule: s3-version-lifecycle-policy-check Alert Criteria Yellow: An Amazon S3 version-enabled bucket with doesn't have a lifecycle policy conﬁgured. Cost optimization API Version 2025-05-13 134 AWS Support Recommended Action User Guide Conﬁgure lifecycle policies for your Amazon S3 buckets to manage your objects so that they are stored cost eﬀectively throughout their lifecycle. For more information, see Setting lifecycle conﬁguration on a bucket. Additional Resources Managing your storage lifecycle Setting lifecycle conﬁguration on a bucket Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time AWS Lambda Functions with Excessive Timeouts Description Checks for Lambda functions with high timeout rates that might result in high cost. Lambda charges based on run time and number of requests for your function. Function timeouts result in errors that may cause retries. Retrying functions will incur additionally request and run time charges. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Cost optimization API Version 2025-05-13 135 AWS Support Check ID L4dfs2Q3C3 Alert Criteria User Guide Yellow: Functions where > 10% of invocations end in an error due to a timeout on any given day within the last 7 days. Recommended Action Inspect function logging and X-ray traces to determine the contributor to the high function duration. Implement logging in your code at relevant parts, such as before or after API calls or database connections. By default, AWS SDK clients timeouts may be longer than the conﬁgured function duration. Adjust API and SDK connection clients to retry or fail within the function timeout. If the expected duration is longer than the conﬁgured timeout, you can increase the timeout setting for the function. For more information, see Monitoring and troubleshooting Lambda applications. Additional Resources • Monitoring and troubleshooting Lambda applications • Lambda Function Retry Timeout SDK • Using AWS Lambda with AWS X-Ray • Accessing Amazon CloudWatch logs for AWS Lambda • Error Processor Sample Application for AWS Lambda Report columns • Status • Region • Function ARN • Max Daily
support-ug-043	support-ug.pdf	43	timeouts may be longer than the conﬁgured function duration. Adjust API and SDK connection clients to retry or fail within the function timeout. If the expected duration is longer than the conﬁgured timeout, you can increase the timeout setting for the function. For more information, see Monitoring and troubleshooting Lambda applications. Additional Resources • Monitoring and troubleshooting Lambda applications • Lambda Function Retry Timeout SDK • Using AWS Lambda with AWS X-Ray • Accessing Amazon CloudWatch logs for AWS Lambda • Error Processor Sample Application for AWS Lambda Report columns • Status • Region • Function ARN • Max Daily Timeout Rate • Date of Max Daily Timeout Rate • Average Daily Timeout Rate • Function Timeout Settings (millisecond) • Lost Daily Compute Cost • Average Daily Invokes • Current Day Invokes Cost optimization API Version 2025-05-13 136 AWS Support User Guide • Current Day Timeout Rate • Last Updated Time AWS Lambda Functions with High Error Rates Description Checks for Lambda functions with high error rates that might result in higher costs. Lambda charges are based on the number of requests and aggregate run time for your function. Function errors may cause retries that incur additional charges. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID L4dfs2Q3C2 Alert Criteria Yellow: Functions where > 10% of invocations end in error on any given day within the last 7 days. Recommended Action Consider the following guidelines to reduce errors. Function errors include errors returned by the function's code and errors returned by the function's runtime. To help you troubleshoot Lambda errors, Lambda integrates with services like Amazon CloudWatch and AWS X-Ray. You can use a combination of logs, metrics, alarms, and X-Ray tracing to quickly detect and identify issues in your function code, API, or other resources that support your application. For more information, see Monitoring and troubleshooting Lambda applications. Cost optimization API Version 2025-05-13 137 AWS Support User Guide For more information on handling errors with speciﬁc runtimes, see Error handling and automatic retries in AWS Lambda. For additional troubleshooting, see Troubleshooting issues in Lambda. You can also choose from an ecosystem of monitoring and observability tools provided by AWS Lambda partners. For more information, see AWS Lambda Partners. Additional Resources • Error Handling and Automatic Retries in AWS Lambda • Monitoring and Troubleshooting Lambda applications • Lambda Function Retry Timeout SDK • Troubleshooting issues in Lambda • API Invoke Errors • Error Processor Sample Application for AWS Lambda Report columns • Status • Region • Function ARN • Max Daily Error Rate • Date for Max Error Rate • Average Daily Error Rate • Lost Daily Compute Cost • Current Day Invokes • Current Day Error Rate • *Average Daily Invokes • Last Updated Time AWS Lambda over-provisioned functions for memory size Description Checks the AWS Lambda functions that were invoked at least once during the lookback period. This check alerts you if any of your Lambda functions were over-provisioned for memory size. Cost optimization API Version 2025-05-13 138 AWS Support User Guide When you have Lambda functions that are over-provisioned for memory sizes, you’re paying for unused resources. Although some scenarios can result in low utilization by design, you can often lower your costs by changing the memory conﬁguration of your Lambda functions. Estimated monthly savings are calculated by using the current usage rate for Lambda functions. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID COr6dfpM05 Alert Criteria Yellow: A Lambda function that was over-provisioned for memory size during the lookback period. To determine if a Lambda function is over-provisioned, we consider all default CloudWatch metrics for that function. The algorithm used to identify over-provisioned Lambda functions for memory size follows AWS best practices. The algorithm is updated when a new pattern has been identiﬁed. Recommended Action Consider reducing the memory size of your Lambda functions. For more information, see Opt in AWS Compute Optimizer for Trusted Advisor checks. Report columns • Status • Region • Function Name • Function Version • Memory Size (MB) • Recommended Memory Size (MB) Cost optimization API Version 2025-05-13 139 AWS Support User Guide • Lookback Period (days) • Savings Opportunity (%) • Estimated Monthly Savings • Estimated Monthly Savings Currency • Last Updated Time AWS Well-Architected
support-ug-044	support-ug.pdf	44	identify over-provisioned Lambda functions for memory size follows AWS best practices. The algorithm is updated when a new pattern has been identiﬁed. Recommended Action Consider reducing the memory size of your Lambda functions. For more information, see Opt in AWS Compute Optimizer for Trusted Advisor checks. Report columns • Status • Region • Function Name • Function Version • Memory Size (MB) • Recommended Memory Size (MB) Cost optimization API Version 2025-05-13 139 AWS Support User Guide • Lookback Period (days) • Savings Opportunity (%) • Estimated Monthly Savings • Estimated Monthly Savings Currency • Last Updated Time AWS Well-Architected high risk issues for cost optimization Description Checks for high risk issues (HRIs) for your workloads in the cost optimization pillar. This check is based on your AWS-Well Architected reviews. Your check results depend on whether you completed the workload evaluation with AWS Well-Architected. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Wxdfp4B1L1 Alert Criteria • Red: At least one active high risk issue was identiﬁed in the cost optimization pillar for AWS Well-Architected. • Green: No active high risk issues were detected in the cost optimization pillar for AWS Well- Architected. Recommended Action AWS Well-Architected detected high risk issues during your workload evaluation. These issues present opportunities to reduce risk and save money. Sign in to the AWS Well-Architected tool to review your answers and take action to resolve your active issues. Cost optimization API Version 2025-05-13 140 User Guide AWS Support Report columns • Status • Region • Workload ARN • Workload Name • Reviewer Name • Workload Type • Workload Started Date • Workload Last Modiﬁed Date • Number of identiﬁed HRIs for Cost Optimization • Number of HRIs resolved for Cost Optimization • Number of questions answered for Cost Optimization • Total number of questions in Cost Optimization pillar • Last Updated Time Idle Load Balancers Description Checks your Elastic Load Balancing conﬁguration for load balancers that are idle. Any load balancer that is conﬁgured accrues charges. If a load balancer has no associated back-end instances, or if network traﬃc is severely limited, the load balancer is not being used eﬀectively. This check currently only checks for Classic Load Balancer type within ELB service. It does not include other ELB types (Application Load Balancer, Network Load Balancer). Check ID hjLMh88uM8 Alert Criteria • Yellow: A load balancer has no active back-end instances. • Yellow: A load balancer has no healthy back-end instances. • Yellow: A load balancer has had less than 100 requests per day for the last 7 days. Cost optimization API Version 2025-05-13 141 AWS Support Recommended Action User Guide If your load balancer has no active back-end instances, consider registering instances or deleting your load balancer. See Registering Your Amazon EC2 Instances with Your Load Balancer or Delete Your Load Balancer. If your load balancer has no healthy back-end instances, see Troubleshooting Elastic Load Balancing: Health Check Conﬁguration. If your load balancer has had a low request count, consider deleting your load balancer. See Delete Your Load Balancer. Additional Resources • Managing Load Balancers • Troubleshoot Elastic Load Balancing Report columns • Region • Load Balancer Name • Reason • Estimated Monthly Savings Inactive AWS Network Firewall Description Checks your AWS Network Firewall endpoints and alerts you when the Network Firewall appears to be inactive. A Network Firewall is considered to be inactive if all its endpoints have no data processed the last 30 days. Network Firewall endpoints incur hourly charges. This check alerts you to Network Firewall with no data processed in the last 30 days. It’s a best practice to either remove unused Network Firewalls or update your architecture. Check ID c2vlfg0bfw Alert Criteria • Yellow: The Network Firewall processed 0 bytes in the last 30 days. • Green: The Network Firewall processed more than 0 bytes in the last 30 days. Cost optimization API Version 2025-05-13 142 AWS Support Recommended Action User Guide If the Network Firewall wasn’t used in the last 30 days, then consider deleting the Network Firewall. If a Transit Gateway is used for inter-VPC communication, then consider deploying your Network Firewalls in a centralized network inspection architectures. This can reduce the hourly charges on inactive Network Firewalls. Additional Resources AWS Network Firewall Pricing Inspection Deployment Models with AWS Network Firewall Report columns • Status • Region • Network Firewall Arn • VPC Id • Subnets • TotalBytesProcessed • Last Updated Time Inactive VPC interface endpoints Description Checks your VPC interface endpoints and alerts you when the endpoints appear
support-ug-045	support-ug.pdf	45	Guide If the Network Firewall wasn’t used in the last 30 days, then consider deleting the Network Firewall. If a Transit Gateway is used for inter-VPC communication, then consider deploying your Network Firewalls in a centralized network inspection architectures. This can reduce the hourly charges on inactive Network Firewalls. Additional Resources AWS Network Firewall Pricing Inspection Deployment Models with AWS Network Firewall Report columns • Status • Region • Network Firewall Arn • VPC Id • Subnets • TotalBytesProcessed • Last Updated Time Inactive VPC interface endpoints Description Checks your VPC interface endpoints and alerts you when the endpoints appear to be inactive. A VPC interface endpoint is considered to be inactive if it has no data processed in the last 30 days. VPC interface endpoints have hourly charges and data processing costs. This check alerts you about VPC interface endpoints with 0 data processed in the last 30 days. It’s a best practice to either remove unused VPC interface endpoints or update your architecture. Check ID c2vlfg0jp6 Alert Criteria • Yellow: VPC interface endpoint has processed 0 bytes in the last 30 days. Cost optimization API Version 2025-05-13 143 AWS Support User Guide • Green: VPC interface endpoint has processed more than 0 bytes in the last 30 days Recommended Action If the VPC interface endpoint had not been used in the last 30 days, consider deleting the VPC interface endpoint. If Transit Gateway is used for inter-VPC communication, then consider deploying your VPC interface endpoints in a centralized architecture to reduce the hourly charges on inactive VPC interface endpoints. Additional Resources • AWS PrivateLink Pricing • Centralized access to VPC private endpoints Report columns • Status • Region • VPC Endpoint Id • VPC Id • Subnet Ids • Service Name • TotalBytesProcessed • Last Updated Time Inactive Gateway Load Balancer endpoints Description Checks your Gateway Load Balancer endpoints and warns when they appear to be inactive. A Gateway Load Balancer endpoint is considered to be underutilized if it has no data processed in the last 30 days. Gateway Load Balancer endpoints have hourly charges and data processed charges. This check alerts you to Gateway Load Balancer endpoints with 0 data processed in the last 30 days. We recommend that you either remove unused Gateway Load Balancer endpoints, or update your architecture. Check ID c2vlfg0k35 Cost optimization API Version 2025-05-13 144 AWS Support Alert Criteria User Guide • Yellow: Gateway Load Balancer endpoint processed 0 bytes in the last 30 days • Green: Gateway Load Balancer endpoint processed more than 0 bytes in the last 30 days Recommended Action If the Gateway Load Balancer endpoint has not been used in the last 30 days, consider deleting the VPC endpoint. If Transit Gateway is used for inter-VPC communication, consider deploying your Gateway Load Balancer endpoints in a centralized network inspection architecture to reduce the hourly charges on inactive Gateway Load Balancer endpoints. Additional Resources AWS PrivateLink Pricing Centralized inspection architecture with AWS Gateway Load Balancer and AWS Transit Gateway Report columns • Status • Region • VPC Endpoint Id • VPC Id • Subnet Id • Service Name • TotalBytesProcessed • Last Updated Time Inactive NAT Gateways Description Checks your NAT Gateways for inactive gateways. A NAT Gateway is considered to be inactive if no data (0 bytes) was processed in the last 30 days. NAT Gateways have hourly charges and data processed charges. Check ID c2vlfg022t Cost optimization API Version 2025-05-13 145 AWS Support Alert Criteria User Guide • Yellow: The NAT Gateway processed 0 bytes in the last 30 days • Green: The NAT Gateway processed more than 0 bytes in the last 30 days Recommended Action Consider deleting any NAT Gateways that weren’t used in the last 30 days and that aren’t required for external network access outside the VPC. If a Transit Gateway is used for inter-VPC communication, then consider deploying a centralized NAT Gateway for egress to internet architecture. This can reduce the hourly cost from inactive NAT Gateways. Additional Resources NAT Gateway Pricing Centralized egress to internet Report columns • Status • Region • NAT Gateway Id • Subnet Id • VPC Id • TotalBytesFromDest • TotalBytesFromSrc • TotalBytes • Last Updated Time Low Utilization Amazon EC2 Instances Description Note An enhanced version of this check is available (Check ID: c1z7kmr00n). The new check oﬀers additional customized recommendations. Cost optimization API Version 2025-05-13 146 AWS Support User Guide Checks the Amazon Elastic Compute Cloud (Amazon EC2) instances that were running at any time during the last 14 days. This check alerts you if the daily CPU utilization was 10% or less and network I/O was 5 MB or less for at least 4 days. Running instances generate hourly usage charges. Although some scenarios can result in low utilization by design, you can often
support-ug-046	support-ug.pdf	46	Low Utilization Amazon EC2 Instances Description Note An enhanced version of this check is available (Check ID: c1z7kmr00n). The new check oﬀers additional customized recommendations. Cost optimization API Version 2025-05-13 146 AWS Support User Guide Checks the Amazon Elastic Compute Cloud (Amazon EC2) instances that were running at any time during the last 14 days. This check alerts you if the daily CPU utilization was 10% or less and network I/O was 5 MB or less for at least 4 days. Running instances generate hourly usage charges. Although some scenarios can result in low utilization by design, you can often lower your costs by managing the number and size of your instances. Estimated monthly savings are calculated by using the current usage rate for On-Demand Instances and the estimated number of days the instance might be underutilized. Actual savings will vary if you are using Reserved Instances or Spot Instances, or if the instance is not running for a full day. To get daily utilization data, download the report for this check. Check ID Qch7DwouX1 Alert Criteria Yellow: An instance had 10% or less daily average CPU utilization and 5 MB or less network I/O on at least 4 of the previous 14 days. Recommended Action Consider stopping or terminating instances that have low utilization, or scale the number of instances by using Auto Scaling. For more information, see Stop and Start Your Instance, Terminate Your Instance, and What is Auto Scaling? Additional Resources • Monitoring Amazon EC2 • Instance Metadata and User Data • Amazon CloudWatch User Guide • Auto Scaling Developer Guide Report columns • Region/AZ • Instance ID • Instance Name • Instance Type • Estimated Monthly Savings Cost optimization API Version 2025-05-13 147 AWS Support User Guide • CPU Utilization 14-day Average • Network I/O 14-Day Average • Number of Days Low Utilization Savings Plan Description Checks your usage of Amazon EC2, Fargate, and Lambda over the last 30 days and provides Savings Plan purchase recommendations. These recommendations allow you to commit to a consistent usage amount measured in dollars per hour for a one- or three-year term in exchange for discounted rates. These are sourced from AWS Cost Explorer, which can get more detailed recommendation information. You can also purchase a savings plan through Cost Explorer. These recommendations should be considered an alternative to your RI recommendations. We suggest that you act on one set of recommendations only. Acting on both sets can lead to over- commitment. This check is not available to accounts linked in consolidated billing. The recommendations for this check are only available for the paying account. Check ID vZ2c2W1srf Alert Criteria Yellow: Optimizing the purchase of Savings Plans can help reduce costs. Recommended Action See the Cost Explorer page for more detailed and customized recommendations and to purchase Savings Plans. Additional Resources • Savings Plan User Guide • Savings Plans FAQ Report columns • Savings Plan type Cost optimization API Version 2025-05-13 148 User Guide AWS Support • Payment option • Upfront cost • Hourly commitment to purchase • Estimated average utilization • Estimated monthly savings • Estimated savings percentage • Term (Years) • Lookback Period (Days) Unassociated Elastic IP Addresses Description Checks for Elastic IP addresses (EIPs) that are not associated with a running Amazon Elastic Compute Cloud (Amazon EC2) instance. EIPs are static IP addresses designed for dynamic cloud computing. Unlike traditional static IP addresses, EIPs mask the failure of an instance or Availability Zone by remapping a public IP address to another instance in your account. A nominal charge is imposed for an EIP that is not associated with a running instance. Check ID Z4AUBRNSmz Alert Criteria Yellow: An allocated Elastic IP address (EIP) is not associated with a running Amazon EC2 instance. Recommended Action Associate the EIP with a running active instance, or release the unassociated EIP. For more information, see Associating an Elastic IP Address with a Diﬀerent Running Instance and Releasing an Elastic IP Address. Additional Resources Elastic IP Addresses Cost optimization API Version 2025-05-13 149 AWS Support Report columns • Region • IP Address Underutilized Amazon EBS Volumes Description User Guide Checks Amazon Elastic Block Store (Amazon EBS) volume conﬁgurations and warns when volumes appear to be underutilized. Charges begin when a volume is created. If a volume remains unattached or has very low write activity (excluding boot volumes) for a period of time, the volume is underutilized. We recommend that you remove underutilized volumes to reduce costs. Check ID DAvU99Dc4C Alert Criteria Yellow: A volume is unattached or had less than 1 IOPS per day for the past 7 days. Recommended Action Consider creating a snapshot and deleting the volume to reduce costs. For more information, see Creating an Amazon EBS Snapshot and Deleting an Amazon EBS Volume. Additional Resources • Amazon Elastic
support-ug-047	support-ug.pdf	47	appear to be underutilized. Charges begin when a volume is created. If a volume remains unattached or has very low write activity (excluding boot volumes) for a period of time, the volume is underutilized. We recommend that you remove underutilized volumes to reduce costs. Check ID DAvU99Dc4C Alert Criteria Yellow: A volume is unattached or had less than 1 IOPS per day for the past 7 days. Recommended Action Consider creating a snapshot and deleting the volume to reduce costs. For more information, see Creating an Amazon EBS Snapshot and Deleting an Amazon EBS Volume. Additional Resources • Amazon Elastic Block Store (Amazon EBS) • Monitoring the Status of Your Volumes Report columns • Region • Volume ID • Volume Name • Volume Type • Volume Size • Monthly Storage Cost • Snapshot ID Cost optimization API Version 2025-05-13 150 AWS Support • Snapshot Name • Snapshot Age Note User Guide If you opted in your account for AWS Compute Optimizer, we recommend that you use the Amazon EBS over-provisioned volumes check instead. For more information, see Opt in AWS Compute Optimizer for Trusted Advisor checks. Underutilized Amazon Redshift Clusters Description Checks your Amazon Redshift conﬁguration for clusters that appear to be underutilized. If an Amazon Redshift cluster has not had a connection for a prolonged period of time, or is using a low amount of CPU, you can use lower-cost options such as downsizing the cluster, or shutting down the cluster and taking a ﬁnal snapshot. Final snapshots are retained even after you delete your cluster. Check ID G31sQ1E9U Alert Criteria • Yellow: A running cluster has not had a connection in the last 7 days. • Yellow: A running cluster had less than 5% cluster-wide average CPU utilization for 99% of the last 7 days. Recommended Action Consider shutting down the cluster and taking a ﬁnal snapshot, or downsizing the cluster. See Shutting Down and Deleting Clusters and Resizing a Cluster. Additional Resources Amazon CloudWatch User Guide Report columns • Status Cost optimization API Version 2025-05-13 151 AWS Support • Region • Cluster • Instance Type • Reason • Estimated Monthly Savings Performance User Guide Improve the performance of your service by checking your service quotas (formerly referred to as limits), so that you can take advantage of provisioned throughput, monitor for overutilized instances, and detect any unused resources. You can use the following checks for the performance category. Check names • Amazon Aurora DB cluster under-provisioned for read workload • Amazon DynamoDB Auto Scaling Not Enabled • Amazon EBS Optimization Not Enabled • Amazon EBS Provisioned IOPS (SSD) Volume Attachment Conﬁguration • Amazon EBS under-provisioned volumes • Amazon EC2 Auto Scaling Group is not Associated with a Launch Template • Amazon EC2 to EBS Throughput Optimization • EC2 Virtualization Type is Paravirtual • Amazon ECS Memory Hard Limit • Amazon EFS Throughput Mode Optimization • Amazon RDS autovacuum parameter is turned oﬀ • Amazon RDS DB clusters support only up to 64 TiB volume • Amazon RDS DB instances in the clusters with heterogeneous instance classes • Amazon RDS DB instances in the clusters with heterogeneous instance sizes • Amazon RDS DB memory parameters are diverging from default • Amazon RDS enable_indexonlyscan parameter is turned oﬀ Performance API Version 2025-05-13 152 AWS Support User Guide • Amazon RDS enable_indexscan parameter is turned oﬀ • Amazon RDS general_logging parameter is turned on • Amazon RDS InnoDB_Change_Buﬀering parameter using less than optimum value • Amazon RDS innodb_open_ﬁles parameter is low • Amazon RDS innodb_stats_persistent parameter is turned oﬀ • Amazon RDS instance under-provisioned for system capacity • Amazon RDS magnetic volume is in use • Amazon RDS parameter groups not using huge pages • Amazon RDS query cache parameter is turned on • Amazon RDS resources instance class update is required • Amazon RDS resources major versions update is required • Amazon RDS resources using end of support engine edition under license-included • Amazon Route 53 Alias Resource Record Sets • AWS Lambda under-provisioned functions for memory size • AWS Lambda Functions without Concurrency Limit Conﬁgured • AWS Well-Architected high risk issues for performance • CloudFront Alternate Domain Names • CloudFront Content Delivery Optimization • CloudFront Header Forwarding and Cache Hit Ratio • High CPU Utilization Amazon EC2 Instances Amazon Aurora DB cluster under-provisioned for read workload Description Checks whether Amazon Aurora DB cluster has the resources to support a read workload. Check ID c1qf5bt038 Alert Criteria Yellow: Performance API Version 2025-05-13 153 AWS Support User Guide Increased database reads: The database load was high and the database was reading more rows than writing or updating the rows. Recommended Action We recommend that you tune your queries to decrease the database load or add a reader DB instance to your DB cluster with the same instance class and size
support-ug-048	support-ug.pdf	48	Cache Hit Ratio • High CPU Utilization Amazon EC2 Instances Amazon Aurora DB cluster under-provisioned for read workload Description Checks whether Amazon Aurora DB cluster has the resources to support a read workload. Check ID c1qf5bt038 Alert Criteria Yellow: Performance API Version 2025-05-13 153 AWS Support User Guide Increased database reads: The database load was high and the database was reading more rows than writing or updating the rows. Recommended Action We recommend that you tune your queries to decrease the database load or add a reader DB instance to your DB cluster with the same instance class and size as the writer DB instance in the cluster. The current conﬁguration has at least one DB instance with a continuously high database load caused mostly by read operations. Distribute these operations by adding another DB instance to the cluster and directing the read workload to the DB cluster read-only endpoint. Additional Resources An Aurora DB cluster has one reader endpoint for read-only connections. This endpoint uses load balancing to manage the queries contributing the most to database load in your DB cluster. The reader endpoint directs these statements to the Aurora Read Replicas and reduces the load on the primary instance. The reader endpoint also scales the capacity to handle concurrent SELECT queries with the number of Aurora Read Replicas in the cluster. For more information, see Adding Aurora Replicas to a DB Cluster and Managing performance and scaling for Aurora DB clusters. Report columns • Status • Region • Resource • Increased database read (count) • Last detection period • Last Updated Time Amazon DynamoDB Auto Scaling Not Enabled Description Checks if your Amazon DynamoDB tables and global secondary indexes have auto scaling or on- demand enabled. Amazon DynamoDB auto scaling uses the Application Auto Scaling service to dynamically adjust provisioned throughput capacity on your behalf in response to actual traﬃc patterns. Performance API Version 2025-05-13 154 AWS Support User Guide This enables a table or a global secondary index to increase its provisioned read and write capacity to handle sudden increases in traﬃc, without throttling. When the workload decreases, Application Auto Scaling decreases the throughput so that you don't pay for unused provisioned capacity. You can adjust the check conﬁguration using the parameters in your AWS Conﬁg rules. For more information, see Managing throughput capacity automatically with DynamoDB auto scaling. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz136 Source AWS Conﬁg Managed Rule: dynamodb-autoscaling-enabled Alert Criteria Yellow: Auto scaling is not enabled for your DynamoDB tables and/or global secondary indexes. Recommended Action Unless you already have a mechanism to automatically scale the provisioned throughput of your DynamoDB table and/or the global secondary indexes based on your workload requirement, consider turning on auto scaling for your Amazon DynamoDB tables. For more information, see Using the AWS Management Console with DynamoDB auto scalingp. Additional Resources Managing throughput capacity automatically with DynamoDB auto scaling Performance API Version 2025-05-13 155 AWS Support Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon EBS Optimization Not Enabled Description Checks if Amazon EBS optimization is enabled for your Amazon EC2 instances. An Amazon EBS–optimized instance uses an optimized conﬁguration stack and provides additional, dedicated capacity for Amazon EBS I/O. This optimization provides the best performance for your Amazon EBS volumes by minimizing contention between Amazon EBS I/ O and other traﬃc from your instance.. For more information, see Amazon EBS–optimized instances. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz142 Source AWS Conﬁg Managed Rule: ebs-optimized-instance Performance API Version 2025-05-13 156 AWS Support Alert Criteria User Guide Yellow: Amazon EBS optimization is not enabled on supported Amazon EC2 instances. Recommended Action Turn on Amazon EBS optimization on supported instances. For more information, see Enable EBS optimization at launch. Additional Resources Amazon EBS–optimized instances Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon EBS Provisioned IOPS (SSD) Volume Attachment Conﬁguration Description Checks for Provisioned IOPS (SSD) volumes that are attached to an Amazon EBS optimizable Amazon Elastic Compute Cloud (Amazon EC2) instance that is not EBS-optimized. Provisioned IOPS (SSD) volumes in the Amazon Elastic Block
support-ug-049	support-ug.pdf	49	User Guide Yellow: Amazon EBS optimization is not enabled on supported Amazon EC2 instances. Recommended Action Turn on Amazon EBS optimization on supported instances. For more information, see Enable EBS optimization at launch. Additional Resources Amazon EBS–optimized instances Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon EBS Provisioned IOPS (SSD) Volume Attachment Conﬁguration Description Checks for Provisioned IOPS (SSD) volumes that are attached to an Amazon EBS optimizable Amazon Elastic Compute Cloud (Amazon EC2) instance that is not EBS-optimized. Provisioned IOPS (SSD) volumes in the Amazon Elastic Block Store (Amazon EBS) are designed to deliver the expected performance only when they are attached to an EBS-optimized instance. Check ID PPkZrjsH2q Alert Criteria Yellow: An Amazon EC2 instance that can be EBS-optimized has an attached Provisioned IOPS (SSD) volume but the instance is not EBS-optimized. Performance API Version 2025-05-13 157 AWS Support Recommended Action User Guide Create a new instance that is EBS-optimized, detach the volume, and reattach the volume to your new instance. For more information, see Amazon EBS-Optimized Instances and Attaching an Amazon EBS Volume to an Instance. Additional Resources • Amazon EBS Volume Types • Amazon EBS Volume Performance Report columns • Status • Region/AZ • Volume ID • Volume Name • Volume Attachment • Instance ID • Instance Type • EBS Optimized Amazon EBS under-provisioned volumes Description Checks the Amazon Elastic Block Store (Amazon EBS) volumes that were running at any time during the lookback period. This check alerts you if any EBS volumes were under-provisioned for your workloads. Consistent high utilization can indicate optimized, steady performance, but can also indicate that an application does not have enough resources. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Performance API Version 2025-05-13 158 AWS Support Check ID COr6dfpM04 Alert Criteria User Guide Yellow: An EBS Volume that was under-provisioned during the lookback period. To determine if a volume is under-provisioned, we consider all default CloudWatch metrics (including IOPS and throughput). The algorithm used to identify under-provisioned EBS volumes follows AWS best practices. The algorithm is updated when a new pattern has been identiﬁed. Recommended Action Consider upsizing volumes that have high utilization. For more information, see Opt in AWS Compute Optimizer for Trusted Advisor checks. Report columns • Status • Region • Volume ID • Volume Type • Volume Size (GB) • Volume Baseline IOPS • Volume Burst IOPS • Volume Burst Throughput • Recommended Volume Type • Recommended Volume Size (GB) • Recommended Volume Baseline IOPS • Recommended Volume Burst IOPS • Recommended Volume Baseline Throughput • Recommended Volume Burst Throughput • Lookback Period (days) • Performance Risk • Last Updated Time Performance API Version 2025-05-13 159 AWS Support User Guide Amazon EC2 Auto Scaling Group is not Associated with a Launch Template Description Checks if an Amazon EC2 Auto Scaling group is created from an Amazon EC2 launch template. Use a launch template to create your Amazon EC2 Auto Scaling groups to ensure access to the latest Auto Scaling group features and improvements. For example, versioning and multiple instance types. For more information, see Launch templates. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz102 Source AWS Conﬁg Managed Rule: autoscaling-launch-template Alert Criteria Yellow: The Amazon EC2 Auto Scaling group isn’t associated with a valid launch template. Recommended Action Use an Amazon EC2 launch template to create your Amazon EC2 Auto Scaling groups. For more information, see Create a launch template for an Auto Scaling group. Additional Resources • Launch templates • Create a launch template Performance API Version 2025-05-13 160 AWS Support Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon EC2 to EBS Throughput Optimization Description Checks for Amazon EBS volumes whose performance might be aﬀected by the maximum throughput capability of the Amazon EC2 instance they are attached to. To optimize performance, you should ensure that the maximum throughput of an Amazon EC2 instance is greater than the aggregate maximum throughput of the attached EBS volumes. This check computes the total EBS volume throughput for each ﬁve-minute period in the preceding day (based on Coordinated Universal Time (UTC)) for each EBS-optimized instance and alerts
support-ug-050	support-ug.pdf	50	Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon EC2 to EBS Throughput Optimization Description Checks for Amazon EBS volumes whose performance might be aﬀected by the maximum throughput capability of the Amazon EC2 instance they are attached to. To optimize performance, you should ensure that the maximum throughput of an Amazon EC2 instance is greater than the aggregate maximum throughput of the attached EBS volumes. This check computes the total EBS volume throughput for each ﬁve-minute period in the preceding day (based on Coordinated Universal Time (UTC)) for each EBS-optimized instance and alerts you if usage in more than half of those periods was greater than 95% of the maximum throughput of the EC2 instance. Check ID Bh2xRR2FGH Alert Criteria Yellow: In the preceding day (UTC), the aggregate throughput (megabytes/sec) of the EBS volumes attached to the EC2 instance exceeded 95% of the published throughput between the instance and the EBS volumes more than 50% of time. Recommended Action Compare the maximum throughput of your Amazon EBS volumes (see Amazon EBS Volume Types) with the maximum throughput of the Amazon EC2 instance they are attached to. See Instance Types That Support EBS Optimization. Consider attaching your volumes to an instance that supports higher throughput to Amazon EBS for optimal performance. Performance API Version 2025-05-13 161 User Guide AWS Support Additional Resources • Amazon EBS Volume Types • Amazon EBS-Optimized Instances • Monitoring the Status of Your Volumes • Attaching an Amazon EBS Volume to an Instance • Detaching an Amazon EBS Volume from an Instance • Deleting an Amazon EBS Volume Report columns • Status • Region • Instance ID • Instance Type • Time Near Maximum EC2 Virtualization Type is Paravirtual Description Checks if the virtualization type of an Amazon EC2 instance is paravirtual. It's a best practice that you use Hardware Virtual Machine (HVM) instances instead of paravirtual instances, when possible. This is because of enhancements in HVM virtualization and the availability of PV drivers for HVM AMIs, which have closed the performance gap that historically existed between PV and HVM guests. It's important to note that current generation instance types do not support PV AMIs. Therefore, choosing an HVM instance type provides the best performance and compatibility with modern hardware. For more information, see Linux AMI virtualization types. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Performance API Version 2025-05-13 162 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz148 Source AWS Conﬁg Managed Rule: ec2-paravirtual-instance-check Alert Criteria Yellow: The virtualization type of Amazon EC2 instances is paravirtual. Recommended Action Use HVM virtualization for your Amazon EC2 instances, and use a compatible instance type. For information on choosing the appropriate virtualization type, see Compatibility for changing the instance type. Additional Resources Compatibility for changing the instance type Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Performance API Version 2025-05-13 163 AWS Support User Guide Amazon ECS Memory Hard Limit Description Checks if Amazon ECS task deﬁnitions have a set memory limit for its container deﬁnitions. The total amount of memory reserved for all containers within a task must be lower than the task memory value. For more information, see Container deﬁnitions. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz176 Source AWS Conﬁg Managed Rule: ecs-task-deﬁnition-memory-hard-limit Alert Criteria Yellow: Amazon ECS memory hard limit is not set. Recommended Action Allocate memory for your Amazon ECS tasks to avoid running out of memory. If your container attempts to exceed the speciﬁed memory, then the container is terminated. For more information, see How can I allocate memory to tasks in Amazon ECS?. Additional Resources Cluster reservation Report columns • Status Performance API Version 2025-05-13 164 AWS Support • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon EFS Throughput Mode Optimization Description Checks if the Amazon EFS ﬁle system is currently conﬁgured to use Bursting throughput mode. Amazon EFS Bursting throughput uses “credits” for performance above baseline throughput (50 KiB/s per GiB). After credits are depleted, performance throttles to baseline throughput, which potentially causes slowness, application failures, and timeouts for your users. To learn more about bursting mode, see Throughput mode
support-ug-051	support-ug.pdf	51	in Amazon ECS?. Additional Resources Cluster reservation Report columns • Status Performance API Version 2025-05-13 164 AWS Support • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon EFS Throughput Mode Optimization Description Checks if the Amazon EFS ﬁle system is currently conﬁgured to use Bursting throughput mode. Amazon EFS Bursting throughput uses “credits” for performance above baseline throughput (50 KiB/s per GiB). After credits are depleted, performance throttles to baseline throughput, which potentially causes slowness, application failures, and timeouts for your users. To learn more about bursting mode, see Throughput mode in the Amazon EFS User Guide Check ID c1dfprch02 Alert Criteria • Yellow: File system is using Bursting throughput mode. Recommended Action If your Bursting throughput credits are low or depleted, consider switching to Provisioned or Elastic throughput mode to provide your users and applications with their desired throughput. With Provisioned throughput, you can set your workload’s required throughput, and you pay for the amount of throughput enabled for the ﬁle system. If you're unsure of your throughput requirements, you can use Elastic throughput mode where your throughput scales elastically with your workload and you only pay for what you use, measured by total data transferred. You can update your ﬁle system conﬁguration to switch between the throughput modes at any time. To learn more about throughput pricing, see Amazon EFS Pricing. You can also estimate your costs using the AWS Pricing Calculator. Additional Resources • Bursting throughput • Amazon EFS Pricing Performance API Version 2025-05-13 165 AWS Support • AWS Pricing Calculator Report columns • Status • Region • EFS File System ID • Throughput mode • Last Updated Time User Guide Amazon RDS autovacuum parameter is turned oﬀ Description The autovacuum parameter is turned oﬀ for your DB instances. Turning autovacuum oﬀ increases the table and index bloat and impacts the performance. We recommend that you turn on autovacuum in your DB parameter groups. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Performance API Version 2025-05-13 166 AWS Support Check ID c1qf5bt025 Alert Criteria User Guide Yellow: DB parameter groups have autovacuum turned oﬀ. Recommended Action Turn on the autovacuum parameter in your DB parameter groups. Additional Resources PostgreSQL database requires periodic maintenance which is known as vacuuming. Autovacuum in PostgreSQL automates running VACCUUM and ANALYZE commands. This process gathers the table statistics and deletes the dead rows. When autovacuum is turned oﬀ, the increase of the table, index bloat, stale statistics will impact the database performance. For more information, see Understanding autovacuum in Amazon RDS for PostgreSQL environments. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS DB clusters support only up to 64 TiB volume Description Your DB clusters support volumes up to 64 TiB. The latest engine versions support volumes up to 128 TiB. We recommend that you upgrade the engine version of your DB cluster to latest versions to support volumes up to 128 TiB. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Performance API Version 2025-05-13 167 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt017 Alert Criteria Yellow: DB clusters have support for volumes only up to 64 TiB. Recommended Action Upgrade the engine version of your DB clusters to support volumes up to 128
support-ug-052	support-ug.pdf	52	can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt017 Alert Criteria Yellow: DB clusters have support for volumes only up to 64 TiB. Recommended Action Upgrade the engine version of your DB clusters to support volumes up to 128 TiB. Additional Resources When you scale up your application on a single Amazon Aurora DB cluster, you may not reach the limit if the storage limit is 128 TiB. The increased storage limit helps to avoid deleting the data or splitting the database across multiple instances. For more information, see Amazon Aurora size limits. Report columns • Status • Region • Resource • Engine Name Performance API Version 2025-05-13 168 AWS Support User Guide • Engine Version Current • Recommended Value • Last Updated Time Amazon RDS DB instances in the clusters with heterogeneous instance classes Description We recommend that you use the same DB instance class and size for all the DB instances in your DB cluster. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt009 Alert Criteria Red: DB clusters have the DB instances with heterogeneous instance classes. Performance API Version 2025-05-13 169 AWS Support Recommended Action User Guide Use the same instance class and size for all the DB instances in your DB cluster. Additional Resources When the DB instances in your DB cluster use diﬀerent DB instance classes or sizes, there can be an imbalance in the workload for the DB instances. During a failover, one of the reader DB instance changes to a writer DB instance. If the DB instances use the same DB instance class and size, the workload can be balanced for the DB instances in your DB cluster. For more information, see Aurora Replicas. Report columns • Status • Region • Resource • Recommended Value • Engine Name • Last Updated Time Amazon RDS DB instances in the clusters with heterogeneous instance sizes Description We recommend that you use the same DB instance class and size for all the DB instances in your DB cluster. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Performance API Version 2025-05-13 170 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt008 Alert Criteria Red: DB clusters have the DB instances with heterogeneous instance sizes. Recommended Action Use the same instance class and size for all the DB instances in your DB cluster. Additional Resources When the DB instances in your DB cluster use diﬀerent DB instance classes or sizes, there can be an imbalance in the workload for the DB instances. During a failover, one of the reader DB instance changes to a writer DB instance. If the DB instances use the same DB instance class and size, the workload can be balanced for the DB instances in your DB cluster. For more information, see Aurora Replicas. Report columns • Status • Region • Resource • Recommended Value • Engine Name • Last Updated Time Performance API Version 2025-05-13 171 AWS Support User Guide Amazon RDS DB memory
support-ug-053	support-ug.pdf	53	in your DB cluster use diﬀerent DB instance classes or sizes, there can be an imbalance in the workload for the DB instances. During a failover, one of the reader DB instance changes to a writer DB instance. If the DB instances use the same DB instance class and size, the workload can be balanced for the DB instances in your DB cluster. For more information, see Aurora Replicas. Report columns • Status • Region • Resource • Recommended Value • Engine Name • Last Updated Time Performance API Version 2025-05-13 171 AWS Support User Guide Amazon RDS DB memory parameters are diverging from default Description The memory parameters of the DB instances are signiﬁcantly diﬀerent from the default values. These settings can impact performance and cause errors. We recommend that you reset the custom memory parameters for the DB instance to their default values in the DB parameter group. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt020 Alert Criteria Yellow: DB parameter groups have memory parameters that diverge considerably from the default values. Performance API Version 2025-05-13 172 AWS Support Recommended Action Reset the memory parameters to their default values. Additional Resources User Guide For more information, see Best practices for conﬁguring parameters for Amazon RDS for MySQL, part 1: Parameters related to performance. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS enable_indexonlyscan parameter is turned oﬀ Description The query planner or optimizer can't use the index-only scan plan type when it is turned oﬀ. We recommend that you set the enable_indexonlyscan parameter value to 1. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the Performance API Version 2025-05-13 173 AWS Support User Guide recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt028 Alert Criteria Yellow: DB parameter groups have enable_indexonlyscan parameter turned oﬀ. Recommended Action Set the parameter enable_indexonlyscan to 1. Additional Resources When you turn oﬀ enable_indexonlyscan parameter, it prevents the query planner from selecting an optimal execution plan. The query planner uses a diﬀerent plan type, such as index scan which can increase the query cost and execution time. The index only scan plan type retrieves the data without accessing the table data. For more information, see enable_indexonlyscan (boolean) on the PostgreSQL documentation website. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Performance API Version 2025-05-13 174 AWS Support User Guide Amazon RDS enable_indexscan parameter is turned oﬀ Description The query planner or optimizer can't use the index scan plan type when it is turned oﬀ. We recommend that you set the enable_indexscan parameter value to 1. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then
support-ug-054	support-ug.pdf	54	requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt029 Alert Criteria Yellow: DB parameter groups have enable_indexscan parameter turned oﬀ. Recommended Action Set the parameter enable_indexscan to 1. Performance API Version 2025-05-13 175 AWS Support Additional Resources User Guide When you turn oﬀ enable_indexscan parameter, it prevents the query planner from selecting an optimal execution plan. The query planner uses a diﬀerent plan type, such as index scan which can increase the query cost and execution time. For more information, see enable_indexscan (boolean) on the PostgreSQL documentation website. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS general_logging parameter is turned on Description The general logging is turned on for your DB instance. This setting is useful while troubleshooting the database issues. However, turning on general logging increases the amount of I/O operations and allocated storage space, which might result in contention and performance degradation. Check your requirements for general logging usage. We recommend that you set the general_logging parameter value to 0. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Performance API Version 2025-05-13 176 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt037 Alert Criteria Yellow: DB parameter groups have general_logging turned on. Recommended Action Check your requirements for general logging usage. If it isn't mandatory, we recommend that you to set the general_logging parameter value to 0. Additional Resources The general query log is turned on when the general_logging parameter value is 1. The general query log contains records of the database server operations. The server writes information to this log when clients connect or disconnect and the logs contain each SQL statement received from the clients. The general query log is useful when you suspect an error in a client and you want to ﬁnd the information the client to sent to the database server. For more information, see Overview of RDS for MySQL database logs. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Performance API Version 2025-05-13 177 AWS Support User Guide Amazon RDS InnoDB_Change_Buﬀering parameter using less than optimum value Description Change buﬀering allows a MySQL DB instance to defer a few writes, which are required to maintain secondary indexes. This feature was useful in environments with slow disks. The change buﬀering conﬁguration improved the DB performance slightly but caused a delay in crash recovery and long shutdown times during upgrade. We recommend that you set the value of innodb_change_buﬀering parameter to NONE. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt021 Alert Criteria Yellow: DB parameter groups have innodb_change_buﬀering parameter set
support-ug-055	support-ug.pdf	55	one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt021 Alert Criteria Yellow: DB parameter groups have innodb_change_buﬀering parameter set to a low optimum value. Performance API Version 2025-05-13 178 AWS Support Recommended Action User Guide Set innodb_change_buﬀering parameter value to NONE in your DB parameter groups. Additional Resources For more information, see Best practices for conﬁguring parameters for Amazon RDS for MySQL, part 1: Parameters related to performance. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS innodb_open_ﬁles parameter is low Description The innodb_open_ﬁles parameter controls the number of ﬁles InnoDB can open at one time. InnoDB opens all of the log and system tablespace ﬁles when mysqld is running. Your DB instance has a low value for the maximum number of ﬁles InnoDB can open at one time. We recommend that you set the innodb_open_ﬁles parameter to a minimum value of 65. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Performance API Version 2025-05-13 179 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt033 Alert Criteria Yellow: DB parameter groups have the InnoDB open ﬁles setting misconﬁgured. Recommended Action Set the innodb_open_ﬁles parameter to a minimum value of 65. Additional Resources The innodb_open_ﬁles parameter controls the number of ﬁles InnoDB can open at one time. InnoDB keeps all the log ﬁles and the system tablespace ﬁles open when mysqld is running. InnoDB also needs to open a few .ibd ﬁles, if ﬁle-per-table storage model is used. When the innodb_open_ﬁles setting is low, it impacts the database performance and the server may fail to start. For more information, see InnoDB Startup Options and System Variables - innodb_open_ﬁles on the MySql documentation website. Report columns • Status • Region • Resource • Parameter Name • Recommended Value Performance API Version 2025-05-13 180 AWS Support • Last Updated Time User Guide Amazon RDS innodb_stats_persistent parameter is turned oﬀ Description Your DB instance isn't conﬁgured to persist the InnoDB statistics to the disk. When the statistics aren't stored, they are recalculated each time the instance restarts and the table accessed. This leads to variations in the query execution plan. You can modify the value of this global parameter at the table level. We recommend that you set the innodb_stats_persistent parameter value to ON. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt032 Alert Criteria Yellow: DB parameter groups have optimizer statistics that aren't persisted to the disk. Performance API Version 2025-05-13 181 AWS Support Recommended Action Set the innodb_stats_persistent parameter value to ON. Additional Resources User Guide If the innodb_stats_persistent parameter is set to ON, then the optimizer statistics are persisted when the instance restarts. This improves the execution plan stability and consistent query performance. You can modify global statistics persistence at the table level by using the clause STATS_PERSISTENT when you create
support-ug-056	support-ug.pdf	56	those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt032 Alert Criteria Yellow: DB parameter groups have optimizer statistics that aren't persisted to the disk. Performance API Version 2025-05-13 181 AWS Support Recommended Action Set the innodb_stats_persistent parameter value to ON. Additional Resources User Guide If the innodb_stats_persistent parameter is set to ON, then the optimizer statistics are persisted when the instance restarts. This improves the execution plan stability and consistent query performance. You can modify global statistics persistence at the table level by using the clause STATS_PERSISTENT when you create or alter a table. For more information, see Best practices for conﬁguring parameters for Amazon RDS for MySQL, part 1: Parameters related to performance. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS instance under-provisioned for system capacity Description Checks whether Amazon RDS instance or Amazon Aurora DB instance has the required system capacity to operate. Check ID c1qf5bt039 Alert Criteria Yellow: Out-of-memory kills: When a process on the database host is stopped because of memory reduction at the OS level, the Out Of Memory (OOM) kills counter increases. Excessive swapping: os.memory.swap.in and os.memory.swap.out metric values were high. Performance API Version 2025-05-13 182 AWS Support Recommended Action User Guide We recommend that you tune your queries to use less memory or use a DB instance type with higher allocated memory. When the instance is running low on memory, this impacts the database performance. Additional Resources Out-of-memory kills were detected: Linux kernel invokes the Out of Memory (OOM) Killer when the processes running on the host require more than the memory physically available from the operating system. In this case, the OOM Killer reviews all the running processes, and stops one or more processes, in order to free up system memory and keep the system running. Swapping is detected: When the memory isn't suﬃcient on the database host, the operating system sends a few minimum used pages to the disk in the swap space. This oﬄoading process impacts the database performance. For more information, see Amazon RDS Instance Types and Scaling yourAmazon RDS instance. Report columns • Status • Region • Resource • Out-of-memory kills (count) • Excessive swapping (count) • Last detection period • Last Updated Time Amazon RDS magnetic volume is in use Description Your DB instances are using magnetic storage. Magnetic storage isn't recommended for most of the DB instances. Choose a diﬀerent storage type: General Purpose (SSD) or Provisioned IOPS. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Performance API Version 2025-05-13 183 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt000 Alert Criteria Yellow: Amazon RDS resources are using magnetic storage. Recommended Action Choose a diﬀerent storage type: General Purpose (SSD) or Provisioned IOPS. Additional Resources Magnetic storage is an earlier generation storage type. The General Purpose (SSD) or Provisioned IOPS is the recommended storage type for new storage requirements. These storage types provide higher and consistent performance, and improved storage size options. For more information, see Previous generation volumes. Report columns • Status • Region • Resource • Recommended Value Performance API Version 2025-05-13 184 AWS Support • Engine Name • Last Updated Time User Guide Amazon RDS parameter groups not using huge pages Description Large pages can increase database scalability, but your DB instance isn't using large pages. We recommend that you set the use_large_pages parameter value to ONLY in the DB parameter group for your DB instance. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the
support-ug-057	support-ug.pdf	57	DB parameter group for your DB instance. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt024 Alert Criteria Yellow: DB parameter groups don't use large pages. Performance API Version 2025-05-13 185 AWS Support Recommended Action User Guide Set the use_large_pages parameter value to ONLY in your DB parameter groups. Additional Resources For more information, see Turning on HugePages for an RDS for Oracle instance. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS query cache parameter is turned on Description When changes require that your query cache is purged, your DB instance will appear to stall. Most workloads don't beneﬁt from a query cache. The query cache was removed from MySQL version 8.0. We recommend that you set the query_cache_type parameter to 0. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the Performance API Version 2025-05-13 186 AWS Support User Guide recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt022 Alert Criteria Yellow: DB parameter groups have query cache turned on. Recommended Action Set the query_cache_type parameter value to 0 in your DB parameter groups. Additional Resources For more information, see Best practices for conﬁguring parameters for Amazon RDS for MySQL, part 1: Parameters related to performance. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS resources instance class update is required Description Your database is running a previous generation DB instance class. We have replaced DB instance classes from a previous generation with DB instance classes with better cost, performance, or both. We recommend that you run your DB instance with a DB instance class from a newer generation. Performance API Version 2025-05-13 187 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt015 Alert Criteria Red: DB instances are using end of support DB instance class. Recommended Action Upgrade to latest DB instance class. Additional Resources For more information, see Supported DB engines for DB instance classes. Report columns • Status • Region • Resource • DB Instance Class Performance API Version 2025-05-13 188 AWS Support User Guide • Recommended Value • Engine Name • Last Updated Time Amazon RDS resources major versions update is required Description Databases with the current major version for the DB engine won't be supported. We recommend that you upgrade to the latest major version which includes new functionality and enhancements. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For
support-ug-058	support-ug.pdf	58	DB instance classes. Report columns • Status • Region • Resource • DB Instance Class Performance API Version 2025-05-13 188 AWS Support User Guide • Recommended Value • Engine Name • Last Updated Time Amazon RDS resources major versions update is required Description Databases with the current major version for the DB engine won't be supported. We recommend that you upgrade to the latest major version which includes new functionality and enhancements. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt014 Alert Criteria Red: RDS resources are using end of support major versions. Performance API Version 2025-05-13 189 AWS Support Recommended Action Upgrade to the latest major version for the DB engine. Additional Resources User Guide Amazon RDS releases new versions for the supported database engines to maintain your databases with the latest version. The new released versions may include bug ﬁxes, security enhancements, and other improvements for the database engine. You can minimize the downtime required for the DB instance upgrade by using a blue/green deployment. For more information, see the following resources: • Upgrading a DB instance engine version • Amazon Aurora updates • Using Amazon RDS Blue/Green Deployments for database updates Report columns • Status • Region • Resource • Engine Name • Engine Current Version • Recommended Value • Last Updated Time Amazon RDS resources using end of support engine edition under license- included Description We recommend that you upgrade the major version to the latest engine version supported by Amazon RDS to continue with the current license support. The engine version of your database won't be supported with the current license. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Performance API Version 2025-05-13 190 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt016 Alert Criteria Red: Amazon RDS resources are using end of support engine edition under license-included model. Recommended Action We recommend that you upgrade your database to the latest supported version in Amazon RDS to continue using the licensed model. Additional Resources For more information, see Oracle major version upgrades. Report columns • Status • Region • Resource • Engine Name • Engine Version Current • Recommended Value Performance API Version 2025-05-13 191 AWS Support • Engine Name • Last Updated Time Amazon Route 53 Alias Resource Record Sets Description User Guide Checks for resource record sets that can be changed to alias resource record sets to improve performance and save money. An alias resource record set routes DNS queries to an AWS resource (for example, an Elastic Load Balancing load balancer or an Amazon S3 bucket) or to another Route 53 resource record set. When you use alias resource record sets, Route 53 routes your DNS queries to AWS resources free of charge. Hosted zones created by AWS services won’t appear in your check results. Check ID B913Ef6fb4 Alert Criteria • Yellow: A resource record set is a CNAME to an Amazon S3 website. • Yellow: A resource record set is a CNAME to an Amazon CloudFront distribution. • Yellow: A resource record set is a CNAME to an Elastic Load Balancing load balancer. Recommended Action Replace the listed CNAME resource record sets with alias resource record sets; see Choosing Between Alias and Non-Alias Resource Record Sets. You also need to change the record type from CNAME to A or AAAA, depending on the
support-ug-059	support-ug.pdf	59	zones created by AWS services won’t appear in your check results. Check ID B913Ef6fb4 Alert Criteria • Yellow: A resource record set is a CNAME to an Amazon S3 website. • Yellow: A resource record set is a CNAME to an Amazon CloudFront distribution. • Yellow: A resource record set is a CNAME to an Elastic Load Balancing load balancer. Recommended Action Replace the listed CNAME resource record sets with alias resource record sets; see Choosing Between Alias and Non-Alias Resource Record Sets. You also need to change the record type from CNAME to A or AAAA, depending on the AWS resource. See Values that You Specify When You Create or Edit Amazon Route 53 Resource Record Sets. Additional Resources Routing Queries to AWS Resources Report columns • Status • Hosted Zone Name Performance API Version 2025-05-13 192 AWS Support • Hosted Zone ID • Resource Record Set Name • Resource Record Set Type • Resource Record Set Identiﬁer • Alias Target User Guide AWS Lambda under-provisioned functions for memory size Description Checks the AWS Lambda functions that were invoked at least once during the lookback period. This check alerts you if any of your Lambda functions were under-provisioned for memory size. When you have Lambda functions that are under-provisioned for memory size, these functions take longer time to complete. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID COr6dfpM06 Alert Criteria Yellow: A Lambda function that was under-provisioned for memory size during the lookback period. To determine if a Lambda function is under-provisioned, we consider all default CloudWatch metrics for that function. The algorithm used to identify under-provisioned Lambda functions for memory size follows AWS best practices. The algorithm is updated when a new pattern has been identiﬁed. Recommended Action Consider increasing the memory size of your Lambda functions. Performance API Version 2025-05-13 193 AWS Support User Guide For more information, see Opt in AWS Compute Optimizer for Trusted Advisor checks. Report columns • Status • Region • Function Name • Function Version • Memory Size (MB) • Recommended Memory Size (MB) • Lookback Period (days) • Performance Risk • Last Updated Time AWS Lambda Functions without Concurrency Limit Conﬁgured Description Checks if AWS Lambda functions are conﬁgured with function-level concurrent execution limit. Concurrency is the number of in-ﬂight requests your AWS Lambda function is handling at the same time. For each concurrent request, Lambda provisions a separate instance of your execution environment. You can specify the minimum and maximum reserved concurrency limit using the concurrencyLimitLow and ConcurrencyLimitHigh parameters in your AWS Conﬁg rules. For more information, see Lambda function scaling. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Performance API Version 2025-05-13 194 AWS Support Check ID c18d2gz181 Source User Guide AWS Conﬁg Managed Rule: lambda-concurrency-check Alert Criteria Yellow: Lambda function has no concurrency limit conﬁgured. Recommended Action Make sure that your Lambda functions have concurrency conﬁgured. A concurrency limit for your Lambda functions helps make sure that your function processes requests reliably and predictably. A concurrency limit reduces the risk of your function being overwhelmed due to a sudden surge in traﬃc. For more information, see Conﬁguring reserved concurrency. Additional Resources • Lambda function scaling • Conﬁguring reserved concurrency Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time AWS Well-Architected high risk issues for performance Description Checks for high risk issues (HRIs) for your workloads in the performance pillar. This check is based on your AWS-Well Architected reviews. Your check results depend on whether you completed the workload evaluation with AWS Well-Architected. Performance API Version 2025-05-13 195 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Wxdfp4B1L2 Alert Criteria • Red: At least one active high risk issue was identiﬁed in the performance pillar for AWS Well- Architected. • Green: No active high risk issues were detected in the performance pillar for AWS Well- Architected. Recommended Action AWS Well-Architected detected high risk issues
support-ug-060	support-ug.pdf	60	this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Wxdfp4B1L2 Alert Criteria • Red: At least one active high risk issue was identiﬁed in the performance pillar for AWS Well- Architected. • Green: No active high risk issues were detected in the performance pillar for AWS Well- Architected. Recommended Action AWS Well-Architected detected high risk issues during your workload evaluation. These issues present opportunities to reduce risk and save money. Sign in to the AWS Well-Architected tool to review your answers and take action to resolve your active issues. Report columns • Status • Region • Workload ARN • Workload Name • Reviewer Name • Workload Type • Workload Started Date • Workload Last Modiﬁed Date • Number of identiﬁed HRIs for Performance • Number of HRIs resolved for Performance Performance API Version 2025-05-13 196 AWS Support User Guide • Number of questions answered for Performance • Total number of questions in Performance pillar • Last Updated Time CloudFront Alternate Domain Names Description Checks Amazon CloudFront distributions for alternate domain names (CNAMES) that have incorrectly conﬁgured DNS settings. If a CloudFront distribution includes alternate domain names, the DNS conﬁguration for the domains must route DNS queries to that distribution. Note This check assumes Amazon Route 53 DNS and Amazon CloudFront distribution are conﬁgured in the same AWS account. As such the alert list might include resources otherwise working as expected due to DNS setting outsides of this AWS account. Check ID N420c450f2 Alert Criteria • Yellow: A CloudFront distribution includes alternate domain names, but the DNS conﬁguration is not correctly set up with a CNAME record or an Amazon Route 53 alias resource record. • Yellow: A CloudFront distribution includes alternate domain names, but Trusted Advisor could not evaluate the DNS conﬁguration because there were too many redirects. • Yellow: A CloudFront distribution includes alternate domain names, but Trusted Advisor could not evaluate the DNS conﬁguration for some other reason, most likely because of a timeout. Recommended Action Update the DNS conﬁguration to route DNS queries to the CloudFront distribution; see Using Alternate Domain Names (CNAMEs). Performance API Version 2025-05-13 197 AWS Support User Guide If you're using Amazon Route 53 as your DNS service, see Routing Traﬃc to an Amazon CloudFront Web Distribution by Using Your Domain Name. If the check timed out, try refreshing the check. Additional Resources Amazon CloudFront Developer Guide Report columns • Status • Distribution ID • Distribution Domain Name • Alternate Domain Name • Reason CloudFront Content Delivery Optimization Description Checks for cases where data transfer from Amazon Simple Storage Service (Amazon S3) buckets could be accelerated by using Amazon CloudFront, the AWS global content delivery service. When you conﬁgure CloudFront to deliver your content, requests for your content are automatically routed to the nearest edge location where content is cached. This routing allows content to be delivered to your users with the best possible performance. A high ratio of data transferred out compared to the data stored in the bucket indicates that you could beneﬁt from using Amazon CloudFront to deliver the data. Check ID 796d6f3D83 Alert Criteria • Yellow: The amount of data transferred out of the bucket to your users by GET requests in the 30 days preceding the check is at least 25 times greater than the average amount of data stored in the bucket. • Red: The amount of data transferred out of the bucket to your users by GET requests in the 30 days preceding the check is at least 10 TB and at least 25 times greater than the average amount of data stored in the bucket. Performance API Version 2025-05-13 198 AWS Support Recommended Action User Guide Consider using CloudFront for better performance. See Amazon CloudFront Product Details. If the data transferred is 10 TB per month or more, see Amazon CloudFront Pricing to explore possible cost savings. Additional Resources • Amazon CloudFront Developer Guide • AWS Case Study: PBS Report columns • Status • Region • Bucket Name • S3 Storage (GB) • Data Transfer Out (GB) • Ratio of Transfer to Storage CloudFront Header Forwarding and Cache Hit Ratio Description Checks the HTTP request headers that CloudFront currently receives from the client and forwards to your origin server. Some headers, such as date, or user-agent, signiﬁcantly reduce the cache hit ratio (the proportion of requests that are served from a CloudFront edge cache). This increases the load on your origin and reduces performance, because CloudFront must forward more requests to your origin. Check ID N415c450f2 Alert Criteria Yellow: One or
support-ug-061	support-ug.pdf	61	• Status • Region • Bucket Name • S3 Storage (GB) • Data Transfer Out (GB) • Ratio of Transfer to Storage CloudFront Header Forwarding and Cache Hit Ratio Description Checks the HTTP request headers that CloudFront currently receives from the client and forwards to your origin server. Some headers, such as date, or user-agent, signiﬁcantly reduce the cache hit ratio (the proportion of requests that are served from a CloudFront edge cache). This increases the load on your origin and reduces performance, because CloudFront must forward more requests to your origin. Check ID N415c450f2 Alert Criteria Yellow: One or more request headers that CloudFront forwards to your origin might signiﬁcantly reduce your cache hit ratio. Performance API Version 2025-05-13 199 AWS Support Recommended Action User Guide Consider whether the request headers provide enough beneﬁt to justify the negative eﬀect on the cache hit ratio. If your origin returns the same object regardless of the value of a given header, we recommend that you don't conﬁgure CloudFront to forward that header to the origin. For more information, see Conﬁguring CloudFront to Cache Objects Based on Request Headers. Additional Resources • Increasing the Proportion of Requests that Are Served from CloudFront Edge Caches • CloudFront Cache Statistics Reports • HTTP Request Headers and CloudFront Behavior Report columns • Distribution ID • Distribution Domain Name • Cache Behavior Path Pattern • Headers High CPU Utilization Amazon EC2 Instances Description Checks the Amazon Elastic Compute Cloud (Amazon EC2) instances that were running at any time during the last 14 days. An alert is sent if daily CPU utilization was greater than 90% on four or more days. Consistent high utilization can indicate optimized, steady performance. However, it can also indicate that an application does not have enough resources. To get daily CPU utilization data, download the report for this check. Check ID ZRxQlPsb6c Alert Criteria Yellow: An instance had more than 90% daily average CPU utilization on at least 4 of the previous 14 days. Performance API Version 2025-05-13 200 AWS Support Recommended Action User Guide Consider adding more instances. For information about scaling the number of instances based on demand, see What is Auto Scaling? Additional Resources • Monitoring Amazon EC2 • Instance Metadata and User Data • Amazon CloudWatch User Guide • Amazon EC2 Auto Scaling User Guide Report columns • Region/AZ • Instance ID • Instance Type • Instance Name • 14-Day Average CPU Utilization • Number of Days over 90% CPU Utilization Security You can use the following checks for the security category. Note If you enabled Security Hub for your AWS account, you can view your ﬁndings in the Trusted Advisor console. For information, see Viewing AWS Security Hub controls in AWS Trusted Advisor. You can view all controls in the AWS Foundational Security Best Practices security standard except for controls that have the Category: Recover > Resilience. For a list of supported controls, see AWS Foundational Security Best Practices controls in the AWS Security Hub User Guide. Check names • Application Load Balancer security group • Amazon CloudWatch Log Group Retention Period Security API Version 2025-05-13 201 AWS Support User Guide • Amazon EC2 instances with Microsoft SQL Server end of support • Amazon EC2 instances with Microsoft Windows Server end of support • Amazon EC2 instances with Ubuntu LTS end of standard support • Amazon EFS clients not using data-in-transit encryption • Amazon EBS Public Snapshots • Amazon RDS Aurora storage encryption is turned oﬀ • Amazon RDS engine minor version upgrade is required • Amazon RDS Public Snapshots • Amazon RDS Security Group Access Risk • Amazon RDS storage encryption is turned oﬀ • Amazon Route 53 mismatching CNAME records pointing directly to S3 buckets • Amazon Route 53 MX Resource Record Sets and Sender Policy Framework • Amazon S3 Bucket Permissions • Amazon VPC Peering Connections with DNS Resolution Disabled • Application Load Balancer Target Groups Encrypted Protocol • AWS Backup Vault Without Resource-based Policy to Prevent Deletion of Recovery Points • AWS CloudTrail Logging • AWS CloudTrail Management Event Logging • AWS Lambda Functions Using Deprecated Runtimes • AWS Well-Architected high risk issues for security • CloudFront Custom SSL Certiﬁcates in the IAM Certiﬁcate Store • CloudFront SSL Certiﬁcate on the Origin Server • ELB Listener Security • Classic Load Balancer Security Groups • Exposed Access Keys • IAM Access Key Rotation • IAM Access Analyzer External Access • IAM Password Policy • IAM SAML 2.0 Identity Provider • MFA on Root Account Security API Version 2025-05-13 202 AWS Support • Root User Access Key • Security Groups – Speciﬁc Ports Unrestricted • Security Groups – Unrestricted Access Application Load Balancer security group Description User Guide Checks the security groups attached to the Application Load Balancer and its Amazon EC2 targets. Application Load
support-ug-062	support-ug.pdf	62	Certiﬁcate Store • CloudFront SSL Certiﬁcate on the Origin Server • ELB Listener Security • Classic Load Balancer Security Groups • Exposed Access Keys • IAM Access Key Rotation • IAM Access Analyzer External Access • IAM Password Policy • IAM SAML 2.0 Identity Provider • MFA on Root Account Security API Version 2025-05-13 202 AWS Support • Root User Access Key • Security Groups – Speciﬁc Ports Unrestricted • Security Groups – Unrestricted Access Application Load Balancer security group Description User Guide Checks the security groups attached to the Application Load Balancer and its Amazon EC2 targets. Application Load Balancer security groups should only allow inbound ports that are conﬁgured in a listener. A target's security groups should not accept direct connections from the internet in the same port the target receives traﬃc from the load balancer. If a security group allows access to ports that are not conﬁgured for the load balancer or allows direct access to targets, the risk of loss of data or malicious attacks increases. This check excludes the following groups: • Target Groups that are not associated with IP addresses or EC2 instances. • Security group rules for IPv6 traﬃc. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID 8604e947f2 Alert Criteria • Red: Target has a public IP and a security group that allows inbound connections on the traﬃc port from everywhere (0.0.0.0/0). • Red: Application Load Balancer has authentication enabled and target allows inbound connections on the traﬃc port from everywhere (0.0.0.0/0). Security API Version 2025-05-13 203 AWS Support User Guide • Yellow: Target's security group allow inbound connections on the traﬃc port from everywhere (0.0.0.0/0). • Yellow: Application Load Balancer security group allow inbound connections on ports that don't have a corresponding listener. • Green: Application Load Balancer security group only allows inbound connections on ports that match with a listener.. Recommended Action For improved security, make sure that your security groups only allow the necessary traﬃc ﬂows: • The Application Load Balancer's security groups should allow inbound connections only for the same ports conﬁgured in its listeners. • Use exclusive security groups for load balancers and targets. • Target security groups should allow connections in the traﬃc port only from the load balancer(s) it’s associated with. Additional Resources • Control traﬃc to your AWS resources using security groups • Security groups for your Application Load Balancer Report columns • Status • Region • Target Group • ALB Name • ALB SG ID • Target SG ID • Auth Enabled • Last Updated Time Amazon CloudWatch Log Group Retention Period Description Checks if Amazon CloudWatch log group retention period is set to 365 days or other speciﬁed number. Security API Version 2025-05-13 204 AWS Support User Guide By default, logs are kept indeﬁnitely and never expire. However, you can adjust the retention policy for each log group to comply with industry regulations or legal requirements for a speciﬁc period. You can specify the minimum retention time and log group names using the LogGroupNames and MinRetentionTime parameters in your AWS Conﬁg rules. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz186 Source AWS Config Managed Rule: cw-loggroup-retention-period-check Alert Criteria Yellow: Retention period of an Amazon CloudWatch log group is less than the desired minimum number of days. Recommended Action Conﬁgure a retention period of more than 365 days for your log data stored in Amazon CloudWatch Logs to meet compliance requirements. For more information, see Change log data retention in CloudWatch Logs. Additional Resources Altering CloudWatch log retention Report columns • Status • Region Security API Version 2025-05-13 205 AWS Support • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon EC2 instances with Microsoft SQL Server end of support Description Checks the SQL Server versions for Amazon Elastic Compute Cloud (Amazon EC2) instances running in the past 24 hours. This check alerts you if the versions are near or have reached the end of support. Each SQL Server version oﬀers 10 years of support, including 5 years of mainstream support and 5 years of extended support. After the end of support, the SQL Server version won’t receive regular security updates. Running applications with unsupported SQL Server versions can bring security
support-ug-063	support-ug.pdf	63	• Input Parameters • Last Updated Time User Guide Amazon EC2 instances with Microsoft SQL Server end of support Description Checks the SQL Server versions for Amazon Elastic Compute Cloud (Amazon EC2) instances running in the past 24 hours. This check alerts you if the versions are near or have reached the end of support. Each SQL Server version oﬀers 10 years of support, including 5 years of mainstream support and 5 years of extended support. After the end of support, the SQL Server version won’t receive regular security updates. Running applications with unsupported SQL Server versions can bring security or compliance risks. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Qsdfp3A4L3 Alert Criteria • Red: An EC2 instance has an SQL Server version that reached the end of support. • Yellow: An EC2 instance has an SQL Server version that will reach the end of support in 12 months. Recommended Action To modernize your SQL Server workloads, consider refactoring to AWS Cloud native databases like Amazon Aurora. For more information, see Modernize Windows Workloads with AWS. Security API Version 2025-05-13 206 AWS Support User Guide To move to a fully managed database, consider replatforming to Amazon Relational Database Service (Amazon RDS). For more information, see Amazon RDS for SQL Server. To upgrade your SQL Server on Amazon EC2, consider using the automation runbook to simplify your upgrade. For more information, see the AWS Systems Manager documentation. If you can’t upgrade your SQL Server on Amazon EC2, consider the End-of-Support Migration Program (EMP) for Windows Server. For more information, see the EMP Website. Additional Resources • Get ready for SQL Server end of support with AWS • Microsoft SQL Server on AWS Report columns • Status • Region • Instance ID • SQL Server Version • Support Cycle • End of Support • Last Updated Time Amazon EC2 instances with Microsoft Windows Server end of support Description This check alerts you if your Microsoft SQL versions are near or have reached the end of support. Each Windows Server version oﬀers 10 years of support, including 5 years of mainstream support and 5 years of extended support. After the end of support, the Windows Server version won't receive regular security updates. Running applications with unsupported Windows Server versions can bring security or compliance risks. Note This check generates results based on the AMI used to launch the EC2 instance. It's possible for the current instance operating system to be diﬀerent from its launch AMI. Security API Version 2025-05-13 207 AWS Support User Guide For example, if you launched an instance from a Windows Server 2016 AMI and later upgrade to Windows Server 2019, the launch AMI doesn't change. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Qsdfp3A4L4 Alert Criteria • Red: An EC2 instance has a Windows Server version that reached the end of support (Windows Server 2003, 2003 R2, 2008, and 2008 R2). • Yellow: An EC2 instance has a Windows Server version that will reach the end of support in less than 18 months (Windows Server 2012 and 2012 R2). Recommended Action To modernize your Windows Server workloads, consider the various options available on Modernize Windows Workloads with AWS. To upgrade your Windows Server workloads to run on more recent versions of Windows Server, you can use an automation runbook. For more information, see the AWS Systems Manager documentation. Please follow the set of steps below: • Upgrade the Windows Server version • Hard stop and start upon upgrading • If using EC2Conﬁg, please migrate to EC2Launch Report columns • Status • Region Security API Version 2025-05-13 208 AWS Support • Instance ID • Windows Server Version • Support Cycle • End of Support • Last Updated Time User Guide Amazon EC2 instances with Ubuntu LTS end of standard support Description This check alerts you if the versions are near or have reached the end of standard support. It is important to take action – either by migrating to the next LTS or upgrading to Ubuntu Pro. After the end of support, your 18.04 LTS machines will not receive any security updates. With an Ubuntu Pro subscription, your Ubuntu 18.04 LTS deployment can receive Expanded Security Maintenance (ESM) until 2028. Security vulnerabilities that
support-ug-064	support-ug.pdf	64	• Windows Server Version • Support Cycle • End of Support • Last Updated Time User Guide Amazon EC2 instances with Ubuntu LTS end of standard support Description This check alerts you if the versions are near or have reached the end of standard support. It is important to take action – either by migrating to the next LTS or upgrading to Ubuntu Pro. After the end of support, your 18.04 LTS machines will not receive any security updates. With an Ubuntu Pro subscription, your Ubuntu 18.04 LTS deployment can receive Expanded Security Maintenance (ESM) until 2028. Security vulnerabilities that remain unpatched open your systems to hackers and the potential of a major breach. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfprch15 Alert Criteria Red: An Amazon EC2 instance has an Ubuntu version that reached the end of standard support (Ubuntu 18.04 LTS, 18.04.1 LTS, 18.04.2 LTS, 18.04.3 LTS, 18.04.4 LTS, 18.04.5 LTS, and 18.04.6 LTS). Yellow: An Amazon EC2 instance has an Ubuntu version that will reach the end of standard support in less than 6 months (Ubuntu 20.04 LTS, 20.04.1 LTS, 20.04.2 LTS, 20.04.3 LTS, 20.04.4 LTS, 20.04.5 LTS, and 20.04.6 LTS). Security API Version 2025-05-13 209 AWS Support User Guide Green: All Amazon EC2 instances are compliant. Recommended Action To upgrade the Ubuntu 18.04 LTS instances to a supported LTS version, please follow the steps mentioned in this article. To upgrade the Ubuntu 18.04 LTS instances to Ubuntu Pro, visit AWS License Manager console and follow the steps mentioned in the AWS License Manager user guide. You can also refer to the Ubuntu blog showing a step by step demo of upgrading Ubuntu instances to Ubuntu Pro. Additional Resources For information about pricing, reach out to Support. Report columns • Status • Region • Ubuntu Lts Version • Expected End Of Support Date • Instance ID • Support Cycle • Last Updated Time Amazon EFS clients not using data-in-transit encryption Description Checks if Amazon EFS ﬁle system is mounted using data-in-transit encryption. AWS recommends that customers use data-in-transit encryption for all data ﬂows to protect data from accidental exposure or unauthorized access. Amazon EFS recommends clients use the ‘-o tls’ mount setting using the Amazon EFS mount helper to encrypt data in transit using TLS v1.2. Check ID c1dfpnchv1 Alert Criteria Yellow: One or more NFS clients for your Amazon EFS ﬁle system are not using the recommended mount settings that provide data-in-transit encryption. Security API Version 2025-05-13 210 AWS Support User Guide Green: All NFS clients for your Amazon EFS ﬁle system are using the recommended mount settings that provide data-in-transit encryption. Recommended Action To take advantage of data-in-transit encryption feature on Amazon EFS, we recommend that you remount your ﬁle system using the Amazon EFS mount helper and the recommended mount settings. Note Some Linux distributions don't include a version of stunnel that supports TLS features by default. If you're using an unsupported Linux distribution (see Supported distributions in the Amazon Elastic File System User Guide), then it's a best practice that you upgrade it before remounting with the recommended mount setting. Additional Resources • Encrypting data in transit Report columns • Status • Region • EFS File System ID • AZs with Unencrypted Connections • Last Updated Time Amazon EBS Public Snapshots Description Checks the permission settings for your Amazon Elastic Block Store (Amazon EBS) volume snapshots and alerts you if any snapshots are publicly accessible. When you make a snapshot public, you give all AWS accounts and users access to all the data on the snapshot. To share a snapshot only with speciﬁc users or accounts, mark the snapshot as private. Then, specify the user or accounts that you want to share the snapshot data with. Security API Version 2025-05-13 211 AWS Support User Guide Note that if you have Block Public Access enabled in ‘block all sharing’ mode, then your public snapshots aren't publicly accessible and don't appear in the results of this check. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Check ID ePs02jT06w Alert Criteria Red: The EBS volume snapshot is publicly accessible. Recommended Action Unless you are certain that you want to share all the data in the snapshot with all AWS accounts and users, modify the permissions: mark the snapshot as private, and then specify the accounts that you want to give permissions to. For more information, see Sharing an
support-ug-065	support-ug.pdf	65	publicly accessible and don't appear in the results of this check. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Check ID ePs02jT06w Alert Criteria Red: The EBS volume snapshot is publicly accessible. Recommended Action Unless you are certain that you want to share all the data in the snapshot with all AWS accounts and users, modify the permissions: mark the snapshot as private, and then specify the accounts that you want to give permissions to. For more information, see Sharing an Amazon EBS Snapshot. Use Block Public Access for EBS Snapshots to control the settings that allow public access to your data. This check can't be excluded from view in the Trusted Advisor console. To modify permissions for your snapshots directly, use a runbook in the AWS Systems Manager console. For more information, see AWSSupport-ModifyEBSSnapshotPermission. Additional Resources Amazon EBS Snapshots Report columns • Status • Region • Volume ID • Snapshot ID • Description Security API Version 2025-05-13 212 AWS Support User Guide Amazon RDS Aurora storage encryption is turned oﬀ Description Amazon RDS supports encryption at rest for all the database engines by using the keys that you manage in AWS Key Management Service. On an active DB instance with Amazon RDS encryption, the data stored at rest in the storage is encrypted, similar to automated backups, read replicas, and snapshots. If encryption isn't turned on while creating an Aurora DB cluster, then you must restore a decrypted snapshot to an encrypted DB cluster. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt005 Alert Criteria Red: Amazon RDS Aurora resources don't have encryption enabled. Security API Version 2025-05-13 213 AWS Support Recommended Action Turn on encryption of data at rest for your DB cluster. Additional Resources User Guide You can turn on encryption while creating a DB instance or use a workaround to turn on the encryption on an active DB instance. You can't modify a decrypted DB cluster to an encrypted DB cluster. However, you can restore a decrypted snapshot to an encrypted DB cluster. When you restore from the decrypted snapshot, you must specify a AWS KMS key. For more information, see Encrypting Amazon Aurora resources. Report columns • Status • Region • Resouce • Engine Name • Last Updated Time Amazon RDS engine minor version upgrade is required Description Your database resources aren't running the latest minor DB engine version. The latest minor version contains the latest security ﬁxes and other improvements. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Security API Version 2025-05-13 214 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt003 Alert Criteria Yellow: Amazon RDS resources aren't running the latest minor DB engine version. Recommended Action Upgrade to the latest engine version. Additional Resources We recommend that you maintain your database with the latest DB engine minor version as this version includes the latest security and functionality ﬁxes. The DB engine minor version upgrades contain only the changes which are backward-compatible with earlier minor versions of the same major version of the DB engine. For more information, see Upgrading a DB instance engine version. Report columns • Status • Region • Resouce • Engine Name • Engine Version Current • Recommended Value • Last Updated
support-ug-066	support-ug.pdf	66	resources aren't running the latest minor DB engine version. Recommended Action Upgrade to the latest engine version. Additional Resources We recommend that you maintain your database with the latest DB engine minor version as this version includes the latest security and functionality ﬁxes. The DB engine minor version upgrades contain only the changes which are backward-compatible with earlier minor versions of the same major version of the DB engine. For more information, see Upgrading a DB instance engine version. Report columns • Status • Region • Resouce • Engine Name • Engine Version Current • Recommended Value • Last Updated Time Security API Version 2025-05-13 215 AWS Support User Guide Amazon RDS Public Snapshots Description Checks the permission settings for your Amazon Relational Database Service (Amazon RDS) DB snapshots and alerts you if any snapshots are marked as public. When you make a snapshot public, you give all AWS accounts and users access to all the data on the snapshot. If you want to share a snapshot only with speciﬁc users or accounts, mark the snapshot as private. Then, specify the user or accounts you want to share the snapshot data with. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Check ID rSs93HQwa1 Alert Criteria Red: The Amazon RDS snapshot is marked as public. Recommended Action Unless you are certain you want to share all the data in the snapshot with all AWS accounts and users, modify the permissions: mark the snapshot as private, and then specify the accounts that you want to give permissions to. For more information, see Sharing a DB Snapshot or DB Cluster Snapshot. This check can't be excluded from view in the Trusted Advisor console. To modify permissions for your snapshots directly, you can use a runbook in the AWS Systems Manager console. For more information, see AWSSupport-ModifyRDSSnapshotPermission. Additional Resources Backing Up and Restoring Amazon RDS DB Instances Report columns • Status Security API Version 2025-05-13 216 AWS Support • Region • DB Instance or Cluster ID • Snapshot ID Amazon RDS Security Group Access Risk Description User Guide Checks security group conﬁgurations for Amazon Relational Database Service (Amazon RDS) and warns when a security group rule grants overly permissive access to your database. The recommended conﬁguration for a security group rule is to allow access only from speciﬁc Amazon Elastic Compute Cloud (Amazon EC2) security groups or from a speciﬁc IP address. Note This check evaluates only security groups that are attached toAmazon RDS instances running outside on an Amazon VPC. Check ID nNauJisYIT Alert Criteria • Yellow: A DB security group rule references an Amazon EC2 security group that grants global access on one of these ports: 20, 21, 22, 1433, 1434, 3306, 3389, 4333, 5432, 5500. • Red: A DB security group rule grants global access (the CIDR rule suﬃx is /0). • Green: A DB security group doesn't include permissive rules. Recommended Action EC2-Classic was retired on August 15, 2022. It's recommend to move your Amazon RDS instances to a VPC and use Amazon EC2 security groups. For more information of moving your DB instance to a VPC see Moving a DB instance not in a VPC into a VPC. If you are unable to migrate your Amazon RDS instances to a VPC, then review your security group rules and restrict access to authorized IP addresses or IP ranges. To edit a security group, use the AuthorizeDBSecurityGroupIngress API or the AWS Management Console. For more information, see Working with DB Security Groups. Security API Version 2025-05-13 217 User Guide AWS Support Additional Resources • Amazon RDS Security Groups • Classless Inter-Domain Routing • List of TCP and UDP port numbers Report columns • Status • Region • RDS Security Group Name • Ingress Rule • Reason Amazon RDS storage encryption is turned oﬀ Description Amazon RDS supports encryption at rest for all the database engines by using the keys that you manage in AWS Key Management Service. On an active DB instance with Amazon RDS encryption, the data stored at rest in the storage is encrypted, similar to automated backups, read replicas, and snapshots. If encryption isn't turned on while creating a DB instance, then you must restore an encrypted copy of the decrypted snapshot before you turn on the encryption. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations
support-ug-067	support-ug.pdf	67	and snapshots. If encryption isn't turned on while creating a DB instance, then you must restore an encrypted copy of the decrypted snapshot before you turn on the encryption. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the Security API Version 2025-05-13 218 AWS Support User Guide recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt006 Alert Criteria Red: Amazon RDS resources don't have encryption enabled. Recommended Action Turn on encryption of data at rest for your DB instance. Additional Resources You can encrypt a DB instance only when you create the DB instance. To encrypt an existing active DB instance: Create an encrypted copy of the original DB instance 1. Create a snapshot of your DB instance. 2. Create an encrypted copy of the snapshot created in step 1. 3. Restore a DB instance from the encrypted snapshot. For more information, see the following resources: • Encrypting Amazon RDS resources • Copying a DB snapshot Report columns • Status • Region • Resouce • Engine Name Security API Version 2025-05-13 219 AWS Support • Last Updated Time User Guide Amazon Route 53 mismatching CNAME records pointing directly to S3 buckets Description Checks the Amazon Route 53 Hosted Zones with CNAME records pointing directly to Amazon S3 bucket hostnames and alerts if your CNAME does not match with your S3 bucket name. Check ID c1ng44jvbm Alert Criteria Red: Amazon Route 53 Hosted Zone has CNAME records pointing to mismatching S3 bucket hostnames. Green: No mismatching CNAME records found in your Amazon Route 53 Hosted Zone. Recommended Action When pointing CNAME records to S3 bucket hostnames, you must make sure that a matching bucket exists for any CNAME or alias record you conﬁgure. By doing this, you avoid the risk of your CNAME records being spoofed. You also prevent any unauthorized AWS user from hosting faulty or malicious web content with your domain. To avoid pointing CNAME records directly to S3 bucket hostnames, consider using origin access control (OAC) to access your S3 bucket web assets through Amazon CloudFront. For more information about associating CNAME with an Amazon S3 bucket hostname, see Customizing Amazon S3 URLs with CNAME records. Additional Resources • How to associate a hostname with an Amazon S3 bucket • Restricting access to an Amazon S3 origin with CloudFront Report columns • Status • Hosted Zone ID • Hosted Zone ARN Security API Version 2025-05-13 220 AWS Support User Guide • Matching CNAME Records • Mismatching CNAME Records • Last Updated Time Amazon Route 53 MX Resource Record Sets and Sender Policy Framework Description For each MX record, checks for an associated TXT record that contains a valid SPF value. The TXT record value must start with “v=spf1". SPF record types are deprecated by the Internet Engineering Task Force (IETF). With Route 53, I'ts a best practice to use a TXT record instead of an SPF record. Trusted Advisor reports this check as green when an MX record has at least one associated TXT record with a valid SPF value. Check ID c9D319e7sG Alert Criteria • Green: An MX resource record set has a TXT resource record that contains a valid SPF value. • Yellow: An MX resource record set has a TXT or SPF resource record that contains a valid SPF value. • Red: An MX resource record set doesn't have a TXT or SPF resource record that contains a valid SPF value. Recommended Action For each MX resource record set, create a TXT resource record set that contains a valid SPF value. For more information, see Sender Policy Framework: SPF Record Syntax and Creating Resource Record Sets By Using the Amazon Route 53 Console. Additional Resources • MX record type • SPF record type • re:Post Guidance • RFC 7208 Report columns • Hosted Zone Name Security API Version 2025-05-13 221 AWS Support User Guide • Hosted Zone ID • Resource Record Set Name • Status Amazon S3 Bucket Permissions Description Checks buckets in Amazon Simple Storage Service (Amazon S3) that have open access permissions, or that allow access to any authenticated AWS user. This check examines explicit bucket
support-ug-068	support-ug.pdf	68	valid SPF value. For more information, see Sender Policy Framework: SPF Record Syntax and Creating Resource Record Sets By Using the Amazon Route 53 Console. Additional Resources • MX record type • SPF record type • re:Post Guidance • RFC 7208 Report columns • Hosted Zone Name Security API Version 2025-05-13 221 AWS Support User Guide • Hosted Zone ID • Resource Record Set Name • Status Amazon S3 Bucket Permissions Description Checks buckets in Amazon Simple Storage Service (Amazon S3) that have open access permissions, or that allow access to any authenticated AWS user. This check examines explicit bucket permissions, as well as bucket policies that might override those permissions. Granting list access permissions to all users for an Amazon S3 bucket is not recommended. These permissions can lead to unintended users listing objects in the bucket at high frequency, which can result in higher than expected charges. Permissions that grant upload and delete access to everyone can lead to security vulnerabilities in your bucket. Check ID Pfx0RwqBli Alert Criteria • Yellow: The bucket ACL allows List access for Everyone or Any Authenticated AWS User. • Yellow: A bucket policy allows any kind of open access. • Yellow: Bucket policy has statements that grant public access. The Block public and cross- account access to buckets that have public policies setting is turned on and has restricted access to only authorized users of that account until public statements are removed. • Yellow: Trusted Advisor does not have permission to check the policy, or the policy could not be evaluated for other reasons. • Red: The bucket ACL allows upload and delete access for Everyone or Any Authenticated AWS User. • Green: All Amazon S3 are compliant based on the ACL and/or bucket policy. Recommended Action If a bucket allows open access, determine if open access is truly needed. For example to host a static website, you can use Amazon CloudFront to serve the content hosted on Amazon S3. See Restricting access to anAmazon S3 origin in the Amazon CloudFront Developer Guide. When possible,, update the bucket permissions to restrict access to the owner or speciﬁc users. Use Security API Version 2025-05-13 222 AWS Support User Guide Amazon S3 Block Public Access to control the settings that allow public access to your data. See Setting Bucket and Object Access Permissions. Additional Resources Managing Access Permissions to Your Amazon S3 Resources Conﬁguring block public access settings for your Amazon S3 buckets Report columns • Status • Region Name • Region API Parameter • Bucket Name • ACL Allows List • ACL Allows Upload/Delete • Policy Allows Access Amazon VPC Peering Connections with DNS Resolution Disabled Description Checks if your VPC peering connections have DNS resolution turned on for both the acceptor and requester VPCs. DNS resolution for a VPC peering connection allows the resolution of public DNS hostnames to private IPv4 addresses when queried from your VPC. This allows the use of DNS names for communication between resources in peered VPCs. DNS resolution in your VPC peering connections makes application development and management simpler and less error-prone, and it ensures that resources always communicate privately over the VPC peering connection. You can specify the VPC IDs, using the vpcIds parameters in your AWS Conﬁg rules. For more information, see Enable DNS resolution for a VPC peering connection. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Security API Version 2025-05-13 223 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz124 Source AWS Config Managed Rule: vpc-peering-dns-resolution-check Alert Criteria Yellow: DNS resolution is not enabled for both the acceptor and the requestor VPCs in a VPC peering connection. Recommended Action Turn on DNS resolution for your VPC peering connections. Additional Resources • Modify VPC peering connection options • DNS attributes in your VPC Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Application Load Balancer Target Groups Encrypted Protocol Description Checks Application Load Balancer (ALB) target groups are using HTTPS protocol to encrypt communication in transit for back-end target types of instance or IP. HTTPS requests between ALB and back-end targets help to maintain data conﬁdentiality for data in transit. Security API Version 2025-05-13 224 AWS Support Check ID c2vlfg0p1w Alert Criteria User Guide • Yellow: Application Load Balancer target group using HTTP. • Green: Application Load Balancer target group using HTTPS. Recommended Action Conﬁgure back-end target types of instance or IP to support HTTPS access, and change target group to use HTTPS protocol to encrypt communication between ALB and
support-ug-069	support-ug.pdf	69	Checks Application Load Balancer (ALB) target groups are using HTTPS protocol to encrypt communication in transit for back-end target types of instance or IP. HTTPS requests between ALB and back-end targets help to maintain data conﬁdentiality for data in transit. Security API Version 2025-05-13 224 AWS Support Check ID c2vlfg0p1w Alert Criteria User Guide • Yellow: Application Load Balancer target group using HTTP. • Green: Application Load Balancer target group using HTTPS. Recommended Action Conﬁgure back-end target types of instance or IP to support HTTPS access, and change target group to use HTTPS protocol to encrypt communication between ALB and back-end target types of instance or IP. Additional Resources Enforce encryption in transit Application Load Balancer Target Types Application Load Balancer Routing Conﬁguration Data Protection in Elastic Load Balancing Report columns • Status • Region • ALB Arn • ALB Name • ALB VPC Id • Target Group Arn • Target Group Name • Target Group Protocol • Last Updated Time Security API Version 2025-05-13 225 AWS Support User Guide AWS Backup Vault Without Resource-based Policy to Prevent Deletion of Recovery Points Description Checks if AWS Backup vaults have an attached resource-based policy that prevents recovery point deletion. The resource-based policy prevents unexpected deletion of recovery points, which allows you to enforce access control with least privileges against your backup data. You can specify the AWS Identity and Access Management ARNs that you don't want the rule to check in the principalArnList parameter of your AWS Conﬁg rules. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz152 Source AWS Config Managed Rule: backup-recovery-point-manual-deletion-disabled Alert Criteria Yellow: There are AWS Backup vaults that don't have a resource-based policy to prevent deletion of recovery points. Recommended Action Create resource-based policies for your AWS Backup vaults to prevent unexpected deletion of recovery points. The policy must include a "Deny" statement with backup:DeleteRecoveryPoint, backup:UpdateRecoveryPointLifecycle, and backup:PutBackupVaultAccessPolicy permissions. Security API Version 2025-05-13 226 AWS Support User Guide For more information, see Set access policies on backup vaults. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time AWS CloudTrail Logging Description Checks your use of AWS CloudTrail. CloudTrail provides increased visibility into activity in your AWS account by recording information about AWS API calls made on the account. You can use these logs to determine, for example, what actions a particular user has taken during a speciﬁed time period, or which users have taken actions on a particular resource during a speciﬁed time period. Because CloudTrail delivers log ﬁles to an Amazon Simple Storage Service (Amazon S3) bucket, CloudTrail must have write permissions for the bucket. If a trail applies to all Regions (the default when creating a new trail), the trail appears multiple times in the Trusted Advisor report. Check ID vjafUGJ9H0 Alert Criteria • Yellow: CloudTrail reports log delivery errors for a trail. • Red: A trail has not been created for a Region, or logging is turned oﬀ for a trail. Recommended Action To create a trail and start logging from the console, go to the AWS CloudTrail console. To start logging, see Stopping and Starting Logging for a Trail. If you receive log delivery errors, check to make sure that the bucket exists and that the necessary policy is attached to the bucket. See Amazon S3 Bucket Policy. Security API Version 2025-05-13 227 User Guide AWS Support Additional Resources • AWS CloudTrail User Guide • Supported Regions • Supported Services Report columns • Status • Region • Trail Name • Logging Status • Bucket Name • Last Delivery Date AWS CloudTrail Management Event Logging Description Checks your use of AWS CloudTrail. CloudTrail provides increased visibility into activity in your AWS account. It does this by recording information about AWS API calls that are made on the account. You can use these logs to determine, for example, what actions a particular user has taken during a speciﬁed time period, or which users have taken actions on a particular resource during a speciﬁed time period. Because CloudTrail delivers log ﬁles to an Amazon Simple Storage Service (Amazon S3) bucket, CloudTrail must have write permissions for the bucket. If a trail applies to all AWS Regions (the default when creating a new trail), then the trail appears multiple times in the Trusted Advisor report. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise
support-ug-070	support-ug.pdf	70	a speciﬁed time period, or which users have taken actions on a particular resource during a speciﬁed time period. Because CloudTrail delivers log ﬁles to an Amazon Simple Storage Service (Amazon S3) bucket, CloudTrail must have write permissions for the bucket. If a trail applies to all AWS Regions (the default when creating a new trail), then the trail appears multiple times in the Trusted Advisor report. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Security API Version 2025-05-13 228 AWS Support Check ID c25hn9x03v Alert Criteria User Guide • Red: No trail is created for an AWS Region, or logging isn’t enabled for any trail. • Yellow: CloudTrail is enabled but all trails report log delivery errors. • Green: CloudTrail is enabled and no log delivery errors are reported. Recommended Action To create a trail and start logging from the console, open the AWS CloudTrail console. To start logging, see Stopping and Starting Logging for a Trail. If you receive log delivery errors, then make sure that the bucket exists and that the necessary policy is attached to the bucket. See Amazon S3 Bucket Policy. Additional Resources • AWS CloudTrail User Guide • Supported Regions • Supported Services • Creating a trail for an organization Report columns • Status • Region • Logging Enabled • Delivery Error Reported • Last Updated Time AWS Lambda Functions Using Deprecated Runtimes Description Checks for Lambda functions whose $LATEST version is conﬁgured to use a runtime that is approaching deprecation, or is deprecated. Deprecated runtimes are not eligible for security updates or technical support Security API Version 2025-05-13 229 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Published Lambda function versions are immutable, which means they can be invoked but not updated. Only the $LATEST version for a Lambda function can be updated. For more information, see Lambda function versions. Check ID L4dfs2Q4C5 Alert Criteria • Red: The function's $LATEST version is conﬁgured to use a runtime that is already deprecated. • Yellow: The function's $LATEST version is running on a runtime that will be deprecated within 180 days. Recommended Action If you have functions that are running on a runtime that is approaching deprecation, you should prepare for migration to a supported runtime. For more information, see Runtime support policy. We recommend that you delete earlier function versions that you’re no longer using. Additional Resources Lambda runtimes Report columns • Status • Region • Function ARN • Runtime • Days to Deprecation • Deprecation Date Security API Version 2025-05-13 230 AWS Support • Average Daily Invokes • Last Updated Time AWS Well-Architected high risk issues for security Description User Guide Checks for high risk issues (HRIs) for your workloads in the security pillar. This check is based on your AWS-Well Architected reviews. Your check results depend on whether you completed the workload evaluation with AWS Well-Architected. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Wxdfp4B1L3 Alert Criteria • Red: At least one active high risk issue was identiﬁed in the security pillar for AWS Well- Architected. • Green: No active high risk issues were detected in the security pillar for AWS Well-Architected. Recommended Action AWS Well-Architected detected high risk issues during your workload evaluation. These issues present opportunities to reduce risk and save money. Sign in to the AWS Well-Architected tool to review your answers and take action to resolve your active issues. Report columns • Status • Region • Workload ARN Security API Version 2025-05-13 231 User Guide AWS Support • Workload Name • Reviewer Name • Workload Type • Workload Started Date • Workload Last Modiﬁed Date • Number of identiﬁed HRIs for Security • Number of HRIs resolved for Security • Number of questions for Security • Total number of questions in Security pillar • Last Updated Time CloudFront Custom SSL Certiﬁcates in the IAM Certiﬁcate Store Description Checks the SSL certiﬁcates for CloudFront alternate domain names in the IAM certiﬁcate store. This check alerts
support-ug-071	support-ug.pdf	71	to resolve your active issues. Report columns • Status • Region • Workload ARN Security API Version 2025-05-13 231 User Guide AWS Support • Workload Name • Reviewer Name • Workload Type • Workload Started Date • Workload Last Modiﬁed Date • Number of identiﬁed HRIs for Security • Number of HRIs resolved for Security • Number of questions for Security • Total number of questions in Security pillar • Last Updated Time CloudFront Custom SSL Certiﬁcates in the IAM Certiﬁcate Store Description Checks the SSL certiﬁcates for CloudFront alternate domain names in the IAM certiﬁcate store. This check alerts you if a certiﬁcate is expired, will expire soon, uses outdated encryption, or is not conﬁgured correctly for the distribution. When a custom certiﬁcate for an alternate domain name expires, browsers that display your CloudFront content might show a warning message about the security of your website. Certiﬁcates that are encrypted by using the SHA-1 hashing algorithm are being deprecated by most web browsers such as Chrome and Firefox. A certiﬁcate must contain a domain name that matches either the Origin Domain Name or the domain name in the host header of a viewer request. If it doesn't match, CloudFront returns an HTTP status code of 502 (bad gateway) to the user. For more information, see Using Alternate Domain Names and HTTPS. Check ID N425c450f2 Alert Criteria • Red: A custom SSL certiﬁcate is expired. • Yellow: A custom SSL certiﬁcate expires in the next seven days. • Yellow: A custom SSL certiﬁcate was encrypted by using the SHA-1 hashing algorithm. Security API Version 2025-05-13 232 AWS Support User Guide • Yellow: One or more of the alternate domain names in the distribution don't appear either in the Common Name ﬁeld or the Subject Alternative Names ﬁeld of the custom SSL certiﬁcate. Recommended Action We recommend using AWS Certiﬁcate Manager to provision, manage, and deploy your server certiﬁcates. With ACM, you can request a new certiﬁcate or deploy an existing ACM or external certiﬁcate to AWS resources. Certiﬁcates provided by ACM are free and can be automatically renewed. For more information about using ACM, see the AWS Certiﬁcate Manager User Guide. To check Regions ACM supports, see AWS Certiﬁcate Manager endpoints and quotas in the AWS General Reference. Renew expired certiﬁcates or certiﬁcates that are about to expire. For more information on renewing a certiﬁcate see Managing server certiﬁcates in IAM. Replace a certiﬁcate that was encrypted by using the SHA-1 hashing algorithm with a certiﬁcate that is encrypted by using the SHA-256 hashing algorithm. Replace the certiﬁcate with a certiﬁcate that contains the applicable values in the Common Name or Subject Alternative Domain Names ﬁelds. Additional Resources Using an HTTPS Connection to Access Your Objects Importing Certiﬁcates AWS Certiﬁcate Manager User Guide Report columns • Status • Distribution ID • Distribution Domain Name • Certiﬁcate Name • Reason Security API Version 2025-05-13 233 AWS Support User Guide CloudFront SSL Certiﬁcate on the Origin Server Description Checks your origin server for SSL certiﬁcates that are expired, about to expire, missing, or that use outdated encryption. If a certiﬁcate has one of these issues, CloudFront responds to requests for your content with HTTP status code 502, Bad Gateway. Certiﬁcates that were encrypted by using the SHA-1 hashing algorithm are being deprecated by web browsers such as Chrome and Firefox. Depending on the number of SSL certiﬁcates that you have associated with your CloudFront distributions, this check might add a few cents per month to your bill with your web hosting provider, for example, AWS if you're using Amazon EC2 or Elastic Load Balancing as the origin for your CloudFront distribution. This check does not validate your origin certiﬁcate chain or certiﬁcate authorities. You can check these in your CloudFront conﬁguration. Check ID N430c450f2 Alert Criteria • Red: An SSL certiﬁcate on your origin has expired or is missing. • Yellow: An SSL certiﬁcate on your origin expires in the next thirty days. • Yellow: An SSL certiﬁcate on your origin was encrypted by using the SHA-1 hashing algorithm. • Yellow: An SSL certiﬁcate on your origin can't be located. The connection might have failed due to timeout, or other HTTPS connection problems. Recommended Action Renew the certiﬁcate on your origin if it has expired or is about to expire. Add a certiﬁcate if one does not exist. Replace a certiﬁcate that was encrypted by using the SHA-1 hashing algorithm with a certiﬁcate that is encrypted by using the SHA-256 hashing algorithm. Additional Resources Using Alternate Domain Names and HTTPS Security API Version 2025-05-13 234 User Guide AWS Support Report columns • Status • Distribution ID • Distribution Domain Name • Origin • Reason ELB Listener Security Description Checks for classic load balancers with listeners that don't use the recommended security conﬁgurations
support-ug-072	support-ug.pdf	72	problems. Recommended Action Renew the certiﬁcate on your origin if it has expired or is about to expire. Add a certiﬁcate if one does not exist. Replace a certiﬁcate that was encrypted by using the SHA-1 hashing algorithm with a certiﬁcate that is encrypted by using the SHA-256 hashing algorithm. Additional Resources Using Alternate Domain Names and HTTPS Security API Version 2025-05-13 234 User Guide AWS Support Report columns • Status • Distribution ID • Distribution Domain Name • Origin • Reason ELB Listener Security Description Checks for classic load balancers with listeners that don't use the recommended security conﬁgurations for encrypted communication. AWS recommends that you use a secure protocol (HTTPS or SSL), up-to-date security policies, and ciphers and protocols that are secure. When you use a secure protocol for a front-end connection (client to load balancer), the requests are encrypted between your clients and the load balancer. This creates a more secure environment. Elastic Load Balancing provides predeﬁned security policies with ciphers and protocols that adhere to AWS security best practices. New versions of predeﬁned policies are released as new conﬁgurations become available. Check ID a2sEc6ILx Alert Criteria • Red: A load balancer has no listeners conﬁgured with a secure protocol (HTTPS). • Yellow: A load balancer HTTPS listener is conﬁgured with a Security Policy that contains a weak cipher. • Yellow: A load balancer HTTPS listener is not conﬁgured with the recommended Security Policy. • Green: A load balancer has at least one HTTPS listener AND all HTTPS listeners are conﬁgured with the recommended policy. Recommended Action If the traﬃc to your load balancer must be secure, use either the HTTPS or the SSL protocol for the front-end connection. Security API Version 2025-05-13 235 AWS Support User Guide Upgrade your load balancer to the latest version of the predeﬁned SSL security policy. Use only the recommended ciphers and protocols. For more information, see Listener Conﬁgurations for Elastic Load Balancing. Additional Resources • Listener Conﬁgurations Quick Reference • Update SSL Negotiation Conﬁguration of Your Load Balancer • SSL Negotiation Conﬁgurations for Elastic Load Balancing • SSL Security Policy Table Report columns • Status • Region • Load Balancer Name • Load Balancer Port • Reason Classic Load Balancer Security Groups Description Checks for load balancers conﬁgured with a security group that allows access to ports that are not conﬁgured for the load balancer. If a security group allows access to ports that are not conﬁgured for the load balancer, the risk of loss of data or malicious attacks increases. Check ID xSqX82fQu Alert Criteria • Yellow: The inbound rules of an Amazon VPC security group associated with a load balancer allow access to ports that are not deﬁned in the load balancer's listener conﬁguration. • Green: The inbound rules of an Amazon VPC security group associated with a load balancer do not allow access to ports that are not deﬁned in the load balancers listener conﬁguration. Security API Version 2025-05-13 236 AWS Support Recommended Action User Guide Conﬁgure the security group rules to restrict access to only those ports and protocols that are deﬁned in the load balancer listener conﬁguration, plus the ICMP protocol to support Path MTU Discovery. See Listeners for Your Classic Load Balancer and Security Groups for Load Balancers in a VPC. If a security group is missing, apply a new security group to the load balancer. Create security group rules that restrict access to only those ports and protocols that are deﬁned in the load balancer listener conﬁguration. See Security Groups for Load Balancers in a VPC. Additional Resources • Elastic Load Balancing User Guide • Migrate your Classic Load Balancer • Conﬁgure Your Classic Load Balancer Report columns • Status • Region • Load Balancer Name • Security Group IDs • Reason Exposed Access Keys Description Checks popular code repositories for access keys that have been exposed to the public and for irregular Amazon Elastic Compute Cloud (Amazon EC2) usage that could be the result of a compromised access key. An access key consists of an access key ID and the corresponding secret access key. Exposed access keys pose a security risk to your account and other users, could lead to excessive charges from unauthorized activity or abuse, and violate the AWS Customer Agreement. If your access key is exposed, take immediate action to secure your account. To protect your account from excessive charges, AWS temporarily limits your ability to create some AWS resources. This does not make your account secure. It only partially limits the unauthorized usage for which you could be charged. Security API Version 2025-05-13 237 AWS Support Note User Guide This check doesn't guarantee the identiﬁcation of exposed access keys or compromised EC2 instances. You are ultimately responsible for the safety and security of your access keys and AWS
support-ug-073	support-ug.pdf	73	from unauthorized activity or abuse, and violate the AWS Customer Agreement. If your access key is exposed, take immediate action to secure your account. To protect your account from excessive charges, AWS temporarily limits your ability to create some AWS resources. This does not make your account secure. It only partially limits the unauthorized usage for which you could be charged. Security API Version 2025-05-13 237 AWS Support Note User Guide This check doesn't guarantee the identiﬁcation of exposed access keys or compromised EC2 instances. You are ultimately responsible for the safety and security of your access keys and AWS resources. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. If a deadline is shown for an access key, AWS may suspend your AWS account if the unauthorized usage is not stopped by that date. If you believe an alert is in error, contact AWS Support. The information displayed in Trusted Advisor might not reﬂect the most recent state of your account. No exposed access keys are marked as resolved until all exposed access keys on the account have been resolved. This data synchronization can take up to one week. Check ID 12Fnkpl8Y5 Alert Criteria • Red: Potentially compromised – AWS has identiﬁed an access key ID and corresponding secret access key that have been exposed on the Internet and may have been compromised (used). • Red: Exposed – AWS has identiﬁed an access key ID and corresponding secret access key that have been exposed on the Internet. • Red: Suspected - Irregular Amazon EC2 usage indicates that an access key may have been compromised, but it has not been identiﬁed as exposed on the Internet. Recommended Action Delete the aﬀected access key as soon as possible. If the key is associated with an IAM user, see Managing Access Keys for IAM Users. Security API Version 2025-05-13 238 AWS Support User Guide Check your account for unauthorized usage. Sign in to the AWS Management Console and check each service console for suspicious resources. Pay special attention to running Amazon EC2 instances, Spot Instance requests, access keys, and IAM users. You can also check overall usage on the Billing and Cost Management console. Additional Resources • Best Practices for Managing AWS Access Keys • AWS Security Audit Guidelines Report columns • Access Key ID • User Name (IAM or Root) • Fraud Type • Case ID • Time Updated • Location • Deadline • Usage (USD per Day) IAM Access Key Rotation Description Checks for active IAM access keys that have not been rotated in the last 90 days. When you rotate your access keys regularly, you reduce the chance that a compromised key could be used without your knowledge to access resources. For the purposes of this check, the last rotation date and time is when the access key was created or most recently activated. The access key number and date come from the access_key_1_last_rotated and access_key_2_last_rotated information in the most recent IAM credential report. Because the regeneration frequency of a credential report is restricted, refreshing this check might not reﬂect recent changes. For more information, see Getting Credential Reports for Your AWS account. In order to create and rotate access keys, a user must have the appropriate permissions. For more information, see Allow Users to Manage Their Own Passwords, Access Keys, and SSH Keys. Security API Version 2025-05-13 239 AWS Support Check ID DqdJqYeRm5 Alert Criteria User Guide • Green: The access key is active and has been rotated in the last 90 days. • Yellow: The access key is active and has been rotated in the last 2 years, but more than 90 days ago. • Red: The access key is active and has not been rotated in the last 2 years. Recommended Action Rotate access keys on a regular basis. See Rotating Access Keys and Managing Access Keys for IAM Users. Additional Resources • IAM Best Practices • How to rotate access keys for IAM users Report columns • Status • IAM user • Access Key • Key Last Rotated • Reason IAM Access Analyzer External Access Description Checks if the IAM Access Analyzer external access at the account level is present. IAM Access Analyzer external access analyzers help identify resources in your accounts that are shared with an external entity. The analyzer then creates a centralized dashboard with the ﬁndings. After the new analyzer is activated in the IAM console, security teams can then prioritize which accounts to review based on excessive permissions. An external access analyzer creates public and cross-account
support-ug-074	support-ug.pdf	74	keys for IAM users Report columns • Status • IAM user • Access Key • Key Last Rotated • Reason IAM Access Analyzer External Access Description Checks if the IAM Access Analyzer external access at the account level is present. IAM Access Analyzer external access analyzers help identify resources in your accounts that are shared with an external entity. The analyzer then creates a centralized dashboard with the ﬁndings. After the new analyzer is activated in the IAM console, security teams can then prioritize which accounts to review based on excessive permissions. An external access analyzer creates public and cross-account access ﬁndings for resources, and is provided at no additional charge. Security API Version 2025-05-13 240 AWS Support Check ID 07602fcad6 Alert Criteria User Guide • Red: The analyzer external access isn’t activated at the account level. • Green: The analyzer external access is activated at the account level. Recommended Action The creation of an external access analyzer per account helps security teams to prioritize which accounts to review based on excessive permissions. For more information, see Getting started with AWS Identity and Access Management Access Analyzer ﬁndings. Additionally, its a best practice to utilize the unused access analyzer, a paid feature that simpliﬁes inspecting unused access to guide you toward least privilege. For more information, see Identifying unused access granted to IAM users and roles. Additional Resources • Using AWS Identity and Access Management Access Analyzer • IAM Access Analyzer updates: Find unused access, check policies before deployment Report columns • Status • Region • Account External Access Analyzer Arn • Organization External Access Analyzer Arns • Last Updated Time IAM Password Policy Description Checks the password policy for your account and warns when a password policy is not enabled, or if password content requirements have not been enabled. Password content requirements increase the overall security of your AWS environment by enforcing the creation of strong user passwords. When you create or change a password policy, the change is enforced immediately for new users but does not require existing users to change their passwords. Security API Version 2025-05-13 241 AWS Support Check ID Yw2K9puPzl Alert Criteria User Guide • Green: A password policy is enabled with recommended content requirement enabled. • Yellow: A password policy is enabled, but at least one content requirement is not enabled. Recommended Action If some content requirements are not enabled, consider enabling them. If no password policy is enabled, create and conﬁgure one. See Setting an Account Password Policy for IAM Users. To access the AWS Management Console, IAM users need passwords. As a best practice, AWS highly recommends that instead of creating IAM users, you use federation. Federation allows users to use their existing corporate credentials to log into the AWS Management Console. Use IAM Identity Center to create or federate the user, and then assume an IAM role into an account. To learn more about identity providers and federation, see Identity providers and federation in the IAM User Guide. To learn more about IAM Identity Center, see the IAM Identity Center User Guide. Additional Resources Managing Passwords Report columns • Password Policy • Uppercase • Lowercase • Number • Non-alphanumeric IAM SAML 2.0 Identity Provider Description Checks if the AWS account is conﬁgured for access via an identity provider (IdP) that supports SAML 2.0. Be sure to follow best practices when you centralize identities and conﬁgure users in an external identity provider or AWS IAM Identity Center. Security API Version 2025-05-13 242 AWS Support Check ID c2vlfg0p86 Alert Criteria User Guide • Yellow: This account isn’t conﬁgured for access via an identity provider (IdP) that supports SAML 2.0. • Green: This account is conﬁgured for access via an identity provider (IdP) that supports SAML 2.0. Recommended Action Activate IAM Identity Center for the AWS account. For more information, see EnablingIAM Identity Center. After you turn on IAM Identity Center, you can then perform common tasks like creating a permission set and assigning access for Identity Center groups. For more information, see Common tasks. It’s a best practice to manage human users in IAM Identity Center. But you can activate federated user access with IAM for human users in the short-term for small scale deployments. For more information see SAML 2.0 federation. Additional Resources What is IAM Identity Center? What IsIAM? Report columns • Status • AWS account Id • Last Updated Time MFA on Root Account Description Checks the root account and warns if multi-factor authentication (MFA) is not enabled. For increased security, we recommend that you protect your account by using MFA, which requires a user to enter a unique authentication code from their MFA hardware or virtual device when interacting with the AWS Management Console and associated websites. Security API Version 2025-05-13 243 AWS Support Note User Guide For your
support-ug-075	support-ug.pdf	75	scale deployments. For more information see SAML 2.0 federation. Additional Resources What is IAM Identity Center? What IsIAM? Report columns • Status • AWS account Id • Last Updated Time MFA on Root Account Description Checks the root account and warns if multi-factor authentication (MFA) is not enabled. For increased security, we recommend that you protect your account by using MFA, which requires a user to enter a unique authentication code from their MFA hardware or virtual device when interacting with the AWS Management Console and associated websites. Security API Version 2025-05-13 243 AWS Support Note User Guide For your AWS Organizations management account, AWS requires multi-factor authentication (MFA) for the root user when accessing the AWS Management Console. For your AWS Organizations member accounts, AWS recommends the use of MFA. In addition to applying MFA, if you use AWS Organizations to manage multiple accounts, you can apply an SCP to restrict access to member account root user. For more information, please see Best practices for member accounts in AWS Organizations User Guide. Check ID 7DAFEmoDos Alert Criteria Red: MFA is not enabled on the root account. Recommended Action Log in to your root account and activate an MFA device. See Checking MFA Status and Setting Up an MFA Device. You can activate MFA on your account at any time by visiting the Security Credentials page. To do this, choose the account menu drop-down in theAWS Management Console. AWS supports multiple industry standard forms of MFA, such as FIDO2 and virtual authenticators. This gives the ﬂexibility to choose a MFA device that meets your needs. It's a best practice to you register more than one MFA device for resiliency in the event that one of your MFA devices is lost or stops working. Additional Resources Please refer to General steps for activating MFA devices and Enable a virtual MFA device for your AWS account root user (console) in theIAM User Guide for additional information. Root User Access Key Description Checks if the root user access key is present. It's strongly recommended that you don't create access key pairs for your root user. Because only a few tasks require the root user and you Security API Version 2025-05-13 244 AWS Support User Guide typically perform those tasks infrequently, it’s a best practice to log in to the AWS Management Console to perform the root user tasks. Before you create access keys, review the alternatives to long-term access keys. Check ID c2vlfg0f4h Alert Criteria Red: The root user access key is present Green: The root user access key isn’t present Recommended Action Delete the access key(s) for the root user. See Deleting access keys for the root user. This task must be performed by the root user. You can't perform these steps as an IAM user or role. Additional Resources Tasks that require root user credentials Resetting a lost or forgotten root user password Report columns • Status • Account ID • Last Updated Time Security Groups – Speciﬁc Ports Unrestricted Description Checks security groups for rules that allow unrestricted access (0.0.0.0/0) to speciﬁc ports. Unrestricted access increases opportunities for malicious activity (hacking, denial-of-service attacks, loss of data). The ports with highest risk are ﬂagged red, and those with less risk are ﬂagged yellow. Ports ﬂagged green are typically used by applications that require unrestricted access, such as HTTP and SMTP. If you have intentionally conﬁgured your security groups in this manner, we recommend using additional security measures to secure your infrastructure (such as IP tables). Security API Version 2025-05-13 245 AWS Support Note User Guide This check only evaluates security groups that you create and their inbound rules for IPv4 addresses. Security groups created by AWS Directory Service are ﬂagged as red or yellow, but they don’t pose a security risk and can be excluded. For more information, see the Trusted Advisor FAQ. Check ID HCP4007jGY Alert Criteria • Green: Security Group provides unrestricted access on ports 80, 25, 443, or 465. • Red: Security Group is attached to a resource and provides unrestricted access to port 20, 21, 22 , 1433, 1434, 3306, 3389, 4333, 5432, or 5500. • Yellow: Security Group provides unrestricted access to any other port. • Yellow: Security Group is not attached to any resource and provides unrestricted access. Recommended Action Restrict access to only those IP addresses that require it. To restrict access to a speciﬁc IP address, set the suﬃx to /32 (for example, 192.0.2.10/32). Be sure to delete overly permissive rules after creating rules that are more restrictive. Review and delete unused security groups. You can use AWS Firewall Manager to centrally conﬁgure and manage security groups at scale across AWS accounts, For more information, see the AWS Firewall Manager documentation. Consider using Systems Manager Sessions Manager for SSH (Port 22) and RDP
support-ug-076	support-ug.pdf	76	Yellow: Security Group is not attached to any resource and provides unrestricted access. Recommended Action Restrict access to only those IP addresses that require it. To restrict access to a speciﬁc IP address, set the suﬃx to /32 (for example, 192.0.2.10/32). Be sure to delete overly permissive rules after creating rules that are more restrictive. Review and delete unused security groups. You can use AWS Firewall Manager to centrally conﬁgure and manage security groups at scale across AWS accounts, For more information, see the AWS Firewall Manager documentation. Consider using Systems Manager Sessions Manager for SSH (Port 22) and RDP (Port 3389) access to EC2 instances. With sessions manager, you can access your EC2 instances without enabling port 22 and 3389 in the security group. Additional Resources • Amazon EC2 Security Groups List of TCP and UDP port numbers • Classless Inter-Domain Routing • Working with Session Manager Security API Version 2025-05-13 246 User Guide AWS Support • AWS Firewall Manager Report columns • Status • Region • Security Group Name • Security Group ID • Protocol • From Port • To Port • Association Security Groups – Unrestricted Access Description Checks security groups for rules that allow unrestricted access to a resource. Unrestricted access increases opportunities for malicious activity (hacking, denial-of-service attacks, loss of data). Note This check evaluates only security groups that you create and their inbound rules for IPv4 addresses. Security groups created by AWS Directory Service are ﬂagged as red or yellow, but they don’t pose a security risk and can be excluded. For more information, see the Trusted Advisor FAQ. Check ID 1iG5NDGVre Alert Criteria • Green: A security group rule has a source IP address with a /0 suﬃx for ports 25, 80, or 443. • Yellow: A security group rule has a source IP address with a /0 suﬃx for ports other than 25, 80, or 443 and security group is attached to a resource. Security API Version 2025-05-13 247 AWS Support User Guide • Red: A security group rule has a source IP address with a /0 suﬃx for ports other than 25, 80, or 443 and security group is not attached to a resource. Recommended Action Restrict access to only those IP addresses that require it. To restrict access to a speciﬁc IP address, set the suﬃx to /32 (for example, 192.0.2.10/32). Be sure to delete overly permissive rules after creating rules that are more restrictive. Review and delete unused security groups. You can use AWS Firewall Manager to centrally conﬁgure and manage security groups at scale across AWS accounts, For more information, see the AWS Firewall Manager documentation. Consider using Systems Manager Sessions Manager for SSH (Port 22) and RDP (Port 3389) access to EC2 instances. With sessions manager, you can access your EC2 instances without enabling port 22 and 3389 in the security group. Additional Resources • Amazon EC2 Security Groups • Classless Inter-Domain Routing • Working with Session Manager • AWS Firewall Manager Report columns • Status • Region • Security Group Name • Security Group ID • Protocol • From Port • To Port • IP Range • Association Fault tolerance You can use the following checks for the fault tolerance category. Fault tolerance API Version 2025-05-13 248 User Guide AWS Support Check names • ALB Multi-AZ • Amazon Aurora MySQL cluster backtracking not enabled • Amazon Aurora DB Instance Accessibility • Amazon CloudFront Origin Failover • Amazon Comprehend Endpoint Access Risk • Amazon DocumentDB Single AZ Clusters • Amazon DynamoDB Point-in-time Recovery • Amazon DynamoDB Table Not Included in Backup Plan • Amazon EBS Not Included in AWS Backup Plan • Amazon EBS Snapshots • Amazon EC2 Auto Scaling does not have ELB Health Check Enabled • Amazon EC2 Auto Scaling Group has Capacity Rebalancing Enabled • Amazon EC2 Auto Scaling is not deployed in multiple AZs or does not meet the minimum number of AZs • Amazon EC2 Availability Zone Balance • Amazon EC2 Detailed Monitoring Not Enabled • Amazon ECS AWSLogs driver in blocking mode • Amazon ECS service using a single AZ • Amazon ECS Multi-AZ placement strategy • Amazon EFS No Mount Target Redundancy • Amazon EFS not in AWS Backup Plan • Amazon ElastiCache Multi-AZ clusters • ElastiCache (Redis OSS) Clusters Automatic Backup • Amazon MemoryDB Multi-AZ clusters • Amazon MSK brokers hosting too many partitions • Amazon MSK Cluster Multi-AZ • Amazon OpenSearch Service domains with less than three data nodes • Amazon RDS Backups • Amazon RDS Continuous Backup Not Enabled • Amazon RDS DB clusters have one DB instance Fault tolerance API Version 2025-05-13 249 AWS Support User Guide • Amazon RDS DB clusters with all instances in the same Availability Zone • Amazon RDS DB clusters with all reader instances in the same Availability Zone • Amazon
support-ug-077	support-ug.pdf	77	• Amazon ElastiCache Multi-AZ clusters • ElastiCache (Redis OSS) Clusters Automatic Backup • Amazon MemoryDB Multi-AZ clusters • Amazon MSK brokers hosting too many partitions • Amazon MSK Cluster Multi-AZ • Amazon OpenSearch Service domains with less than three data nodes • Amazon RDS Backups • Amazon RDS Continuous Backup Not Enabled • Amazon RDS DB clusters have one DB instance Fault tolerance API Version 2025-05-13 249 AWS Support User Guide • Amazon RDS DB clusters with all instances in the same Availability Zone • Amazon RDS DB clusters with all reader instances in the same Availability Zone • Amazon RDS DB Instance Enhanced Monitoring not enabled • Amazon RDS DB instances have storage autoscaling turned oﬀ • Amazon RDS DB instances not using Multi-AZ deployment • Amazon RDS DiskQueueDepth • Amazon RDS FreeStorageSpace • Amazon RDS log_output parameter is set to table • Amazon RDS innodb_default_row_format parameter setting is unsafe • Amazon RDS innodb_ﬂush_log_at_trx_commit parameter is not 1 • Amazon RDS max_user_connections parameter is low • Amazon RDS Multi-AZ • Amazon RDS Not In AWS Backup Plan • Amazon RDS Read Replicas are open in writable mode • Amazon RDS resource automated backups is turned oﬀ • Amazon RDS sync_binlog parameter is turned oﬀ • RDS DB Cluster has no Multi-AZ replication enabled • RDS Multi-AZ Standby Instance Not Enabled • Amazon RDS ReplicaLag • Amazon RDS synchronous_commit parameter is turned oﬀ • Amazon Redshift cluster automated snapshots • Amazon Route 53 Deleted Health Checks • Amazon Route 53 Failover Resource Record Sets • Amazon Route 53 High TTL Resource Record Sets • Amazon Route 53 Name Server Delegations • Amazon Route 53 Resolver Endpoint Availability Zone Redundancy • Amazon S3 Bucket Logging • Amazon S3 Bucket Replication Not Enabled • Amazon S3 Bucket Versioning • Application, Network, and Gateway Load Balancers Not Spanning Multiple Availability Zones Fault tolerance API Version 2025-05-13 250 AWS Support User Guide • Auto Scaling available IPs in Subnets • Auto Scaling Group Health Check • Auto Scaling Group Resources • AWS CloudHSM clusters running HSM instances in a single AZ • AWS Direct Connect Location Resiliency • AWS Lambda functions without a dead-letter queue conﬁgured • AWS Lambda On Failure Event Destinations • AWS Lambda VPC-enabled Functions without Multi-AZ Redundancy • AWS Outposts Single Rack deployment • AWS Resilience Hub Application Component check • AWS Resilience Hub policy breached • AWS Resilience Hub resilience scores • AWS Resilience Hub assessment age • AWS Site-to-Site VPN has at least one tunnel in DOWN status • AWS Well-Architected high risk issues for reliability • Classic Load Balancer has no multiple AZs conﬁgured • CLB Connection Draining • ELB Target Imbalance • GWLB - endpoint AZ independence • Load Balancer Optimization • NAT Gateway AZ Independence • Network Firewall endpoint AZ Independence • Network Firewall Multi-AZ • Network Load Balancers Cross Load Balancing • NLB - Internet-facing resource in private subnet • NLB Multi-AZ • Number of AWS Regions in an Incident Manager replication set • Single AZ Application Check • VPC interface endpoint network interfaces in multiple AZs • VPN Tunnel Redundancy Fault tolerance API Version 2025-05-13 251 AWS Support User Guide • ActiveMQ Availability Zone Redundancy • RabbitMQ Availability Zone Redundancy ALB Multi-AZ Description Checks if your Application Load Balancers are conﬁgured to use more than one Availability Zone (AZ). An AZ is a distinct location that is insulated from failures in other zones. Conﬁgure your load balancer in multiple AZs in the same Region to help improve your workload availability. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfprch08 Alert Criteria Yellow: ALB is in a single AZ. Green: ALB has two or more AZs. Recommended Action Make sure that your load balancer is conﬁgured with at least two Availability Zones. For more information, see Availability Zones for your Application Load Balancer. Additional Resources For more information, see the following documentation: • How Elastic Load Balancing works • Regions, Availability Zones, and Local Zones Fault tolerance API Version 2025-05-13 252 User Guide AWS Support Report columns • Status • Region • ALB Name • ALB Rule • ALB ARN • Number of AZs • Last Updated Time Amazon Aurora MySQL cluster backtracking not enabled Description Checks if an Amazon Aurora MySQL cluster has backtracking enabled. Amazon Aurora MySQL cluster backtracking is a feature that allows you to restore an Aurora DB cluster to a previous point in time without creating a new cluster. It enables you to roll back your database to a speciﬁc point
support-ug-078	support-ug.pdf	78	Balancing works • Regions, Availability Zones, and Local Zones Fault tolerance API Version 2025-05-13 252 User Guide AWS Support Report columns • Status • Region • ALB Name • ALB Rule • ALB ARN • Number of AZs • Last Updated Time Amazon Aurora MySQL cluster backtracking not enabled Description Checks if an Amazon Aurora MySQL cluster has backtracking enabled. Amazon Aurora MySQL cluster backtracking is a feature that allows you to restore an Aurora DB cluster to a previous point in time without creating a new cluster. It enables you to roll back your database to a speciﬁc point in time within a retention period, without the need to restore from a snapshot. You can adjust the backtracking time window (hours) in the BacktrackWindowInHours parameter of the AWS Conﬁg rules. For more information, see Backtracking an Aurora DB cluster. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz131 Fault tolerance API Version 2025-05-13 253 AWS Support Source User Guide AWS Config Managed Rule: aurora-mysql-backtracking-enabled Alert Criteria Yellow: Amazon Aurora MySQL clusters backtracking is not enabled. Recommended Action Turn on backtracking for your Amazon Aurora MySQL cluster. For more information, see Backtracking an Aurora DB cluster. Additional Resources Backtracking an Aurora DB cluster Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon Aurora DB Instance Accessibility Description Checks for cases where an Amazon Aurora DB cluster has both private and public instances. When your primary instance fails, a replica can be promoted to a primary instance. If that replica is private, users who have only public access would no longer be able to connect to the database after failover. We recommend that all the DB instances in a cluster have the same accessibility. Check ID xuy7H1avtl Fault tolerance API Version 2025-05-13 254 AWS Support Alert Criteria User Guide Yellow: The instances in an Aurora DB cluster have diﬀerent accessibility (a mix of public and private). Recommended Action Modify the Publicly Accessible setting of the instances in the DB cluster so that they are all either public or private. For details, see the instructions for MySQL instances at Modifying a DB Instance Running the MySQL Database Engine. Additional Resources Fault Tolerance for an Aurora DB Cluster Report columns • Status • Region • Cluster • Public DB Instances • Private DB Instances • Reason Amazon CloudFront Origin Failover Description Checks that an origin group is conﬁgured for distributions that include two origins in Amazon CloudFront. For more information, see Optimizing high availability with CloudFront origin failover. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 255 AWS Support Check ID c18d2gz112 Source User Guide AWS Config Managed Rule: cloudfront-origin-failover-enabled Alert Criteria Yellow: Amazon CloudFront origin failover is not enabled. Recommended Action Make sure that you turn on the origin failover feature for your CloudFront distributions to help ensure high availability of your content delivery to end users. When you turn on this feature, traﬃc is automatically routed to the backup origin server if the primary origin server is unavailable. This minimizes potential downtime and ensures continuous availability of your content. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon Comprehend Endpoint Access Risk Description Checks the AWS Key Management Service (AWS KMS) key permissions for an endpoint where the underlying model was encrypted by using customer managed keys. If the customer managed key is disabled, or the key policy was changed to alter the allowed permissions for Amazon Comprehend, the endpoint availability might be aﬀected. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Fault tolerance API Version 2025-05-13 256 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Cm24dfsM13 Alert Criteria Red: The customer managed key is disabled or the key policy was changed to alter the allowed permissions for Amazon Comprehend access. Recommended Action If the customer managed key was disabled, we recommend that you enable it.
support-ug-079	support-ug.pdf	79	automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Fault tolerance API Version 2025-05-13 256 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Cm24dfsM13 Alert Criteria Red: The customer managed key is disabled or the key policy was changed to alter the allowed permissions for Amazon Comprehend access. Recommended Action If the customer managed key was disabled, we recommend that you enable it. For more information, see Enabling keys. If the key policy was altered and you want to keep using the endpoint, we recommend that you update the AWS KMS key policy. For more information, see Changing a key policy. Additional Resources AWS KMS Permissions Report columns • Status • Region • Endpoint ARN • Model ARN • KMS KeyId • Last Updated Time Amazon DocumentDB Single AZ Clusters Description Checks if there are Amazon DocumentDB clusters conﬁgured as Single-AZ. Running Amazon DocumentDB workloads in a Single-AZ architecture is not suﬃcient for highly critical workloads and it can take up to 10 minutes to recover from a component failure. Fault tolerance API Version 2025-05-13 257 AWS Support User Guide Customers should deploy replica instances in additional availability zones to ensure availability during maintenance, instance failures, component failures, or availability zone failures. Note Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c15vnddn2x Alert Criteria Yellow: Amazon DocumentDB cluster has instances in less than three availability zones. Green: Amazon DocumentDB cluster has instances in three availability zones. Recommended Action If your application requires high availability, modify your DB instance to enable Multi-AZ using replica instances. See Amazon DocumentDB High Availability and Replication Additional Resources Understanding Amazon DocumentDB Cluster Fault Tolerance Regions and Availability Zones Report columns • Status • Region • Availability Zone • DB Cluster Identiﬁer Fault tolerance API Version 2025-05-13 258 AWS Support • DB Cluster ARN • Last Updated Time Amazon DynamoDB Point-in-time Recovery Description User Guide Checks if point-in time-recovery is enabled for your Amazon DynamoDB tables. Point-in time-recovery helps protect your DynamoDB tables from accidental write or delete operations. With point-in time-recovery, you don't have to worry about creating, maintaining, or scheduling on-demand backups. Point-in time-recovery restores tables to any point in time during the last 35 days. DynamoDB maintains incremental backups of your table. For more information, see Point-in-time recovery for DynamoDB. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz138 Source AWS Config Managed Rule: dynamodb-pitr-enabled Alert Criteria Yellow: Point-in-time recovery is not enabled for your DynamoDB tables. Recommended Action Turn on point-in-time recovery in Amazon DynamoDB to continuously back up your table data. For more information, see Point-in-time recovery: How it works. Fault tolerance API Version 2025-05-13 259 User Guide AWS Support Additional Resources Point-in-time recovery for DynamoDB Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon DynamoDB Table Not Included in Backup Plan Description Checks if Amazon DynamoDB tables are part of an AWS Backup plan. AWS Backup provides incremental backups for DynamoDB tables that capture changes made since the last backup. Including DynamoDB tables in an AWS Backup plan helps protect your data from accidental data loss scenarios and automates the backup process. This provides a reliable and scalable backup solution for your DynamoDB tables, helping to ensure that your valuable data is protected and available for recovery as needed. For more information, see Creating backups of DynamoDB tables with AWS Backup Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz107 Fault tolerance API Version 2025-05-13 260 AWS Support Source User Guide AWS Config Managed Rule: dynamodb-in-backup-plan Alert Criteria Yellow: Amazon DynamoDB table is not included in AWS Backup plan. Recommended Action Ensure that your Amazon DynamoDB tables are part of an AWS Backup plan. Additional Resources Scheduled backups
support-ug-080	support-ug.pdf	80	are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz107 Fault tolerance API Version 2025-05-13 260 AWS Support Source User Guide AWS Config Managed Rule: dynamodb-in-backup-plan Alert Criteria Yellow: Amazon DynamoDB table is not included in AWS Backup plan. Recommended Action Ensure that your Amazon DynamoDB tables are part of an AWS Backup plan. Additional Resources Scheduled backups What is AWS Backup? Creating backup plans using the AWS Backup console Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon EBS Not Included in AWS Backup Plan Description Checks if Amazon EBS volumes are present in backup plans for AWS Backup. Include Amazon EBS volumes in an AWS Backup plan to automate regular backups for the data stored on those volumes. This protects you against data loss, makes data management easier, and allows for data restoration when needed. A backup plan helps to ensure that your data is safe and that you're able to meet recovery time and point objectives (RTO/RPO) for your application and services. For more information, see Creating a backup plan Fault tolerance API Version 2025-05-13 261 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz106 Source AWS Config Managed Rule: ebs-in-backup-plan Alert Criteria Yellow: Amazon EBS volume is not included in AWS Backup plan. Recommended Action Make sure that your Amazon EBS volumes are part of an AWS Backup plan. Additional Resources Creating backup plans using the AWS Backup console What is AWS Backup? Getting started 3: Create a scheduled backup Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Fault tolerance API Version 2025-05-13 262 AWS Support Amazon EBS Snapshots Description User Guide Checks the age of the snapshots for your Amazon EBS volumes (either available or in-use). Failures can occur even if Amazon EBS volumes are replicated. Snapshots are persisted toAmazon S3 for durable storage and point-in-time recovery. Check ID H7IgTzjTYb Alert Criteria • Yellow: The most recent volume snapshot is between 7 and 30 days old. • Red: The most recent volume snapshot is more than 30 days old. • Red: The volume does not have a snapshot. Recommended Action Create weekly or monthly snapshots of your volumes. For more information, see Creating an Amazon EBS Snapshot. To automate the creation of EBS snapshots, you can consider using AWS Backup or Amazon Data Lifecycle Manager. Additional Resources Amazon Elastic Block Store (Amazon EBS) Amazon EBS Snapshots AWS Backup Amazon Data Lifecycle Manager Report columns • Status • Region • Volume ID • Volume Name • Snapshot ID Fault tolerance API Version 2025-05-13 263 AWS Support User Guide • Snapshot Name • Snapshot Age • Volume Attachment • Reason Amazon EC2 Auto Scaling does not have ELB Health Check Enabled Description Checks if your Amazon EC2 Auto Scaling groups that are associated with a Classic Load Balancer are using Elastic Load Balancing health checks. The default health checks for an Auto Scaling group are Amazon EC2 status checks only. If an instance fails these status checks, it is marked unhealthy and is terminated. Amazon EC2 Auto Scaling launches a new replacement instance. The Elastic Load Balancing health check periodically monitors Amazon EC2 instances to detect and terminate unhealthy instances and then launch new instances. For more information, see Add Elastic Load Balancing health checks. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz104 Source AWS Config Managed Rule: autoscaling-group-elb-healthcheck-required Alert Criteria Yellow: Amazon EC2 Auto Scaling group attached to Classic Load Balancer has not enabled Elastic Load Balancing health checks. Fault tolerance API Version 2025-05-13 264 AWS Support Recommended Action User Guide Ensure that your Auto Scaling groups that are associated with a Classic Load Balancer use Elastic Load Balancing health checks. Elastic Load Balancing health checks report if the load balancer is healthy and available to handle requests. This ensures high availability for your application. For more information, see Add Elastic
support-ug-081	support-ug.pdf	81	or more resources from your Trusted Advisor results. Check ID c18d2gz104 Source AWS Config Managed Rule: autoscaling-group-elb-healthcheck-required Alert Criteria Yellow: Amazon EC2 Auto Scaling group attached to Classic Load Balancer has not enabled Elastic Load Balancing health checks. Fault tolerance API Version 2025-05-13 264 AWS Support Recommended Action User Guide Ensure that your Auto Scaling groups that are associated with a Classic Load Balancer use Elastic Load Balancing health checks. Elastic Load Balancing health checks report if the load balancer is healthy and available to handle requests. This ensures high availability for your application. For more information, see Add Elastic Load Balancing health checks to an Auto Scaling group Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon EC2 Auto Scaling Group has Capacity Rebalancing Enabled Description Checks if Capacity Rebalancing is enabled for Amazon EC2 Auto Scaling groups that use multiple instance types. Conﬁguring Amazon EC2 Auto Scaling groups with capacity rebalancing helps ensure that Amazon EC2 instances are evenly distributed across Availability Zones, regardless of instance types and purchasing options. It uses a target tracking policy associated with the group, such as CPU utilization or network traﬃc. For more information, see Auto Scaling groups with multiple instance types and purchase options. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Fault tolerance API Version 2025-05-13 265 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID AWS Config c18d2gz103 Source AWS Conﬁg Managed Rule: autoscaling-capacity-rebalancing Alert Criteria Yellow: Amazon EC2 Auto Scaling group capacity rebalancing is not enabled. Recommended Action Ensure that capacity rebalancing is enabled for your Amazon EC2 Auto Scaling groups that use multiple instance types. For more information, see Enable Capacity Rebalancing (console) Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon EC2 Auto Scaling is not deployed in multiple AZs or does not meet the minimum number of AZs Description Checks if the Amazon EC2 Auto Scaling group is deployed in multiple Availability Zones, or the minimum number of Availability Zones speciﬁed. Deploy Amazon EC2 instances in multiple Availability Zones to ensure high availability. Fault tolerance API Version 2025-05-13 266 AWS Support User Guide You can adjust the minimum number of Availability Zones using the minAvailibilityZones parameter in your AWS Conﬁg rules. For more information, see Auto Scaling groups with multiple instance types and purchase options. Check ID c18d2gz101 Source AWS Config Managed Rule: autoscaling-multiple-az Alert Criteria Red: The Amazon EC2 Auto Scaling group doesn't have multiple AZs conﬁgured, or doesn't meet the minimum number of AZs speciﬁed. Recommended Action Make sure that your Amazon EC2 Auto Scaling group is conﬁgured with multiple AZs. Deploy Amazon EC2 instances in multiple Availability Zones to ensure high availability. Additional Resources Create an Auto Scaling group using a launch template Create an Auto Scaling group using a launch conﬁguration Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon EC2 Availability Zone Balance Description Checks the distribution of Amazon Elastic Compute Cloud (Amazon EC2) instances across Availability Zones in a Region. Fault tolerance API Version 2025-05-13 267 AWS Support User Guide Availability Zones are distinct locations that are insulated from failures in other Availability Zones. This allows inexpensive, low-latency network connectivity between Availability Zones in the same Region. By launching instances in multiple Availability Zones in the same Region, you can help protect your applications from a single point of failure. Check ID wuy7G1zxql Alert Criteria • Yellow: The Region has instances in multiple zones, but the distribution is uneven (the diﬀerence between the highest and lowest instance counts in utilized Availability Zones is greater than 20%). • Red: The Region has instances only in a single Availability Zone. Recommended Action Balance your Amazon EC2 instances evenly across multiple Availability Zones. You can do this by launching instances manually or by using Auto Scaling to do it automatically. For more information, see Launch Your Instance and Load Balance Your Auto Scaling Group. Additional Resources • Amazon EC2 Auto Scaling User Guide • Placement groups for your Amazon EC2 instances • Amazon EC2 instance types Report columns • Status • Region • Zone a Instances • Zone b Instances • Zone c Instances • Zone e Instances • Zone f Instances • Reason Fault tolerance API Version 2025-05-13 268 AWS Support User Guide Amazon EC2 Detailed Monitoring Not Enabled Description Checks if detailed monitoring is enabled for yourAmazon EC2 instances. Amazon EC2 detailed monitoring provides
support-ug-082	support-ug.pdf	82	to do it automatically. For more information, see Launch Your Instance and Load Balance Your Auto Scaling Group. Additional Resources • Amazon EC2 Auto Scaling User Guide • Placement groups for your Amazon EC2 instances • Amazon EC2 instance types Report columns • Status • Region • Zone a Instances • Zone b Instances • Zone c Instances • Zone e Instances • Zone f Instances • Reason Fault tolerance API Version 2025-05-13 268 AWS Support User Guide Amazon EC2 Detailed Monitoring Not Enabled Description Checks if detailed monitoring is enabled for yourAmazon EC2 instances. Amazon EC2 detailed monitoring provides more frequent metrics, published at one-minute intervals, instead of the ﬁve-minute intervals used in Amazon EC2 basic monitoring. Enabling detailed monitoring for Amazon EC2 helps you better manage your Amazon EC2 resources, so that you can ﬁnd trends and take action faster. For more information, see Basic monitoring and detailed monitoring. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID AWS Config c18d2gz144 Source AWS Conﬁg Managed Rule: ec2-instance-detailed-monitoring-enabled Alert Criteria Yellow: Detailed monitoring is not enabled for Amazon EC2 instances. Recommended Action Turn on detailed monitoring for your Amazon EC2 instances to increase the frequency at which Amazon EC2 metric data is published to Amazon CloudWatch (from 5-minute to 1-minute intervals). Report columns • Status • Region Fault tolerance API Version 2025-05-13 269 AWS Support • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon ECS AWSLogs driver in blocking mode Description Checks for Amazon ECS task deﬁnitions conﬁgured with the AWSLogs logging driver in blocking mode. A driver conﬁgured in the blocking mode risks system availability. Note Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dvkm4z6b Alert Criteria Yellow: The awslogs driver logging conﬁguration parameter mode is set to blocking or missing. A missing mode parameter indicates a default blocking conﬁgurations. Green: Amazon ECS task deﬁnition is not using the awslogs driver or the awslogs driver is conﬁgured in non-blocking mode. Recommended Action To mitigate the availability risk, consider changing the task deﬁnition AWSLogs driver conﬁguration from blocking to non-blocking. With non-blocking mode, you will have to set a Fault tolerance API Version 2025-05-13 270 AWS Support User Guide value for the max-buﬀer-size parameter. For more information and guidance on conﬁguration parameters, see . See Preventing log loss with non-blocking mode in the AWSLogs container log driver Additional Resources Using the AWS logs log driver Choosing container logging options to avoid backpressure Preventing log loss with non-blocking mode in the AWSLogs container log driver Report columns • Status • Region • Task Deﬁnition ARN • Container Deﬁnition Names • Last Updated Time Amazon ECS service using a single AZ Description Checks that your service conﬁguration uses a single Availability Zone (AZ). An AZ is a distinct location that is insulated from failures in other zones. This supports inexpensive, low-latency network connectivity between AZs in the same AWS Region. By launching instances in multiple AZs in the same Region, you can help protect your applications from a single point of failure. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 271 User Guide AWS Support Check ID c1z7dfpz01 Alert Criteria • Yellow: An Amazon ECS service is running all tasks in a single AZ. • Green: An Amazon ECS service is running tasks in at least two diﬀerent AZs. Recommended Action Create at least one more task for the service in a diﬀerent AZ. Additional Resources Amazon ECS capacity and availability Report columns • Status • Region • ECS Cluster Name/ECS Service Name • Number of Availability Zones • Last Updated Time Amazon ECS Multi-AZ placement strategy Description Checks that your Amazon ECS service uses the spread placement strategy based on Availability Zone (AZ). This strategy distributes tasks across Availability Zones in the same AWS Region and can help protect your applications from a single point of failure. For tasks that run as part of an Amazon ECS
support-ug-083	support-ug.pdf	83	AZs. Recommended Action Create at least one more task for the service in a diﬀerent AZ. Additional Resources Amazon ECS capacity and availability Report columns • Status • Region • ECS Cluster Name/ECS Service Name • Number of Availability Zones • Last Updated Time Amazon ECS Multi-AZ placement strategy Description Checks that your Amazon ECS service uses the spread placement strategy based on Availability Zone (AZ). This strategy distributes tasks across Availability Zones in the same AWS Region and can help protect your applications from a single point of failure. For tasks that run as part of an Amazon ECS service, spread is the default task placement strategy. This check also veriﬁes that spread is the ﬁrst or only strategy in your list of enabled placement strategies. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Fault tolerance API Version 2025-05-13 272 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1z7dfpz02 Alert Criteria • Yellow: Spread by availability zone is disabled or isn't the ﬁrst strategy in your list of enabled placement strategies for your Amazon ECS service. • Green: Spread by availability zone is the ﬁrst strategy in your list of enabled placement strategies or the only placement strategy enabled for your Amazon ECS service. Recommended Action Enable the spread task placement strategy to distribute tasks across multiple AZs. Verify that spread by availability zone is the ﬁrst strategy for all enabled task placement strategies or the only strategy used. If you choose to manage AZ placement, you can use a mirrored service in another AZ to mitigate these risks. Additional Resources Amazon ECS task placement strategies Report columns • Status • Region • ECS Cluster Name/ECS Service Name • Spread Task Placement Strategy Enabled and Applied Correctly • Last Updated Time Amazon EFS No Mount Target Redundancy Description Checks if mount targets exist in multiple Availability Zones for an Amazon EFS ﬁle system. Fault tolerance API Version 2025-05-13 273 AWS Support User Guide An Availability Zone is a distinct location that is insulated from failures in other zones. By creating mount targets in multiple geographically separated Availability Zones within an AWS Region, you can achieve the highest levels of availability and durability for your Amazon EFS ﬁle systems. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfprch01 Alert Criteria • Yellow: File system has 1 mount target created in a single Availability Zone. Green: File system has 2 or more mount targets created in multiple Availability Zones. Recommended Action For EFS ﬁle systems using One Zone storage classes, we recommend you create new ﬁle systems that use Standard storage classes by restoring a backup to a new ﬁle system. Then create mount targets in multiple Availability Zones. For EFS ﬁle systems using Standard storage classes, we recommend you create mount targets in multiple Availability Zones. Additional Resources • Managing mount targets using the Amazon EFS console • Amazon EFS Quotas and Limits Report columns • Status • Region • EFS File System ID • Number of mount targets Fault tolerance API Version 2025-05-13 274 AWS Support • Number of AZs • Last Updated Time Amazon EFS not in AWS Backup Plan Description User Guide Checks if Amazon EFS ﬁle systems are included in backup plans with AWS Backup. AWS Backup is a uniﬁed backup service designed to simplify the creation, migration, restoration, and deletion of backups, while providing improved reporting and auditing. For more information, see Backing up your Amazon EFS ﬁle systems. Check ID c18d2gz117 Source AWS Config Managed Rule: EFS_IN_BACKUP_PLAN Alert Criteria Red: Amazon EFS are not included in AWS Backup plan. Recommended Action Make sure that your Amazon EFS ﬁle systems are included in your AWS Backup plan to protect against accidental data loss or data corruption. Additional Resources Backing up your Amazon EFS ﬁle systems Amazon EFS Backup and Restore using AWS Backup. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Fault tolerance API Version 2025-05-13 275 AWS Support User Guide Amazon ElastiCache Multi-AZ clusters Description Checks for ElastiCache clusters that deploy in a single Availability Zone (AZ). This check alerts you if Multi-AZ is inactive in a cluster. Deployments in multiple AZs enhance ElastiCache cluster availability by asynchronously replicating to read-only
support-ug-084	support-ug.pdf	84	your AWS Backup plan to protect against accidental data loss or data corruption. Additional Resources Backing up your Amazon EFS ﬁle systems Amazon EFS Backup and Restore using AWS Backup. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Fault tolerance API Version 2025-05-13 275 AWS Support User Guide Amazon ElastiCache Multi-AZ clusters Description Checks for ElastiCache clusters that deploy in a single Availability Zone (AZ). This check alerts you if Multi-AZ is inactive in a cluster. Deployments in multiple AZs enhance ElastiCache cluster availability by asynchronously replicating to read-only replicas in a diﬀerent AZ. When planned cluster maintenance occurs, or a primary node is unavailable, ElastiCache automatically promotes a replica to primary. This failover allows cluster write operations to resume, and doesn't require an administrator to intervene. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID ECHdfsQ402 Alert Criteria • Green: Multi-AZ is active in the cluster. • Yellow: Multi-AZ is inactive in the cluster. Recommended Action Create at least one replica per shard, in an AZ that is diﬀerent than the primary. Additional Resources For more information, see Minimizing downtime in ElastiCache (Redis OSS) with Multi-AZ. Report columns • Status • Region • Cluster Name Fault tolerance API Version 2025-05-13 276 AWS Support • Last Updated Time User Guide ElastiCache (Redis OSS) Clusters Automatic Backup Description Checks if the Amazon ElastiCache (Redis OSS) clusters have automatic backup turned on and if the snapshot retention period is above the speciﬁed or 15 day default limit. When automatic backups are enabled, ElastiCache creates a backup of the cluster on a daily basis. You can specify your desired snapshot retention limit using the snapshotRetentionPeriod parameters of your AWS Conﬁg rules. For more information, see Backup and restore for ElastiCache (Redis OSS). Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz178 Source AWS Config Managed Rule: elasticache-redis-cluster-automatic-backup- check Alert Criteria Red: Amazon ElastiCache (Redis OSS) clusters do not have automatic backup turned on or the snapshot retention period is below the limit. Recommended Action Make sure that Amazon ElastiCache (Redis OSS) clusters have automatic backup turned on and the snapshot retention period is above the speciﬁed or 15 day default limit. Automatic backups Fault tolerance API Version 2025-05-13 277 AWS Support User Guide can help guard against data loss. In the event of a failure, you can create a new cluster, restoring your data from the most recent backup. For more information, see Backup and restore for ElastiCache (Redis OSS). Additional Resources For more information, see Scheduling automatic backups. Report columns • Status • Region • Cluster Name • Last Updated Time Amazon MemoryDB Multi-AZ clusters Description Checks for MemoryDB clusters that deploy in a single Availability Zone (AZ). This check alerts you if Multi-AZ is inactive in a cluster. Deployments in multiple AZs enhance MemoryDB cluster availability by asynchronously replicating to read-only replicas in a diﬀerent AZ. When planned cluster maintenance occurs, or a primary node is unavailable, MemoryDB automatically promotes a replica to primary. This failover allows cluster write operations to resume, and doesn't require an administrator to intervene. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID MDBdfsQ401 Fault tolerance API Version 2025-05-13 278 User Guide AWS Support Alert Criteria • Green: Multi-AZ is active in the cluster. • Yellow: Multi-AZ is inactive in the cluster. Recommended Action Create at least one replica per shard, in an AZ that is diﬀerent than the primary. Additional Resources For more information, see Minimizing downtime in MemoryDB with Multi-AZ. Report columns • Status • Region • Cluster Name • Last Updated Time Amazon MSK brokers hosting too many partitions Description Checks that the brokers of a Managed Streaming for Kafka (MSK) Cluster do not have more than the recommended number of partitions assigned. Check ID Cmsvnj8vf1 Alert Criteria • Red: Your MSK broker has reached or exceeded 100% of the recommended maximum partition limit • Yellow: Your MSK has reached
support-ug-085	support-ug.pdf	85	Action Create at least one replica per shard, in an AZ that is diﬀerent than the primary. Additional Resources For more information, see Minimizing downtime in MemoryDB with Multi-AZ. Report columns • Status • Region • Cluster Name • Last Updated Time Amazon MSK brokers hosting too many partitions Description Checks that the brokers of a Managed Streaming for Kafka (MSK) Cluster do not have more than the recommended number of partitions assigned. Check ID Cmsvnj8vf1 Alert Criteria • Red: Your MSK broker has reached or exceeded 100% of the recommended maximum partition limit • Yellow: Your MSK has reached 80% of the recommended maximum partition limit Recommended Action Follow the MSK recommended best practices to scale your MSK Cluster or delete any unused partitions. Additional Resources • Right-sizing your Cluster Fault tolerance API Version 2025-05-13 279 User Guide AWS Support Report columns • Status • Region • Cluster ARN • Broker ID • Partition Count Amazon MSK Cluster Multi-AZ Description Checks the number of Availability Zones (AZs) for your Amazon MSK provisioned cluster. The Amazon MSK cluster is formed of several brokers that work together and distribute the data and load. Production might be interrupted during maintenance or broker issues in a 2-AZ cluster. Check ID 90046ff5b5 Alert Criteria • Yellow: The Amazon MSK cluster is provisioned with brokers in only two AZs • Green: The Amazon MSK cluster is provisioned with brokers across three or more AZs Recommended Action To increase availability of the cluster, you can create another cluster in a 3 AZs setup. Then migrate the existing cluster to the new cluster that you created. You can use Amazon MSK replication for this migration. Additional Resources Amazon MSK high availability Amazon MSK migration Report columns • Status • Region • MSK Cluster ARN Fault tolerance API Version 2025-05-13 280 AWS Support • Number of AZs • Last Updated Time User Guide Amazon OpenSearch Service domains with less than three data nodes Description Checks if Amazon OpenSearch Service domains are conﬁgured with at least three data nodes and ZoneAwarenessEnabled is true. With ZoneAwarenessEnabled enabled, Amazon OpenSearch Service ensures that each primary shard and its corresponding replica are allocated in diﬀerent Availability Zones. For more information, see Conﬁguring a multi-AZ domain in Amazon OpenSearch Service. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz183 Source AWS Config Managed Rule: opensearch-data-node-fault-tolerance Alert Criteria Yellow: Amazon OpenSearch Service domains are conﬁgured with less than three data nodes. Recommended Action Make sure that Amazon OpenSearch Service domains are conﬁgured with a minimum of three data nodes. Conﬁgure a multi-AZ domain to enhance the availability of the Amazon OpenSearch Service cluster by allocating nodes and replicating data across three Availability Zones within the same Region. This prevents data loss and minimizes downtime in the event of node or data center (AZ) failure. Fault tolerance API Version 2025-05-13 281 AWS Support User Guide For more information, see Increase availability for Amazon OpenSearch Service by deploying in three Availability Zones. Additional Resources • Increase availability for Amazon OpenSearch Service by deploying in three Availability Zones Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon RDS Backups Description Checks for automated backups of Amazon RDS DB instances. By default, backups are enabled with a retention period of one day. Backups reduce the risk of unexpected data loss and allow for point-in-time recovery. Check ID opQPADkZvH Alert Criteria Red: A DB instance has the backup retention period set to 0 days. Recommended Action Set the retention period for the automated DB instance backup to 1 to 35 days as appropriate to the requirements of your application. See Working With Automated Backups. Additional Resources Getting Started with Amazon RDS Report columns • Status • Region/AZ Fault tolerance API Version 2025-05-13 282 AWS Support • DB Instance • VPC ID • Backup Retention Period Amazon RDS Continuous Backup Not Enabled Description User Guide Checks if an Amazon RDS instance is enabled with automated backups using Amazon RDS or with continuous backups of AWS Backup. Continuous backups reduce the risk of unexpected data loss and allow for point-in-time recovery. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID 44fde09ab5 Alert Criteria • Red:
support-ug-086	support-ug.pdf	86	Enabled Description User Guide Checks if an Amazon RDS instance is enabled with automated backups using Amazon RDS or with continuous backups of AWS Backup. Continuous backups reduce the risk of unexpected data loss and allow for point-in-time recovery. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID 44fde09ab5 Alert Criteria • Red: The instance doesn't have automated backup enabled in Amazon RDS or continuous backup in AWS Backup. • Red: MySQL versions below 5.6 don't support automated or continuous backup. To provide resiliency, ﬁrst upgrade the database version and then enable automated or continuous backup. • Green: The instance has automated backup enabled in Amazon RDS. • Green: The instance has continuous backup enabled in AWS Backup. Recommended Action Make sure that Amazon RDS instances have automated backup conﬁgured either by setting a retention period greater than 0 in Amazon RDS or by creating a continuous backup plan using AWS Backup. Fault tolerance API Version 2025-05-13 283 AWS Support Additional Resources • Getting Started with Amazon RDS • Managing automated backups • Introduction to backups • Continuous backups and point-in-time restore (PITR) • AWS Backup feature availability User Guide Report columns • Status • Region • DB Instance Identiﬁer • DB Instance ARN • Deployment Type • Backup Type • Reason • Last Updated Time Amazon RDS DB clusters have one DB instance Description Add at least another DB instance to the DB cluster to improve availability and performance. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the Fault tolerance API Version 2025-05-13 284 AWS Support User Guide recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt011 Alert Criteria Yellow: DB clusters have only one DB instance. Recommended Action Add a reader DB instance to the DB cluster. Additional Resources In the current conﬁguration, one DB instance is used for both read and write operations. You can add another DB instance to allow read redistribution and a failover option. For more information, see High availability for Amazon Aurora. Report columns • Status • Region • Resource • Engine Name • DB Instance Class • Last Updated Time Amazon RDS DB clusters with all instances in the same Availability Zone Description The DB clusters are currently in a single Availability Zone. Use multiple Availability Zones to improve the availability. Fault tolerance API Version 2025-05-13 285 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt007 Alert Criteria Yellow: DB clusters have all the instances in the same Availability Zone. Recommended Action Add the DB instances to multiple Availability Zones in your DB cluster. Additional Resources We recommend that you add the DB instances to multiple Availability Zones in a DB cluster. Adding DB instances to multiple Availability Zones improvesthe availability of your DB cluster. For more information, see High availability for Amazon Aurora. Report columns • Status Fault tolerance API Version 2025-05-13 286 AWS Support • Region • Resource • Engine Name • Last Updated Time User Guide Amazon RDS DB clusters with all reader instances in the same Availability Zone Description Your DB cluster has all
support-ug-087	support-ug.pdf	87	Availability Zone. Recommended Action Add the DB instances to multiple Availability Zones in your DB cluster. Additional Resources We recommend that you add the DB instances to multiple Availability Zones in a DB cluster. Adding DB instances to multiple Availability Zones improvesthe availability of your DB cluster. For more information, see High availability for Amazon Aurora. Report columns • Status Fault tolerance API Version 2025-05-13 286 AWS Support • Region • Resource • Engine Name • Last Updated Time User Guide Amazon RDS DB clusters with all reader instances in the same Availability Zone Description Your DB cluster has all the reader instances in the same Availability Zone. We recommend that you distribute the Reader instances across multiple Availability Zones in your DB cluster. Distribution increases the availability of the database, and improves the response time by reducing network latency between clients and the database. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt018 Fault tolerance API Version 2025-05-13 287 AWS Support Alert Criteria User Guide Red: DB clusters have the reader instances in the same Availability Zone. Recommended Action Distribute the reader instances across multiple Availability Zones. Additional Resources Availability Zones (AZs) are locations that are distinct from each other to provide isolation in case of outages within each AWS Region. We recommend that you distribute the primary instance and reader instances in your DB cluster across multiple AZs to improve the availability of your DB cluster. You can create a Multi-AZ cluster using the AWS Management Console, AWS CLI, or Amazon RDS API when you create the cluster. You can modify the existing Aurora cluster to a Multi-AZ cluster by adding a new reader instance and specifying a diﬀerent AZ. For more information, see High availability for Amazon Aurora. Report columns • Status • Region • Resource • Engine Name • Last Updated Time Amazon RDS DB Instance Enhanced Monitoring not enabled Description Checks if your Amazon RDS DB instances have Enhanced Monitoring enabled. Amazon RDS Enhanced Monitoring provides metrics in real time for the operating system (OS) that your DB instance runs on. All system metrics and process information for your Amazon RDS DB instances can be view on the Amazon RDS console. And, you can customize the dashboard. With Enhanced Monitoring, you have visibility of your Amazon RDS instance operation status in near real time, allowing you to respond to operational issues faster. You can specify your desired monitoring interval using the monitoringInterval parameter of your AWS Conﬁg rules. Fault tolerance API Version 2025-05-13 288 AWS Support User Guide For more information, see Overview of Enhanced Monitoring and OS metrics in Enhanced Monitoring. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz158 Source AWS Config Managed Rule: rds-enhanced-monitoring-enabled Alert Criteria Yellow: Your Amazon RDS DB instances don't have Enhanced Monitoring enabled or are not conﬁgured with the desired interval. Recommended Action Enable Enhanced Monitoring for your Amazon RDS DB instances to improve the visibility of your Amazon RDS instance operation status. For more information, see Monitoring OS metrics with Enhanced Monitoring. Additional Resources OS metrics in Enhanced Monitoring Report columns • Status • Region • Resource • AWS Conﬁg Rule Fault tolerance API Version 2025-05-13 289 AWS Support • Input Parameters • Last Updated Time User Guide Amazon RDS DB instances have storage autoscaling turned oﬀ Description Amazon RDS storage autoscaling isn't turned on for your DB instance. When there is an increase in the database workload, RDS Storage autoscaling automatically scales the storage capacity with zero downtime. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or
support-ug-088	support-ug.pdf	88	API Version 2025-05-13 289 AWS Support • Input Parameters • Last Updated Time User Guide Amazon RDS DB instances have storage autoscaling turned oﬀ Description Amazon RDS storage autoscaling isn't turned on for your DB instance. When there is an increase in the database workload, RDS Storage autoscaling automatically scales the storage capacity with zero downtime. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt013 Alert Criteria Red: DB instances don't have storage autoscaling turned on. Fault tolerance API Version 2025-05-13 290 AWS Support Recommended Action User Guide Turn on Amazon RDS storage autoscaling with a speciﬁed maximum storage threshold. Additional Resources Amazon RDS storage autoscaling automatically scales storage capacity with zero downtime when the database workload increases. Storage autoscaling monitors the storage usage and automatically scales up the capacity when the usage is close to the provisioned storage capacity. You can specify a maximum limit on the storage that Amazon RDS can allocate to the DB instance. There is no additional cost for storage autoscaling. You pay only for the Amazon RDS resources that are allocated to your DB instance. We recommend that you turn on Amazon RDS storage autoscaling. For more information, see Managing capacity automatically with Amazon RDS storage autoscaling. Report columns • Status • Region • Resource • Recommended Value • Engine Name • Last Updated Time Amazon RDS DB instances not using Multi-AZ deployment Description We recommend that you use Multi-AZ deployment. The Multi-AZ deployments enhance the availability and durability of the DB instance. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Fault tolerance API Version 2025-05-13 291 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt019 Alert Criteria Yellow: DB instances aren't using Multi-AZ deployment. Recommended Action Set up Multi-AZ for the impacted DB instances. Additional Resources In an Amazon RDS Multi-AZ deployment, Amazon RDS automatically creates a primary database instance and replicates the data to an instance in a diﬀerent availability zone. When it detects a failure, Amazon RDS automatically fails over to a standby instance without manual intervention. For more information, see Pricing. Report columns • Status • Region • Resource Fault tolerance API Version 2025-05-13 292 AWS Support • Engine Name • Last Updated Time Amazon RDS DiskQueueDepth Description User Guide Checks to see if the CloudWatch metric DiskQueueDepth shows that number of queued writes to the RDS Instance database storage has grown to a level where an operational investigation should be suggested. Check ID Cmsvnj8db3 Alert Criteria • Red: DiskQueueDepth CloudWatch metric has exceeded 10 • Yellow: DiskQueueDepth CloudWatch metric is greater than 5 but less than or equal to 10 • Green: DiskQueueDepth CloudWatch metric is less than or equal to 5 Recommended Action Consider moving to instances and storage volumes that support the read/write characteristics. Report columns • Status • Region • DB Instance ARN • DiskQueueDepth Metric Amazon RDS FreeStorageSpace Description Checks to see if the FreeStorageSpace CloudWatch metric for an RDS database instance has decreased below an operationally reasonable threshold. Check ID Cmsvnj8db2 Fault tolerance API Version 2025-05-13 293 AWS Support Alert Criteria User Guide • Red: FreeStorageSpace has less than 10% of total capacity • Yellow: FreeStorageSpace is between 10% and 20% of total capacity • Green: FreeStorageSpace is more than 20% of total capacity Recommended Action Scale up the storage space for the RDS database instance
support-ug-089	support-ug.pdf	89	that support the read/write characteristics. Report columns • Status • Region • DB Instance ARN • DiskQueueDepth Metric Amazon RDS FreeStorageSpace Description Checks to see if the FreeStorageSpace CloudWatch metric for an RDS database instance has decreased below an operationally reasonable threshold. Check ID Cmsvnj8db2 Fault tolerance API Version 2025-05-13 293 AWS Support Alert Criteria User Guide • Red: FreeStorageSpace has less than 10% of total capacity • Yellow: FreeStorageSpace is between 10% and 20% of total capacity • Green: FreeStorageSpace is more than 20% of total capacity Recommended Action Scale up the storage space for the RDS database instance that is running low on free storage using the Amazon RDS Management Console, Amazon RDS API or AWS Command Line Interface. Report columns • Status • Region • DB Instance ARN • FreeStorageSpace Metric (MB) • DB Instance Allocated Storage (MB) • DB Instance Storage Used Percent Amazon RDS log_output parameter is set to table Description When log_output is set to TABLE, more storage is used than when log_output is set to FILE. We recommend that you set the parameter to FILE, to avoid reaching the storage size limit. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 294 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt023 Alert Criteria Yellow: DB parameter groups have log_output parameter set to TABLE. Recommended Action Set the log_output parameter value to FILE in your DB parameter groups. Additional Resources For more information, see MySQL database log ﬁles. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Fault tolerance API Version 2025-05-13 295 AWS Support User Guide Amazon RDS innodb_default_row_format parameter setting is unsafe Description Your DB instance encounters a known issue: A table created in a MySQL version lower than 8.0.26 with the row_format set to COMPACT or REDUNDANT is inaccessible and unrecoverable when the index exceeds 767 bytes. We recommend that you set the innodb_default_row_format parameter value to DYNAMIC. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt036 Alert Criteria Red: DB parameter groups have an unsafe setting for the innodb_default_row_format parameter. Fault tolerance API Version 2025-05-13 296 AWS Support Recommended Action User Guide Set the innodb_default_row_format parameter to DYNAMIC. Additional Resources When a table is created with MySQL version lower than 8.0.26 with row_format set to COMPACT or REDUNDANT, creating indexes with a key preﬁx shorter than 767 bytes isn't enforced. After the database restarts, these tables can't be accessed or recovered. For more information, see Changes in MySQL 8.0.26 (2021-07-20, General Availability)n on the MySQL documentation website. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS innodb_ﬂush_log_at_trx_commit parameter is not 1 Description The value of the innodb_ﬂush_log_at_trx_commit parameter of your DB instance isn't a safe value. This parameter controls the persistence of commit operations to disk. We recommend that you set the innodb_ﬂush_log_at_trx_commit parameter to 1. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 297 AWS Support
support-ug-090	support-ug.pdf	90	is not 1 Description The value of the innodb_ﬂush_log_at_trx_commit parameter of your DB instance isn't a safe value. This parameter controls the persistence of commit operations to disk. We recommend that you set the innodb_ﬂush_log_at_trx_commit parameter to 1. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 297 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt030 Alert Criteria Yellow: DB parameter groups have innodb_ﬂush_log_at_trx_commit set to other than 1. Recommended Action Set the innodb_ﬂush_log_at_trx_commit parameter value to 1 Additional Resources The database transaction is durable when the log buﬀer is saved to the durable storage. However, saving to the disk impacts performance. Depending on the value set for innodb_ﬂush_log_at_trx_commit parameter, the behavior of how logs are written and saved to the disk can vary. • When the parameter value is 1, the logs are written and saved to the disk after each committed transaction. • When the parameter value is 0, the logs are written and saved to the disk once per second. • When the parameter value is 2, the logs are written after each transaction is committed and saved to the disk once per second. The data moves from the InnoDB memory buﬀer to the operating system's cache which is also in the memory. Note When the parameter value is not 1, InnoDB doesn't assure ACID properties. The recent transactions for the last second may be lost when the database crashes. Fault tolerance API Version 2025-05-13 298 AWS Support User Guide For more information, see Best practices for conﬁguring parameters for Amazon RDS for MySQL, part 1: Parameters related to performance. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS max_user_connections parameter is low Description Your DB instance has a low value for the maximum number of simultaneous connections for each database account. We recommend setting the max_user_connections parameter to a number greater than 5. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. Fault tolerance API Version 2025-05-13 299 AWS Support User Guide If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt034 Alert Criteria Yellow: DB parameter groups have max_user_connections misconﬁgured. Recommended Action Increase the value of the max_user_connections parameter to a number greater than 5. Additional Resources The max_user_connections setting controls the maximum number of simultaneous connections allowed for a MySQL user account. Reaching this connection limit cause failures in the Amazon RDS instance administration operations, such as backup, patching, and parameters changes. For more information, see Setting Account Resource Limits on the MySQL documentation website. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS Multi-AZ Description Checks for DB instances that are deployed in a single Availability Zone (AZ). Multi-AZ deployments enhance database availability by synchronously replicating to a standby instance in a diﬀerent Availability Zone. During planned database maintenance, or the failure Fault tolerance API Version 2025-05-13 300 AWS Support User Guide of a DB instance or Availability Zone, Amazon RDS automatically fails over to the standby. This failover allows database operations to resume quickly without administrative intervention. Because Amazon RDS does not support Multi-AZ deployment for Microsoft SQL Server, this check does not examine SQL Server instances. Check ID f2iK5R6Dep Alert Criteria Yellow: A DB instance is deployed in a single Availability Zone. Recommended Action If your
support-ug-091	support-ug.pdf	91	Multi-AZ deployments enhance database availability by synchronously replicating to a standby instance in a diﬀerent Availability Zone. During planned database maintenance, or the failure Fault tolerance API Version 2025-05-13 300 AWS Support User Guide of a DB instance or Availability Zone, Amazon RDS automatically fails over to the standby. This failover allows database operations to resume quickly without administrative intervention. Because Amazon RDS does not support Multi-AZ deployment for Microsoft SQL Server, this check does not examine SQL Server instances. Check ID f2iK5R6Dep Alert Criteria Yellow: A DB instance is deployed in a single Availability Zone. Recommended Action If your application requires high availability, modify your DB instance to enable Multi-AZ deployment. See High Availability (Multi-AZ). Additional Resources Regions and Availability Zones Report columns • Status • Region/AZ • DB Instance • VPC ID • Multi-AZ Amazon RDS Not In AWS Backup Plan Description Checks if your Amazon RDS DB instances are included in a backup plan in AWS Backup. AWS Backup is a fully managed backup service that makes it easy to centralize and automate backing up data across AWS services. Including your Amazon RDS DB instance in a backup plan is important for regulatory compliance obligations, disaster recovery, business policies for data protection, and business continuity goals. Fault tolerance API Version 2025-05-13 301 AWS Support User Guide For more information, see What is AWS Backup?. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz159 Source AWS Config Managed Rule: rds-in-backup-plan Alert Criteria Yellow: An Amazon RDS DB instance is not included in a backup plan with AWS Backup. Recommended Action Include your Amazon RDS DB instances in a backup plan with AWS Backup. For more information, see Amazon RDS Backup and Restore Using AWS Backup. Additional Resources Assigning resources to a backup plan Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Fault tolerance API Version 2025-05-13 302 AWS Support User Guide Amazon RDS Read Replicas are open in writable mode Description Your DB instance has a read replica in writable mode, which allows updates from clients. We recommend that you set the the read_only parameter to TrueIfReplica so that the read replicas isn't in writable mode. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt035 Alert Criteria Yellow: DB parameter groups turn on writable mode for the read replicas. Recommended Action Set the read_only parameter value to TrueIfReplica. Fault tolerance API Version 2025-05-13 303 AWS Support Additional Resources User Guide The read_only parameter controls the write permission from the clients to a database instance. The default value for this parameter is TrueIfReplica. For a replica instance, TrueIfReplica sets the read_only value to ON (1) and disables any write activity from the clients. For a master/ writer instance, TrueIfReplica sets the value to OFF (0) and enables the write activity from the clients for the instance. When the read replica is opened in writable mode, the data stored in this instance may diverge from the primary instance which causes replication errors. For more information, see Best practices for conﬁguring parameters for Amazon RDS for MySQL, part 2: Parameters related to replication on the MySQL documentation website. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS resource automated backups is turned oﬀ Description Automated backups are disabled on your DB resources. Automated backups enable point-in- time recovery of your DB instance. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor
support-ug-092	support-ug.pdf	92	documentation website. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Amazon RDS resource automated backups is turned oﬀ Description Automated backups are disabled on your DB resources. Automated backups enable point-in- time recovery of your DB instance. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 304 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt001 Alert Criteria Red: Amazon RDS resources don't have automated backups turned on Recommended Action Turn on automated backups with a retention period of up to 14 days. Additional Resources Automated backups enable point-in-time recovery of your DB instances. We recommend turning on automated backups. When you turn on automated backups for a DB instance, Amazon RDS automatically performs a full backup of your data daily during your preferred backup window. The backup captures transaction logs when there are updates to your DB instance. You get backup storage up to the storage size of your DB instance at no additional cost. For more information, see the following resources: • Enabling automated backups • Demystifying Amazon RDS backup storage costs Report columns • Status • Region • Resource • Recommended Value Fault tolerance API Version 2025-05-13 305 AWS Support • Engine Name • Last Updated Time User Guide Amazon RDS sync_binlog parameter is turned oﬀ Description The synchronization of the binary log to disk isn't enforced before the transaction commits are acknowledged in your DB instance. We recommend that you set the sync_binlog parameter value to 1. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt031 Alert Criteria Yellow: DB parameter groups have synchronous binary logging turned oﬀ. Fault tolerance API Version 2025-05-13 306 AWS Support Recommended Action Set the sync_binlog parameter to 1. Additional Resources User Guide The sync_binlog parameter controls how MySQL pushes the binary log to disk. When the value of this parameter is set to 1, it turns on binary log synchronization to disk before transactions are committed. When the value of this parameter is set to 0, it turns oﬀ the binary log synchronization to the disk. Typically, MySQL server depends on the operating system to push the binary log to disk regularly similar to other ﬁles. The sync_binlog parameter value set to 0 can enhance the performance. However, during a power failure or an operating system crash, the server loses all the committed transactions that weren't synchronized to the binary logs. For more information, see Best practices for conﬁguring parameters for Amazon RDS for MySQL, part 2: Parameters related to replication. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time RDS DB Cluster has no Multi-AZ replication enabled Description Checks if your Amazon RDS DB clusters have Multi-AZ replication enabled. A Multi-AZ DB cluster has a writer DB instance and two reader DB instances in three separate Availability Zones. Multi-AZ DB clusters provide high availability, increased capacity for read workloads, and lower latency when compared to Multi-AZ deployments. For more information, see Creating a Multi-AZ DB cluster. Fault tolerance API Version 2025-05-13 307 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or
support-ug-093	support-ug.pdf	93	Checks if your Amazon RDS DB clusters have Multi-AZ replication enabled. A Multi-AZ DB cluster has a writer DB instance and two reader DB instances in three separate Availability Zones. Multi-AZ DB clusters provide high availability, increased capacity for read workloads, and lower latency when compared to Multi-AZ deployments. For more information, see Creating a Multi-AZ DB cluster. Fault tolerance API Version 2025-05-13 307 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz161 Source AWS Config Managed Rule: rds-cluster-multi-az-enabled Alert Criteria Yellow: Your Amazon RDS DB cluster does not have Multi-AZ replication conﬁgured Recommended Action Turn on Multi-AZ DB cluster deployment when you create an Amazon RDS DB cluster. For more information, see Creating a Multi-AZ DB cluster. Additional Resources Multi-AZ DB cluster deployments Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Fault tolerance API Version 2025-05-13 308 AWS Support User Guide RDS Multi-AZ Standby Instance Not Enabled Description Checks if your Amazon RDS DB instances have a Multi-AZ standby replica conﬁgured. Amazon RDS Multi-AZ provides high availability and durabiliy for database instances by replicating data to a standby replica in a diﬀerent Availability Zone. This provides automatic failover, improve performance, and enhances data durability. In a Multi-AZ DB instance deployment, Amazon RDS automatically provisions and maintains a synchronous standby replica in a diﬀerent Availability Zone. The primary DB instance is synchronously replicated across Availability Zones to a standby replica to provide data redundancy and minimize latency spikes during system backups. Running a DB instance with high availability enhances availability during planned system maintenance. It can also help protect your databases against DB instance failure and Availability Zone disruption. For more information, see Multi-AZ DB instance deployments. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz156 Source AWS Config Managed Rule: rds-multi-az-support Alert Criteria Yellow: An Amazon RDS DB instance does not have a Multi-AZ replica conﬁgured. Recommended Action Turn on Multi-AZ deployment when you create an Amazon RDS DB instance. Fault tolerance API Version 2025-05-13 309 AWS Support User Guide This check can't be excluded from view in the Trusted Advisor console. Additional Resources Multi-AZ DB instance deployments Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon RDS ReplicaLag Description Checks to see if the ReplicaLag CloudWatch metric for an RDS database instance has increased above an operationally reasonable threshold over the past week. ReplicaLag metric measures the number of seconds a read replica is behind the primary instance. Replication lag occurs when the asynchronous updates made to the read replica cannot keep up with the updates happening on the primary database instance. In the event of a failure to the primary instance, data could be missing from the read replica if the ReplicaLag is above an operationally reasonable threshold. Check ID Cmsvnj8db1 Alert Criteria • Red: ReplicaLag metric exceeded 60 seconds at least once during the week. • Yellow: ReplicaLag metric exceeded 10 seconds at least once during the week. • Green: ReplicaLag is less than 10 seconds. Recommended Action There are several possible causes for ReplicaLag to increase beyond operationally safe levels. For example, it can be caused by recently replaced/launched replica instances from older backups and these replicas requiring substantial time to “catch-up” to the primary database Fault tolerance API Version 2025-05-13 310 AWS Support User Guide instance and live transactions. This ReplicaLag may dwindle over time as catch-up occurs. Another example could be that the transaction velocity able to be achieved on the primary database instance is higher than the replication process or replica infrastructure is able to match. This ReplicaLag may grow over time as replication fails to keep pace with the primary database performance. Finally, the workload may be bursty throughout diﬀerent periods of the day/month/etc. that result in occasional ReplicaLag to fall behind. Your team should investigate which possible root cause has contributed to high ReplicaLag for the database, and possibly change the database instance type or other characteristics of the workload to ensure data continuity on the replica matches your requirements. Additional Resources • Working with read replicas for Amazon RDS for PostgreSQL • Working with MySQL replication in
support-ug-094	support-ug.pdf	94	replica infrastructure is able to match. This ReplicaLag may grow over time as replication fails to keep pace with the primary database performance. Finally, the workload may be bursty throughout diﬀerent periods of the day/month/etc. that result in occasional ReplicaLag to fall behind. Your team should investigate which possible root cause has contributed to high ReplicaLag for the database, and possibly change the database instance type or other characteristics of the workload to ensure data continuity on the replica matches your requirements. Additional Resources • Working with read replicas for Amazon RDS for PostgreSQL • Working with MySQL replication in Amazon RDS • Working with MySQL read replicas Report columns • Status • Region • DB Instance ARN • ReplicaLag Metric Amazon RDS synchronous_commit parameter is turned oﬀ Description When the synchronous_commit parameter is turned oﬀ, data can be lost in a database crash. The durability of the database is at risk. We recommend that you turn on the synchronous_commit parameter. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 311 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt026 Alert Criteria Red: DB parameter groups have synchronous_commit parameter turned oﬀ. Recommended Action Turn on synchronous_commit parameter in your DB parameter groups. Additional Resources The synchronous_commit parameter deﬁnes the Write-Ahead Logging (WAL) process completion before the database server sends a successful notiﬁcation to the client. This commit is called as an asynchronous commit because the client acknowledges the commit before WAL saves the transaction in the disk. If the synchronous_commit parameter is turned oﬀ, then the transactions can be lost, DB instance durability might be compromised, and data might be lost when a database crashes. For more information, see MySQL database log ﬁles. Report columns • Status • Region • Resource • Parameter Name • Recommended Value • Last Updated Time Fault tolerance API Version 2025-05-13 312 AWS Support User Guide Amazon Redshift cluster automated snapshots Description Checks if automated snapshots are enabled for your Amazon Redshift clusters. Amazon Redshift automatically takes incremental snapshots that track changes to the cluster since the previous automated snapshot. Automated snapshots retain all of the data required to restore a cluster from a snapshot. To disable automated snapshots, set the retention period to zero. You can't disable automated snapshots for RA3 node types. You can specify your desired minimum and maximum retention period using the MinRetentionPeriod and MaxRetentionPeriod parameter of your AWS Conﬁg rules. Amazon Redshift snapshots and backups Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz135 Source AWS Config Managed Rule: redshift-backup-enabled Alert Criteria Red: Amazon Redshift does not have automated snapshots conﬁgured within the desired retention period. Recommended Action Make sure that automated snapshots are enabled for your Amazon Redshift clusters. For more information, see Managing snapshots using the console. Fault tolerance API Version 2025-05-13 313 AWS Support Additional Resources Amazon Redshift snapshots and backups For more information, see Working with backups. User Guide Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon Route 53 Deleted Health Checks Description Checks for resource record sets that are associated with health checks that have been deleted. Route 53 does not prevent you from deleting a health check that is associated with one or more resource record sets. If you delete a health check without updating the associated resource record sets, the routing of DNS queries for your DNS failover conﬁguration will not work as intended. Hosted zones created by AWS services won't appear in your check results. Check ID Cb877eB72b Alert Criteria Yellow: A resource record set is associated with a health check that has been deleted. Recommended Action Create a new health check and associate it with the resource record set. See Creating, Updating, and Deleting Health
support-ug-095	support-ug.pdf	95	does not prevent you from deleting a health check that is associated with one or more resource record sets. If you delete a health check without updating the associated resource record sets, the routing of DNS queries for your DNS failover conﬁguration will not work as intended. Hosted zones created by AWS services won't appear in your check results. Check ID Cb877eB72b Alert Criteria Yellow: A resource record set is associated with a health check that has been deleted. Recommended Action Create a new health check and associate it with the resource record set. See Creating, Updating, and Deleting Health Checks and Adding Health Checks to Resource Record Sets. Additional Resources • Amazon Route 53 Health Checks and DNS Failover Fault tolerance API Version 2025-05-13 314 AWS Support User Guide • How Health Checks Work in Simple Amazon Route 53 Conﬁgurations Report columns • Hosted Zone Name • Hosted Zone ID • Resource Record Set Name • Resource Record Set Type • Resource Record Set Identiﬁer Amazon Route 53 Failover Resource Record Sets Description Checks for Amazon Route 53 failover resource record sets that have a misconﬁguration. When Amazon Route 53 health checks determine that the primary resource is unhealthy, Amazon Route 53 responds to queries with a secondary, backup resource record set. You must create correctly conﬁgured primary and secondary resource record sets for failover to work. Hosted zones created by AWS services won't appear in your check results. Check ID b73EEdD790 Alert Criteria • Yellow: A primary failover resource record set does not have a corresponding secondary resource record set. • Yellow: A secondary failover resource record set does not have a corresponding primary resource record set. • Yellow: Primary and secondary resource record sets that have the same name are associated with the same health check. Recommended Action If a failover resource set is missing, create the corresponding resource record set. See Creating Failover Resource Record Sets. If your resource record sets are associated with the same health check, create separate health checks for each one. See Creating, Updating, and Deleting Health Checks. Fault tolerance API Version 2025-05-13 315 AWS Support Additional Resources Amazon Route 53 Health Checks and DNS Failover User Guide Report columns • Hosted Zone Name • Hosted Zone ID • Resource Record Set Name • Resource Record Set Type • Reason Amazon Route 53 High TTL Resource Record Sets Description Checks for resource record sets that can beneﬁt from having a lower time-to-live (TTL) value. TTL is the number of seconds that a resource record set is cached by DNS resolvers. When you specify a long TTL, DNS resolvers take longer to request updated DNS records, which can cause unnecessary delay in rerouting traﬃc (for example, when DNS Failover detects and responds to a failure of one of your endpoints). This check looks only at records with a policy of Failover, or if there is an associated health check. Hosted zones created by AWS services won’t appear in your check results. Check ID C056F80cR3 Alert Criteria • Yellow: A resource record set whose routing policy is Failover has a TTL greater than 60 seconds. • Green: A resource record either has no failover policy, or has a failover policy with a TTL less than 60. Recommended Action Enter a TTL value of 60 seconds for the listed resource record sets. For more information, see Working with Resource Record Sets. Fault tolerance API Version 2025-05-13 316 AWS Support Additional Resources Amazon Route 53 Health Checks and DNS Failover User Guide Report columns • Status • Hosted Zone Name • Hosted Zone ID • Resource Record Set Name • Resource Record Set Type • Resource Record Set ID • TTL Amazon Route 53 Name Server Delegations Description Checks for Amazon Route 53 hosted zones for which your domain registrar or DNS is not using the correct Route 53 name servers. When you create a hosted zone, Route 53 assigns a delegation set of four name servers. The names of these servers are ns-###.awsdns-##.com, .net, .org, and .co.uk, where ### and ## typically represent diﬀerent numbers. Before Route 53 can route DNS queries for your domain, you must update your registrar's name server conﬁguration to remove the name servers that the registrar assigned. Then, you must add all four name servers in the Route 53 delegation set. For maximum availability, you must add all four Route 53 name servers. Hosted zones created by AWS services won't appear in your check results. Check ID cF171Db240 Alert Criteria Yellow: A hosted zone for which the registrar for your domain does not use all four of the Route 53 name servers in the delegation set. Fault tolerance API Version 2025-05-13 317 AWS Support Recommended Action User Guide Add or update name server records with your registrar or with the
support-ug-096	support-ug.pdf	96	the name servers that the registrar assigned. Then, you must add all four name servers in the Route 53 delegation set. For maximum availability, you must add all four Route 53 name servers. Hosted zones created by AWS services won't appear in your check results. Check ID cF171Db240 Alert Criteria Yellow: A hosted zone for which the registrar for your domain does not use all four of the Route 53 name servers in the delegation set. Fault tolerance API Version 2025-05-13 317 AWS Support Recommended Action User Guide Add or update name server records with your registrar or with the current DNS service for your domain to include all four of the name servers in your Route 53 delegation set. To ﬁnd these values, see Getting the Name Servers for a Hosted Zone. For information about adding or updating name server records, see Creating and Migrating Domains and Subdomains to Amazon Route 53. Additional Resources Working with Hosted Zones Report columns • Hosted Zone Name • Hosted Zone ID • Number of Name Server Delegations Used Amazon Route 53 Resolver Endpoint Availability Zone Redundancy Description Checks to see if your service conﬁguration has IP addresses speciﬁed in at least two Availability Zones (AZs) for redundancy. An AZ is a distinct location that is insulated from failures in other zones. By specifying IP addresses in multiple AZs in the same Region, you can help protect your applications from a single point of failure. Check ID Chrv231ch1 Alert Criteria • Yellow: IP addresses are speciﬁed only in one AZ • Green: IP addresses are speciﬁed in at least two AZs Recommended Action Specify IP addresses in at least two Availability Zones for redundancy. Additional Resources • If you require more than one elastic network interface endpoint to be available at all times, we recommend that you create at least one more network interface than you need, to make sure you have additional capacity available for handling possible traﬃc surges. The additional Fault tolerance API Version 2025-05-13 318 AWS Support User Guide network interface also ensures availability during service operations like maintenance or upgrades. • High availability for Resolver endpoints Report columns • Status • Region • Resource ARN • Number of AZs Amazon S3 Bucket Logging Description Checks the logging conﬁguration of Amazon Simple Storage Service (Amazon S3) buckets. When server access logging is enabled, detailed access logs are delivered hourly to a bucket that you choose. An access log record contains details about each request, such as the request type, the resources speciﬁed in the request, and the time and date the request was processed. By default, bucket logging is not enabled. You should enable logging if you want to perform security audits or learn more about users and usage patterns. When logging is initially enabled, the conﬁguration is automatically validated. However, future modiﬁcations can result in logging failures. This check examines explicit Amazon S3 bucket permissions, but it does not examine associated bucket policies that might override the bucket permissions. Check ID BueAdJ7NrP Alert Criteria • Yellow: The bucket does not have server access logging enabled. • Yellow: The target bucket permissions do not include the root account, so Trusted Advisor cannot check it. • Red: The target bucket does not exist. • Red: The target bucket and the source bucket have diﬀerent owners. • Red: The log deliverer does not have write permissions for the target bucket. Fault tolerance API Version 2025-05-13 319 AWS Support Recommended Action User Guide Enable bucket logging for most buckets. See Enabling Logging Using the Console and Enabling Logging Programmatically. If the target bucket permissions do not include the root account and you want Trusted Advisor to check the logging status, add the root account as a grantee. See Editing Bucket Permissions. If the target bucket does not exist, select an existing bucket as a target or create a new one and select it. See Managing Bucket Logging. If the target and source have diﬀerent owners, change the target bucket to one that has the same owner as the source bucket. See Managing Bucket Logging. If the log deliverer does not have write permissions for the target (write not enabled), grant Upload/Delete permissions to the Log Delivery group. See Editing Bucket Permissions. Additional Resources • Working with Buckets • Server Access Logging • Server Access Log Format • Deleting Log Files Report columns • Status • Region • Bucket Name • Target Name • Target Exists • Same Owner • Write Enabled • Reason Fault tolerance API Version 2025-05-13 320 AWS Support User Guide Amazon S3 Bucket Replication Not Enabled Description Checks if your Amazon S3 buckets have replication rules enabled for Cross-Region Replication, Same-Region Replication, or both. Replication is the automatic, asynchronous copying of objects across buckets in the same or diﬀerent AWS
support-ug-097	support-ug.pdf	97	the Log Delivery group. See Editing Bucket Permissions. Additional Resources • Working with Buckets • Server Access Logging • Server Access Log Format • Deleting Log Files Report columns • Status • Region • Bucket Name • Target Name • Target Exists • Same Owner • Write Enabled • Reason Fault tolerance API Version 2025-05-13 320 AWS Support User Guide Amazon S3 Bucket Replication Not Enabled Description Checks if your Amazon S3 buckets have replication rules enabled for Cross-Region Replication, Same-Region Replication, or both. Replication is the automatic, asynchronous copying of objects across buckets in the same or diﬀerent AWS Regions. Replication copies newly created objects and object updates from a source bucket to a destination bucket or buckets. Use Amazon S3 bucket replication to help improve the resilience and compliance of your applications and data storage. For more information, see Replicating objects. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz119 Source AWS Config Managed Rule: s3-bucket-replication-enabled Alert Criteria Yellow: Amazon S3 bucket replication rules are not enabled for Cross-Region Replication, Same- Region Replication, or both. Recommended Action Turn on Amazon S3 bucket replication rules to improve the resiliency and compliance of your applications and data storage. For more information, see View your backup jobs and recovery points and Setting up replication. Fault tolerance API Version 2025-05-13 321 AWS Support Additional Resources Walkthroughs: Examples for conﬁguring replication User Guide Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon S3 Bucket Versioning Description Checks for Amazon Simple Storage Service buckets that do not have versioning enabled, or that have versioning suspended. When versioning is enabled, you can easily recover from both unintended user actions and application failures. Versioning allows you to preserve, retrieve, and restore any version of any object stored in a bucket. You can use lifecycle rules to manage all versions of your objects, as well as their associated costs, by automatically archiving objects to the Glacier storage class. Rules can also be conﬁgured to remove versions of your objects after a speciﬁed period of time. You can also require multi-factor authentication (MFA) for any object deletions or conﬁguration changes to your buckets. Versioning can't be deactivated after it has been enabled. However, it can be suspended, which prevents new versions of objects from being created. Using versioning can increase your costs for Amazon S3, because you pay for storage of multiple versions of an object. Check ID R365s2Qddf Alert Criteria • Green: Versioning is enabled for the bucket. • Yellow: Versioning is not enabled for the bucket. Fault tolerance API Version 2025-05-13 322 AWS Support User Guide • Yellow: Versioning is suspended for the bucket. Recommended Action Enable bucket versioning on most buckets to prevent accidental deletion or overwriting. See Using Versioning and Enabling Versioning Programmatically. If bucket versioning is suspended, consider re-enabling versioning. For information on working with objects in a versioning-suspended bucket, see Managing Objects in a Versioning- Suspended Bucket. When versioning is enabled or suspended, you can deﬁne lifecycle conﬁguration rules to mark certain object versions as expired or to permanently remove unneeded object versions. For more information, see Object Lifecycle Management. MFA Delete requires additional authentication when the versioning status of the bucket is changed or when versions of an object are deleted. It requires the user to enter credentials and a code from an approved authentication device. For more information, see MFA Delete. Additional Resources Working with Buckets Report columns • Status • Region • Bucket Name • Versioning • MFA Delete Enabled Application, Network, and Gateway Load Balancers Not Spanning Multiple Availability Zones Description Checks If your load balancers (Application, Network, and Gateway Load Balancer) are conﬁgured with subnets across multiple Availability Zones. You can specify your desired minimum Availability Zones in the minAvailabilityZones parameters of your AWS Conﬁg rules. Fault tolerance API Version 2025-05-13 323 AWS Support User Guide For more information, see Availability Zones for your Application Load Balancer, Availability Zones - Network Load Balancers, and Create a Gateway Load Balancer. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz169 Source AWS Config Managed Rule: elbv2-multiple-az Alert Criteria Yellow: Application, Network, or Gateway Load Balancers conﬁgured with subnets in less than two
support-ug-098	support-ug.pdf	98	information, see Availability Zones for your Application Load Balancer, Availability Zones - Network Load Balancers, and Create a Gateway Load Balancer. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz169 Source AWS Config Managed Rule: elbv2-multiple-az Alert Criteria Yellow: Application, Network, or Gateway Load Balancers conﬁgured with subnets in less than two Availability Zones. Recommended Action Conﬁgure your Application, Network, and Gateway Load Balancers with subnets across multiple Availability Zones. Additional Resources Availability Zones for your Application Load Balancer Availability Zones (Elastic Load Balancing) Create a Gateway Load Balancer Report columns • Status • Region • Resource • AWS Conﬁg Rule Fault tolerance API Version 2025-05-13 324 AWS Support • Input Parameters • Last Updated Time Auto Scaling available IPs in Subnets Description User Guide Checks that suﬃcient available IPs remain among targeted Subnets.Having suﬃcient IPs available for use would help when Auto Scaling Group reaches its maximum size and needs to launch additional instances. Check ID Cjxm268ch1 Alert Criteria • Red: The maximum number of instances and IP addresses that could be created by an ASG exceed the number of IP addresses remaining in the conﬁgured subnets. • Green: There are suﬃcient IP addresses available for the remaining scale possible in the ASG. Recommended Action Increase the number of available IP addresses Report columns • Status • Region • Resource ARN • Maximum instances that can be created • Number of available instances Auto Scaling Group Health Check Description Examines the health check conﬁguration for Auto Scaling groups. If Elastic Load Balancing is being used for an Auto Scaling group, the recommended conﬁguration is to enable an Elastic Load Balancing health check. If an Elastic Load Balancing health check is not used, Auto Scaling can only act upon the health of the Amazon Elastic Fault tolerance API Version 2025-05-13 325 AWS Support User Guide Compute Cloud (Amazon EC2) instance. Auto Scaling will not act on the application running on the instance. Check ID CLOG40CDO8 Alert Criteria • Yellow: An Auto Scaling group has an associated load balancer, but the Elastic Load Balancing health check is not enabled. • Yellow: An Auto Scaling group does not have an associated load balancer, but the Elastic Load Balancing health check is enabled. Recommended Action If the Auto Scaling group has an associated load balancer, but the Elastic Load Balancing health check is not enabled, see Add an Elastic Load Balancing Health Check to your Auto Scaling Group. If the Elastic Load Balancing health check is enabled, but no load balancer is associated with the Auto Scaling group, see Set Up an Auto-Scaled and Load-Balanced Application. Additional Resources Amazon EC2 Auto Scaling User Guide Report columns • Status • Region • Auto Scaling Group Name • Load Balancer Associated • Health Check Auto Scaling Group Resources Description Checks the availability of resources associated with your launch conﬁgurations, launch templates, and your Auto Scaling groups. Auto Scaling groups that point to unavailable resources cannot launch new Amazon Elastic Compute Cloud (Amazon EC2) instances. When properly conﬁgured, Auto Scaling causes the Fault tolerance API Version 2025-05-13 326 AWS Support User Guide number of Amazon EC2 instances to increase seamlessly during demand spikes, and decrease automatically during demand lulls. Auto Scaling groups and launch conﬁgurations/launch templates that point to unavailable resources do not operate as intended. Check ID 8CNsSllI5v Alert Criteria • Red: An Auto Scaling group is associated with a deleted load balancer. • Red: A launch conﬁguration is associated with a deleted Amazon Machine Image (AMI). • Red: A launch template is associated with a deleted Amazon Machine Image (AMI). Recommended Action If the load balancer has been deleted, either create a new load balancer or target group and then associate it to the Auto Scaling group. or create a new Auto Scaling group without the load balancer. For information about creating a new Auto Scaling group with a new load balancer, see Set Up an Auto-Scaled and Load-Balanced Application. For information about creating a new Auto Scaling group without a load balancer, see Create Auto Scaling Group in Getting Started With Auto Scaling Using the Console. If the AMI has been deleted, then create a new launch conﬁguration or launch template version using a valid AMI and associate it with an Auto Scaling group. For information on how to create a new launch conﬁguration, see Create a launch conﬁguration in the Amazon EC2 Auto Scaling User Guide. For information on how to create a launch template, see Create a launch template for an Auto Scaling
support-ug-099	support-ug.pdf	99	Auto-Scaled and Load-Balanced Application. For information about creating a new Auto Scaling group without a load balancer, see Create Auto Scaling Group in Getting Started With Auto Scaling Using the Console. If the AMI has been deleted, then create a new launch conﬁguration or launch template version using a valid AMI and associate it with an Auto Scaling group. For information on how to create a new launch conﬁguration, see Create a launch conﬁguration in the Amazon EC2 Auto Scaling User Guide. For information on how to create a launch template, see Create a launch template for an Auto Scaling group in the Amazon EC2 Auto Scaling User Guide. Note For security reasons, the check results don’t include any resources referenced using AWS Systems Manager parameters in the launch template. If your launch templates include an AWS Systems Manager parameter that include an Amazon Machine Image (AMI) ID , then review the launch template to make sure that the parameters reference a valid AMI ID, or make the appropriate changes in the AWS Systems Manager parameter store. For more information, see Use AWS Systems Manager parameters instead of AMI IDs in the Amazon EC2 Auto Scaling User Guide. Fault tolerance API Version 2025-05-13 327 AWS Support Additional Resources • Troubleshooting Auto Scaling: Amazon EC2 AMIs • Troubleshooting Auto Scaling: Load Balancer Conﬁguration • Amazon EC2 Auto Scaling User Guide • Use AWS Systems Manager parameters instead of AMI IDs User Guide Report columns • Status • Region • Auto Scaling Group Name • Launch Type • Resource Type • Resource Name AWS CloudHSM clusters running HSM instances in a single AZ Description Checks your clusters that run HSM instances in a single Availability Zone (AZ). This check alerts you if your clusters are at risk of not having the most recent backup. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID hc0dfs7601 Alert Criteria • Yellow: A CloudHSM cluster is running all HSM instances in a single Availability Zone for more than 1 hour. Fault tolerance API Version 2025-05-13 328 AWS Support User Guide • Green: A CloudHSM cluster is running all HSM instances in at least two diﬀerent Availability Zones. Recommended Action Create at least one more instance for the cluster in a diﬀerent Availability Zone. Additional Resources Best practices for AWS CloudHSM Report columns • Status • Region • Cluster ID • Number of HSM Instances • Last Updated Time AWS Direct Connect Location Resiliency Description Checks the resilience of the AWS Direct Connect used to connect your on-premises to each Direct Connect gateway or virtual private gateway. This check alerts you if any Direct Connect gateway or virtual private gateway isn't conﬁgured with virtual interfaces across at least two distinct Direct Connect locations. Lack of location resiliency can result in unexpected downtime during maintenance, a ﬁber cut, a device failure, or a complete location failure. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Note Direct Connect is implemented with Transit Gateway using Direct Connect gateway. Fault tolerance API Version 2025-05-13 329 AWS Support Check ID c1dfpnchv2 Alert Criteria User Guide Red: The Direct Connect gateway or virtual private gateway is conﬁgured with one or more virtual interfaces on a single Direct Connect device. Yellow: The Direct Connect gateway or virtual private gateway is conﬁgured with virtual interfaces across multiple Direct Connect devices in a single Direct Connect location. Green: The Direct Connect gateway or virtual private gateway is conﬁgured with virtual interfaces across two or more distinct Direct Connect locations. Recommended Action To build Direct Connect location resiliency, you can conﬁgure the Direct Connect gateway or virtual private gateway to connect to at least two distinct Direct Connect locations. For more information, see AWS Direct Connect Resiliency Recommendation. Additional Resources AWS Direct Connect Resiliency Recommendations AWS Direct Connect Failover Test Report columns • Status • Region • Last Updated Time • Resiliency Status • Location • Connection ID • Gateway ID AWS Lambda functions without a dead-letter queue conﬁgured Description Checks if an AWS Lambda function is conﬁgured with a dead-letter queue. Fault tolerance API Version 2025-05-13 330 AWS Support User Guide A dead-letter queue is a feature of AWS Lambda that allows you to capture and analyze failed events, providing a way to handle those events accordingly. Your code might raise an exception, time out, or run out of memory, resulting in failed asynchronous executions of your Lambda function. A
support-ug-100	support-ug.pdf	100	columns • Status • Region • Last Updated Time • Resiliency Status • Location • Connection ID • Gateway ID AWS Lambda functions without a dead-letter queue conﬁgured Description Checks if an AWS Lambda function is conﬁgured with a dead-letter queue. Fault tolerance API Version 2025-05-13 330 AWS Support User Guide A dead-letter queue is a feature of AWS Lambda that allows you to capture and analyze failed events, providing a way to handle those events accordingly. Your code might raise an exception, time out, or run out of memory, resulting in failed asynchronous executions of your Lambda function. A dead-letter queue stores messages from failed invocations, providing a way to handle the messages and troubleshoot the failures. You can specify the dead-letter queue resource that you want to check using the dlqArns parameter in your AWS Conﬁg rules. For more information, see Dead-letter queues. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz182 Source AWS Config Managed Rule: lambda-dlq-check Alert Criteria Yellow: AWS Lambda function has no dead-letter queue conﬁgured. Recommended Action Make sure that your AWS Lambda functions have a dead-letter queue conﬁgured to control message handling for all failed asynchronous invocations. For more information, see Dead-letter queues. Additional Resources • Robust Serverless Application Design with AWS Lambda Dead Letter Queues Report columns • Status Fault tolerance API Version 2025-05-13 331 AWS Support • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide AWS Lambda On Failure Event Destinations Description Checks that Lambda functions in your account have On Failure event destination or Dead Letter Queue (DLQ) conﬁgured for asynchronous invocations, so that records from failed invocations can be routed to a destination for further investigation or processing. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfprch05 Alert Criteria • Yellow: Function does not have any On Failure event destination or DLQ conﬁgured. Recommended Action Please set up On Failure event destination or DLQ for your Lambda functions to send failed invocations along with other details to one of the available destination AWS services for further debugging or processing. Additional Resources • Asynchronous Invocation Fault tolerance API Version 2025-05-13 332 AWS Support User Guide • AWS Lambda On Failure Event Destinations Report columns • Status • Region • The function with version which is ﬂagged. • Current day async requests dropped percentage • Current day async requests • Average daily async requests dropped percentage • Average daily async requests • Last Updated Time AWS Lambda VPC-enabled Functions without Multi-AZ Redundancy Description Checks the $LATEST version of VPC-enabled Lambda functions that are vulnerable to service interruption in a single Availability Zone. It’s a best practice that VPC-enabled functions are connected to multiple Availability Zones for high availability. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID L4dfs2Q4C6 Alert Criteria Yellow: The $LATEST version of a VPC-enabled Lambda function is connected to subnets in a single Availability Zone. Fault tolerance API Version 2025-05-13 333 AWS Support Recommended Action User Guide When conﬁguring functions for access to your VPC, choose subnets in multiple Availability Zones to ensure high availability. Additional Resources • Conﬁguring a Lambda function to access resources in a VPC • Resilience in AWS Lambda Report columns • Status • Region • Function ARN • VPC ID • Average daily Invokes • Last Updated Time AWS Outposts Single Rack deployment Description Checks for Outposts Racks balance. This evaluates if a customers Outposts instances are deployed across multiple Outposts Racks or to a single Outpost Rack. A single Outposts rack creates a single point of failure for issues that involve a single Rack (for example, environmental failures). These scenarios can be mitigated by deploying outposts across multiple Racks. Check ID c243hjzrhn Alert Criteria • Yellow: Your Outpost is deployed on single Rack • Green: Your Outpost is deployed across multiple Racks. Recommended Action If you are running production workloads on AWS Outposts, then its a best practice to use the
support-ug-101	support-ug.pdf	101	deployment Description Checks for Outposts Racks balance. This evaluates if a customers Outposts instances are deployed across multiple Outposts Racks or to a single Outpost Rack. A single Outposts rack creates a single point of failure for issues that involve a single Rack (for example, environmental failures). These scenarios can be mitigated by deploying outposts across multiple Racks. Check ID c243hjzrhn Alert Criteria • Yellow: Your Outpost is deployed on single Rack • Green: Your Outpost is deployed across multiple Racks. Recommended Action If you are running production workloads on AWS Outposts, then its a best practice to use the following resilient architecture. A single AWS Outposts rack creates a single point of failure. Consider adding a second AWS Outposts rack to that location with enough capacity for a failover event, and then distribute workloads across racks. Fault tolerance API Version 2025-05-13 334 User Guide AWS Support Additional Resources Failure mode 4: Racks or data centers Report columns • Status • Resource ARN • AZ • Number of Racks • Last Updated Time AWS Resilience Hub Application Component check Description Checks if an Application Component (AppComponent) in your application is unrecoverable. If an AppComponent doesn't recover in the case of a disruption event, you might experience unknown data loss and system downtime. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Check ID RH23stmM04 Alert Criteria Red: AppComponent is unrecoverable. Recommended Action To ensure that your AppComponent is recoverable, review and implement the resiliency recommendations, and then run a new assessment. For more information about reviewing the resiliency recommendations, see Additional Resources. Additional Resources Reviewing resiliency recommendations Fault tolerance API Version 2025-05-13 335 AWS Support User Guide AWS Resilience Hub concepts AWS Resilience Hub User Guide Report columns • Status • Region • Application Name • AppComponent Name • Last Updated Time AWS Resilience Hub policy breached Description Checks Resilience Hub for applications that don't meet the recovery time objective (RTO) and recovery point objective (RPO) that the policy deﬁnes. The check alerts you if your application doesn't meet the RTO and RPO objectives you've set for an application in Resilience Hub. Note Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID RH23stmM02 Alert Criteria • Green: The application has a policy and meets the RTO and RPO objectives. • Yellow: The application hasn't been assessed yet. Fault tolerance API Version 2025-05-13 336 AWS Support User Guide • Red: The application has a policy but doesn’t meet the RTO and RPO objectives. Recommended Action Sign in to the Resilience Hub console and review the recommendations so that your application meets the RTO and RPO objectives. Additional Resources Resilience Hub concepts Report columns • Status • Region • Application Name • Last Updated Time AWS Resilience Hub resilience scores Description Checks if you have run an assessment for your applications in Resilience Hub. This check alerts you if your resilience scores are below a speciﬁc value. Note Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID RH23stmM01 Fault tolerance API Version 2025-05-13 337 AWS Support Alert Criteria • Green: Your application has a resilience score of 70 or greater. • Yellow: Your application has a resilience score of 40 through 69. • Yellow: The application hasn't been assessed yet. • Red: Your application has a resilience score of less than 40. Recommended Action User Guide Sign in to the Resilience Hub console and run an assessment for your application. Review the recommendations to improve the resilience score. Additional Resources Resilience Hub concepts Report columns • Status • Region • Application Name • Application Resilience Score • Last Updated Time AWS Resilience Hub assessment age Description Checks how long since you last ran an application assessment. This check alerts you if you haven’t run an application assessment for a speciﬁed number of days. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API
support-ug-102	support-ug.pdf	102	Application Name • Application Resilience Score • Last Updated Time AWS Resilience Hub assessment age Description Checks how long since you last ran an application assessment. This check alerts you if you haven’t run an application assessment for a speciﬁed number of days. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 338 User Guide AWS Support Check ID RH23stmM03 Alert Criteria • Green: Your application assessment ran in the last 30 days. • Yellow: Your application assessment hasn't run in the last 30 days. Recommended Action Sign in to the Resilience Hub console and run an assessment for your application. Additional Resources Resilience Hub concepts Report columns • Status • Region • Application Name • Days Since the Last Assessment Ran • Last Assessment Run Time • Last Updated Time AWS Site-to-Site VPN has at least one tunnel in DOWN status Description Checks the number of tunnels that are active for each of your AWS Site-to-Site VPNs. A VPN should have two tunnels conﬁgured at all times. This provides redundancy in case of outage or planned maintenance of the devices at the AWS endpoint. For some hardware, only one tunnel is active at a time. If a VPN has no active tunnels, charges for the VPN might still apply. For more information, see What is AWS Site-to-Site VPN? Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Fault tolerance API Version 2025-05-13 339 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz123 Source AWS Config Managed Rule: vpc-vpn-2-tunnels-up Alert Criteria Yellow: A Site-to-Site VPN has at least one tunnel DOWN. Recommended Action Make sure that two tunnels are conﬁgured for VPN connections. And, if your hardware supports it, then make sure that both tunnels are active. If you no longer need a VPN connection, then delete it to avoid charges. For more information, see Your customer gateway device and the content available on the AWS Knowledge Center. Additional Resources • AWS Site-to-Site VPN User Guide • Adding a Virtual Private Gateway to Your VPC Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Fault tolerance API Version 2025-05-13 340 AWS Support User Guide AWS Well-Architected high risk issues for reliability Description Checks for high risk issues (HRIs) for your workloads in the reliability pillar. This check is based on your AWS-Well Architected reviews. Your check results depend on whether you completed the workload evaluation with AWS Well-Architected. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID Wxdfp4B1L4 Alert Criteria • Red: At least one active high risk issue was identiﬁed in the reliability pillar for AWS Well- Architected. • Green: No active high risk issues were detected in the reliability pillar for AWS Well- Architected. Recommended Action AWS Well-Architected detected high risk issues during your workload evaluation. These issues present opportunities to reduce risk and save money. Sign in to the AWS Well-Architected tool to review your answers and take action to resolve your active issues. Report columns • Status • Region • Workload ARN • Workload Name • Reviewer Name Fault tolerance API Version 2025-05-13 341 AWS Support User Guide • Workload Type • Workload Started Date • Workload Last Modiﬁed Date • Number of identiﬁed HRIs for Reliability • Number of HRIs resolved for Reliability • Number of questions answered for Reliability • Total number of questions in Reliability pillar • Last Updated Time Classic Load Balancer has no multiple AZs conﬁgured Description Checks if Classic Load Balancer spans multiple Availability Zones (AZs). A load balancer distributes incoming application traﬃc across multiple Amazon EC2 instances in multiple Availability Zones. By default, the load balancer distributes traﬃc evenly across the Availability Zones that you enable for your load balancer. If one Availability Zone experiences an outage, then load balancer nodes automatically forward requests to the healthy registered instances in one or more Availability Zones. You can adjust the minimum number of Availability Zones using the minAvailabilityZones parameter in
support-ug-103	support-ug.pdf	103	in Reliability pillar • Last Updated Time Classic Load Balancer has no multiple AZs conﬁgured Description Checks if Classic Load Balancer spans multiple Availability Zones (AZs). A load balancer distributes incoming application traﬃc across multiple Amazon EC2 instances in multiple Availability Zones. By default, the load balancer distributes traﬃc evenly across the Availability Zones that you enable for your load balancer. If one Availability Zone experiences an outage, then load balancer nodes automatically forward requests to the healthy registered instances in one or more Availability Zones. You can adjust the minimum number of Availability Zones using the minAvailabilityZones parameter in your AWS Conﬁg rules For more information, see What is a Classic Load Balancer?. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz154 Fault tolerance API Version 2025-05-13 342 AWS Support Source AWS Config Managed Rule: clb-multiple-az Alert Criteria User Guide Yellow: Classic Load Balancer does not have Multi-AZ conﬁgured or does not meet the minimum number of AZs speciﬁed. Recommended Action Make sure that your Classic Load Balancers have multiple Availability Zones conﬁgured. Span your load balancer across multiple AZs to make sure that you have high availability of your application. For more information, see Tutorial: Create a Classic Load Balancer. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time CLB Connection Draining Description Checks for Classic load balancers that do not have connection draining enabled. When connection draining is not enabled and you deregister an Amazon EC2 instance from a Classic load balancer, the Classic load balancer stops routing traﬃc to that instance and closes the connection. When connection draining is enabled, the Classic load balancer stops sending new requests to the deregistered instance but keeps the connection open to serve active requests. Check ID 7qGXsKIUw Fault tolerance API Version 2025-05-13 343 AWS Support Alert Criteria • Yellow: Connection draining is not enabled for a Classic load balancer. • Green: Connection draining is enabled for Classic load balancer. . Recommended Action User Guide Enable connection draining for the Classic load balancer. For more information, see Connection Draining and Enable or Disable Connection Draining for Your Load Balancer. Additional Resources Elastic Load Balancing Concepts Report columns • Status • Region • Load Balancer Name • Reason ELB Target Imbalance Description Checks the target groups’ target distribution across Availability Zones (AZs) for Application Load Balancer (ALB), Network Load Balancer (NLB), and Gateway Load Balancer (GWLB). This check excludes the following: • Load balancers conﬁgured with a single Availability Zone (AZ). • Load balancers where the diﬀerence in the number of targets between the most and least populated AZs is equal to or less than 1. • Target groups with IP-based targets where the AvailabilityZone attribute is set to 'all'. Check ID b92b83d667 Alert Criteria • Red: A single AZ represents more than 66% of the load balancer capacity. • Yellow: A single AZ represents more than 50% of the load balancer capacity. • Green: No AZs represents more than 50% of the load balancer capacity. Fault tolerance API Version 2025-05-13 344 AWS Support Recommended Action User Guide For better resilience, make sure that your targets groups have same number of targets across AZs. Additional Resources Target groups for your Application Load Balancers Register targets with your Application Load Balancer target group Report columns • Status • Region • Load Balancer Name • Load Balancer Type • Target Group ARN (arn) • Diﬀerence in registered targets across AZs • Last Updated Time GWLB - endpoint AZ independence Description Checks if your Gateway Load Balancer (GWLB) endpoints are conﬁgured as route destination from another Availability Zone (AZ). Gateway Load Balancer endpoints forward network traﬃc to ﬁrewall appliances behind a Gateway Load Balancer for inspection. Each Gateway Load Balancer endpoint operates within a designated AZ and is built with redundancy in only that AZ. So any resources in a particular AZ must use a Gateway Load Balancer endpoint in the same AZ. This makes sure that any potential outage of a Gateway Load Balancer endpoint or its AZ doesn’t impact your resources in another AZ. Check ID 528d6f5ee7 Alert Criteria • Yellow: Traﬃc from your subnet in one AZ is being routed through a Gateway Load Balancer endpoint in a diﬀerent AZ. Fault tolerance API Version 2025-05-13 345 AWS Support User Guide • Green: Traﬃc from your subnet in one AZ is being routed through a Gateway Load Balancer endpoint in the same AZ. Recommended Action Check the AZ of your subnet and conﬁgure its
support-ug-104	support-ug.pdf	104	Load Balancer endpoint in the same AZ. This makes sure that any potential outage of a Gateway Load Balancer endpoint or its AZ doesn’t impact your resources in another AZ. Check ID 528d6f5ee7 Alert Criteria • Yellow: Traﬃc from your subnet in one AZ is being routed through a Gateway Load Balancer endpoint in a diﬀerent AZ. Fault tolerance API Version 2025-05-13 345 AWS Support User Guide • Green: Traﬃc from your subnet in one AZ is being routed through a Gateway Load Balancer endpoint in the same AZ. Recommended Action Check the AZ of your subnet and conﬁgure its route table to route traﬃc through a Gateway Load Balancer endpoint in the same AZ. If there is no Gateway Load Balancer endpoint in the AZ, then create a new one and then route your subnet traﬃc through it. If you have the same route table associated across subnets in diﬀerent AZs, then keep this route table associated to the subnets that reside in the same AZ as the Gateway Load Balancer endpoint. For subnets in the other AZ, you can then associate a separate route table with a route to a Gateway Load Balancer endpoint in the this AZ. It’s a best practice to choose a maintenance window for architecture changes in your Amazon VPC. Additional Resources • Availability Zone Independence • Conﬁgure Routing for Gateway Load Balancer endpoint • AWS Well-Architected Tool - Use bulkhead architectures to limit scope of impact Report columns • Status • Region • Cross AZ Subnet Id List • Gateway Load Balancer Endpoint Id • Gateway Load Balancer Endpoint Subnet Id • VPC Endpoint Subnet AZ • Last Updated Time Load Balancer Optimization Description Checks your load balancer conﬁguration. Fault tolerance API Version 2025-05-13 346 AWS Support User Guide To help increase the level of fault tolerance in Amazon Elastic Compute Cloud (Amazon EC2) when using Elastic Load Balancing , we recommend running an equal number of instances across multiple Availability Zones in a Region. A load balancer that is conﬁgured accrues charges, so this is a cost-optimization check as well. Check ID iqdCTZKCUp Alert Criteria • Yellow: A load balancer is enabled for a single Availability Zone. • Yellow: A load balancer is enabled for an Availability Zone that has no active instances. • Yellow: The Amazon EC2 instances that are registered with a load balancer are unevenly distributed across Availability Zones. (The diﬀerence between the highest and lowest instance counts in utilized Availability Zones is more than 1, and the diﬀerence is more than 20% of the highest count.) Recommended Action Ensure that your load balancer points to active and healthy instances in at least two Availability Zones. For more information, see Add Availability Zone. If your load balancer is conﬁgured for an Availability Zone with no healthy instances, or if there is an imbalance of instances across the Availability Zones, determine if all the Availability Zones are necessary. Omit any unnecessary Availability Zones and ensure there is a balanced distribution of instances across the remaining Availability Zones. For more information, see Remove Availability Zone. Additional Resources • Availability Zones and Regions • Managing Load Balancers • Best Practices in Evaluating Elastic Load Balancing Report columns • Status • Region • Load Balancer Name • # of Zones Fault tolerance API Version 2025-05-13 347 AWS Support User Guide • Zone a Instances • Zone b Instances • Zone c Instances • Zone d Instances • Zone e Instances • Zone f Instances • Reason NAT Gateway AZ Independence Description Checks if your NAT Gateways are conﬁgured with Availability Zone (AZ) independence. A NAT Gateway enables resources in your private subnet to securely connect to services outside the subnet using the NAT Gateway’s IP addresses and drops any unsolicited inbound traﬃc. Each NAT Gateway operates within a designated Availability Zone (AZ) and is built with redundancy in that AZ only. Therefore, your resources in a particular AZ should use a NAT Gateway in the same AZ so that any potential outage of a NAT Gateway or its AZ does not impact your resources in another AZ. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfptbg10 Alert Criteria • Red: Traﬃc from your subnet in one AZ is being routed through a NATGW in a diﬀerent AZ. • Green: Traﬃc from your subnet in one AZ is being routed through a NATGW in the same AZ. Fault tolerance API Version 2025-05-13 348 AWS Support Recommended Action User Guide Please check the AZ of your subnet
support-ug-105	support-ug.pdf	105	allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfptbg10 Alert Criteria • Red: Traﬃc from your subnet in one AZ is being routed through a NATGW in a diﬀerent AZ. • Green: Traﬃc from your subnet in one AZ is being routed through a NATGW in the same AZ. Fault tolerance API Version 2025-05-13 348 AWS Support Recommended Action User Guide Please check the AZ of your subnet and route traﬃc through a NAT Gateway in the same AZ. If there is no NATGW in the AZ, please create one and then route your subnet traﬃc through it. If you have the same route table associated across subnets in diﬀerent AZs, keep this route table associated to the subnets that reside in the same AZ as the NAT Gateway and for subnets in the other AZ, please associate a separate route table with a route to a NAT Gateway in this other AZ. We recommend choosing a maintenance window for architecture changes in your Amazon VPC. Additional Resources • How to create a NAT Gateway • How to conﬁgure routes for diﬀerent NAT Gateway use cases Report columns • Status • Region • NAT Availability Zone • NAT ID • Subnet Availability Zone • Subnet ID • Route Table ID • NAT ARN • Last Updated Time Network Firewall endpoint AZ Independence Description Checks if your AWS Network Firewall endpoints are conﬁgured as a route destination from another Availability Zone (AZ). Network Firewall endpoints forward network traﬃc to a Network Firewall for inspection. Each Network Firewall endpoint operates within a designated AZ and is built with redundancy only Fault tolerance API Version 2025-05-13 349 AWS Support User Guide in that AZ. Your resources in a particular AZ should use a Network Firewall endpoint in the same AZ. This makes sure that any potential outage of a Network Firewall endpoint or its AZ doesn’t impact your resources in another AZ. Network traﬃc that originates in a diﬀerent AZ for traﬃc inspection incurs cross-AZ data transfer charges. It’s a best practice to make sure that all resources in a speciﬁc AZ use a Network Firewall in the same AZ to avoid cross-AZ data charges. Check ID 7040ea389a Alert Criteria • Yellow: Traﬃc from a subnet in one AZ is being routed through a Network Firewall endpoint in a diﬀerent AZ. • Green: Traﬃc from a subnet in one AZ is being routed through a Network Firewall endpoint in the same AZ. Recommended Action Check the AZ of your subnet and route traﬃc through a Network Firewall endpoint in the same AZ. If there is no Network Firewall endpoint in the AZ, then create a new Network Firewall and route your subnet traﬃc through it. If the same route table is associated across multiple subnets in diﬀerent AZs, then keep this route table associated to the subnets that reside in the same AZ as the Network Firewall endpoint. For subnets in other AZs, associate a separate route table with a route to a Network Firewall endpoint in that AZ. It’s a best practice to choose a maintenance window for architecture changes in your Amazon VPC. Additional Resources Data Transfer within the same AWS Region Understanding data transfer charges Availability Zone Independence High Level steps for implementing a ﬁrewall Fault tolerance API Version 2025-05-13 350 AWS Support Creating a ﬁrewall User Guide AWS Well-Architected Tool - Use bulkhead architectures to limit scope of impact Report columns • Status • Region • Network Firewall Endpoint Id • Network Firewall Arn • Network Firewall Endpoint Subnet • Network Firewall Endpoint AZ • Cross AZ Subnets List • Last Updated Time Network Firewall Multi-AZ Description Checks if your Network Firewalls are conﬁgured to use more than one Availability Zone (AZ) for ﬁrewall endpoints. An AZ is a distinct location that’s insulated from failures in other zones. If the Network Firewall endpoint is deployed in only 1 AZ, then it can be a single point of failure and can impair workloads from other AZs using the Network Firewall for traﬃc inspection. It’s a best practice to conﬁgure your Network Firewalls in multiple AZs in the same Region to mprove your workload availability. Check ID c2vlfg0gqd Alert Criteria • Yellow: Network Firewall endpoint is deployed in 1 AZ. • Green: Network Firewall endpoints is deployed in at least two AZs. Recommended Action Make sure that your Network Firewall is conﬁgured with at least two AZs for production workloads. Fault tolerance API Version 2025-05-13 351 AWS Support Additional Resources VPC subnet conﬁguration forAWS Network Firewall Creating a ﬁrewall Availability Zone AWS Well-Architected Tool - Deploy the workload to
support-ug-106	support-ug.pdf	106	Network Firewall for traﬃc inspection. It’s a best practice to conﬁgure your Network Firewalls in multiple AZs in the same Region to mprove your workload availability. Check ID c2vlfg0gqd Alert Criteria • Yellow: Network Firewall endpoint is deployed in 1 AZ. • Green: Network Firewall endpoints is deployed in at least two AZs. Recommended Action Make sure that your Network Firewall is conﬁgured with at least two AZs for production workloads. Fault tolerance API Version 2025-05-13 351 AWS Support Additional Resources VPC subnet conﬁguration forAWS Network Firewall Creating a ﬁrewall Availability Zone AWS Well-Architected Tool - Deploy the workload to multiple locations User Guide Appliance in a shared services VPC Report columns • Status • Region • Network Firewall Arn • VPC Id • Network Firewall Subnets • Network Firewall Subnets AZs • Last Updated Time Network Load Balancers Cross Load Balancing Description Checks if cross-zone load balancing is enabled on Network Load Balancers. Cross-zone load balancing helps maintain even distribution of incoming traﬃc across instances in diﬀerent Availability Zones. This prevents the load balancer from routing all traﬃc to instances in the same Availability Zone, which can cause uneven traﬃc distribution and potential overloading. The feature also helps application reliability by automatically routing traﬃc to healthy instances in other Availability Zones in the event of a single Availability Zone failure. For more information, see Cross-zone load balancing. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Fault tolerance API Version 2025-05-13 352 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz105 Source AWS Config Managed Rule: nlb-cross-zone-load-balancing-enabled Alert Criteria • Yellow: Network Load Balancer does not have cross-zone load balancing enabled. Recommended Action Ensure that cross-zone load balancing is enabled on Network Load Balancers. Additional Resources Cross-zone load balancing (Network Load Balancers) Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time NLB - Internet-facing resource in private subnet Description Checks if an internet-facing Network Load Balancer (NLB) is conﬁgured with a private subnet. An internet-facing Network Load Balancer (NLB) must be conﬁgured in public subnets in order to receive traﬃc. A public subnet is deﬁned as a subnet that has a direct route to an internet gateway. If the subnet is conﬁgured as private, then it’s Availability Zone (AZ) doesn’t receive traﬃc, which can cause availability issues. Fault tolerance API Version 2025-05-13 353 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfpnchv4 Alert Criteria Red: NLB is conﬁgured with one or more private subnets Green: No private subnet is conﬁgured for internet-facing NLB Recommended Action Conﬁrm that the subnets conﬁgured in an internet-facing load balancer are public. A public subnet is deﬁned as a subnet that has a direct route to an internet gateway. Use one of following options: • Create a new load balancer and select a diﬀerent subnet with a direct route to an internet gateway. • Change the subnet that’s currently attached to the load balancer from private to public. To do this, change its route table and associate an internet gateway. Additional Resources • Conﬁgure a load balancer and a listener • Subnets for your VPC • Associate a gateway with a route table Report columns • Status • Region • NLB Arn • NLB Name Fault tolerance API Version 2025-05-13 354 AWS Support • Subnet ID • NLB Scheme • Subnet Type • Last Updated Time NLB Multi-AZ Description User Guide Checks if your Network Load Balancers are conﬁgured to use more than one Availability Zone (AZ). An AZ is a distinct location that is insulated from failures in other zones. Conﬁgure your load balancer in multiple AZs in the same Region to help improve your workload availability. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfprch09 Alert Criteria Yellow: NLB is in a single AZ. Green: NLB has two or more AZs. Recommended Action Make sure that your load balancer is conﬁgured with at least two Availability Zones. Additional Resources
support-ug-107	support-ug.pdf	107	the same Region to help improve your workload availability. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfprch09 Alert Criteria Yellow: NLB is in a single AZ. Green: NLB has two or more AZs. Recommended Action Make sure that your load balancer is conﬁgured with at least two Availability Zones. Additional Resources For more information, see the following documentation: • Availability Zones • AWS Well-Architected - Deploy the workload to multiple locations Fault tolerance API Version 2025-05-13 355 AWS Support User Guide • Regions and Availability Zones Report columns • Status • Region • Number of AZs • NLB ARN • NLB Name • Last Updated Time Number of AWS Regions in an Incident Manager replication set Description Checks that an Incident Manager replication set’s conﬁguration uses more than one AWS Region to support regional failover and response. For incidents created by CloudWatch alarms or EventBridge events, Incident Manager creates an incident in the same AWS Region as the alarm or event rule. If Incident Manager is temporarily unavailable in that Region, the system attempts to create an incident in another Region in the replication set. If the replication set includes only one Region, the system fails to create an incident record while Incident Manager is unavailable. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID cIdfp1js9r Alert Criteria • Green: The replication set contains more than one Region. • Yellow: The replication set contains one Region. Fault tolerance API Version 2025-05-13 356 AWS Support Recommended Action User Guide Add at least one more Region to the replication set. Additional Resources For more information, see Cross-region Incident management. Report columns • Status • Multi-region • Replication Set • Last Updated Time Single AZ Application Check Description Checks through network patterns if your egress network traﬃc is routing through a single Availability Zone (AZ). An AZ is a distinct location that is insulated from any impact in other zones. By spreading your service across multiple AZs, you limit the blast radius of an AZ failure. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1dfptbg11 Alert Criteria • Yellow: Your application may be deployed in only one AZ based on observed egress network patterns. If this is true and your application expects high availability, we recommend that you Fault tolerance API Version 2025-05-13 357 AWS Support User Guide provision your application resources and implement your network ﬂows to utilize multiple Availability Zones. Recommended Action If your application requires high availability, consider implementing a multi-AZ architecture for higher availability. Report columns • Status • Region • VPC ID • Last Updated Time VPC interface endpoint network interfaces in multiple AZs Description Checks if your AWS PrivateLink VPC interface endpoints are conﬁgured to use more than one Availability Zone (AZ). An AZ is a distinct location that is insulated from failures in other zones. This supports inexpensive, low-latency network connectivity between AZs in the same AWS Region. Select subnets in multiple AZs when you create interface endpoints to help protect your applications from a single point of failure. Note This check currently includes only interface endpoints. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 358 AWS Support Check ID c1dfprch10 Alert Criteria Yellow: VPC endpoint is in a single AZ. Green: VPC endpoint is in at least two AZs. Recommended Action User Guide Make sure that your VPC interface endpoint is conﬁgured with at least two Availability Zones. Additional Resources For more information, see the following documentation: • Access an AWS service using an interface VPC endpoint • Private IP address of the endpoint network interface • AWS PrivateLink concepts • Regions and Availability Zones Report columns • Status •
support-ug-108	support-ug.pdf	108	one or more resources from your Trusted Advisor results. Fault tolerance API Version 2025-05-13 358 AWS Support Check ID c1dfprch10 Alert Criteria Yellow: VPC endpoint is in a single AZ. Green: VPC endpoint is in at least two AZs. Recommended Action User Guide Make sure that your VPC interface endpoint is conﬁgured with at least two Availability Zones. Additional Resources For more information, see the following documentation: • Access an AWS service using an interface VPC endpoint • Private IP address of the endpoint network interface • AWS PrivateLink concepts • Regions and Availability Zones Report columns • Status • Region • VPC Endpoint ID • Is Multi AZ • Last Updated Time VPN Tunnel Redundancy Description Checks the number of tunnels that are active for each of your Site-to-Site VPNs. A VPN should have two tunnels conﬁgured at all times. This provides redundancy in case of outage or planned maintenance of the devices at the AWS endpoint. For some hardware, only one tunnel is active at a time. If a VPN has no active tunnels, charges for the VPN might still apply. For more information, see AWS Site-to-Site VPN User Guide. Fault tolerance API Version 2025-05-13 359 AWS Support Check ID S45wrEXrLz Alert Criteria User Guide • Yellow: A VPN has one active tunnel (this is normal for some hardware). • Yellow: A VPN has no active tunnels. Recommended Action Be sure that two tunnels are conﬁgured for your VPN connection, and that both are active if your hardware supports it. If you no longer need a VPN connection, you can delete it to avoid charges. For more information, see Your customer gateway device or Delete a Site-to-Site VPN connection. Additional Resources • AWS Site-to-Site VPN User Guide • Create a target gateway Report columns • Status • Region • VPN ID • VPC • Virtual Private Gateway • Customer Gateway • Active Tunnels • Reason ActiveMQ Availability Zone Redundancy Description Checks that Amazon MQ for ActiveMQ brokers are conﬁgured for high availability with an active/standby broker in multiple Availability Zones. Fault tolerance API Version 2025-05-13 360 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1t3k8mqv1 Alert Criteria • Yellow: An Amazon MQ for ActiveMQ broker is conﬁgured in a single Availability Zone. Green: An Amazon MQ for ActiveMQ broker is conﬁgured in at least two Availability Zones. Recommended Action Create a new broker with active/standby deployment mode. Additional Resources • Creating an ActiveMQ broker Report columns • Status • Region • ActiveMQ Broker ID • Broker Engine Type • Deployment Mode • Last Updated Time RabbitMQ Availability Zone Redundancy Description Checks that Amazon MQ for RabbitMQ brokers are conﬁgured for high availability with cluster instances in multiple Availability Zones. Fault tolerance API Version 2025-05-13 361 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c1t3k8mqv2 Alert Criteria • Yellow: An Amazon MQ for RabbitMQ broker is conﬁgured in a single Availability Zone. Green: An Amazon MQ for RabbitMQ broker is conﬁgured in multiple Availability Zones. Recommended Action Create a new broker with the cluster deployment mode. Additional Resources • Creating a RabbitMQ broker Report columns • Status • Region • RabbitMQ Broker ID • Broker Engine Type • Deployment Mode • Last Updated Time Service limits See the following checks for the service limits (also known as quotas) category. All checks in this category have the following descriptions: Service limits API Version 2025-05-13 362 AWS Support Alert Criteria • Yellow: 80% of limit reached. • Red: 100% of limit reached. User Guide • Blue: Trusted Advisor was unable to retrieve utilization or limits in one or more AWS Regions. Recommended Action If you expect to exceed a service limit, request an increase directly from the Service Quotas console. If Service Quotas doesn’t support your service yet, you can open a support case in Support Center. Report columns • Status • Service • Region • Limit Amount • Current Usage Note • Values are based on a snapshot, so your current usage might diﬀer. Quota and usage data can take up to 24 hours to reﬂect any changes. In cases where quotas have been recently increased, you might temporarily see utilization that exceeds the quota. Check
support-ug-109	support-ug.pdf	109	or more AWS Regions. Recommended Action If you expect to exceed a service limit, request an increase directly from the Service Quotas console. If Service Quotas doesn’t support your service yet, you can open a support case in Support Center. Report columns • Status • Service • Region • Limit Amount • Current Usage Note • Values are based on a snapshot, so your current usage might diﬀer. Quota and usage data can take up to 24 hours to reﬂect any changes. In cases where quotas have been recently increased, you might temporarily see utilization that exceeds the quota. Check names • Auto Scaling Groups • Auto Scaling Launch Conﬁgurations • CloudFormation Stacks • DynamoDB Read Capacity • DynamoDB Write Capacity • EBS Active Snapshots • EBS Cold HDD (sc1) Volume Storage • EBS General Purpose SSD (gp2) Volume Storage Service limits API Version 2025-05-13 363 AWS Support User Guide • EBS General Purpose SSD (gp3) Volume Storage • EBS Magnetic (standard) Volume Storage • EBS Provisioned IOPS SSD (io1) Volume Aggregate IOPS • EBS Provisioned IOPS SSD (io1) Volume Storage • EBS Provisioned IOPS SSD (io2) Volume Storage • EBS Throughput Optimized HDD (st1) Volume Storage • EC2 On-Demand Instances • EC2 Reserved Instance Leases • EC2-Classic Elastic IP Addresses • EC2-VPC Elastic IP Address • ELB Application Load Balancers • ELB Classic Load Balancers • ELB Network Load Balancers • IAM Group • IAM Instance Proﬁles • IAM Policies • IAM Roles • IAM Server Certiﬁcates • IAM Users • Kinesis Shards per Region • Lambda Code Storage Usage • RDS Cluster Parameter Groups • RDS Cluster Roles • RDS Clusters • RDS DB Instances • RDS DB Manual Snapshots • RDS DB Parameter Groups • RDS DB Security Groups • RDS Event Subscriptions • RDS Max Auths per Security Group Service limits API Version 2025-05-13 364 User Guide AWS Support • RDS Option Groups • RDS Read Replicas per Master • RDS Reserved Instances • RDS Subnet Groups • RDS Subnets per Subnet Group • RDS Total Storage Quota • Route 53 Hosted Zones • Route 53 Max Health Checks • Route 53 Reusable Delegation Sets • Route 53 Traﬃc Policies • Route 53 Traﬃc Policy Instances • SES Daily Sending Quota • VPC • VPC Internet Gateways Auto Scaling Groups Description Checks for usage that is more than 80% of the Auto Scaling Groups quota. Check ID fW7HH0l7J9 Additional Resources Auto Scaling quotas Auto Scaling Launch Conﬁgurations Description Checks for usage that is more than 80% of the Auto Scaling launch conﬁgurations quota. Check ID aW7HH0l7J9 Service limits API Version 2025-05-13 365 AWS Support Additional Resources Auto Scaling quotas CloudFormation Stacks Description Checks for usage that is more than 80% of the CloudFormation stacks quota. User Guide Check ID gW7HH0l7J9 Additional Resources AWS CloudFormation quotas DynamoDB Read Capacity Description Checks for usage that is more than 80% of the DynamoDB provisioned throughput limit for reads per AWS account. Check ID 6gtQddfEw6 Additional Resources DynamoDB quotas DynamoDB Write Capacity Description Checks for usage that is more than 80% of the DynamoDB provisioned throughput limit for writes per AWS account. Check ID c5ftjdfkMr Service limits API Version 2025-05-13 366 AWS Support Additional Resources DynamoDB quotas EBS Active Snapshots Description User Guide Checks for usage that is more than 80% of the EBS active snapshots quota. Check ID eI7KK0l7J9 Additional Resources Amazon EBS limits EBS Cold HDD (sc1) Volume Storage Description Checks for usage that is more than 80% of the EBS Cold HDD (sc1) volume storage quota. Check ID gH5CC0e3J9 Additional Resources Amazon EBS limits EBS General Purpose SSD (gp2) Volume Storage Description Checks for usage that is more than 80% of the EBS General Purpose SSD (gp2) volume storage quota. Check ID dH7RR0l6J9 Service limits API Version 2025-05-13 367 AWS Support Additional Resources Amazon EBS limits User Guide EBS General Purpose SSD (gp3) Volume Storage Description Checks for usage that is more than 80% of the EBS General Purpose SSD (gp3) volume storage quota. Check ID dH7RR0l6J3 Additional Resources Amazon EBS limits EBS Magnetic (standard) Volume Storage Description Checks for usage that is more than 80% of the EBS Magnetic (standard) volume storage quota. Check ID cG7HH0l7J9 Additional Resources Amazon EBS limits EBS Provisioned IOPS SSD (io1) Volume Aggregate IOPS Description Checks for usage that is more than 80% of the EBS Provisioned IOPS SSD (io1) volume aggregate IOPS quota. Check ID tV7YY0l7J9 Service limits API Version 2025-05-13 368 AWS Support Additional Resources Amazon EBS limits User Guide EBS Provisioned IOPS SSD (io1) Volume Storage Description Checks for usage that is more than 80% of the EBS Provisioned IOPS SSD (io1) volume storage quota. Check ID gI7MM0l7J9 Additional Resources Amazon EBS limits EBS Provisioned IOPS SSD (io2) Volume Storage Description Checks for usage that is more than
support-ug-110	support-ug.pdf	110	Additional Resources Amazon EBS limits EBS Provisioned IOPS SSD (io1) Volume Aggregate IOPS Description Checks for usage that is more than 80% of the EBS Provisioned IOPS SSD (io1) volume aggregate IOPS quota. Check ID tV7YY0l7J9 Service limits API Version 2025-05-13 368 AWS Support Additional Resources Amazon EBS limits User Guide EBS Provisioned IOPS SSD (io1) Volume Storage Description Checks for usage that is more than 80% of the EBS Provisioned IOPS SSD (io1) volume storage quota. Check ID gI7MM0l7J9 Additional Resources Amazon EBS limits EBS Provisioned IOPS SSD (io2) Volume Storage Description Checks for usage that is more than 80% of the EBS Provisioned IOPS SSD (io2) volume storage quota. Check ID gI7MM0l7J2 Additional Resources Amazon EBS limits EBS Throughput Optimized HDD (st1) Volume Storage Description Checks for usage that is more than 80% of the EBS Throughput Optimized HDD (st1) volume storage quota. Check ID wH7DD0l3J9 Service limits API Version 2025-05-13 369 AWS Support Additional Resources Amazon EBS limits EC2 On-Demand Instances Description Checks for usage that is more than 80% of the EC2 On-Demand Instances quota. User Guide Check ID 0Xc6LMYG8P Additional Resources Amazon EC2 quotas EC2 Reserved Instance Leases Description Checks for usage that is more than 80% of the EC2 Reserved Instance leases quota. Check ID iH7PP0l7J9 Additional Resources Amazon EC2 quotas EC2-Classic Elastic IP Addresses Description Checks for usage that is more than 80% of the EC2-Classic Elastic IP addresses quota. Check ID aW9HH0l8J6 Additional Resources Amazon EC2 quotas Service limits API Version 2025-05-13 370 AWS Support EC2-VPC Elastic IP Address Description User Guide Checks for usage that is more than 80% of the EC2-VPC Elastic IP address quota. Check ID lN7RR0l7J9 Additional Resources VPC Elastic IP quotas ELB Application Load Balancers Description Checks for usage that is more than 80% of the ELB Application Load Balancers quota. Check ID EM8b3yLRTr Additional Resources Elastic Load Balancing quotas ELB Classic Load Balancers Description Checks for usage that is more than 80% of the ELB Classic Load Balancers quota. Check ID iK7OO0l7J9 Additional Resources Elastic Load Balancing quotas Service limits API Version 2025-05-13 371 AWS Support User Guide ELB Network Load Balancers Description Checks for usage that is more than 80% of the ELB Network Load Balancers quota. Check ID 8wIqYSt25K Additional Resources Elastic Load Balancing quotas IAM Group Description Checks for usage that is more than 80% of the IAM group quota. Check ID sU7XX0l7J9 Additional Resources IAM quotas IAM Instance Proﬁles Description Checks for usage that is more than 80% of the IAM instance proﬁles quota. Check ID nO7SS0l7J9 Additional Resources IAM quotas Service limits API Version 2025-05-13 372 AWS Support IAM Policies Description Checks for usage that is more than 80% of the IAM policies quota. User Guide Check ID pR7UU0l7J9 Additional Resources IAM quotas IAM Roles Description Checks for usage that is more than 80% of the IAM roles quota. Check ID oQ7TT0l7J9 Additional Resources IAM quotas IAM Server Certiﬁcates Description Checks for usage that is more than 80% of the IAM server certiﬁcates quota. Check ID rT7WW0l7J9 Additional Resources IAM quotas Service limits API Version 2025-05-13 373 AWS Support IAM Users Description Checks for usage that is more than 80% of the IAM users quota. User Guide Check ID qS7VV0l7J9 Additional Resources IAM quotas Kinesis Shards per Region Description Checks for usage that is more than 80% of the Kinesis shards per Region quota. Check ID bW7HH0l7J9 Additional Resources Kinesis quotas Lambda Code Storage Usage Description Checks for code storage usage that is more than 80% of the account limit. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Service limits API Version 2025-05-13 374 AWS Support Check ID c1dfprch07 Alert Criteria • Yellow: 80% of limit reached. Recommended Action User Guide Please identify unused lambda functions or versions and remove them to free up the code storage for your account in the region. If you need additional storage, please create a support case in Support Center. If you expect to exceed a service limit, request an increase directly from the Service Quotas console. If Service Quotas doesn’t support your service yet, you can open a support case in Support Center. Additional Resources • Lambda Code Storage Usage Report columns • Status • Region • The qualiﬁed function ARN for this resource. • The function code storage usage in MegaBytes with 2 decimals. • The amount of versions in the function • Last Updated Time RDS Cluster Parameter Groups Description Checks for usage that is more than 80% of the RDS cluster parameter groups quota. Check
support-ug-111	support-ug.pdf	111	Center. If you expect to exceed a service limit, request an increase directly from the Service Quotas console. If Service Quotas doesn’t support your service yet, you can open a support case in Support Center. Additional Resources • Lambda Code Storage Usage Report columns • Status • Region • The qualiﬁed function ARN for this resource. • The function code storage usage in MegaBytes with 2 decimals. • The amount of versions in the function • Last Updated Time RDS Cluster Parameter Groups Description Checks for usage that is more than 80% of the RDS cluster parameter groups quota. Check ID jtlIMO3qZM Additional Resources Amazon RDS quotas Service limits API Version 2025-05-13 375 AWS Support RDS Cluster Roles Description Checks for usage that is more than 80% of the RDS cluster roles quota. User Guide Check ID 7fuccf1Mx7 Additional Resources Amazon RDS quotas RDS Clusters Description Checks for usage that is more than 80% of the RDS clusters quota. Check ID gjqMBn6pjz Additional Resources Amazon RDS quotas RDS DB Instances Description Checks for usage that is more than 80% of the RDS DB instances quota. Check ID XG0aXHpIEt Additional Resources Amazon RDS quotas Service limits API Version 2025-05-13 376 AWS Support RDS DB Manual Snapshots Description User Guide Checks for usage that is more than 80% of the RDS DB manual snapshots quota. Check ID dV84wpqRUs Additional Resources Amazon RDS quotas RDS DB Parameter Groups Description Checks for usage that is more than 80% of the RDS DB parameter groups quota. Check ID jEECYg2YVU Additional Resources Amazon RDS quotas RDS DB Security Groups Description Checks for usage that is more than 80% of the RDS DB security groups quota. Check ID gfZAn3W7wl Additional Resources Amazon RDS quotas Service limits API Version 2025-05-13 377 AWS Support RDS Event Subscriptions Description User Guide Checks for usage that is more than 80% of the RDS event subscriptions quota. Check ID keAhfbH5yb Additional Resources Amazon RDS quotas RDS Max Auths per Security Group Description Checks for usage that is more than 80% of the RDS max auths per security group quota. Check ID dBkuNCvqn5 Additional Resources Amazon RDS quotas RDS Option Groups Description Checks for usage that is more than 80% of the RDS option groups quota. Check ID 3Njm0DJQO9 Additional Resources Amazon RDS quotas Service limits API Version 2025-05-13 378 AWS Support User Guide RDS Read Replicas per Master Description Checks for usage that is more than 80% of the RDS read replicas per master quota. Check ID pYW8UkYz2w Additional Resources Amazon RDS quotas RDS Reserved Instances Description Checks for usage that is more than 80% of the RDS Reserved Instances quota. Check ID UUDvOa5r34 Additional Resources Amazon RDS quotas RDS Subnet Groups Description Checks for usage that is more than 80% of the RDS subnet groups quota. Check ID dYWBaXaaMM Additional Resources Amazon RDS quotas Service limits API Version 2025-05-13 379 AWS Support User Guide RDS Subnets per Subnet Group Description Checks for usage that is more than 80% of the RDS subnets per subnet group quota. Check ID jEhCtdJKOY Additional Resources Amazon RDS quotas RDS Total Storage Quota Description Checks for usage that is more than 80% of the RDS total storage quota. Check ID P1jhKWEmLa Additional Resources Amazon RDS quotas Route 53 Hosted Zones Description Checks for usage that is more than 80% of the Route 53 hosted zones quota per account. Check ID dx3xfcdfMr Additional Resources Route 53 quotas Service limits API Version 2025-05-13 380 AWS Support User Guide Route 53 Max Health Checks Description Checks for usage that is more than 80% of the Route 53 health checks quota per account. Check ID ru4xfcdfMr Additional Resources Route 53 quotas Route 53 Reusable Delegation Sets Description Checks for usage that is more than 80% of the Route 53 reusable delegation sets quota per account. Check ID ty3xfcdfMr Additional Resources Route 53 quotas Route 53 Traﬃc Policies Description Checks for usage that is more than 80% of the Route 53 traﬃc policies quota per account. Check ID dx3xfbjfMr Additional Resources Route 53 quotas Service limits API Version 2025-05-13 381 AWS Support User Guide Route 53 Traﬃc Policy Instances Description Checks for usage that is more than 80% of the Route 53 traﬃc policy instances quota per account. Check ID dx8afcdfMr Additional Resources Route 53 quotas SES Daily Sending Quota Description Checks for usage that is more than 80% of the Amazon SES daily sending quota. Check ID hJ7NN0l7J9 Additional Resources Amazon SES quotas VPC Description Checks for usage that is more than 80% of the VPC quota. Check ID jL7PP0l7J9 Additional Resources VPC quotas Service limits API Version 2025-05-13 382 AWS Support VPC Internet Gateways Description User Guide Checks for usage that is more than 80% of the VPC Internet gateways quota. Check ID kM7QQ0l7J9 Additional Resources VPC quotas Operational
support-ug-112	support-ug.pdf	112	53 traﬃc policy instances quota per account. Check ID dx8afcdfMr Additional Resources Route 53 quotas SES Daily Sending Quota Description Checks for usage that is more than 80% of the Amazon SES daily sending quota. Check ID hJ7NN0l7J9 Additional Resources Amazon SES quotas VPC Description Checks for usage that is more than 80% of the VPC quota. Check ID jL7PP0l7J9 Additional Resources VPC quotas Service limits API Version 2025-05-13 382 AWS Support VPC Internet Gateways Description User Guide Checks for usage that is more than 80% of the VPC Internet gateways quota. Check ID kM7QQ0l7J9 Additional Resources VPC quotas Operational Excellence You can use the following checks for the operational excellence category. Check names • Amazon API Gateway Not Logging Execution Logs • Amazon API Gateway REST APIs Without X-Ray Tracing Enabled • Amazon CloudFront Access Log Conﬁgured • Amazon CloudWatch Alarm Action is Disabled • Amazon EC2 Instance Not Managed by AWS Systems Manager • Amazon ECR Repository With Tag Immutability Disabled • Amazon ECS clusters with Container Insights disabled • Amazon ECS task logging not enabled • Amazon OpenSearch Service logging CloudWatch not conﬁgured • Amazon RDS DB instances in the clusters with heterogeneous parameter groups • Amazon RDS Enhanced Monitoring is turned oﬀ • Amazon RDS Performance Insights is turned oﬀ • Amazon RDS track_counts parameter is turned oﬀ • Amazon Redshift cluster audit logging • Amazon S3 Access Logs Enabled • Amazon S3 does not have Event Notiﬁcations enabled Operational Excellence API Version 2025-05-13 383 AWS Support User Guide • Amazon SNS Topics Not Logging Message Delivery Status • Amazon VPC Without Flow Logs • Application Load Balancers and Classic Load Balancers Without Access Logs Enabled • AWS CloudFormation Stack Notiﬁcation • AWS CloudTrail data events logging for objects in an S3 bucket • AWS CodeBuild Project Logging • AWS CodeDeploy Auto Rollback and Monitor Enabled • AWS CodeDeploy Lambda is using all-at-once deployment conﬁguration • AWS Elastic Beanstalk Enhanced Health Reporting is not Conﬁgured • AWS Elastic Beanstalk with Managed Platform Updates Disabled • AWS Fargate platform version is not latest • AWS Systems Manager State Manager Association in Non-compliant Status • CloudTrail trails are not conﬁgured with Amazon CloudWatch Logs • Elastic Load Balancing Deletion Protection Not Enabled for Load Balancers • RDS DB Cluster Deletion Protection Check • RDS DB Instance Automatic Minor Version Upgrade Check Amazon API Gateway Not Logging Execution Logs Description Checks if Amazon API Gateway has CloudWatch Logs turned on at the desired logging level. Turn on CloudWatch logging for REST API methods or WebSocket API routes in Amazon API Gateway to collect execution logs in CloudWatch Logs for requests received by your APIs. The information contained in the execution logs helps identify and troubleshoot issues related to your API. You can specify the logging level (ERROR, INFO) ID in the loggingLevel parameter in the AWS Conﬁg rules. Refer to the REST API or WebSocket API documentation for more information about CloudWatch logging in Amazon API Gateway. Operational Excellence API Version 2025-05-13 384 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz125 Source AWS Config Managed Rule: api-gw-execution-logging-enabled Alert Criteria Yellow: The CloudWatch logging setting for execution log collection isn't enabled at the desired logging level for an Amazon API Gateway. Recommended Action Turn on CloudWatch logging for execution logs for your Amazon API Gateway REST APIs or WebSocket APIs with the appropriate logging level (ERROR, INFO). For more information, see Create a ﬂow log Additional Resources • Setting up CloudWatch logging for a REST API in API Gateway • Conﬁguring logging for a WebSocket API Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Operational Excellence API Version 2025-05-13 385 AWS Support User Guide Amazon API Gateway REST APIs Without X-Ray Tracing Enabled Description Checks if Amazon API Gateway REST APIs have AWS X-Ray tracing turned on. Turn on X-Ray tracing for your REST APIs to allow API Gateway to sample API invocation requests with trace information. This allows you to take advantage of AWS X-Ray to trace and analyze requests as they travel through your API Gateway REST APIs to the downstream services. For more information, see Tracing user requests to REST APIs using X-Ray. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion
support-ug-113	support-ug.pdf	113	on. Turn on X-Ray tracing for your REST APIs to allow API Gateway to sample API invocation requests with trace information. This allows you to take advantage of AWS X-Ray to trace and analyze requests as they travel through your API Gateway REST APIs to the downstream services. For more information, see Tracing user requests to REST APIs using X-Ray. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz126 Source AWS Config Managed Rule: api-gw-xray-enabled Alert Criteria Yellow: X-Ray tracing is not turned on for an API Gateway REST API. Recommended Action Turn on X-Ray tracing for your API Gateway REST APIs. For more information, see Setting up AWS X-Ray with API Gateway REST APIs. Additional Resources • Tracing user requests to REST APIs using X-Ray Operational Excellence API Version 2025-05-13 386 User Guide AWS Support • What is AWS X-Ray? Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon CloudFront Access Log Conﬁgured Description Checks if Amazon CloudFront distributions are conﬁgured to capture information from Amazon S3 server access logs. Amazon S3 server access logs contain detailed information about every user request that CloudFront receives. You can adjust the the name of the Amazon S3 bucket for storing server access logs, using the S3BucketName parameter in your AWS Conﬁg rules. For more information, see Conﬁguring and using standard logs (access logs). Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz110 Source AWS Config Managed Rule: cloudfront-accesslogs-enabled Operational Excellence API Version 2025-05-13 387 AWS Support Alert Criteria Yellow: Amazon CloudFront access logging is not enabled Recommended Action User Guide Make sure that you turn on CloudFront access logging to capture detailed information about every user request that CloudFront receives. You can turn on standard logs when you create or update a distribution. For more information, see Values that you specify when you create or update a distribution. Additional Resources • Values that you specify when you create or update a distribution • Conﬁguring and using standard logs (access logs) Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon CloudWatch Alarm Action is Disabled Description Checks if your Amazon CloudWatch alarm action is in a disabled state. You can use the AWS CLI to enable or disable the action feature in your alarm. Or, you can programatically disable or enable the action feature using the AWS SDK. When the alarm action feature is turned oﬀ, CloudWatch doesn't perform any deﬁned action in any state (OK, INSUFFICIENT_DATA, ALARM). Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Operational Excellence API Version 2025-05-13 388 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz109 Source AWS Config Managed Rule: cloudwatch-alarm-action-enabled-check Alert Criteria Yellow: Amazon CloudWatch alarm action is not enabled. No action is performed in any alarm state. Recommended Action Enable actions in your CloudWatch alarms unless you have a valid reason to disable them, such as for testing purposes. If the CloudWatch alarm is no longer needed, delete it to avoid incurring unnecessary costs. For more information, see enable-alarm-actions in the AWS CLI Command Reference and func (*CloudWatch) EnableAlarmActions in the AWS SDK for Go API Reference. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon EC2 Instance Not Managed by AWS Systems Manager Description Checks if the Amazon EC2 instances in your account are managed by AWS Systems Manager. Operational Excellence API Version 2025-05-13 389 AWS Support User Guide Systems Manager helps you understand and control the current state of your Amazon EC2 instance and OS conﬁgurations. With Systems Manager, you can collect software conﬁguration and inventory information about your ﬂeet of instances, including the software installed on them. This allows you to track detailed system conﬁguration, OS patch levels, application conﬁgurations, and other details about your deployment. For more information, see Setting up Systems Manager for EC2 instances. Note
support-ug-114	support-ug.pdf	114	AWS Systems Manager Description Checks if the Amazon EC2 instances in your account are managed by AWS Systems Manager. Operational Excellence API Version 2025-05-13 389 AWS Support User Guide Systems Manager helps you understand and control the current state of your Amazon EC2 instance and OS conﬁgurations. With Systems Manager, you can collect software conﬁguration and inventory information about your ﬂeet of instances, including the software installed on them. This allows you to track detailed system conﬁguration, OS patch levels, application conﬁgurations, and other details about your deployment. For more information, see Setting up Systems Manager for EC2 instances. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz145 Source AWS Config Managed Rule: ec2-instance-managed-by-systems-manager Alert Criteria Yellow: The Amazon EC2 instances are not managed by Systems Manager. Recommended Action Conﬁgure your Amazon EC2 instance to be managed by Systems Manager. This check can't be excluded from view in the Trusted Advisor console. For more information, see Why is my EC2 instance not displaying as a managed node or showing a "Connection lost" status in Systems Manager?. Additional Resources Setting up Systems Manager for EC2 instances Report columns • Status Operational Excellence API Version 2025-05-13 390 AWS Support • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon ECR Repository With Tag Immutability Disabled Description Checks if a private Amazon ECR repository has image tag immutability turned on. Turn on image tag immutability for a private Amazon ECR repository to prevent image tags from being overwritten. This allows you to rely on descriptive tags as a reliable mechanism to track and uniquely identify images.For example, if image tag immutability is turned on, then users can reliably use an image tag to correlate a deployed image version with the build that produced such image. For more information, see Image tag mutability. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz129 Source AWS Config Managed Rule: ecr-private-tag-immutability-enabled Alert Criteria Yellow: An Amazon ECR private repository doesn’t have tag immutability turned on. Operational Excellence API Version 2025-05-13 391 AWS Support Recommended Action User Guide Turn on image tag immutability for your Amazon ECR private repositories. For more information, see Image tag mutability. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon ECS clusters with Container Insights disabled Description Checks if Amazon CloudWatch Container Insights is turned on for your Amazon ECS clusters. CloudWatch Container Insights collects, aggregates, and summarizes metrics and logs from your containerized applications and microservices. The metrics include utilization for resources such as CPU, memory, disk, and network. For more information, see Amazon ECS CloudWatch Container Insights. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz173 Operational Excellence API Version 2025-05-13 392 AWS Support Source User Guide AWS Config Managed Rule: ecs-container-insights-enabled Alert Criteria Yellow: Amazon ECS cluster does not have container insights enabled. Recommended Action Turn on CloudWatch Container Insights on your Amazon ECS clusters. For more information, see Using Container Insights. Additional Resources Amazon ECS CloudWatch Container Insights Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon ECS task logging not enabled Description Checks if log conﬁguration is set on active Amazon ECS task deﬁnitions. Checking the log conﬁguration in your Amazon ECS task deﬁnitions makes sure that logs generated by containers are properly conﬁgured and stored. This helps identify and troubleshoot issues more quickly, optimize performance, and meet compliance requirements. By default, the logs that are captured show the command output that you typically see in an interactive terminal if you ran the container locally. The awslogs driver passes these logs from Docker to Amazon CloudWatch Logs. For more information, see Using the awslogs log driver. Operational Excellence API Version 2025-05-13 393 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It
support-ug-115	support-ug.pdf	115	makes sure that logs generated by containers are properly conﬁgured and stored. This helps identify and troubleshoot issues more quickly, optimize performance, and meet compliance requirements. By default, the logs that are captured show the command output that you typically see in an interactive terminal if you ran the container locally. The awslogs driver passes these logs from Docker to Amazon CloudWatch Logs. For more information, see Using the awslogs log driver. Operational Excellence API Version 2025-05-13 393 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz175 Source AWS Config Managed Rule: ecs-task-definition-log-configuration Alert Criteria Yellow: Amazon ECS task deﬁnition does not have a logging conﬁguration. Recommended Action Consider specifying the log driver conﬁguration in container deﬁnition to send log information to CloudWatch Logs or a diﬀerent logging driver. For more information, see LogConﬁguration. Additional Resources Consider specifying the log driver conﬁguration in container deﬁnition to send log information to CloudWatch Logs or a diﬀerent logging driver. For more information, see Example task deﬁnitions. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Operational Excellence API Version 2025-05-13 394 AWS Support User Guide Amazon OpenSearch Service logging CloudWatch not conﬁgured Description Checks if Amazon OpenSearch Service domains are conﬁgured to send logs to Amazon CloudWatch Logs. Monitoring logs is crucial for maintaining the reliability, availability, and performance of OpenSearch Service. Search slow logs, indexing slow logs, and error logs are useful for troubleshooting performance and stability issues your workload. These logs need to be enabled to capture data. You can specify which log types that you want to ﬁlter (error, search, index) using the logTypes parameter in your AWS Conﬁg rules. For more information, see Monitoring Amazon OpenSearch Service domains. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz184 Source AWS Config Managed Rule: opensearch-logs-to-cloudwatch Alert Criteria Yellow: Amazon OpenSearch Service does not have a logging conﬁguration with Amazon CloudWatch Logs Recommended Action Conﬁgure OpenSearch Service domains to publish logs to CloudWatch Logs. Operational Excellence API Version 2025-05-13 395 AWS Support User Guide For more information, see Enabling log publishing (console). Additional Resources • Monitoring OpenSearch Service cluster metrics with Amazon CloudWatch Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon RDS DB instances in the clusters with heterogeneous parameter groups Description We recommend that all of the DB instances in the DB cluster use the same DB parameter group. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Operational Excellence API Version 2025-05-13 396 AWS Support Check ID c1qf5bt010 Alert Criteria User Guide Yellow: DB clusters have the DB instances with heterogeneous parameter groups. Recommended Action Associate the DB instance with the DB parameter group associated with the writer instance in your DB cluster. Additional Resources When the DB instances in your DB cluster use diﬀerent DB parameter groups, there can be an inconsistent behavior during a failover or compatibility issues between the DB instances in your DB cluster. For more information, see Working with parameter groups. Report columns • Status • Region • Resource • Recommended Value • Engine Name • Last Updated Time Amazon RDS Enhanced Monitoring is turned oﬀ Description Your database resources don't have Enhanced Monitoring turned on. Enhanced Monitoring provides real-time operating system metrics for monitoring and troubleshooting. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few
support-ug-116	support-ug.pdf	116	diﬀerent DB parameter groups, there can be an inconsistent behavior during a failover or compatibility issues between the DB instances in your DB cluster. For more information, see Working with parameter groups. Report columns • Status • Region • Resource • Recommended Value • Engine Name • Last Updated Time Amazon RDS Enhanced Monitoring is turned oﬀ Description Your database resources don't have Enhanced Monitoring turned on. Enhanced Monitoring provides real-time operating system metrics for monitoring and troubleshooting. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Operational Excellence API Version 2025-05-13 397 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt004 Alert Criteria Yellow: Amazon RDS resources don't have Enhanced Monitoring turned on. Recommended Action Turn on Enhanced Monitoring. Additional Resources Enhanced Monitoring for Amazon RDS provides additional visibility on the health of your DB instances. We recommend that you turn on Enhanced Monitoring. When the Enhanced Monitoring option is turned on for your DB instance, it collects vital operating system metrics and process information. For more information, see Monitoring OS metrics with Enhanced Monitoring. Report columns • Status • Region • Resource Operational Excellence API Version 2025-05-13 398 AWS Support User Guide • Recommended Value • Engine Name • Last Updated Time Amazon RDS Performance Insights is turned oﬀ Description Amazon RDS Performance Insights monitors your DB instance load to help you analyze and resolve database performance issues. We recommend that you turn on Performance Insights. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Note When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt012 Alert Criteria Yellow: Amazon RDS resources don't have Performance Insights turned on. Operational Excellence API Version 2025-05-13 399 AWS Support Recommended Action Turn on Performance Insights. Additional Resources User Guide Performance Insights uses a lightweight data collection method that doesn't impact the performance of your applications. Performance Insights helps you assess the database load quickly. For more information, see Monitoring DB load with Performance Insights on Amazon RDS. Report columns • Status • Region • Resource • Recommended Value • Engine Name • Last Updated Time Amazon RDS track_counts parameter is turned oﬀ Description When the track_counts parameter is turned oﬀ, the database doesn't collect the database activity statistics. Autovacuum requires these statistics to work correctly. We recommend that you set track_counts parameter to 1 Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Operational Excellence API Version 2025-05-13 400 AWS Support Note User Guide When a DB instance or DB cluster is stopped, you can view the Amazon RDS recommendations in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt027 Alert Criteria Yellow: DB parameter groups have track_counts parameter turned oﬀ. Recommended Action Set track_counts parameter to 1 Additional Resources When track_counts parameter is turned oﬀ, it disables the collection of database activity statistics. The autovacuum
support-ug-117	support-ug.pdf	117	in Trusted Advisor for 3 to 5 days. After ﬁve days, the recommendations are not available in Trusted Advisor. To view the recommendations, open the Amazon RDS console, and then choose Recommendations. If you delete a DB instance or DB cluster, then recommendations associated with those instances or clusters are not available in Trusted Advisor or the Amazon RDS management console. Check ID c1qf5bt027 Alert Criteria Yellow: DB parameter groups have track_counts parameter turned oﬀ. Recommended Action Set track_counts parameter to 1 Additional Resources When track_counts parameter is turned oﬀ, it disables the collection of database activity statistics. The autovacuum daemon requires the collected statistics to identify the tables for autovacuum and autoanalyze. For more information, see Run-time Statistics for PostgreSQL on the PostgreSQL documentation website. Report columns • Status • Region • Resource • Parameter Value • Recommended Value • Last Updated Time Operational Excellence API Version 2025-05-13 401 AWS Support User Guide Amazon Redshift cluster audit logging Description Checks if your Amazon Redshift clusters have database audit logging turned on. Amazon Redshift logs information about connections and user activities in your database. You can specify your desired logging Amazon S3 bucket name to match in the bucketNames parameter of your AWS Conﬁg rules. For more information, see Database audit logging. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz134 Source AWS Config Managed Rule: redshift-audit-logging-enabled Alert Criteria Yellow: An Amazon Redshift cluster has database audit logging disabled Recommended Action Turn on logging and monitoring for your Amazon Redshift clusters. For more information, see Conﬁguring auditing using the console. Additional Resources Logging and monitoring in Amazon Redshift Report columns • Status Operational Excellence API Version 2025-05-13 402 User Guide AWS Support • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon S3 Access Logs Enabled Description Checks the logging conﬁguration of Amazon Simple Storage Service buckets. Activating server access logging delivers detailed hourly access logs to a speciﬁed Amazon S3 bucket. Access logs contain request details including type, speciﬁed resources, and processing time/date. Logging is turned oﬀ by default. Customers should activate access logging to perform security audits or analyze user behavior and usage patterns. When logging is initially activated, the conﬁguration is automatically validated. However, future modiﬁcations can result in logging failures. Note that currently this check doesn’t examine Amazon S3 bucket write permissions. Check ID c1fd6b96l4 Alert Criteria • Yellow: The bucket does not have server access logging enabled. • Yellow: The target bucket permissions do not include the root account, so Trusted Advisor cannot check it. • Red: The target bucket does not exist. • Red: The target bucket and the source bucket have diﬀerent owners. • Green: Bucket has server access logging enabled, the target exists, and permissions to write to target exists Recommended Action Activate server access logging for all relevant Amazon S3 buckets. Server access logs provide an audit trail that can be used to understand bucket access patterns and investigate suspicious activity. Activating logging on all applicable buckets will improve visibility into access events Operational Excellence API Version 2025-05-13 403 AWS Support User Guide across your Amazon S3 environment. See Enabling Logging Using the Console and Enabling Logging Programmatically. If the target bucket permissions do not include the root account and you want Trusted Advisor to check the logging status, add the root account as a grantee. See Editing Bucket Permissions. If the target bucket does not exist, select an existing bucket as a target or create a new one and select it. See Managing Bucket Logging. If the target and source have diﬀerent owners, change the target bucket to one that has the same owner as the source bucket. See Managing Bucket Logging. Additional Resources Working with buckets Server access logging Server access log format Deleting log ﬁles Report columns • Status • Region • Resource ARN • Bucket Name • Target Name • Target Exists • Same Owner • Write Enabled • Reason • Last Updated Time Operational Excellence API Version 2025-05-13 404 AWS Support User Guide Amazon S3 does not have Event Notiﬁcations enabled Description Checks if Amazon S3 Event Notiﬁcations is enabled or is correctly conﬁgured with the desired destination or types. The Amazon S3 Event Notiﬁcations feature sends notiﬁcations when certain events happen in your Amazon S3 buckets. Amazon S3 can send notiﬁcation messages to Amazon SQS queues, Amazon SNS topics, and AWS Lambda functions. You can specify your desired destination and event types using the destinationArn and eventTypes parameters of your AWS
support-ug-118	support-ug.pdf	118	Same Owner • Write Enabled • Reason • Last Updated Time Operational Excellence API Version 2025-05-13 404 AWS Support User Guide Amazon S3 does not have Event Notiﬁcations enabled Description Checks if Amazon S3 Event Notiﬁcations is enabled or is correctly conﬁgured with the desired destination or types. The Amazon S3 Event Notiﬁcations feature sends notiﬁcations when certain events happen in your Amazon S3 buckets. Amazon S3 can send notiﬁcation messages to Amazon SQS queues, Amazon SNS topics, and AWS Lambda functions. You can specify your desired destination and event types using the destinationArn and eventTypes parameters of your AWS Conﬁg rules. For more information, see Amazon S3 Event Notiﬁcations. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz163 Source AWS Config Managed Rule: s3-event-notifications-enabled Alert Criteria Yellow: Amazon S3 does not have Event Notiﬁcations enabled, or not conﬁgured with the desired destination or types. Recommended Action Conﬁgure Amazon S3 Event Notﬁications for object and bucket events. For more information, see Enabling and conﬁguring event notiﬁcations using the Amazon S3 console. Operational Excellence API Version 2025-05-13 405 AWS Support Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide Amazon SNS Topics Not Logging Message Delivery Status Description Checks if Amazon SNS topics have message delivery status logging turned on. Conﬁgure Amazon SNS topics for logging message delivery status to help provide better operational insights. For example, message delivery logging veriﬁes if a message was delivered to a particular Amazon SNS endpoint. And, it also helps identify the response sent from the endpoint. For more information, see Amazon SNS message delivery status. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz121 Source AWS Config Managed Rule: sns-topic-message-delivery-notification-enabled Operational Excellence API Version 2025-05-13 406 AWS Support Alert Criteria User Guide Yellow: Message delivery status logging is not turned on for an Amazon SNS topic. Recommended Action Turn on message delivery status logging for your SNS topics. For more information, see Conﬁguring delivery status logging using the AWS Management Console. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Amazon VPC Without Flow Logs Description Checks if Amazon Virtual Private Cloud Flow Logs are created for a VPC. You can specify the traﬃc type using the traﬃcType parameter in your AWS Conﬁg rules. For more information, see Logging IP traﬃc using VPC Flow Logs. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz122 Operational Excellence API Version 2025-05-13 407 AWS Support Source User Guide AWS Config Managed Rule: vpc-flow-logs-enabled Alert Criteria Yellow: VPCs do not have Amazon VPC Flow Logs. Recommended Action Create VPC Flow Logs for each of your VPCs. For more information, see Create a ﬂow log Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Application Load Balancers and Classic Load Balancers Without Access Logs Enabled Description Checks if Application Load Balancers and Classic Load Balancers have access logging enabled. Elastic Load Balancing provides access logs that capture detailed information about requests sent to your load balancer. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. You can use these access logs to analyze traﬃc patterns and troubleshoot issues. Access logs are an optional feature of Elastic Load Balancing that is disabled by default. After you enable access logs for your load balancer, Elastic Load Balancing captures the logs and stores them in the Amazon S3 bucket that you specify. You can specify the access log Amazon S3 bucket that you want to check using the s3BucketNames parameter in your AWS Conﬁg rules. Operational Excellence API Version 2025-05-13 408 AWS Support User Guide For more information, see Access logs for your Application Load Balancer or Access logs for your Classic Load Balancer. Note Results for this check are automatically refreshed several
support-ug-119	support-ug.pdf	119	are an optional feature of Elastic Load Balancing that is disabled by default. After you enable access logs for your load balancer, Elastic Load Balancing captures the logs and stores them in the Amazon S3 bucket that you specify. You can specify the access log Amazon S3 bucket that you want to check using the s3BucketNames parameter in your AWS Conﬁg rules. Operational Excellence API Version 2025-05-13 408 AWS Support User Guide For more information, see Access logs for your Application Load Balancer or Access logs for your Classic Load Balancer. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz167 Source AWS Config Managed Rule: elb-logging-enabled Alert Criteria Yellow: Access logs feature not enabled for an Application Load Balancer or Classic Load Balancer. Recommended Action Enable access logs for your Application Load Balancers and Classic Load Balancers. For more information, see Enable access logs for your Application Load Balancer or Enable access logs for your Classic Load Balancer. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Operational Excellence API Version 2025-05-13 409 AWS Support User Guide AWS CloudFormation Stack Notiﬁcation Description Checks if all of your AWS CloudFormation stacks use Amazon SNS to receive notiﬁcations when an event occurs. You can conﬁgure this check to look for speciﬁc Amazon SNS topic ARNs using parameters in your AWS Conﬁg rules. For more information, see Setting AWS CloudFormationstack options. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz111 Source AWS Config Managed Rule: cloudformation-stack-notification-check Alert Criteria Yellow: Amazon SNS event notiﬁcations for your AWS CloudFormation stacks are not turned on. Recommended Action Make sure that your AWS CloudFormation stacks use Amazon SNS to receive notiﬁcations when an event occurs. Monitoring stack events helps you to respond quickly to unauthorized actions that might alter your AWS environment. Additional Resources How can I receive an email alert when my AWS CloudFormation stack enters ROLLBACK_IN_PROGRESS status? Operational Excellence API Version 2025-05-13 410 User Guide AWS Support Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time AWS CloudTrail data events logging for objects in an S3 bucket Description Checks if at least one AWS CloudTrail trail logs Amazon S3 data events for all of your Amazon S3 buckets. For more information, see Logging Amazon S3 API calls using AWS CloudTrail. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz166 Source AWS Config Managed Rule: cloudtrail-s3-dataevents-enabled Alert Criteria Yellow: AWS CloudTrail event logging for Amazon S3 buckets is not conﬁgured Operational Excellence API Version 2025-05-13 411 AWS Support Recommended Action User Guide Enable CloudTrail event logging for Amazon S3 buckets and objects to track requests for target bucket access. For more information, see Enabling CloudTrail event logging for S3 buckets and objects. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time AWS CodeBuild Project Logging Description Checks if the AWS CodeBuild project environment uses logging. Logging options can be logs in Amazon CloudWatch Logs, or built in a speciﬁed Amazon S3 bucket, or both. Enabling logging in a CodeBuild project can provide several beneﬁts such as debugging and auditing. You can specify the name of the Amazon S3 bucket or CloudWatch Logs group for storing the logs, using the s3BucketNames or cloudWatchGroupNames parameter in your AWS Conﬁg rules. For more information, see Monitoring AWS CodeBuild. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Operational Excellence API Version 2025-05-13 412 AWS Support Check ID c18d2gz113 Source User Guide AWS Config Managed Rule: codebuild-project-logging-enabled Alert Criteria Yellow: AWS CodeBuild project logging is not enabled. Recommended Action Make sure
support-ug-120	support-ug.pdf	120	parameter in your AWS Conﬁg rules. For more information, see Monitoring AWS CodeBuild. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Operational Excellence API Version 2025-05-13 412 AWS Support Check ID c18d2gz113 Source User Guide AWS Config Managed Rule: codebuild-project-logging-enabled Alert Criteria Yellow: AWS CodeBuild project logging is not enabled. Recommended Action Make sure that logging is turned on in your AWS CodeBuild project. This check can't be excluded from view in the AWS Trusted Advisor console. For more information, see Logging and monitoring in AWS CodeBuild. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time AWS CodeDeploy Auto Rollback and Monitor Enabled Description Checks if the deployment group is conﬁgured with automatic deployment rollback and deployment monitoring with alarms attached. If something goes wrong during a deployment, it is automatically rolled back, and your application remains in a stable state For more information, see Redeploy and roll back a deployment with CodeDeploy. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. Operational Excellence API Version 2025-05-13 413 AWS Support User Guide For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz114 Source AWS Config Managed Rule: codedeploy-auto-rollback-monitor-enabled Alert Criteria Yellow: AWS CodeDeploy automatic deployment rollback and deployment monitoring are not enabled. Recommended Action Conﬁgure a deployment group or deployment to automatically roll back when a deployment fails or when a monitoring threshold you specify is met. Conﬁgure alarm to monitor various metrics, such as CPU usage, memory usage, or network traﬃc, during the deployment process. If any of these metrics exceed certain thresholds, the alarms trigger, and the deployment is stopped or rolled back. For information on setting up automatic rollbacks and conﬁguring alarms for your deployment groups, see Conﬁgure advanced options for a deployment group. Additional Resources What is CodeDeploy? Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters Operational Excellence API Version 2025-05-13 414 AWS Support • Last Updated Time User Guide AWS CodeDeploy Lambda is using all-at-once deployment conﬁguration Description Checks if the AWS CodeDeploy deployment group for AWS Lambda compute platform is using all-at-once deployment conﬁguration. To reduce the risk of deployment failures of your Lambda functions in CodeDeploy, it's a best practice to use the canary or linear deployment conﬁguration instead of the default option where all traﬃc is shifted from the original Lambda function to the updated function at once. For more information, see Lambda function versions and Deployment conﬁguration. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz115 Source AWS Config Managed Rule: codedeploy-lambda-allatonce-traffic-shift- disabled Alert Criteria Yellow: AWS CodeDeploy Lambda deployment uses the all-at-once deployment conﬁguration to shift all traﬃc to the updated Lambda functions at once. Recommended Action Use the Canary or Linear deployment conﬁguration of CodeDeploy deployment group for the Lambda compute platform. Operational Excellence API Version 2025-05-13 415 User Guide AWS Support Additional Resources Deployment conﬁguration Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time AWS Elastic Beanstalk Enhanced Health Reporting is not Conﬁgured Description Checks if an AWS Elastic Beanstalk environment is conﬁgured for enhanced health reporting. Elastic Beanstalk enhanced health reporting provides detailed performance metrics, such as CPU usage, memory usage, network traﬃc, and infrastructure health information, such as number of instances and load balancer status. For more information, see Enhanced health reporting and monitoring. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz108 Source AWS Config Managed Rule: beanstalk-enhanced-health-reporting-enabled Operational Excellence API Version 2025-05-13 416 AWS Support Alert Criteria User Guide Yellow: Elastic Beanstalk environment is not conﬁgured for enhanced health reporting Recommended Action Make sure that an Elastic Beanstalk environment is conﬁgured for enhanced health reporting. For more
support-ug-121	support-ug.pdf	121	this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz108 Source AWS Config Managed Rule: beanstalk-enhanced-health-reporting-enabled Operational Excellence API Version 2025-05-13 416 AWS Support Alert Criteria User Guide Yellow: Elastic Beanstalk environment is not conﬁgured for enhanced health reporting Recommended Action Make sure that an Elastic Beanstalk environment is conﬁgured for enhanced health reporting. For more information, see Enabling enhanced health reporting using the Elastic Beanstalk console. Additional Resources • Enabling Elastic Beanstalk enhanced health reporting • Enhanced health reporting and monitoring Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time AWS Elastic Beanstalk with Managed Platform Updates Disabled Description Checks if managed platform updates in Elastic Beanstalk environments and conﬁguration templates are enabled. AWS Elastic Beanstalk regularly releases platform updates to provide ﬁxes, software updates, and new features. With managed platform updates,Elastic Beanstalk can automatically perform platform updates for new patch and minor platform versions. You can specify your desired update level in the UpdateLevel parameters of your AWS Conﬁg rules. For more information, see Updating your Elastic Beanstalk environment's platform version. Operational Excellence API Version 2025-05-13 417 AWS Support Note User Guide Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz177 Source AWS Config Managed Rule: elastic-beanstalk-managed-updates-enabled Alert Criteria Yellow: AWS Elastic Beanstalk managed platform updates is not conﬁgured at all, including at a minor or patch level. Recommended Action Enable managed platform updates in your Elastic Beanstalk environments, or conﬁgure it at a minor or update level. For more information, see Managed platform updates. Additional Resources • Enabling Elastic Beanstalk enhanced health reporting • Enhanced health reporting and monitoring Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Operational Excellence API Version 2025-05-13 418 AWS Support User Guide AWS Fargate platform version is not latest Description Checks if Amazon ECS is running the latest platform version of AWS Fargate. The Fargate platform version refers to a speciﬁc runtime environment for Fargate task infrastructure. It's a combination of the kernel and container runtime versions. New platform versions are released as runtime environment evolves. For example, if there are kernel or operating system updates, new features, bug ﬁxes, or security updates. For more information, see Fargate task maintenance. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz174 Source AWS Config Managed Rule: ecs-fargate-latest-platform-version Alert Criteria Yellow: Amazon ECS is not running on the latest version of the Fargate platform. Recommended Action Update to the latest Fargate platform version. For more information, see Fargate task maintenance. Report columns • Status • Region Operational Excellence API Version 2025-05-13 419 AWS Support • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time User Guide AWS Systems Manager State Manager Association in Non-compliant Status Description Checks if the status of the AWS Systems Manager association compliance is COMPLIANT or NON_COMPLIANT after the association execution on the instance. State Manager, a capability of AWS Systems Manager, is a secure and scalable conﬁguration management service that automates the process of keeping your managed nodes and other AWS resources in a state that you deﬁne. A State Manager association is a conﬁguration that you assign to your AWS resources. The conﬁguration deﬁnes the state that you want to maintain on your resources, so it helps you to achieve the target, such as avoidance of conﬁguration drifts across your Amazon EC2 instances. For more information, see AWS Systems Manager State Manager. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz147 Source AWS Config Managed Rule: ec2-managedinstance-association-compliance- status-check Operational Excellence API Version 2025-05-13 420 AWS Support Alert Criteria User Guide Yellow: The status of the AWS Systems Manager
support-ug-122	support-ug.pdf	122	conﬁguration drifts across your Amazon EC2 instances. For more information, see AWS Systems Manager State Manager. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz147 Source AWS Config Managed Rule: ec2-managedinstance-association-compliance- status-check Operational Excellence API Version 2025-05-13 420 AWS Support Alert Criteria User Guide Yellow: The status of the AWS Systems Manager association compliance is NON_COMPLIANT. Recommended Action Validate the status of the State Manager associations, and then take any needed actions to return the status back to COMPLIANT. For more information, see About State Manager. Additional Resources AWS Systems Manager State Manager Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time CloudTrail trails are not conﬁgured with Amazon CloudWatch Logs Description Checks if AWS CloudTrail trails are conﬁgured to send logs to CloudWatch Logs. Monitor CloudTrail Log ﬁles with CloudWatch Logs to trigger an automated response when critical events are captured in AWS CloudTrail. For more information, see Monitoring CloudTrail Log Files with CloudWatch Logs. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Operational Excellence API Version 2025-05-13 421 AWS Support Check ID c18d2gz164 Source User Guide AWS Config Managed Rule: cloud-trail-cloud-watch-logs-enabled Alert Criteria Yellow: AWS CloudTrail is not set up with CloudWatch Logs integration. Recommended Action Conﬁgure CloudTrail trails to send log events to CloudWatch Logs. For more information, see Creating CloudWatch alarms for CloudTrail events: examples. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Elastic Load Balancing Deletion Protection Not Enabled for Load Balancers Description Checks if deletion protection is turned on for your load balancers. Elastic Load Balancing supports deletion protection for your Application Load Balancers, Network Load Balancers, and Gateway Load Balancers. Turn on deletion protection to prevent your load balancer from accidental deletion. Deletion protection is turned oﬀ by default when you create a load balancer. If your load balancers are part of a production environment, then consider turning on deletion protection. Access logs are an optional feature of Elastic Load Balancing that is disabled by default. After you enable access logs for your load balancer, Elastic Load Balancing captures the logs and stores them in the Amazon S3 bucket that you specify. Operational Excellence API Version 2025-05-13 422 AWS Support User Guide For more information, see Application Load Balancer Deletion protection, Network Load Balancers Deletion protection, or Gateway Load Balancers Deletion protection. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz168 Source AWS Config Managed Rule: elb-deletion-protection-enabled Alert Criteria Yellow: Deletion protection is not enabled for a load balancer. Recommended Action Turn on deletion protection for your Application Load Balancers, Network Load Balancers, and Gateway Load Balancers. For more information, see Application Load Balancer Deletion protection, Network Load Balancers Deletion protection, or Gateway Load Balancers Deletion protection. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Operational Excellence API Version 2025-05-13 423 AWS Support User Guide RDS DB Cluster Deletion Protection Check Description Checks if your Amazon RDS DB clusters have deletion protection enabled. When a cluster is conﬁgured with deletion protection, the database cannot be deleted by any user. Deletion protection is available for Amazon Aurora and RDS for MySQL, RDS for MariaDB, RDS for Oracle, RDS for PostgreSQL, and RDS for SQL Server database instances in all AWS Regions. For more information, see Deletion protection for Aurora clusters. Check ID c18d2gz160 Source AWS Config Managed Rule: rds-cluster-deletion-protection-enabled Alert Criteria Yellow: You have Amazon RDS DB clusters that don't have deletion protection enabled. Recommended Action Turn on deletion protection when you create an Amazon RDS DB cluster. You can only delete clusters that don't have deletion protection enabled. Enabling deletion protection adds an extra layer of protection and avoids data loss from accidental or non- accidental deletion of a database instance. Deletion protection also helps meet regulatory compliance requirements and ensure business continuity. For more information, see Deletion protection
support-ug-123	support-ug.pdf	123	Regions. For more information, see Deletion protection for Aurora clusters. Check ID c18d2gz160 Source AWS Config Managed Rule: rds-cluster-deletion-protection-enabled Alert Criteria Yellow: You have Amazon RDS DB clusters that don't have deletion protection enabled. Recommended Action Turn on deletion protection when you create an Amazon RDS DB cluster. You can only delete clusters that don't have deletion protection enabled. Enabling deletion protection adds an extra layer of protection and avoids data loss from accidental or non- accidental deletion of a database instance. Deletion protection also helps meet regulatory compliance requirements and ensure business continuity. For more information, see Deletion protection for Aurora clusters. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Operational Excellence API Version 2025-05-13 424 User Guide AWS Support Additional Resources Deletion protection for Aurora clusters Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time RDS DB Instance Automatic Minor Version Upgrade Check Description Checks if Amazon RDS DB instances have automatic minor version upgrades conﬁgured. Turn on automatic minor version upgrades for an Amazon RDS instance to make sure that the database is always running the latest secure and stable version. Minor upgrades provide security updates, bug ﬁxes, performance improvements, and maintain compatibility with existing applications. For more information, see Upgrading a DB instance engine version. Note Results for this check are automatically refreshed several times daily, and refresh requests are not allowed. It might take a few hours for changes to appear. For Business, Enterprise On-Ramp, or Enterprise Support customers, you can use the BatchUpdateRecommendationResourceExclusion API to include or exclude one or more resources from your Trusted Advisor results. Check ID c18d2gz155 Operational Excellence API Version 2025-05-13 425 AWS Support Source User Guide AWS Config Managed Rule: rds-automatic-minor-version-upgrade-enabled Alert Criteria Yellow: RDS DB instance does not have automatic minor version upgrades turned on. Recommended Action Turn on automatic minor version upgrades when you create a Amazon RDS DB instance. When you turn on minor version upgrade, the database version automatically upgrades if it is running a minor version of the DB engine that is lower than the Manually upgrading the engine version. Report columns • Status • Region • Resource • AWS Conﬁg Rule • Input Parameters • Last Updated Time Change log for AWS Trusted Advisor See the following topic for recent changes to Trusted Advisor checks. Note If you use the Trusted Advisor console or the AWS Support API, checks that were removed won't appear in check results. If you use a removed check, such as specifying the check ID in an AWS Support API operation or your code, then you receive API call errors. Remove these checks to avoid errors. For more information about the available checks, see the AWS Trusted Advisor check reference. Change log for AWS Trusted Advisor API Version 2025-05-13 426 User Guide AWS Support Revised checks The following checks have been revised: Check name Check ID Amazon EFS Throughput Mode Optimization c1dfprch02 Amazon EC2 instances with Microsoft Windows Server end of support Qsdfp3A4L4 The description of this check has changed. For more information, see the following: • Amazon EC2 instances with Microsoft Windows Server end of support The description and recommendation for this check has changed. For more information, see the following: • Amazon EFS Throughput Mode Optimization Deprecated AWS Security Hub checks The following AWS Security Hub checks are deprecated: Check name S3.10 - S3 general purpose buckets with versioning enabled should have Lifecycle conﬁgurations Check ID Hs4Ma3G211 S3.11 - S3 general purpose buckets should have event notiﬁcations enabled Hs4Ma3G212 CodeBuild.5 - CodeBuild project environments should not have privileged mode enabled Hs4Ma3G218 Revised checks API Version 2025-05-13 427 User Guide AWS Support Check name CloudFormation.1 - CloudFormation stacks should be integrated with Amazon Simple Notiﬁcation Service (SNS) Check ID Hs4Ma3G245 SNS.2 - Logging of delivery status should be enabled for notiﬁcation messages sent to a Hs4Ma3G263 topic Athena.1 - Athena workgroups should be encrypted at rest Hs4Ma3G294 New check: Amazon RDS Continuous Backup Not Enabled Trusted Advisor added the following check on December 23, 2024. Check name Check category Check ID Amazon RDS Continuous Backup Not Enabled Fault tolerance 44fde09ab5 Checks if an Amazon RDS instance is enabled with automated backups using Amazon RDS or with continuous backups of AWS Backup. Continuous backups reduce the risk of unexpected data loss and allow for point-in-time recovery. For more information, see Amazon RDS Continuous Backup Not Enabled. New check: AWS CloudTrail Management Events Logging Trusted Advisor added the following check on December 23, 2024.
support-ug-124	support-ug.pdf	124	be encrypted at rest Hs4Ma3G294 New check: Amazon RDS Continuous Backup Not Enabled Trusted Advisor added the following check on December 23, 2024. Check name Check category Check ID Amazon RDS Continuous Backup Not Enabled Fault tolerance 44fde09ab5 Checks if an Amazon RDS instance is enabled with automated backups using Amazon RDS or with continuous backups of AWS Backup. Continuous backups reduce the risk of unexpected data loss and allow for point-in-time recovery. For more information, see Amazon RDS Continuous Backup Not Enabled. New check: AWS CloudTrail Management Events Logging Trusted Advisor added the following check on December 23, 2024. Check name Check category Check ID AWS CloudTrail Management Events Logging Security c25hn9x03v New check: Amazon RDS Continuous Backup Not Enabled API Version 2025-05-13 428 AWS Support User Guide Checks your use of AWS CloudTrail. For more information, see AWS CloudTrail Management Event Logging. Updated the Auto Scaling Group Resources check Trusted Advisor updated the following check on December 23, 2024. Check name Check category Check ID Auto Scaling Group Resources Fault tolerance 8CNsSllI5v The description of this check is updated to include launch conﬁgurations and launch templates. A new alert critera, Red: A launch template is associated with a deleted Amazon Machine Image (AMI). was added. For more information, see Auto Scaling Group Resources. Updated the IAM Access Analyzer External Access check Trusted Advisor updated the following check on December 23, 2024. Check name Check category Check ID IAM Access Analyzer External Access Security 07602fcad6 The description of this check is updated to indicate that it analyzes IAM access at the account level. For more information, see IAM Access Analyzer External Access. Added 1 new check Trusted Advisor added 1 new check on November 22, 2024: • 8604e947f2 - Application Load Balancer Security Groups Updated the Auto Scaling Group Resources check API Version 2025-05-13 429 User Guide AWS Support Updated 3 checks Trusted Advisor updated 3 checks on November 7, 2024: • b92b83d667 - ELB Target Imbalance • 8CNsSllI5v - Auto Scaling Group Resources • wuy7G1zxql - Amazon EC2 Availability Zone Balance Added 4 checks Trusted Advisor added 4 new checks on October 11, 2024: • 07602fcad6 - IAM Access Analyzer - external access • 528d6f5ee7 - GWLB - Endpoint AZ • c2vlfg0jp6 - Inactive VPC interface endpoints • c2vlfg0k35 - Inactive Gateway Load Balancer endpoints Updated 3 checks Trusted Advisor updated 3 checks on October 2, 2024: • Check ID 7040ea389a moved from Cost Optimization pillar to the Fault Tolerance pillar • Updated Check ID 7DAFEmoDos • Updated Check ID Cmsvnj8db2 Added 9 new checks Trusted Advisor added 9 new checks on August 23, 2024: • c2vlfg0p86 - [IAM] - SAML 2.0 Identity Provider • 7040ea389a - Network Firewall endpoint Cross-AZ Data Transfer • c2vlfg0bfw - Low utilization Network Firewall • c2vlfg0gqd - Network Firewall Multi-AZ • c2vlfg0p1w - Application Load Balancer Target Groups encrypted protocol Updated 3 checks API Version 2025-05-13 430 AWS Support User Guide • c2vlfg022t - [NAT Gateway] - Underutilized Resource • c243hjzrhn - AWS Outposts Single Rack deployment • b92b83d667 - ELB Target Imbalance • 90046ﬀ5b5 - MSK availability is limited to two zones For more information, see the AWS Trusted Advisor check reference. Updated 1 Security check and added 1 Security check Trusted Advisor updated 1 Operational Excellence checks on August 22, 2024: • c1fd6b96l4 Trusted Advisor added 1 Security checks on August 22, 2024: • c2vlfg0f4h For more information, see the AWS Trusted Advisor check reference. Updated 6 Security checks Trusted Advisor updated 6 Security checks on August 20, 2024: • nNauJisYIT • c9D319e7sG • a2sEc6ILx • HCP4007jGY • 1iG5NDGVre • Yw2K9puPzl For more information, see the AWS Trusted Advisor check reference. Updated 1 fault tolerance checks Trusted Advisor updated the 1 fault tolerance check and 1 security on August 12, 2024: Updated 1 Security check and added 1 Security check API Version 2025-05-13 431 AWS Support • VPN Tunnel Redundancy • Amazon RDS engine minor version upgrade is required User Guide For more information, see the AWS Trusted Advisor check reference. Updated 9 checks Trusted Advisor updated the 9 checks on July 21, 2024: • 7qGXsKIUw • ZRxQlPsb6c • N425c450f2 • 7DAFEmoDos • Pfx0RwqBli • H7IgTzjTYb • C056F80cR3 • Yw2K9puPzl • xSqX82fQu For more information, see the AWS Trusted Advisor check reference. Removed 5 checks and added 1 check Trusted Advisor deprecated 3 Fault Tolerance checks, 1 Perfomance check, and 1 Security check on May 15, 2024: • IAM Use • ELB Cross-Zone Load Balancing • Overutilized Amazon EBS Magnetic Volumes • Large Number of EC2 Security Group Rules Applied to an Instance • Large Number of Rules in an EC2 Security Group Trusted Advisor added 1 new security check on May 15, 2024: Updated 9 checks API Version 2025-05-13 432 AWS Support User Guide • Amazon S3 Server Access
support-ug-125	support-ug.pdf	125	• xSqX82fQu For more information, see the AWS Trusted Advisor check reference. Removed 5 checks and added 1 check Trusted Advisor deprecated 3 Fault Tolerance checks, 1 Perfomance check, and 1 Security check on May 15, 2024: • IAM Use • ELB Cross-Zone Load Balancing • Overutilized Amazon EBS Magnetic Volumes • Large Number of EC2 Security Group Rules Applied to an Instance • Large Number of Rules in an EC2 Security Group Trusted Advisor added 1 new security check on May 15, 2024: Updated 9 checks API Version 2025-05-13 432 AWS Support User Guide • Amazon S3 Server Access Logs Enabled For more information, see the AWS Trusted Advisor check reference. Removed fault tolerance checks Trusted Advisor deprecated 3 Fault Tolerance check on April 25, 2024: • AWS Direct Connect Connection Redundancy • AWS Direct Connect Location Redundancy • AWS Direct Connect Virtual Interface Redundancy For more information, see the AWS Trusted Advisor check reference. New fault tolerance check Trusted Advisor added 1 Fault Tolerance check on February 29, 2024: • NLB - Internet-facing resource in private subnet For more information, see the AWS Trusted Advisor check reference. Updated fault tolerance and security checks Trusted Advisor added 1 new Fault Tolerance check and amended 1 existing Fault tolerance and 1 Security check on March 28 2024: • Added AWS Resilience Hub Application Component check • Updated AWS Lambda VPC-enabled Functions without Multi-AZ Redundancy • Updated AWS Lambda Functions Using Deprecated Runtimes For more information, see the AWS Trusted Advisor check reference. New fault tolerance check Trusted Advisor added 1 Fault Tolerance check on January 31, 2024: • AWS Direct Connect Location Resiliency Removed fault tolerance checks API Version 2025-05-13 433 AWS Support User Guide For more information, see the AWS Trusted Advisor check reference. Updated fault tolerance check Trusted Advisor amended 1 Fault Tolerance check on January 08, 2024: • Amazon RDS innodb_ﬂush_log_at_trx_commit parameter is not 1 For more information, see the AWS Trusted Advisor check reference. Updated security check Trusted Advisor amended 1 Security check on December 21, 2023: • AWS Lambda Functions Using Deprecated Runtimes For more information, see the AWS Trusted Advisor check reference. New security and performance checks Trusted Advisor added 2 new Security checks and 2 new Performance checks on December 20, 2023: • Amazon EFS clients not using data-in-transit encryption • Amazon Aurora DB cluster under-provisioned for read workload • Amazon RDS instance under-provisioned for system capacity • Amazon EC2 instances with Ubuntu LTS end of standard support For more information, see the AWS Trusted Advisor check reference. New security check Trusted Advisor added 1 new Security check on December 15, 2023: • Amazon Route 53 mismatching CNAME records pointing directly to S3 buckets For more information, see the AWS Trusted Advisor check reference. Updated fault tolerance check API Version 2025-05-13 434 AWS Support User Guide New fault tolerance and cost optimization checks Trusted Advisor added 2 new Fault Tolerance checks and 1 new Cost Optimization check on December 07, 2023: • Amazon DocumentDB Single-AZ clusters • Amazon S3 Incomplete Multipart Upload Abort Conﬁguration • Amazon ECS AWSLogs driver in blocking mode For more information, see the AWS Trusted Advisor check reference. New fault tolerance checks Trusted Advisor added 3 new fault tolerance checks on November 17, 2023: • ALB Multi-AZ • NLB Multi-AZ • VPC interface endpoint network interfaces in multiple AZs For more information, see the AWS Trusted Advisor check reference. New checks for Amazon RDS Trusted Advisor added 37 new checks for Amazon RDS on November 15, 2023. For more information, see the AWS Trusted Advisor check reference. New AWS Trusted Advisor API AWS Trusted Advisor introduces new APIs to enable you to programmatically access Trusted Advisor best practice checks, recommendations, and prioritized recommendations. Trusted Advisor APIs enable you to programmatically integrate Trusted Advisor with your preferred operational tool to automate and optimize your workloads at scale. Available to Business, Enterprise On-Ramp, or Enterprise Support customers, the new APIs provide access to Trusted Advisor recommendations for your account or all the linked accounts within a payer account. Enterprise Support customers with access to management or delegated administrator accounts can additionally programmatically retrieve prioritized recommendations across their organization. New fault tolerance and cost optimization checks API Version 2025-05-13 435 AWS Support User Guide The new Trusted Advisor APIs will replace the 3 functionalities previously oﬀered through AWS Support API (SAPI). SAPI will continue to oﬀer case and other support information. Trusted Advisor APIs are generally available in the US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Paciﬁc (Seoul), Asia Paciﬁc (Sydney), and Europe (Ireland) Regions. To learn more, please visit the AWS Trusted Advisor API page. Trusted Advisor check removal Trusted Advisor removed the following checks on November 9, 2023. Check name Check category Check ID EBS volumes
support-ug-126	support-ug.pdf	126	and cost optimization checks API Version 2025-05-13 435 AWS Support User Guide The new Trusted Advisor APIs will replace the 3 functionalities previously oﬀered through AWS Support API (SAPI). SAPI will continue to oﬀer case and other support information. Trusted Advisor APIs are generally available in the US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Paciﬁc (Seoul), Asia Paciﬁc (Sydney), and Europe (Ireland) Regions. To learn more, please visit the AWS Trusted Advisor API page. Trusted Advisor check removal Trusted Advisor removed the following checks on November 9, 2023. Check name Check category Check ID EBS volumes should be attached to EC2 instances S3 buckets should have server-side encryption enabled CloudFront distributions should have origin access identity enabled Security Security Hs4Ma3G119 Hs4Ma3G167 Security Hs4Ma3G195 Integration of AWS Conﬁg checks into Trusted Advisor Trusted Advisor added 64 new checks powered by AWS Conﬁg on October 30, 2023. For more information, see the View AWS Trusted Advisor checks powered by AWS Conﬁg. New fault tolerance checks Trusted Advisor added the following checks on October 12, 2023. • Amazon RDS ReplicaLag • Amazon RDS FreeStorageSpace • Amazon RDS DiskQueueDepth • Amazon Route 53 Resolver Endpoint Availability Zone Redundancy Trusted Advisor check removal API Version 2025-05-13 436 AWS Support User Guide • Auto Scaling available IPs in Subnets • Amazon MSK brokers hosting too many partitions For more information, see the Fault tolerance category. New service limits check Trusted Advisor added the following check on August 17, 2023. • Lambda Code Storage Usage For more information, see the Service limits category. New fault tolerance check Trusted Advisor added the following check on August 3, 2023. • AWS Lambda On Failure Event Destinations For more information, see the Fault tolerance category. New fault tolerance and performance checks Trusted Advisor added the following checks on June 1, 2023. • Amazon EFS No Mount Target Redundancy • Amazon EFS Throughput Mode Optimization • ActiveMQ Availability Zone Redundancy • RabbitMQ Availability Zone Redundancy For more information, see the Fault tolerance category and Performance category. New fault tolerance checks Trusted Advisor added the following checks on May 16, 2023. • NAT Gateway AZ Independence • Single AZ Application Check New service limits check API Version 2025-05-13 437 AWS Support User Guide For more information, see the Fault tolerance category. New fault tolerance checks Trusted Advisor added the following checks on April 27, 2023. • Number of AWS Regions in an Incident Manager replication set • AWS Resilience Hub assessment age For more information, see the Fault tolerance category. Region Expansion of Amazon ECS Fault Tolerance Checks Trusted Advisor expanded the following checks into additional regions on April 27, 2023. Trusted Advisor checks for Amazon ECS are now available in all regions where Amazon ECS is generally available. • Amazon ECS service using a single AZ • Amazon ECS Multi-AZ placement strategy Regions expanded into include Africa (Cape Town), Asia Paciﬁc (Hong Kong), Asia Paciﬁc (Hyderabad), Asia Paciﬁc (Jakarta), Asia Paciﬁc (Melbourne), Europe (Milan), Europe (Spain), Europe (Zurich), Middle East (Bahrain), Middle East (UAE). New fault tolerance checks Trusted Advisor added the following checks on March 30, 2023. • Amazon ECS service using a single AZ • Amazon ECS Multi-AZ placement strategy For more information, see the Fault tolerance category. New fault tolerance checks Trusted Advisor added the following checks on December 15, 2022. • AWS CloudHSM clusters running HSM instances in a single AZ New fault tolerance checks API Version 2025-05-13 438 AWS Support User Guide • Amazon ElastiCache Multi-AZ clusters • Amazon MemoryDB Multi-AZ clusters To receive results in Trusted Advisor for your AWS CloudHSM, ElastiCache, and MemoryDB clusters, you must have clusters in your Availability Zones. For more information, see the following documentation: • AWS CloudHSM User Guide • Amazon MemoryDB Developer Guide Trusted Advisor updated the following check information on December 15, 2022. • AWS Resilience Hub policy breached – App Name was updated to Application Name • AWS Resilience Hub resilience scores – App Name and App Resilience Score were updated to Application Name and Application Resilience Score For more information, see the Fault tolerance category. Updates to the Trusted Advisor integration with AWS Security Hub Trusted Advisor made the following update on November 17, 2022. If you disable Security Hub or AWS Conﬁg for an AWS Region, Trusted Advisor now removes your control ﬁndings for that AWS Region within 7-9 days. Previously, the time frame to remove your Security Hub data from Trusted Advisor was 90 days. For more information, see the following sections in the Troubleshooting topic: • I turned oﬀ Security Hub or AWS Conﬁg in a Region • My control is archived in Security Hub, but I still see the ﬁndings in Trusted Advisor New fault tolerance checks for AWS Resilience Hub Trusted Advisor added the following checks
support-ug-127	support-ug.pdf	127	on November 17, 2022. If you disable Security Hub or AWS Conﬁg for an AWS Region, Trusted Advisor now removes your control ﬁndings for that AWS Region within 7-9 days. Previously, the time frame to remove your Security Hub data from Trusted Advisor was 90 days. For more information, see the following sections in the Troubleshooting topic: • I turned oﬀ Security Hub or AWS Conﬁg in a Region • My control is archived in Security Hub, but I still see the ﬁndings in Trusted Advisor New fault tolerance checks for AWS Resilience Hub Trusted Advisor added the following checks on November 17, 2022. • AWS Resilience Hub policy breached • AWS Resilience Hub resilience scores Updates to the Trusted Advisor integration with AWS Security Hub API Version 2025-05-13 439 AWS Support User Guide You can use these checks to view the latest resilience policy status and resilience score for your applications. Resilience Hub provides you with a central place to deﬁne, track, and manage the resiliency and availability of your applications. To receive results in Trusted Advisor for your Resilience Hub applications, you must deploy an AWS application and use Resilience Hub to track the resiliency posture of the application. For more information, see the AWS Resilience Hub User Guide. To receive results in Trusted Advisor for your ElastiCache and MemoryDB clusters, you must have clusters in your Availability Zones. For more information, see the following documentation: Amazon MemoryDB Developer Guide For more information, see the Fault tolerance category. Update to the Trusted Advisor console Trusted Advisor added the following change on November 16, 2022. The Trusted Advisor Dashboard in the console is now Trusted Advisor Recommendations. The Trusted Advisor Recommendations page still shows the check results and the available checks for each category for your AWS account. This name change only updates the Trusted Advisor console. You can continue to use the Trusted Advisor console and the Trusted Advisor operations in the Support API as usual. For more information, see Get started with Trusted Advisor Recommendations. New checks for Amazon EC2 Trusted Advisor added the following check on September 1, 2022. • Amazon EC2 instances with Microsoft Windows Server end of support For more information, see the Security category. Added Security Hub checks to Trusted Advisor As of June 23, 2022, Trusted Advisor only supports Security Hub controls available through April 7, 2022. This release supports all controls in the AWS Foundational Security Best Practices security Update to the Trusted Advisor console API Version 2025-05-13 440 AWS Support User Guide standard except for controls in the Category: Recover > Resilience. For more information, see Viewing AWS Security Hub controls in AWS Trusted Advisor. For a list of supported controls, see AWS Foundational Security Best Practices controls in the AWS Security Hub User Guide. Added checks from AWS Compute Optimizer Trusted Advisor added the following checks on May 4, 2022. Check name Check category Check ID Amazon EBS over-provisioned volumes Amazon EBS under-pro visioned volumes AWS Lambda over-prov isioned functions for memory size AWS Lambda under-pro visioned functions for memory size Cost optimization COr6dfpM03 Performance COr6dfpM04 Cost optimization COr6dfpM05 Performance COr6dfpM06 You must opt in your AWS account for Compute Optimizer so that these checks can receive data from your Lambda and Amazon EBS resources. For more information, see Opt in AWS Compute Optimizer for Trusted Advisor checks. Updates to the Exposed Access Keys check Trusted Advisor updated the following check on April 25, 2022. Check name Check category Check ID Exposed Access Keys Security 12Fnkpl8Y5 Added checks from AWS Compute Optimizer API Version 2025-05-13 441 AWS Support User Guide Trusted Advisor now refreshes this check for you automatically. This check can't be refreshed manually from the Trusted Advisor console or the AWS Support API. If your application or code refreshes this check for your AWS account, we recommend that you update it to no longer refresh this check. Otherwise, you will receive the InvalidParameterValue error. Any access keys that you excluded before this update will no longer be excluded and will appear as aﬀected resources. You can't exclude access keys from your check results. For more information, see Exposed Access Keys. Note If you created your AWS account after April 25, 2022, the check results for Exposed Access Keys initially shows the gray icon ( even for unexposed access keys. This means that Trusted Advisor hasn't identiﬁed any changes to the check. If Trusted Advisor identiﬁes a resource at risk, the status changes to the action recommended icon ( After you ﬁx or delete the resource, the check result shows the check mark icon ( ) ). ). Updated checks for AWS Direct Connect Trusted Advisor updated the following checks on March 29, 2022. Check name Check category Check ID AWS Direct Connect Connection Redundancy AWS Direct Connect
support-ug-128	support-ug.pdf	128	after April 25, 2022, the check results for Exposed Access Keys initially shows the gray icon ( even for unexposed access keys. This means that Trusted Advisor hasn't identiﬁed any changes to the check. If Trusted Advisor identiﬁes a resource at risk, the status changes to the action recommended icon ( After you ﬁx or delete the resource, the check result shows the check mark icon ( ) ). ). Updated checks for AWS Direct Connect Trusted Advisor updated the following checks on March 29, 2022. Check name Check category Check ID AWS Direct Connect Connection Redundancy AWS Direct Connect Location Redundancy AWS Direct Connect Virtual Interface Redundancy Fault tolerance 0t121N1Ty3 Fault tolerance 8M012Ph3U5 Fault tolerance 4g3Nt5M1Th Updated checks for AWS Direct Connect API Version 2025-05-13 442 AWS Support User Guide • The value for the Region column now shows the AWS Region code instead of the full name. For example, resources in US East (N. Virginia) will now have the us-east-1 value. • The value for the Time Stamp column now appears in the RFC 3339 format, such as 2022-03-30T01:02:27.000Z. • Resources that don't have any detected problems will now appear in the check table. These resources will have a check mark icon ( next to them. Previously, only resources that Trusted Advisor recommended that you investigate appeared in the table. These resources have a warning icon ( next to them. ) ) AWS Security Hub controls added to the AWS Trusted Advisor console AWS Trusted Advisor added 111 Security Hub controls to the Security category on January 18, 2022. You can view your ﬁndings for Security Hub controls from the AWS Foundational Security Best Practices security standard. This integration doesn't include controls that have the Category: Recover > Resilience. For more information about this feature, see Viewing AWS Security Hub controls in AWS Trusted Advisor. New checks for Amazon EC2 and AWS Well-Architected Trusted Advisor added the following checks on December 20, 2021. • Amazon EC2 instances consolidation for Microsoft SQL Server • Amazon EC2 instances over-provisioned for Microsoft SQL Server • Amazon EC2 instances with Microsoft SQL Server end of support • AWS Well-Architected high risk issues for cost optimization • AWS Well-Architected high risk issues for performance • AWS Well-Architected high risk issues for security • AWS Well-Architected high risk issues for reliability AWS Security Hub controls added to the AWS Trusted Advisor console API Version 2025-05-13 443 AWS Support User Guide For more information, see the AWS Trusted Advisor check reference. Updated check name for Amazon OpenSearch Service Trusted Advisor updated the name for the Amazon OpenSearch Service Reserved Instance Optimization check on September 8, 2021. The check recommendations, category, and ID are the same. Check name Check category Check ID Cost optimization 7ujm6yhn5t Amazon OpenSearch Service Reserved Instance Optimizat ion Note If you use Trusted Advisor for Amazon CloudWatch metrics, the metric name for this check is also updated. For more information, see Creating Amazon CloudWatch alarms to monitor AWS Trusted Advisor metrics. Added checks for Amazon Elastic Block Store volume storage Trusted Advisor added the following checks on June 8, 2021. Check name Check category Check ID EBS General Purpose SSD (gp3) Volume Storage EBS Provisioned IOPS SSD (io2) Volume Storage Service limits dH7RR0l6J3 Service limits gI7MM0l7J2 Added checks for AWS Lambda Trusted Advisor added the following checks on March 8, 2021. Updated check name for Amazon OpenSearch Service API Version 2025-05-13 444 AWS Support User Guide Check name Check category Check ID AWS Lambda Functions with Excessive Timeouts AWS Lambda Functions with High Error Rates Cost optimization L4dfs2Q3C3 Cost optimization L4dfs2Q3C2 AWS Lambda Functions Using Deprecated Runtimes Security L4dfs2Q4C5 AWS Lambda VPC-enabled Functions without Multi-AZ Redundancy Fault tolerance L4dfs2Q4C6 For more information about how to use these checks with Lambda, see Example AWS Trusted Advisor workﬂow to view recommendations in the AWS Lambda Developer Guide. Trusted Advisor check removal Trusted Advisor removed the following check for the AWS GovCloud (US) Region on March 8, 2021. Check name Check category Check ID EC2 Elastic IP Addresses Service limits aW9HH0l8J6 Updated checks for Amazon Elastic Block Store Trusted Advisor updated the unit of Amazon EBS volume from gibibyte (GiB) to tebibyte (TiB) for the following checks on March 5, 2021. Note If you use Trusted Advisor for Amazon CloudWatch metrics, the metric names for these ﬁve checks are also updated. For more information, see Creating Amazon CloudWatch alarms to monitor AWS Trusted Advisor metrics. Trusted Advisor check removal API Version 2025-05-13 445 AWS Support User Guide Check name Check category Check ID EBS Cold HDD (sc1) Volume Storage EBS General Purpose SSD (gp2) Volume Storage EBS Magnetic (standard) Volume Storage EBS Provisioned IOPS SSD (io1) Volume Storage EBS Throughput Optimized HDD (st1) Volume Storage Service limits gH5CC0e3J9 Service limits dH7RR0l6J9 Service limits cG7HH0l7J9 Service
support-ug-129	support-ug.pdf	129	following checks on March 5, 2021. Note If you use Trusted Advisor for Amazon CloudWatch metrics, the metric names for these ﬁve checks are also updated. For more information, see Creating Amazon CloudWatch alarms to monitor AWS Trusted Advisor metrics. Trusted Advisor check removal API Version 2025-05-13 445 AWS Support User Guide Check name Check category Check ID EBS Cold HDD (sc1) Volume Storage EBS General Purpose SSD (gp2) Volume Storage EBS Magnetic (standard) Volume Storage EBS Provisioned IOPS SSD (io1) Volume Storage EBS Throughput Optimized HDD (st1) Volume Storage Service limits gH5CC0e3J9 Service limits dH7RR0l6J9 Service limits cG7HH0l7J9 Service limits gI7MM0l7J9 Service limits wH7DD0l3J9 Trusted Advisor check removal Updated CloudWatc h metric for ServiceLimit Cold HDD (sc1) volume storage (TiB) General Purpose SSD (gp2) volume storage (TiB) Magnetic (standard) volume storage (TiB) Provisioned IOPS (SSD) storage (TiB) Throughput Optimized HDD (st1) volume storage (TiB) Note Trusted Advisor removed the following checks on November 18, 2020. Checks removed on November 18, 2020 EC2Conﬁg Service for EC2 Windows Instances Check category Check ID Fault tolerance V77iOLlBqz Trusted Advisor check removal API Version 2025-05-13 446 User Guide AWS Support Checks removed on November 18, 2020 ENA Driver Version for EC2 Windows Instances NVMe Driver Version for EC2 Windows Instances PV Driver Version for EC2 Windows Instances Check category Check ID Fault tolerance TyfdMXG69d Fault tolerance yHAGQJV9K5 Fault tolerance Wnwm9Il5bG EBS Active Volumes Service limits fH7LL0l7J9 Amazon Elastic Block Store no longer has a limit on the number of volumes that you can provision. You can monitor your Amazon EC2 instances and verify they are up to date by using AWS Systems Manager Distributor, other third-party tools, or write your own scripts to return driver information for Windows Management Instrumentation (WMI). Trusted Advisor check removal Trusted Advisor removed the following check on February 18, 2020. Check name Check category Check ID Service Limits Performance eW7HH0l7J9 Trusted Advisor check removal API Version 2025-05-13 447 AWS Support User Guide AWS Support App in Slack You can use the AWS Support App to manage your AWS support cases in Slack. Invite your team members to chat channels, respond to case updates, and chat directly with support agents. Use the AWS Support App to manage support cases quickly in Slack. Use the AWS Support App to do the following: • Create, update, search for, and resolve support cases in Slack channels • Attach ﬁles to support cases • Request quota increases from Service Quotas • Share support case details with your team without leaving the Slack channel • Start a live chat session with support agents When you create, update, or resolve a support case in the AWS Support App, the case is also updated in the AWS Support Center Console. You don't need to sign in to the Support Center Console to manage your support cases separately. Notes • The response times for support cases are the same, whether you created the case from Slack or from the Support Center Console. • You can create a support case for account and billing support, service quota increases, and technical support. Topics • Prerequisites • Authorize a Slack workspace • Conﬁguring a Slack channel • Creating support cases in a Slack channel • Replying to support cases in Slack • Join a live chat session with Support • Searching for support cases in Slack API Version 2025-05-13 448 AWS Support User Guide • Resolving a support case in Slack • Reopening a support case in Slack • Requesting service quota increases • Deleting a Slack channel conﬁguration from the AWS Support App • Deleting a Slack workspace conﬁguration from the AWS Support App • AWS Support App in Slack commands • View AWS Support App correspondences in the AWS Support Center Console • Creating AWS Support App in Slack resources with AWS CloudFormation Prerequisites You must meet the following requirements to use the AWS Support App in Slack: • You have a Business, Enterprise On-Ramp, or Enterprise Support plan. You can ﬁnd your support plan from the AWS Support Center Console or from the Support plans page. For more information, see Compare AWS Support plans. • You have a Slack workspace and channel for your organization. You must be a Slack workspace administrator, or have permission to add apps to that Slack workspace. For more information, see the Slack Help Center. • You sign in to the AWS account as an AWS Identity and Access Management (IAM) user or role with the required permissions. For more information, see Managing access to the AWS Support App widget. • You will need to create an IAM role that has the required permissions to perform actions for you. The AWS Support App uses this role to make API calls to diﬀerent services. For more information, see Managing access to the AWS
support-ug-130	support-ug.pdf	130	be a Slack workspace administrator, or have permission to add apps to that Slack workspace. For more information, see the Slack Help Center. • You sign in to the AWS account as an AWS Identity and Access Management (IAM) user or role with the required permissions. For more information, see Managing access to the AWS Support App widget. • You will need to create an IAM role that has the required permissions to perform actions for you. The AWS Support App uses this role to make API calls to diﬀerent services. For more information, see Managing access to the AWS Support App. Topics • Managing access to the AWS Support App widget • Managing access to the AWS Support App Managing access to the AWS Support App widget You can attach an AWS Identity and Access Management (IAM) policy to grant an IAM user permission to conﬁgure the AWS Support App widget in the AWS Support Center Console. Prerequisites API Version 2025-05-13 449 AWS Support User Guide For more information about how to add a policy to an IAM entity, see Adding IAM identity permissions (console) in the IAM User Guide. Note You can also sign in as the root user in your AWS account, but we don't recommend that you do this. For more information about root user access, see Safeguard your root user credentials and don't use them for everyday tasks in the IAM User Guide. Example IAM policy You can attach the following policy to an entity, such as an IAM user or group. This policy allows a user to authorize a Slack workspace and conﬁgure Slack channels in the Support Center Console. { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "supportapp:GetSlackOauthParameters", "supportapp:RedeemSlackOauthCode", "supportapp:DescribeSlackChannels", "supportapp:ListSlackWorkspaceConfigurations", "supportapp:ListSlackChannelConfigurations", "supportapp:CreateSlackChannelConfiguration", "supportapp:DeleteSlackChannelConfiguration", "supportapp:DeleteSlackWorkspaceConfiguration", "supportapp:GetAccountAlias", "supportapp:PutAccountAlias", "supportapp:DeleteAccountAlias", "supportapp:UpdateSlackChannelConfiguration", "iam:ListRoles" ], "Resource": "*" } ] } Manage access to the AWS Support App widget API Version 2025-05-13 450 AWS Support User Guide Permissions required to connect the AWS Support App to Slack The AWS Support App includes permission-only actions that don't directly correspond to an API operation. These actions are indicated in the Service Authorization Reference with [permission only]. The AWS Support App uses the following API actions to connect to Slack and then lists your public Slack channels in the AWS Support Center Console: • supportapp:GetSlackOauthParameters • supportapp:RedeemSlackOauthCode • supportapp:DescribeSlackChannels These API actions are not intended to be called by your code. Therefore, these API actions are not included in the AWS CLI and AWS SDKs. Managing access to the AWS Support App After you have permissions to the AWS Support App widget, you must also create an AWS Identity and Access Management (IAM) role. This role performs actions from other AWS services for you, such as the AWS Support API and Service Quotas. You then attach an IAM policy to this role so that the role has the required permissions to complete these actions. You choose this role when you create your Slack channel conﬁguration in the Support Center Console. Users in your Slack channel have the same permissions that you grant to the IAM role. For example, if you specify read-only access to your support cases, then users in your Slack channel can view your support cases, but can't update them. Important When you request a live chat with a support agent and choose new private channel as your live chat channel preference, the AWS Support App creates a separate Slack channel. This Slack channel has the same permissions as the channel where you created the case or initiated the chat. Manage access to the AWS Support App API Version 2025-05-13 451 AWS Support User Guide If you change the IAM role or the IAM policy, your changes apply to the Slack channel that you conﬁgured and to any new live chat Slack channels that the AWS Support App creates for you. Follow these procedures to create your IAM role and policy. Topics • Use an AWS managed policy or create a customer managed policy • Create an IAM role • Troubleshooting Use an AWS managed policy or create a customer managed policy To grant your role permissions, you can use either an AWS managed policy or a customer managed policy. Tip If you don't want to create a policy manually, we recommend that you use an AWS managed policy instead and skip this procedure. Managed policies automatically have the required permissions for the AWS Support App. You don't need to update the policies manually. For more information, see AWS managed policies for AWS Support App in Slack. Follow this procedure to create a customer managed policy for your role. This procedure uses the JSON policy editor in the IAM console. To create a customer managed policy for the AWS Support App 1. Sign in to the AWS
support-ug-131	support-ug.pdf	131	customer managed policy. Tip If you don't want to create a policy manually, we recommend that you use an AWS managed policy instead and skip this procedure. Managed policies automatically have the required permissions for the AWS Support App. You don't need to update the policies manually. For more information, see AWS managed policies for AWS Support App in Slack. Follow this procedure to create a customer managed policy for your role. This procedure uses the JSON policy editor in the IAM console. To create a customer managed policy for the AWS Support App 1. Sign in to the AWS Management Console and open the IAM console at https:// console.aws.amazon.com/iam/. 2. In the navigation pane, choose Policies. 3. Choose Create policy. 4. Choose the JSON tab. 5. Enter your JSON, and then replace the default JSON in the editor. You can use the example policy. Manage access to the AWS Support App API Version 2025-05-13 452 AWS Support 6. Choose Next: Tags. User Guide 7. (Optional) You can use tags as key–value pairs to add metadata to the policy. 8. Choose Next: Review. 9. On the Review policy page, enter a Name, such as AWSSupportAppRolePolicy, and a Description (optional). 10. Review the Summary page to see the permissions that the policy allows and then choose Create policy. This policy deﬁnes the actions that the role can take. For more information, see Creating IAM policies (console) in the IAM User Guide. Example IAM policy You can attach the following example policy to your IAM role. This policy allows the role to have full permissions to all required actions for the AWS Support App. After you conﬁgure a Slack channel with the role, any user in your channel has the same permissions. Note For a list of AWS managed policies, see AWS managed policies for AWS Support App in Slack. You can update the policy to remove a permission from the AWS Support App. { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "servicequotas:GetRequestedServiceQuotaChange", "servicequotas:GetServiceQuota", "servicequotas:RequestServiceQuotaIncrease", "support:AddAttachmentsToSet", "support:AddCommunicationToCase", "support:CreateCase", "support:DescribeCases", "support:DescribeCommunications", Manage access to the AWS Support App API Version 2025-05-13 453 AWS Support User Guide "support:DescribeSeverityLevels", "support:InitiateChatForCase", "support:ResolveCase" ], "Resource": "" }, { "Effect": "Allow", "Action": "iam:CreateServiceLinkedRole", "Resource": "", "Condition": { "StringEquals": {"iam:AWSServiceName": "servicequotas.amazonaws.com"} } } ] } For descriptions for each action, see the following topics in the Service Authorization Reference: • Actions, resources, and condition keys for AWS Support • Actions, resources, and condition keys for Service Quotas • Actions, resources, and condition keys for AWS Identity and Access Management Create an IAM role After you have your policy, you must create an IAM role, and then attach the policy to that role. You choose this role when you create a Slack channel conﬁguration in the Support Center Console. To create a role for the AWS Support App 1. 2. 3. Sign in to the AWS Management Console and open the IAM console at https:// console.aws.amazon.com/iam/. In the navigation pane, choose Roles, and then choose Create role. For Select trusted entity, choose AWS service. 4. Choose AWS Support App. 5. Choose Next: Permissions. 6. Enter the policy name. You can choose the AWS managed policy or choose a customer managed policy that you created, such as AWSSupportAppRolePolicy. Then select the check box next to the policy. Manage access to the AWS Support App API Version 2025-05-13 454 AWS Support 7. Choose Next: Tags. User Guide 8. (Optional) You can use tags as key–value pairs to add metadata to the role. 9. Choose Next: Review. 10. For Role name, enter a name, such as AWSSupportAppRole. 11. (Optional) For Role description, enter a description for the role. 12. Review the role and then choose Create role. You can now choose this role when you conﬁgure a Slack channel in the Support Center Console. See Conﬁguring a Slack channel. For more information, see Creating a role for an AWS service in the IAM User Guide. Troubleshooting See the following topics to manage access to the AWS Support App. Contents • I want to restrict speciﬁc users in my Slack channel from speciﬁc actions • When I conﬁgure a Slack channel, I don't see the IAM role that I created • My IAM role is missing a permission • A Slack error says that my IAM role isn't valid • The AWS Support App says that I'm missing an IAM role for Service Quotas I want to restrict speciﬁc users in my Slack channel from speciﬁc actions By default, users in your Slack channel have the same permissions speciﬁed in the IAM policy that you attach to the IAM role that you create. This means anyone in the channel has read or write access to your support cases, whether or not they have an AWS account or an IAM user. We recommend

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.