-
Notifications
You must be signed in to change notification settings - Fork 177
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
[LakeFormation] Error deploying last (third) CloudFormation Stack (AWS Workshop) #1080
Comments
do you have the CUR2 deployed as per workshop? |
Yeap, there's a data export named "cid-cur2", inside the cur 2.0 table, deployed in the payer/mpa account. |
Normally the stack deploy a report in bucket in the payer/mpa account but database and table are deployed in another account. Please make sure that in payer/mpa account the parameter Destination Account is correct and in Destination account that the UPD. sorry in Destination account the Destination account parameter must be the current account |
Updated my recommendation above. Sorry for confusion |
Thanks for your reply @iakov-aws . Yeap, I double checked the source/destination accounts when I deployed the stacks. The main issue, I guess, is in the third stack. Is not finding the table in the athena database, and for sure is there 🤔 |
i see. do you know if you have Lake Formation on this account? |
Yes, we have Lake Formation |
Looks like for LF wee need an additional set of these permissions for this new Database. I think we missed this part. can you add a similar set of permissions manually? |
Hey @iakov-aws sorry for delay I was off during the festive days. So seems the permissions are not working for LakeFormation? How would you recommend adding those permissions manually ? |
We are facing the same Issue without LakeFormation.
![]() |
@joacodm96 Did you find a solution/workaround? |
You need to add a set of permissions manually There are several permissions and you can take them from here just replacing with the dedicated database:
|
@iakov-aws Hey sir! We would really appreciate that extra CFN you mentioned earlier. |
Sorry to hear that. |
@iakov-aws I’ll try to get you that debug call. Meanwhile, we tried deploying with both "yes" and "no" options, but it didn’t work. It seems CFN conditions statements are not working as expected. We also tried granting permissions from the LakeFormation console to the QuickSightRole before the stack deployment failed and started the rollback, but we encountered the same issue. |
Hi guys!
I'm just following up the deployment guide from AWS Workshops, it usually works but this time I have this issue when I deploy the third CloudFormationStack
Seems something change in the stacks/resources-names. Any idea how to solve this?
The text was updated successfully, but these errors were encountered: