Here are some ways the XGBoost CI server can be hit with massive bandwidth bill:
Someone may hard-link a nightly build of XGBoost in their Dockerfile or a Kubernetes script, and each deployment will download the build (~100 MB) from our S3 bucket.
A mis-configured script or CI may send lots of requests to our S3 bucket or the website https://xgboost-ci.net.
AWS charges a premium for outgoing traffic:
This results in surprise bills for many users. Here's one recent example: https://news.ycombinator.com/item?id=23956671
Here are some ways the XGBoost CI server can be hit with massive bandwidth bill:
We need to implement the following mitigation measures:
cc @trivialfis