Configure AWS Trusted Advisor Integration

Overview

The AWS Trusted Advisor integration imports optimization recommendations from AWS into Yarken, enabling you to review cost optimization opportunities alongside your cloud spend data.

The integration uses an automation recipe to retrieve Trusted Advisor recommendations from AWS and synchronize them with Yarken.

Use this integration when you want to:

• Import AWS Trusted Advisor recommendations automatically.

• Review optimization opportunities in Yarken.

• Eliminate manual exports from AWS.

• Keep recommendation data synchronized on a scheduled basis.

How the integration works

The integration retrieves recommendations from AWS and imports them into Yarken using an automation recipe.

AWS Trusted Advisor > Advanced Connection > Automation Recipe > Yarken

After the recipe completes successfully, the imported recommendations become available for reporting and analysis within Yarken.

Before you begin

Before configuring this integration, ensure that:

• AWS Business Support (or a higher support plan) is enabled.

• The required AWS IAM permissions have been configured.

• The AWS Advanced Connection has been authorized.

• The required automation recipe has been deployed to your environment.

Implementation responsibilities

Configure the integration

Complete the following steps to configure the AWS Trusted Advisor integration.

Step 1: Authorize the AWS connection

Authorize the AWS Advanced Connection using an IAM Role or AWS access keys.

Using an IAM Role is recommended because it provides a more secure authentication method and simplifies credential management.

For instructions, see Authorize Advanced Connections.

Step 2: Review the automation recipe

Navigate to Admin > Pipelines > ADVANCED and open the AWS Trusted Advisor recipe.

Review the recipe configuration and confirm that:

• The AWS connection is configured correctly.

• The execution schedule meets your business requirements.

• Any additional configuration values are correct.

Step 3: Activate the recipe

Start the recipe after verifying the configuration.

Once activated, the recipe retrieves Trusted Advisor recommendations according to its configured schedule.

Validate the integration

After the recipe completes its first execution:

• Verify that the recipe completed successfully.

• Review the recipe execution history.

• Confirm that AWS Trusted Advisor recommendations have been imported into Yarken.

• Verify that recommendation data is available in the appropriate reports or dashboards.

If recommendations are not displayed immediately, allow the synchronization process to complete before validating the results.

Required AWS permissions

The integration requires AWS IAM permissions to access Trusted Advisor recommendations and related optimization services.

Expand the following section to view the minimum required IAM policy.

{
	"Version": "2012-10-17",
	"Statement": [
		{
			"Sid": "CostExplorerRecommendationPermissions",
			"Effect": "Allow",
			"Action": [
				"ce:GetRightsizingRecommendation",
				"ce:GetReservationPurchaseRecommendation",
				"ce:GetSavingsPlansPurchaseRecommendation"
			],
			"Resource": "*"
		},
		{
			"Sid": "ComputeOptimizerRecommendationPermissions",
			"Effect": "Allow",
			"Action": [
				"compute-optimizer:GetEC2InstanceRecommendations",
				"compute-optimizer:GetEBSVolumeRecommendations",
				"compute-optimizer:GetLambdaFunctionRecommendations",
				"compute-optimizer:GetAutoScalingGroupRecommendations",
				"compute-optimizer:GetECSServiceRecommendations"
			],
			"Resource": "*"
		},
		{
			"Sid": "ComputeOptimizerResourceReadPermissions",
			"Effect": "Allow",
			"Action": [
				"ec2:DescribeInstances",
				"ec2:DescribeVolumes",
				"lambda:ListFunctions",
				"lambda:ListProvisionedConcurrencyConfigs",
				"autoscaling:DescribeAutoScalingGroups",
				"ecs:ListClusters",
				"ecs:ListServices"
			],
			"Resource": "*"
		},
		{
			"Sid": "TrustedAdvisorRecommendationPermissions",
			"Effect": "Allow",
			"Action": [
				"trustedadvisor:ListChecks",
				"trustedadvisor:ListRecommendations",
				"trustedadvisor:ListRecommendationResources",
				"support:DescribeTrustedAdvisorChecks",
				"support:DescribeTrustedAdvisorCheckResult"
			],
			"Resource": "*"
		},
		{
			"Sid": "CostOptimizationHubRecommendationPermissions",
			"Effect": "Allow",
			"Action": [
				"cost-optimization-hub:ListRecommendations"
			],
			"Resource": "*"
		},
		{
			"Sid": "RegionDiscoveryPermissions",
			"Effect": "Allow",
			"Action": [
				"ec2:DescribeRegions"
			],
			"Resource": "*"
		}
	]
}

Keeping the IAM policy in an expandable section improves readability while making the required permissions readily available.

Best practices

To improve the reliability and security of this integration:

• Use an IAM Role instead of long-term AWS access keys whenever possible.

• Apply the principle of least privilege when assigning IAM permissions.

• Review recommendation data regularly to identify new optimization opportunities.

• Monitor recipe execution to ensure recommendations continue to synchronize successfully.

Troubleshooting

Related content

• Authorize Advanced Connections

• Manage Automation Recipes

• Automate File Uploads from Cloud Storage

• Troubleshoot Advanced Integrations