Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AWS MQ now supports RabbitMQ engine #1262

Closed
sebandgo opened this issue Dec 7, 2020 · 2 comments
Closed

AWS MQ now supports RabbitMQ engine #1262

sebandgo opened this issue Dec 7, 2020 · 2 comments
Assignees
@stack72
Labels
area/providers kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Milestone
0.71

Comments

@sebandgo
Copy link

sebandgo commented Dec 7, 2020

File: docs/reference/pkg/aws/mq/broker.md

According to AWS (Nov. / 2020 announcement), RabbitMQ engine is now available: https://aws.amazon.com/about-aws/whats-new/2020/11/announcing-amazon-mq-rabbitmq/ and also https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/broker-engine.html

PS: Sorry, not sure if this supposed to be submitted on Issues
@leezen leezen transferred this issue from pulumi/docs Dec 11, 2020
@leezen
Copy link
Contributor

leezen commented Dec 11, 2020

Tracked upstream in hashicorp/terraform-provider-aws#16030

@stack72 stack72 self-assigned this Apr 21, 2022
@stack72 stack72 added kind/enhancement Improvements or new features resolution/fixed This issue was fixed labels Apr 21, 2022
@stack72 stack72 added this to the 0.71 milestone Apr 21, 2022
@stack72
Copy link
Contributor

stack72 commented Apr 21, 2022

This has been fixed and released - sorry for the lack of response here

Paul

@stack72 stack72 closed this as completed Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stack72 stack72

Labels
area/providers kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Milestone
0.71
Development

No branches or pull requests
3 participants
@stack72 @leezen @sebandgo