-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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.
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
Amazon MSK multi-VPC private connectivity and cross-account access #31062
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I'm so looking forward to this feature. Thank you. |
Those changes have been implemented in awscc:
It seems to match the current implementation of the AWS provider, so wouldn't it be better to follow this solution rather than to create a new aws_msk_cluster_policy? |
We will need to create a new resource for that as per my experiments. Because ability to set the resource policy for MSK cluster only enabled (in the AWS console and AWS CLI) after I enabled multi-VPC connectivity in the cluster. Also why can't they implement it on normal TF aws provider instead of this |
Hi, i will start working with this, this week |
This is my experience as well, you have to start by setting things to false, and then enabling them. |
@ewbankkit Thank you very much for getting the |
This functionality has been released in v5.13.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Amazon MSK now offers multi-VPC private connectivity and cross-account access.
Announcement.
Blog post.
New Resources
aws_msk_vpc_connection
aws_msk_cluster_policy
Requires AWS SDK for Go v1.44.252: #31028.
The text was updated successfully, but these errors were encountered: