blocking launches originating from most cloud providers, being free anonymous compute, is vulnerable to abuse, especially by cryptocurrency miners. We have various measures to prevent abuse, but given the permissive nature of Binder’s spec, that often means identifying patterns of abusive behavior and disabling them, which can catch legitimate use in the net.

The latest pattern we have identified is automating requests originating from datacenters, especially AWS. As a result, we are going to start blocking launch requests coming from known datacenters (AWS, Google, Azure). This means, for example, that you won’t be able to request new binder launches from within binder itself.

The downside: There may be legitimate use cases that stop working! If you see an error like “Requests from AWS are not allowed”, let us know what you are trying to do and we’ll see if there’s something we can solve.