vivekl · HackerTrans

hace 5 añosdiscuss

Don't hold having an MBA against Jassy :). I have been in those ops meetings at AWS when Andy Jassy and Charlie Bell used to hold court. There wasn't much MBA-speak there. Jassy can burrow through deeply technical issues, spot fundamental flaws and process a monumental amount of information on the spot - skills they sure as hell don't teach at any B-school I know of...

vivekl

hace 6 añosdiscuss

This problem would have been even more pronounced if running from a co-lo/non-cloud entity. Imagine getting a court-ordered shutdown or confiscation of servers for evidence etc. Frankly you would expect a "high"-profile/controversial service like Parler to have at least conceived of the possibility of a take-down from a cloud service and had a plan in place for it. Amazon had already cut ties with Gab last year [1] so this should not have been a huge surprise.

[1] https://www.buzzfeednews.com/article/ryanmac/far-right-haven...

vivekl

hace 6 añosdiscuss

We reported this issue back in 2018 to AWS! In our case it was exacerbated because of a NAT through which traffic to the cross-AZ loadbalancer would flow. As mentioned in the article, the client side is free to reuse ports as long as the destination in the tuple is different - as would be the case for cross-AZ NLB.

We reduced the severity of this by randomizing port mappings on the NAT but that just reduces the probability. They claimed that it was a high priority issue for them back then but seems this is still in the wild - insane!

vivekl

hace 7 añosdiscuss

While AWS has ruffled a bunch of feathers with their Elasticsearch and Kafka managed offerings which can be easily construed as attempts to steam roll the respective open source-first entities, I am actually quite impressed by the mechanism that Azure has employed with Azure Managed Applications: https://docs.microsoft.com/en-us/azure/managed-applications/.... Hashicorp recently announced their collaboration with Azure to bring forth managed consul offering using this: https://www.hashicorp.com/blog/announcing-consul-service-on-...

This in my opinion is the right way to solve the problem, i.e. provide the customers that want a managed offering the means to get a managed version directly from the entity most active behind the project, (e.g. Hashicorp) while getting the most from the cloud provider's infrastructure. I would be willing to trust Confluent or Hashicorp with operating/managing my Kafka or consul cluster but taking another dependency on their respective cloud offerings should be of concern.

I am quite surprised that its Azure that has shown creativity here while AWS and Google have limited themselves to offering marketplace AMIs/images at ridiculous markups.

comments