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.

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

Imported Datasets with KMS key blocks the environment stack update #1024

Closed
ozggumus-aws opened this issue Jan 31, 2024 · 4 comments
Closed
Labels
status: can't reproduce This doesn't seem right status: closing-soon type: bug Something isn't working

Comments

@ozggumus-aws
Copy link

ozggumus-aws commented Jan 31, 2024

Describe the bug

After we import an S3 bucket that is encrypted with a KMS key, we can't update the environment. I receive this error in the cdkproxy logs:
Failed to get kms key id of alias/SSE-S3: An error occurred (NotFoundException) when calling the DescribeKey operation: Alias arn:aws:kms:eu-central-1:AWSAccountNumber:alias/SSE-S3 is not found.

Currently solved this issue by adding manual permissions to pivot role to describe key for SSE-S3.

How to Reproduce

  1. import a bucket with KMS key
  2. try to update the environment stack

Expected behavior

No response

Your project

No response

Screenshots

No response

OS

Win

Python version

python3.9

AWS data.all version

v2.2.0

Additional context

No response

@dlpzx
Copy link
Contributor

dlpzx commented Feb 5, 2024

Hi @ozggumus-aws, thanks for raising an issue. This issue looks a lot like an issue that was solved a couple of versions ago. Which version of the code are you running?

@dlpzx dlpzx added type: bug Something isn't working status: needs more info labels Feb 5, 2024
@ozggumus-aws
Copy link
Author

@dlpzx It's v2.2, we still have this issue when a new s3 bucket is imported

@dlpzx
Copy link
Contributor

dlpzx commented Mar 12, 2024

We have been testing this issue and are not able to duplicate. Does the error persists? @ozggumus-aws, are you using auto-cerated CDK pivot role or manual created pivot role?

@dlpzx
Copy link
Contributor

dlpzx commented Apr 15, 2024

We will close this item as it has been stale for a while. @ozggumus-aws If this issue persist, please let us know in this issue or in another new issue and we will work on it.

@dlpzx dlpzx closed this as completed Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: can't reproduce This doesn't seem right status: closing-soon type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants