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

fix: add glue:GetWorkflows to GLUE statement #111

Closed

Conversation

BenChmark1
Copy link

Summary

Add glue:GetWorkflows permissions to GLUE statement in order to resolve AWS Health alert and to prevent issues on the 16th December when AWS implements the fix mentioned below:

Currently, Glue BatchGet* APIs run successfully despite a Deny condition on one or more of the underlying Get operations. On December 16, 2024, we will deploy a fix for this to ensure BatchGet* APIs will fail with an AccessDeniedException if there is a Deny condition on one of the corresponding Get* operations. Your account has policies which include these contradicting statements. Please refer to the 'Affected resources' tab of your AWSHealth Dashboard to see your impacted IAM resources.

You must update your policies to deny or allow AWS Glue Batch* APIs and their corresponding Get* API operations by this date. If you do not take action, the Batch API will not retrieve the resources of the Batch API call being made.

How did you test this change?

Manually updated the policy in an affected AWS account to confirm the issue is resolved.

Issue

#109

@BenChmark1
Copy link
Author

This has been fixed: #112

@BenChmark1 BenChmark1 closed this Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants