How Picnic Configured Multi-Provider OAuth for Amazon MQ RabbitMQ
This post details how Picnic, an Amsterdam-based tech scale-up, configured Amazon MQ for RabbitMQ to authenticate users from multiple OAuth 2.0 identity providers simultaneously. It showcases a solution where a single RabbitMQ broker trusts both Keycloak for human operators and AWS IAM for services, leveraging the `aud` claim for provider selection. This approach enables distinct authentication strategies for different user types without disrupting existing connections. The guide provides architecture and implementation steps, illustrating how to map provider scopes to RabbitMQ permissions.
Notes (1) ›
- Configuring Multi-Provider OAuth for Amazon MQ RabbitMQ
The post details a solution for Amazon MQ for RabbitMQ to handle authentication from multiple OAuth 2.0 identity providers concurrently. It explains how to configure a single broker to trust both Keycloak for human operators and AWS IAM for service workloads, demonstrating how to map provider scopes to RabbitMQ permissions and roll out changes without disruption.
https://aws.amazon.com/blogs/big-data/how-picnic-configured-multiple-oauth-providers-for-amazon-mq/
Related releases
- Break-Glass Access for Amazon EKS When Federated Identity Fails AWS Containers Blog ·
- IAM Roles Anywhere adds Java SDK plugin for direct temporary credentials AWS What's New ·
- AWS Lake Formation Enables Fine-Grained Access for S3 Tables with BigQuery AWS Big Data Blog ·
- Enable Cross-Cloud Analytics with S3 Tables and Google BigQuery via IAM AWS Big Data Blog ·
- AWS Lambda functions now support full IAM resource-based policies AWS What's New ·
- Amazon EKS now supports multiple external OIDC identity providers per cluster AWS What's New ·