It will really depend on your workflows, what services you use, what risks you're trying to manage and what trade-offs you're willing to accept on usability vs security.
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.
Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York 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 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 | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York 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 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 | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York 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 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 | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York 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 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 | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York 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 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 | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York 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 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 | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York
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 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 | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York
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 | systems/devops/sre engineer | Los Angeles, CA | ONSITE | Full-time
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.
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.
[1] https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_p... [2] https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_a...