Closed laurentiush closed 4 months ago
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.
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.
Hi again,
I noticed that you have created a branch which addresses my question and was wondering if you plan to include those changes in a next release.
Hi,
I started working on this some time ago but got distracted with other things. I will try to make some progress soon.
Thanks a lot! I see that it is now available.
Yes, I still need to release the new version. I will do that today.
Hi,
I am running tibanna regularly, but am incurring quite some costs for 2 specific 'usage types':
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