-
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
Support for SAML/AD principals in aws_lakeformation_permissions #16848
Comments
Probably “validateprincipal” should be replaced by something lighter for this field - given the wider possibilities of what a LF principal can be - not only SAML/AD but as well Quicksight. |
How about support for IAM federated users? We're using |
Hi , federated-user ? You mean SAml or AD ? The linked pull request supports all allowed principals , as listed here https://docs.aws.amazon.com/lake-formation/latest/dg/lf-permissions-reference.html |
In this case, authentication is done via GetFederationToken (FederatedUser), I was able to apply Lake Formation permissions via CLI using the ARN pattern |
ok, yes, I see. Interesting , never used that. Chris |
Thanks so much! |
adapted validatePrincipal to all allowed lakeformation principals types, solves #16848
This has been released in version 3.38.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 for triage. Thanks! |
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. |
Community Note
Description
The brand new aws_lakeformation_permissions does not seem to support SAML/AD principals (see console, the CLI accepts them without issues)
on lakeformation.tf line 65, in resource "aws_lakeformation_permissions" "xxx":
65: principal = "${local.saml_provider}:group/xxx"
Error: "principal" doesn't look like a user or role: "arn:aws:iam::yyyy:saml-provider/zzz:group/xxx"
New or Affected Resource(s)
aws_lakeformation_permissions
The text was updated successfully, but these errors were encountered: