The AWS Trusted Advisor integration imports supported AWS optimization recommendations into Yarken so you can review cost optimization opportunities alongside your cloud spend data.
Yarken deploys and maintains the Advanced Integration for your environment. Your organization prepares the required AWS access and authorizes the Advanced Connection.
The integration helps you:
-
Import AWS Trusted Advisor recommendations automatically.
-
Review optimization opportunities in Yarken.
-
Reduce manual exports from AWS.
-
Keep recommendation data synchronized through the deployed Advanced pipeline.
How the integration works
The integration follows this flow:
-
AWS Trusted Advisor provides supported recommendation data.
-
AWS Recommendations Advanced Connection authenticates Yarken with AWS.
-
Yarken-managed integration workflow retrieves and processes the recommendation data.
-
Advanced pipeline runs the integration and records the execution result.
-
Recommendations displays the imported recommendation records in Yarken.
Before you begin
Before you configure the integration:
-
Confirm that Yarken has enabled the AWS Recommendations Advanced Integration for your environment.
-
Confirm that AWS Trusted Advisor is available for the AWS account you want to connect.
-
Prepare the AWS authorization details required by the deployed connection.
-
Configure the AWS permissions required by the connection.
-
If you need member-account recommendations, confirm that Cost Optimization Hub organization enrollment is enabled.
-
Use a Yarken administrator account to authorize the Advanced Connection.
Implementation responsibilities
|
Activity |
Responsibility |
|---|---|
|
Deploy and maintain the Advanced Integration |
Yarken |
|
Configure the integration workflow |
Yarken |
|
Configure AWS permissions and credentials |
Your AWS administrator |
|
Authorize the AWS Recommendations connection |
Your Yarken administrator |
|
Run or activate the Advanced pipeline |
Admin or Cost Model Manager |
|
Validate imported recommendations |
Your organization |
Authorize the AWS Recommendations connection
-
Go to Admin > Pipelines > Connections.
-
Select the ADVANCED tab.
-
Open the AWS Recommendations connection.
-
Complete the required connection fields.
-
Select Connect.
-
Confirm that the connection status changes to Connected.
|
Field |
Requirement |
Description |
|---|---|---|
|
AWS authorization type |
Required |
Select the authorization method for the connection. IAM role is recommended where supported. |
|
Access key ID |
Required when using Access key |
Enter the AWS access key ID used by the connection. |
|
Secret access key |
Required when using Access key |
Enter the corresponding AWS secret access key. |
|
Session token |
Optional |
Required when you use temporary AWS STS credentials. |
|
AWS region |
Optional |
Use us-east-1 for the Trusted Advisor API unless your implementation requires a different value. |
Required AWS permissions
Ensure the AWS identity used for the integration has the following permissions:
-
trustedadvisor:List* -
cost-optimization-hub:ListRecommendations -
sts:GetCallerIdentity
Cost Optimization Hub organization enrollment is required to return member-account recommendations.
Assign only the permissions required for the integration.
Run the AWS Recommendations pipeline
After the connection shows Connected:
-
Go to Admin > Pipelines > Pipelines.
-
Select the ADVANCED tab.
-
Locate the AWS Recommendations pipeline.
-
Select Run to start an immediate execution, or activate recurring execution when required.
-
Open the pipeline to review the run result.
See Manage Advanced pipelines for the common pipeline controls.
Validate the integration
After the first successful pipeline run:
-
Confirm that the AWS Recommendations connection shows Connected.
-
Confirm that the latest Advanced pipeline run succeeded.
-
Open Admin > Recommendations.
-
Confirm that AWS recommendation records are available.
-
Review a sample recommendation to confirm that the source, resource, savings, and status information is populated as expected.
If recommendations are not displayed immediately, allow the synchronization process to complete before validating the results.
Best practices
-
Use an IAM role where your environment supports it.
-
Apply least-privilege AWS permissions.
-
Protect and rotate AWS credentials according to your organization's security policy.
Do not expose AWS access keys, secret access keys, or session tokens in screenshots, documentation, email, chat, or support tickets.
-
Validate a newly authorized connection with a manual pipeline run.
-
Review failed runs promptly.
-
Review imported recommendations before using them for savings reporting or action planning.
Troubleshooting
|
Issue |
Possible cause |
What to check |
|---|---|---|
|
No recommendations are imported |
AWS returned no supported recommendations, or required access is missing. |
Confirm that AWS Trusted Advisor has recommendation data for the connected account and verify the required AWS permissions. |
|
Member-account recommendations are missing |
Cost Optimization Hub organization enrollment is not enabled. |
Confirm that Cost Optimization Hub organization enrollment is enabled. |
|
Authentication fails |
The AWS credentials are invalid, expired, or incomplete. |
Verify the authorization type, Access key ID, Secret access key, and Session token when temporary STS credentials are used. |
|
The pipeline fails |
Connection, permission, or provider issue. |
Review the failed run and job details, then confirm that the Advanced Connection still shows Connected. |
|
The pipeline succeeds but recommendations do not appear |
No supported recommendation records were returned or synchronization is still completing. |
Confirm that AWS has recommendations for the account and allow the synchronization process to complete before checking again. |
For general Advanced Integration issues, see Troubleshoot Advanced Integrations.
Related content