Fix CUR 2.0 export query and crawler IAM boundary#110
Merged
Conversation
- CUR query: use SELECT * (CUR 2.0 column names differ from legacy docs) - Crawler role: add permissions_boundary (org boundary requires it on all roles) - Pass org_boundary_arn to cost-analytics module
Terraform Plan🚧 Changes detected — Plan: 7 to add, 0 to change, 0 to destroy. Plan outputLLM ReviewRisk: 🟢 LOW Plan adds cost analytics infrastructure (CUR export, Glue crawler) and DNS AAAA records with no destructive or security-impacting changes.
|
Alexanderamiri
added a commit
that referenced
this pull request
May 9, 2026
## Summary Fixes two CI failures from the CUR 2.0 deployment (#103): 1. **CUR 2.0 query**: `SELECT *` instead of explicit column names — CUR 2.0 column names differ from legacy CUR. `table_configurations` already controls what's included. 2. **Crawler IAM role**: Added `permissions_boundary` — the org boundary requires all roles to carry a boundary. ## Test plan - [ ] CI plan + apply succeeds - [ ] CUR export created in us-east-1 - [ ] Glue crawler role created with boundary
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes two CI failures from the CUR 2.0 deployment (#103):
SELECT *instead of explicit column names — CUR 2.0 column names differ from legacy CUR.table_configurationsalready controls what's included.permissions_boundary— the org boundary requires all roles to carry a boundary.Test plan