golovast

We currently self-host on kubernets/aws. The thing that really got to me isn't the new charge per se. It's the fact that GHA has a ton of problems. I can hold my nose and deal with them when it's free. But now that you're squeezing me, at least you could have created something like GHA 2.0 and added a charge for that. Instead, there are vague roadmap promises which don't even include things that I care about. Specifically:

- Jenkins had better kubernetes integration years ago. It's crazy that GHA can't beat that.

- "Reintroducing multi-label functionality" - yeah, so they first broke it. They did supply "reasons", which looked like they never talked to a customer. [1]

- Still no SDK of any kind.

- "Actions Data Stream" - or you can just fix your logging.

There are dozens more complains, which are easy enough to find. This kind of an approach just makes me want to make sure that I don't use GHA again. Even if I end up paying another vendor, at least I'll be treated as a customer.

For some scenarios, resource-based policies can form the foundation of your auth flow. If you look at the flows described in the docs [1], resource evalutionn is simpler. You still need to solve the problem of effectively managing all of those resource policies and limitations on where they can be applied [2]. That might be an easier problem to solve then dealing with trying to express everything as an identity policy. You're then less concerned with wider permissions at the IAM level and move the responsibility to the owner of the resource.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standarize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

Factual is a location data company. A startup, but we have been around for ~10 years. Some of the tech we use: AWS, colo, hadoop ecosystem, kubernetes and much more. Looking to expand and grow our systems engineering discipline.

Factual is a location data company. A startup, but we have been around for ~10 years. Some of the tech we use: AWS, colo, hadoop ecosystem, kubernetes and much more. Looking to expand and grow our systems engineering discipline.

Factual is a location data company. A startup, but we have been around for ~10 years. Some of the tech we use: AWS, colo, hadoop ecosystem, kubernetes and much more. Looking to expand and grow our systems engineering discipline.

But in another place we decided to use troposphere[0] and I liked it more (at least for AWS-only shops). A lot more flexibility and you're relying on Cloudformation to do some of the heavy lifting around states. We basically ended up with a tool based on that library which would generate deployable CF stacks (and some other things).