Fix CUR 2.0 export query and crawler IAM boundary#108
Merged
Conversation
Migrate DNS from Domeneshop to Route53 for all javaBin domains. Registrar stays at Domeneshop — only DNS management moves to AWS. Creates 4 hosted zones with all existing records: - java.no: Google Workspace MX, SPF, DMARC, DKIM (Mailchimp/SendGrid), wildcard A, GitHub Pages subdomains - javabin.no: MX forwarding to mail.java.no, DMARC - javabin.com: DMARC only (+ Domeneshop default A/AAAA) - teknologihuset.no: Google MX, Domeneshop email autodiscovery, CalDAV/CardDAV SRV records, GitHub org verification After apply, NS records at Domeneshop need to be updated per domain to complete the cutover. Migration order: javabin.com → javabin.no → java.no → teknologihuset.no.
Alexanderamiri
added a commit
that referenced
this pull request
May 9, 2026
## Summary Fixes two CI failures from the CUR 2.0 deployment: 1. **CUR 2.0 query**: `SELECT *` instead of explicit column names — CUR 2.0 column names differ from legacy CUR docs. The `table_configurations` block already controls what's included (DAILY granularity, RESOURCES, etc.) 2. **Crawler IAM role**: Added `permissions_boundary = var.org_boundary_arn` — the org boundary requires all IAM roles to carry a boundary, otherwise `iam:CreateRole` is denied ## Test plan - [ ] CI plan + apply succeeds - [ ] CUR export is created in us-east-1 - [ ] Glue crawler role is created with boundary attached
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
1 participant
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:
CUR 2.0 query:
SELECT *instead of explicit column names — CUR 2.0 column names differ from legacy CUR docs. Thetable_configurationsblock already controls what's included (DAILY granularity, RESOURCES, etc.)Crawler IAM role: Added
permissions_boundary = var.org_boundary_arn— the org boundary requires all IAM roles to carry a boundary, otherwiseiam:CreateRoleis deniedTest plan