Amazon MQ now supports OAuth 2.0 authentication and authorization for RabbitMQ brokers with public identity providers in both single instance and highly available Multi-AZ cluster deployments. This feature enables RabbitMQ brokers to authenticate clients and users using JWT-encoded OAuth 2.0 access tokens, providing enhanced security and flexibility in access management.
You can configure OAuth 2.0 on your RabbitMQ broker on Amazon MQ using the AWS Console, AWS CloudFormation, AWS Command Line Interface (CLI), or the AWS Cloud Development Kit (CDK). This feature is available in all AWS regions where Amazon MQ is available. To get started, create a new RabbitMQ broker with OAuth 2.0 authentication or update your existing broker’s configuration to enable OAuth2.0 support. This feature maintains compatibility with standard RabbitMQ OAuth 2.0 implementations, ensuring seamless migration for existing OAuth 2.0 enabled brokers. For detailed configuration options and steps, refer to the Amazon MQ documentation page.
Categories: general:products/amazon-mq,marketing:marchitecture/messaging,marketing:marchitecture/analytics,marketing:marchitecture/developer-tools
Source: Amazon Web Services
Latest Posts
- (Updated) Microsoft Teams: External domains anomalies report [MC1219794]
- AWS Step Functions adds 28 new service integrations, including Amazon Bedrock AgentCore
- Amazon EC2 I8ge instances are now generally available in additional AWS regions
- AWS Lambda supports up to 32 GB of memory and 16 vCPUs for Lambda Managed Instances
