Set up Recommendation Integrations

Use this page to configure recommendation data ingestion through Advanced Integrations, including provider connections, pipelines, activation, and monitoring.

Overview

Recommendation integrations bring provider-generated optimization recommendations into Yarken so teams can review, prioritize, action, and report on them alongside manual recommendations.

Recommendations are configured through Advanced Integrations in Yarken. Administrators configure the required connection, activate the related pipeline, refresh internal data after changes, and then validate that recommendation records are appearing in the Recommendations workspace and reporting views.

AWS Recommendations are confirmed in the current documentation and screenshots. Other provider connections and pipelines may appear in your environment depending on what Yarken has enabled for your organization.

How recommendation ingestion works

The integration flow has five parts:

1. A provider source generates recommendations, such as AWS Trusted Advisor Cost Optimization recommendations.

2. A connection in Admin > Pipelines > Connections > Advanced stores the provider authentication settings.

3. A pipeline in Admin > Pipelines > Pipelines > Advanced retrieves, processes, and loads recommendation data into Yarken.

4. Cube Refresh refreshes internal data after recommendation data, connection settings, or pipeline configuration has been updated.

5. The loaded recommendation records appear in Admin > Recommendations and feed reporting such as Recommendations Overview, Recommendations Data, and savings cards on the Home dashboard.

This separates source authentication from the pipeline that loads and monitors the data, while Cube Refresh helps update the internal reporting data after changes.

Before you begin

Before configuring a recommendation integration, confirm that:

1. Advanced Integrations has been enabled for your Yarken environment.

2. The required recommendation connection is available in Connections > Advanced.

3. The related recommendation pipeline is available in Pipelines > Advanced.

4. You have the required Yarken administrative permissions.

5. You have access to the provider account or subscription that will supply recommendations.

6. Required provider credentials, roles, regions, and permissions are prepared.

7. You understand whether the integration should run manually, on a schedule, or through an automation pattern supported in your environment.

For AWS Trusted Advisor, confirm that AWS Trusted Advisor is available for the account and that the required IAM role or access key credentials have been prepared.

Open Advanced Connections

To open recommendation connections:

1. Go to Admin.

2. Open Pipelines.

3. Select Connections.

4. Select the Advanced tab.

5. Open the required recommendation connection, such as AWS Recommendations.

The connection list shows available advanced connections and their connection status.

Configure the AWS Recommendations connection

The AWS Recommendations connection allows Yarken to retrieve AWS Trusted Advisor Cost Optimization recommendations through Advanced Integrations.

To configure the connection:

1. Open Admin > Pipelines > Connections.

2. Select the Advanced tab.

3. Open AWS Recommendations.

4. Select the AWS authorization type.

5. Enter the required authentication details.

6. Enter the AWS region where required.

7. Test or validate the connection where the option is available.

8. Save the configuration.

9. Confirm the connection status shows Connected.

The available fields depend on the authorization method selected.

AWS authorization options

The AWS Recommendations connection supports AWS authentication details required by the configured connector.

The source reference document describes two supported approaches:

Yarken recommends IAM Role where possible because it avoids long-lived access keys and better aligns with AWS security practices.

If using access key authentication, protect and rotate access keys according to your organization's security policy.

AWS permission requirements

For AWS Trusted Advisor recommendation ingestion, the AWS role or user must have the permissions required to retrieve Trusted Advisor recommendation data and validate the AWS identity.

The source reference identifies the minimum permissions as:

Confirm these permissions with your AWS administrator before testing the connection.

AWS region

The AWS Recommendations connection includes an AWS region field.

The screenshots show us-east-1 with guidance that the Trusted Advisor API is hosted in us-east-1. Keep the default unless AWS documentation or Yarken implementation guidance changes.

Open Advanced Pipelines

To open recommendation pipelines:

1. Go to Admin.

2. Open Pipelines.

3. Select Pipelines.

4. Select the Advanced tab.

5. Find the recommendation pipeline, such as AWS Recommendations.

