Level: Beginner

Hey Everyone, I made a video of the basics of Ansible Playbooks. Hoping the Animation and walkthrough of running the playbook will help someone.

Video:

https://www.youtube.com/watch?v=GG8ToAngabQ

If you're interested in the code:

https://devopslifecycle.com/lessons/15/ansible-playbooks

Hi all,

Since Reddit and Twitter are getting flaky as services, I have setup a permanent, safe location to consume news: https://devopsish.com/firehose

The page is simple but filled with over 50,000 links from across years of reading and sharing information with y'all. There's even an RSS feed.

Kick the tires and let me know what you think!

Hey r/devopsish - I hope this is okay to post here but if not, let me know.

I’m Curtis, and I’m excited to announce the open-source launch of IAMbic (IAM, but in code), a multi-cloud control plane that simplifies IAM management in a GitOps workflow. It’s like Terraform for Cloud IAM, but way easier. See for yourself on GitHub.

During my time on Netflix’s Cloud Security team, we faced the challenge of managing IAM at scale. We had to manage shared user roles with different permissions for dev and prod accounts, grant temporary access to developers to test new services (which we forgot to remove), protect sensitive policies from misconfiguration, and help users with IAM. Things only got more complex as we added more employees, AWS accounts, applications, and cloud resources. It was like playing Clue to find IAM misconfigurations, Jenga to carefully remove temporary/unused permissions, and Tetris to organize the right access rules for each user and app. These tasks were time consuming and made us dread being on-call.

As permissions piled up, the mental burden of maintenance increased, and security risks and mistakes grew over time. We knew it was only a matter of time before an over-provisioned developer caused critical infrastructure to fail, or even worse, for a sensitive application role to be compromised.

We created IAMbic to solve these problems by making it easy to unify all cloud identities, going beyond access to manage complex cloud permissions, tracking access all the way from users to cloud resources, and presenting everything in a human-readable, as-code, and open-source format.

IAMbic supports bidirectional syncing and round-trip capabilities in a GitOps workflow, and includes the following key features:

• Universal Cloud Identity: Integrate identities from AWS IAM and Identity Center, Okta, Azure AD, and Google Workspace with more to come.

• Dynamic AWS Permissions: Multi-account roles with different permissions and access rules on different accounts.

• Temporary Access: Declaratively define and automate expiration dates for cloud access, fine-grained permissions, and identities.

• Drift prevention: Prevent out-of-band changes to IAM resources you want to be exclusively managed via IAMbic, like cookie-cutter roles or sensitive identity provider groups.

• Change History: Keeps a full audit trail of IAM changes in Git, regardless of whether these changes happened through IAMbic

We’re just getting started on our journey to change the way cloud IAM is managed. We’re huge fans of open source and eager to grow together through your feedback and contributions. Try out IAMbic by following the Getting Started guide. We’d love to chat and hear about your experiences in our Slack community.

Hello,

Are you tired of dealing with microservice failures? Check out DoorDash Engineering's latest blog post to learn about common failures and the drawbacks of local countermeasures. The post also explores load shedding, circuit breakers, auto-scaling, and introduces Aperture - an open-source reliability management system that enhances fault tolerance in microservice architectures.

If you're interested in learning more about Aperture, it enables flow control through Aperture Agents and an Aperture Controller. Aperture Agents provide flow control components, such as a weighted fair queuing scheduler for prioritized load-shedding and a distributed rate-limiter for abuse prevention. The Aperture Controller continuously tracks deviations from SLOs and calculates recovery or escalation actions.

Deploy Aperture into your service instances through Service Mesh (using Envoy) or Aperture SDKs. Check out the full post and start building more reliable applications with effective flow control.

DoorDash Engineering Blog Post: https://doordash.engineering/2023/03/14/failure-mitigation-for-microservices-an-intro-to-aperture/
GitHub: https://github.com/fluxninja/aperture
Docs: https://docs.fluxninja.com/