nl5887

I'm using a script that will request an AWS spot instance for 6 hours, reporting the address when fulfilled:

https://gist.github.com/nl5887/56912b70b782baa4bd580ae22bde6...

https://transfer.sh which I built because I needed it myself, now being used by hundred thousands of people a month and http://slackarchive.io used by 500 slack teams.

It is based on the json reference of the aws api, which is being used to generated all different SDKs.

I've created this as my quick and easy reference to all Amazon api's. This works for me better to browse quickly between different calls, and suits my personal workflow more.

Don't know if you've seen it, but different versions have been added.

To be sure, I did it a few months again. Will update and add the version as well. That will allow everyone to choose the right version.

Will take a look at this.

Thx!

thx, will look at that. The docs.json is being generated from the rest-api-spec repo (https://github.com/elastic/elasticsearch/tree/master/rest-ap...). Will see if I can add more on the query dsl as well.

Exactly, who trusts server side encryption anyway?

Yeah, but the thing is that with transfer.sh you don't have to install any applications on your machine. And if you look at the code, you'll see that the max size isn't being enforced.

Big difference with curl.io is that you don't need to register the file upfront.

Sure. You're looking at recorded sessions of real attacks on our honeypots. The commands they're entering, the malware they are uploading.

Good question. We're looking into making this a commercial application if there is interest on it. I can imagine that we'll add pricing models when scheduling over an amount of instances. Lowest tier will be free.

Check out this library: https://github.com/dutchcoders/honos. It adds filtering on host, uri and content type to each request.

Exactly, but now it is integrated in nginx. So this could be an alternative for proprietary software, or Squid.

Added Python and Ruby support btw. Supporting 9 languages now.

The commit status have been added :-).

The release with commenting on pull requests is active now. Linthubot will comment on the pull request itself instead of the commit.

Yeah, true. We've tightened the scope, read/write is not necessary any longer. Only for private repo's, the linthubot user needs to be added to the repo with read access.

This is exactly why we've develop this. To enforce code quality to pull requests and save the repository owners time.