Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turn off cloudwatch and costexplorer #401

Open
laurentiush opened this issue Feb 8, 2024 · 2 comments
Open

Turn off cloudwatch and costexplorer #401

laurentiush opened this issue Feb 8, 2024 · 2 comments

Comments

@laurentiush
Copy link

laurentiush commented Feb 8, 2024

Hi,

I am running tibanna regularly, but am incurring quite some costs for 2 specific 'usage types':

  • EU-CW:MetricMonitorUsage (CloudWatch)
  • USE1-APIRequest (Cost Explorer)

Now that my pipeline is up and running, I don't really need all the detailed information. Is there a way to turn off this logging and monitoring?

One option could be to remove the rights to access Cost Explorer, but I don't know if this will break tibanna:

https://repost.aws/questions/QUhjMTBYs2QGSFcgto3BdJMA/disable-aws-cost-explorer-permissions

@alexander-veit
Copy link
Member

Hi,

currently there is no option to switch it off, but I agree that there should be one. I will look into it.

I think that simply removing Tibanna's permissions to Cloudwatch will probably break it.

@laurentiush
Copy link
Author

Thanks! Especially if you have a lot of small tasks those costs can quickly add up.

At some point I tried grouping rules in snakemake to reduce the number of instances required, but somehow the output was not detected by snakemake after transferring it back to S3 and pipelines would always fail because of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants