irabinovitch1
a) Is there an example of a cloud provider adopting or building on top of your existing AGPL code bases? The big 3 all have fairly well known internal policies that forbid AGPL use. Ever wonder why there isn't there a MongoDB service being offered by any of the major cloud providers? AGPL.
All that being said I doubt they would want your modules anyways. Their track record tends to be:
* AWS would grab the core BSD licensed project, ignore your management tooling regardless of license, and build their own management tooling that integrates with their ecosystem. Theres a few exceptions to this like [Chef and AWS on OpsWorks](https://twitter.com/adamhjk/status/1032312528196575234).
* Google. They wont use your software either. If anything they'll build some wizbang redis like protocol and interface on one of their internal proprietary databases. All the software will work the same, but it'll be "better" because its powered by BigTable/Spanner/whatever.
* Microsoft. 50/50 shot they might actually just license your code and partner if they thought customers wanted it.
b) I'm not surprised that large customers aren't AGPL fans. Isn't this where they should come in with a dual-license approach and sell commercial licenses to the software you develop? So whats the win here?
Moitorama 2018 Talks
Protocol Buffers Parsing and Performance in Python
Apache Spark Cluster Monitoring with Databricks and Datadog
Interferon: OSS Alerting Framework at Airbnb
Redux-Doghouse – Creating Reusable React-Redux Components Through Scoping
On Friday, September 30th a number of Datadog-AWS shared customers received an erroneous email notification from AWS about compromised AWS access keys associated with Datadog. AWS intended to reach out to shared customers that had been lax in deactivating and deleting access keys associated with the 7/8/2016 Datadog breach (https://www.datadoghq.com/blog/2016-07-08-security-notice/). AWS accidentally sent out a standard compromise notification to the original list of shared customers. False positives abound! You can validate this error by contacting your AWS support contact.
As recommended in our original communication, if you have not you should deactivate and delete any service integration credential shared with Datadog on or prior to 7/8/2016 immediately and for AWS transition to Role Delegation as outlined here: https://help.datadoghq.com/hc/en-us/articles/210376966-Revok...
The AWS communication was made in error. If you received the initial message you should have also received a retraction. Customers that have been lax in deactivating and deleting these access keys will receive additional communication directly from AWS.
Ilan from Datadog here. Thanks for posting this and for your patience as we conduct our investigation. We emailed all users and administrators early this morning that we were resetting their passwords, and to encourage they rotate credentials as appropriate.
We have posted a notice (https://www.datadoghq.com/blog/2016-07-08-security-notice/) on our website as well. As is our practice, you can expect a post-mortem with additional details once our investigation is complete. In the mean time if we can help address any questions or concerns please do reach out via [email protected]. I can also personally be reached at [email protected].
Regards, Ilan