This is the news section. It has two categories: News and Releases.
Files in these directories will be listed in reverse chronological order.
This is the multi-page printable view of this section. Click here to print.
This is the news section. It has two categories: News and Releases.
Files in these directories will be listed in reverse chronological order.
Some automation only works in the management/payer account. Cost Explorer alarms, organization-wide billing notifications, anything that has to read AWS::Billing data or talk to the Organizations API as the master account. That stuff doesn’t fit in a workload account, and it doesn’t fit in the security account either.
Until now, the answer was “click that CloudFormation in by hand” or “stand up a second Terraform config just for the payer.” Both options suck.
Org Kickstart now has a payer_cloudformation_stacks variable. Drop a map entry, point it at a template (local file or S3 URL), pick your regions, set your parameters. The next apply deploys it into the payer.
payer_cloudformation_stacks = {
billing_alerts = {
stack_name = "slack_billing_alerts"
template_file = "cloudformation/slack-Template.yaml"
regions = ["us-east-1"]
parameters = {
pExecutionRate = "cron(0 09 * * ? *)"
pEventInput = <<-EOT
{
"threshold": "10",
"alert_percent": "20"
}
EOT
pSlackWebhookSecret = "SlackWebHook"
pRuleState = "ENABLED"
pAccountDescription = "My-Payer"
}
}
}
A few things worth knowing:
aws_cloudformation_stack.payer["<key>-<region>"] (e.g., billing_alerts-us-east-1). Add a second region later and the existing stack doesn’t get renamed.template_file vs template_url. Exactly one per stack. template_file is a local path relative to your tfvars repo root. template_url is an HTTPS or S3 URL.regions is optional. Omit it and the stack deploys only in the base org-kickstart region.CAPABILITY_IAM, CAPABILITY_NAMED_IAM, and CAPABILITY_AUTO_EXPAND. If you want stricter capabilities, this isn’t the feature for you.jsondecode | jsonencode so the literal you write in tfvars matches what CFN stores. Non-JSON strings pass through unchanged.See the parameter reference for the full schema and an example tfvars for context.
Org Kickstart v0.3.0 is now available — the largest release yet. It adds the newest AWS Organizations policy types, first-class CloudFormation deployment, a managed Terraform state bucket, declarative resource adoption, the Account Configurator integration, and a full documentation site at aws-kickstart.org.
payer_cloudformation_stacks
and security_account_stacks to deploy arbitrary CloudFormation stacks (per-region) into the
payer and security accounts directly from Terraform.manage_state_bucket (default on) adopts your existing
backend_bucket and enforces versioning, public-access-block, and encryption, with
prevent_destroy so it can’t be deleted.examples/local-deploy/import.tf adopts the Organization, payer
account, and state bucket via import blocks, so a brand-new org no longer needs
scripts/import_org.sh for the foundational resources.make account-configurator) to harden new accounts on creation.
See the docs.security_account block gives the security account
the same configuration options as every other account.aws_service_access_principals / enabled_policy_types exclusions (thanks
Ashex!).examples/local-deploy.security_account block is now
required in your tfvars. Apply SSO delegated admin there if you want it.org_policies module and attachments switched from count to for_each. Resources will be
renamed/recreated unless you terraform state mv them — see the
full notes for the
exact commands.depends_on to several Organizations resources (AI policy, RAM sharing, the
SCP/RCP/Declarative modules, and the CUR report) that previously raced creation on a first apply.granted Make target so it always runs and writes granted/aws-config.Going forward, latest is the default working branch — it always holds the newest changes.
Each release is a frozen, tagged version (like 0.3.0); pin to one with
source = "github.com/primeharbor/org-kickstart?ref=0.3.0".
We target quarterly releases, but may cut a new version sooner when significant new AWS organization-management features warrant it. See the Releases page for details.
The full v0.3.0 release notes — including the security-services provider→region migration — are on GitHub.
Org Kickstart v0.3.1 is a small bug-fix release.
sso_instance_region. Previously only the data sources were region-aware, so deploying with
Identity Center enabled in a non-default region targeted the wrong region. Thanks to
@mattgillard for the fix and for flagging it (PR #30).See the full release notes on GitHub.
Org Kickstart v0.2.0 is now available with expanded account management capabilities and several new optional features.
security_account block is now required in the tfvars fileSee the full release notes on GitHub.