EC2 and RDS Recommendations Not Generated Despite Underutilized Instances

[Haritha-06]

Hi team,

We have successfully configured OptScale on our Ubuntu machine and integrated it with our AWS account. Billing data is being collected correctly, however, EC2 and RDS recommendations (underutilized instances) are not being generated. The dashboard displays “All Good,” even though we do have underutilized resources.

[VR-Hystax]

Hello @Haritha-06
Could you please provide:

1. Commit or release version from which you deployed OptScale
2. Error trace from the DevTools browser( in Console tab) for Integrations page:

[Haritha-06]

Hi Team,

Thanks for the response, please find below required details.

1. commit 1c9144f (HEAD -> integration, origin/integration, origin/HEAD)
   Merge: 5ef0b8b 9f8c748
   Author: stanfra 142495589+stanfra@users.noreply.github.com
   Date: Fri Jul 4 12:13:43 2025 +0400

   Pull request update/250704

   9f8c748 OSN-979. Fixed Azure reimport

[VR-Hystax]

Hello @Haritha-06
Our OptScale engineering team will investigate it and issue a conclusion.

[VR-Hystax]

Hello @Haritha-06
Please check is a credentials service that insider uses to take pricing from the cloud.
Use the link below:
https://github.com/hystax/optscale/blob/integration/optscale-deploy/overlay/user_template.yml#L7

[Haritha-06]

Hello team,

Thanks for update,

I have updated the user_template.yml file accordingly by adding valid AWS access and secret keys under service_credentials.aws, exactly as shown in the
https://github.com/hystax/optscale/blob/integration/optscale-deploy/overlay/user_template.yml#L7

After making the change, I redeployed the cluster using the following command to apply the updated credentials:

./runkube.py --with-elk --no-pull -o overlay/user_template.yml -- local

Post-deployment, I manually force-checked the in the UI, but recommendations for EC2 and RDS are still not being generated.

Could you please confirm the following:

Is there any additional step required after updating credentials to trigger the recommendation engine

If we have multiple data sources (AWS accounts) added in the UI, how to include them under service_credentials

[Haritha-06]

Hi @VR-Hystax

We're still awaiting for response, and your support would be really helpful for us to proceed further. Kindly let us know if there's any update or if any additional information is needed from our side.

[VR-Hystax]

Hello @Haritha-06
Please provide the logs of bumiworker and insider from the Kibana service.
You can find out how to use the Kibana service by clicking on the link below:
documentation/kibana_logs.md

[Haritha-06]

Hi @VR-Hystax

Thanks for the reply, please find the logs of bumiworker and insider.

Untitled discover search.csv
Untitled discover search (1).csv

[VR-Hystax]

Hello @Haritha-06
We will review the information you provided and provide a conclusion as soon as possible.

[Haritha-06]

Hello @VR-Hystax

We're awaiting for response, and your support would be really helpful for us to proceed further. Kindly let us know if there's any update

[VR-Hystax]

Hello @Haritha-06
We are still working on your issue.
As soon as we complete the work, I will notify you immediately.

[VR-Hystax]

Hello @Haritha-06
We found this entry in the logs:

ht742_default_bumiworker-8286315fca216e4ac8d4c2604db6f2b85474e9dc3ac8b2a22087558793fcc709.log","72,794","bumiworker-7fccf4ccbc-ht742 botocore.exceptions.ClientError: An error occurred (AuthFailure) when calling the DescribeRegions operation: AWS was not able to validate the provided access credentials","bumiworker-7fccf4ccbc-ht742 botocore.exceptions.ClientError: An error occurred (AuthFailure) when calling the DescribeRegions operation: AWS was not able to validate the provided access credentials"

Looks like the root cause is a invalid credentials.

[Haritha-06]

Hi @VR-Hystax,

Thanks for the update. The error occurred after we updated the user_template.yml file by adding AWS access and secret keys under service_credentials.aws. Since the data sources had already been added in the dashboard before updating the credentials in the user_template.yml, we removed the data sources and added them again.

Now, we are able to retrieve cost-related data. However, regarding recommendations, we are still only receiving the same two as before: Obsolete Images and Inactive IAM Users. These two recommendations were visible even before we raised this issue, and the situation remains unchanged.

I am sharing the updated logs and screenshots for your reference.

Untitled discover search (4).csv
Untitled discover search (3).csv

[VR-Hystax]

@Haritha-06
We will investigate the information you provided and try to give a conclusion as soon as possible.

[VR-Hystax]

Hello @Haritha-06
Again, credentials looks invalid:
DescribeRegions operation: AWS was not able to validate the provided access credentials'}, {'module': 'obsolete_snapshots', 'error': 'An error occurred (AuthFailure) when calling the DescribeRegions operation: AWS was not able to validate the provided access credentials'}, {'module': 'abandoned_instances', 'error': 'Timeout error while process task 1752915526 (organization_id d1252ed9-f722-45ae-b702-b9f9eb05a493, module abandoned_instances(archive), try 0), step Process'},