Compute Optimizer recommendations supported by Trusted Remediator - AMS Advanced User Guide

Compute Optimizer recommendations supported by Trusted Remediator

The following table lists the supported Compute Optimizer recommendations, SSM automation documents, preconfigured parameters, and the expected outcome of the automation documents. Review the expected outcome to help you understand possible risks based on your business requirements before you enable an SSM automation document for check remediation.

Make sure that the corresponding config rule for each Compute Optimizer check is present for the supported checks that you want to enable remediation for. For more information, see Opt in AWS Compute Optimizer for Trusted Advisor checks.

Optimization option SSM document name and expected outcome Supported preconfigured parameters and constraints
Rightsizing

Amazon EC2 instance recommendations

AWSManagedServices-TrustedRemediatorResizeInstanceByComputeOptimizerRecommendation

Amazon EC2 instance type updated according Compute Optimizer recommendations. The most optimal options are chosen while maintain the same platform parameters (Architecture, Hypervisor, Network interface, Virtualization type, and so forth) if the option exists.

  • MinimumDaysSinceLastChange: The parameter to specify minimum number of days since the last instance type change. The default is 7 days.

    No constraints

  • CreateAMIBeforeResize: To create the instance AMI as backup before resizing, set to 'True.' To not create a backup, set to 'False.' Default is 'True'.

    No constraints

Amazon EBS volume recommendations

AWSManagedServices-ModifyEBSVolume

The Amazon EBS volume is modified according to Compute Optimizer recommendations. Modification may include volume type, size, IOPS, volume generation (gp2, gp3 etc).

  • CreateSnapshot: To create a snapshot before modifying the volume, set to 'True.' To not create a snapshot, set to 'False.' The default is 'True'.

    No constraints

  • VolumeType: The desired volume type. If no type is specified, the existing type is retained.

    No constraints

  • VolumeSize: The desired size of the volume, in GiB. The target volume size must be greater than or equal to the existing size of the volume. If no size is specified, the existing size is retained.

    No constraints

  • Iops: The requested number of I/O operations per second (IOPS). This parameter is only valid for io1, io2 and gp3 volumes.

    No constraints

  • Throughput: The throughput to provision for a volume, with a maximum of 1000 MiB/s. This parameter is valid only for gp3 volumes.

    No constraints

  • RemediateStackDrift: To initiate drift remediation, if any drift is caused by volume modification, set to 'True.' To not attempt drift remediation, set to 'False.' Default is 'True'.

    No constraints

Lambda function recommendations

AWSManagedServices-TrustedRemediatorOptimizeLambdaMemory

AWS Lambda function memory optimized according to Compute Optimizer recommendations.

RecommendedMemorySize : Custom memory size, if different from recommended options.

No constraints

Idle resources

Idle Amazon EBS volume

AWSManagedServices-DeleteUnusedEBSVolume

Unattached Amazon EBS volume will be deleted.

  • CreateSnapshot: To create a snapshot before deleting the volume, set to 'True.' To not create a snapshot, set to 'False.' The default is 'True'.

    No constraints

  • MinimumUnattachedDays: Minimum unattached days of the Amazon EBS volume to delete, up to 62 days. Default is 7.

    No constraints

Idle Amazon EC2 instance

AWSManagedServices-StopEC2Instance

The idle Amazon EC2 instance will be stopped.

ForceStopWithInstanceStore: To force stop for instances using instance store, set to 'True.' To not force stop, set to 'False.' Default value 'False' prevents the instance from stopping.

No constraints

Idle Amazon RDS instance

AWSManagedServices-StopIdleRDSInstance

Stop an idle Amazon RDS instance. Supported engines are: MariaDB, Microsoft SQL Server, MySQL, Oracle, PostgreSQL. This document doesn't apply to Aurora MySQL and Aurora PostgreSQL. The instance will be stopped up to 7 days and relaunched automatically.

No preconfigured parameters are allowed.

No constraints