feat(msk): IAM access control for clusters #14647
Conversation
|
|
github-actions
bot
added
@aws-cdk/aws-iam
iliapolo
added
effort/small
curtiseppel
force-pushed
the
msk-iam-auth
branch
from
a8075bd to
796f99d
Compare
MSK now supports IAM access control for client authentication with a MSK cluster. https://aws.amazon.com/about-aws/whats-new/2021/05/introducing-iam-access-control-amazon-msk/
curtiseppel
force-pushed
the
msk-iam-auth
branch
from
796f99d to
e18a4e3
Compare
peterwoodworth
removed
the
response-requested
|
@curtiseppel Can I ask you to resolve the conflicts so the diff is up to date? Thanks! |
iliapolo
added
the
response-requested
There was a problem hiding this comment.
@curtiseppel PR looks good. But build is still failing. Happy to approve after the build passes.
Got mixed up in the previous merge commit
iliapolo
changed the title
iliapolo
changed the title
iliapolo
changed the title
iliapolo
removed
the
response-requested
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
MSK now supports IAM access control for client authentication with a MSK cluster. https://aws.amazon.com/about-aws/whats-new/2021/05/introducing-iam-access-control-amazon-msk/ ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
As far as I can see from the UI the MSK can have both enabled, IAM and SASL/SCRAM, any ideas why we do not allow this in the CDK Level? |
|
@gmuslia Looks like a bug here with the @curtiseppel Not sure how involved you are with CDK anymore but jfyi 😄 |
|
I think this should do it: #31743 cc/ @gmuslia @curtiseppel |
Pointed out [here](#14647 (comment)) and verified in the Console, both `SASL/SCRAM` and `IAM` can be enabled together. Closes #32779 It's a little confusing because [CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-msk-cluster-sasl.html) groups `Iam` and `Scram` together under `Sasl`, but the Console separates the two and allows both at the same time. I'd like to refactor this further but this change unblocks the issue where `SASL/SCRAM` and `IAM` cannot be enabled together. 
MSK now supports IAM access control for client authentication with a MSK
cluster.
https://aws.amazon.com/about-aws/whats-new/2021/05/introducing-iam-access-control-amazon-msk/
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license