-
Notifications
You must be signed in to change notification settings - Fork 81
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
Upgrade Athena engine version to v3 #886
Conversation
|
It seems that Athena has deprecated engine version 2 in some regions but not all. When running the command Regions that CANNOT use Athena engine v2:
I tested this PR in eu-central-1 and it solves the issue. Also tested upgrade from engine 2 to 3 and the environment stack updates successfully |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
### Feature or Bugfix <!-- please choose --> - Bugfix ### Detail - When trying to update an Environment to use the latest Athena Version (from this [previous PR](#886)) and having CDK use the data.all provided CDK Execution Policy ran into an `Update_Failed` error on the Environment CloudFormation Stack due to missing permissions for `athena:UpdateWorkGroup` - Added `athena:UpdateWorkGroup` to the CDK Exec Policy YAML file ### Relates - N/A ### Security Please answer the questions below briefly where applicable, or write `N/A`. Based on [OWASP 10](https://owasp.org/Top10/en/). - Does this PR introduce or modify any input fields or queries - this includes fetching data from storage outside the application (e.g. a database, an S3 bucket)? - Is the input sanitized? - What precautions are you taking before deserializing the data you consume? - Is injection prevented by parametrizing queries? - Have you ensured no `eval` or similar functions are used? - Does this PR introduce any functionality or component that requires authorization? - How have you ensured it respects the existing AuthN/AuthZ mechanisms? - Are you logging failed auth attempts? - Are you using or adding any cryptographic features? - Do you use a standard proven implementations? - Are the used keys controlled by the customer? Where are they stored? - Are you introducing any new policies/roles/users? - Have you used the least-privilege principle? How? By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Feature or Bugfix
Detail
It is not a bug yet but Athena has already included he following warning at workgroup creation
Athena engine version 2 will be deprecated in the near future. You can view this information in your AWS Personal Health Dashboard. Workgroups not upgraded by the deprecation date will be upgraded to version 3 automatically.
To avoid future failures, we are updating the engine version selected for the creation to new workgroups in data.all to version 3.
Here is the documentation of version 3 which include the breaking changes from v2. Engine version 3 was released on October 13, 2022 and as it can be verified in the Athena release notes, it has been constantly improved during this year, surpassing in features athena v2.
Relates
Security
Please answer the questions below briefly where applicable, or write
N/A
. Based onOWASP 10.
N/A
fetching data from storage outside the application (e.g. a database, an S3 bucket)?
eval
or similar functions are used?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.