The pipeline list shows the source, destination, run control, activation toggle, and active or inactive state.

Activate or deactivate a recommendation pipeline

The pipeline activation toggle controls whether the pipeline is active.

To activate or deactivate a recommendation pipeline:

1. Open Admin > Pipelines > Pipelines.

2. Select the Advanced tab.

3. Find the recommendation pipeline.

4. Use the activation toggle to activate or deactivate the pipeline.

5. Confirm the pipeline status shows the expected state.

Deactivate a pipeline only when recommendation ingestion should pause or when configuration needs to be corrected before the next run.

Run a recommendation pipeline manually

A recommendation pipeline can be run manually where the run control is available.

To run the pipeline:

1. Open Admin > Pipelines > Pipelines.

2. Select the Advanced tab.

3. Find the recommendation pipeline.

4. Select Run.

5. Wait for the run to finish.

6. Open the pipeline details to confirm the run status.

7. Open Admin > Recommendations to validate that recommendations were loaded or updated.

8. Run Cube Refresh from the bottom of the Admin menu so internal data refreshes after the pipeline run.

Use manual runs after a connection is first configured, after a mapping change, or when validating a corrected setup.

Monitor pipeline run history

Open the pipeline details to review recent runs.

The run history shows information such as:

Selecting a run may show job details and processing steps. Use these details when troubleshooting failures or confirming that the pipeline retrieved and uploaded recommendation data.

Refresh after integration changes

Run Cube Refresh from the bottom of the Admin menu after recommendation connection settings, pipeline configuration, pipeline activation, manual runs, or recommendation ingestion data are updated.

Cube Refresh helps refresh internal data so provider-sourced recommendations and savings values are reflected more quickly across the Recommendations workspace, Home dashboard savings cards, Recommendations Overview, and Recommendations Data.

Validate recommendation ingestion

After configuring and running the integration:

1. Confirm the provider connection status is Connected.

2. Confirm the pipeline status is Active.

3. Confirm the most recent pipeline run shows Succeeded.

4. Open Admin > Recommendations.

5. Check that recommendations appear on the Details tab.

6. Filter by source or resource type to confirm provider-sourced recommendations are present.

7. Review a sample recommendation to confirm savings, source, resource, and status values look correct.

8. Run Cube Refresh from the bottom of the Admin menu.

9. Open Recommendations Overview or Recommendations Data to confirm reporting reflects the recommendation records.

Potential and realized savings from loaded recommendations may also appear elsewhere in Yarken, including savings cards on the Home dashboard where configured.

Troubleshooting recommendation integrations

If provider recommendations do not appear in Yarken, check:

1. The connection status is Connected.

2. The provider credentials, role, or access key are valid.

3. Required provider permissions are assigned.

4. The AWS region is correct for the connector.

5. The related pipeline is Active.

6. The pipeline has run after the connection was configured.

7. The latest run did not fail.

8. Run history errors have been reviewed.

9. Cube Refresh was run after connection, pipeline, upload, or recommendation data changes.

10. Recommendation records are not hidden by filters in the Recommendations workspace.

11. The provider has generated recommendations for the connected account.

If the connection is valid but the pipeline fails, review the run history and job details first. If the pipeline succeeds but no recommendations appear, check whether the provider returned supported recommendation records.

Recommended practices

1. Use IAM Role for AWS connections where possible.

2. Keep provider credentials protected and rotate them according to your organization's policy.

3. Validate a new connection with a manual pipeline run before relying on scheduled ingestion.

4. Run Cube Refresh after connection changes, pipeline changes, manual runs, or recommendation ingestion updates.

5. Review run history after activation.

6. Document which source accounts or subscriptions feed recommendations into Yarken.

7. Review imported recommendations before using them for executive savings reporting.

8. Coordinate with cloud owners before acting on provider-generated recommendations.

9. Treat provider estimates as directional until implementation and realized savings are confirmed.

Next step

Recommendations Overview

Related content

Recommendations

Manage Recommendations

Upload Recommendations

Recommendations Data