Self-service AWS CodePipeline platform — developers ship compliant CI/CD pipelines in minutes via dashboard, CLI, CDK, or AI prompt, while platform teams enforce policy-as-code guardrails, governance, and per-team isolation.
Add-on bundles are purchasable packs that stack on top of an account’s subscription tier to raise its caps or unlock features — without moving the whole account to a higher tier. A team that needs a few more seats or one more pipeline buys the matching pack instead of jumping from Pro to Enterprise.
Bundles complement the feature tiers: the tier sets the baseline, bundles adjust it. For the org/team model the caps apply to, see Organization Benefits → Organizations, Teams & Billing.
An account’s effective limit for any quota is its tier baseline plus the sum of every applied bundle’s grant, scaled by quantity:
effective[quota] = tierBase[quota] + Σ (bundle.grant[quota] × quantity)
-1, e.g. Team/Enterprise apiCalls) stays unlimited — bundles never shrink it.Billing computes the effective entitlement and syncs it to the enforcing services: the nine tracked quota types go to the quota service, while seats and purchased features (audit_log, sso) go to the platform service (PUT /organization/{orgId}/seat-limit). Both target the account root.
Prices are the built-in defaults (USD); annual defaults to 10× monthly. Every price, grant, and eligible-tier list is env-overridable (see Overrides).
| Bundle | Grant | Monthly | Annual | Available to | Stackable |
|---|---|---|---|---|---|
| Seat Pack | +5 member seats | $25 | $250 | all tiers | ✅ |
| Pipeline Pack | +10 pipelines | $15 | $150 | all tiers | ✅ |
| Plugin Pack | +100 plugins | $15 | $150 | all tiers | ✅ |
| API Pack | +1,000,000 API calls / period | $20 | $200 | all tiers | ✅ |
| AI Pack | +5,000 AI calls / period | $75 | $750 | all tiers | ✅ |
| Storage Pack | +50 GB registry storage | $25 | $250 | all tiers | ✅ |
| Audit Log | unlocks the audit_log feature |
$20 | $200 | Pro | ❌ |
| SSO / IdP | unlocks sso + up to 5 IdP configs |
$40 | $400 | Pro, Team | ❌ |
Notes:
For an account with teams (the org → team hierarchy), bundle grants raise the root account’s pooled caps, and the whole subtree draws from that shared pool:
Bundles are managed through the billing service (dashboard Billing page or the API). Mutations require an org admin/owner.
| Action | Endpoint |
|---|---|
| List available bundles | GET /bundles |
| Preview the effect of an add-on change | POST /subscriptions/:id/addons/preview |
| Add / change an add-on | POST /subscriptions/:id/addons |
| Remove an add-on | DELETE /subscriptions/:id/addons/:bundleId |
| Open the billing portal | POST /portal |
The preview endpoint returns the new effective limits before you commit, so you can confirm exactly which caps change.
Bundles are only offered when the operator enables them, and each bundle’s economics are env-tunable:
| Variable | Effect |
|---|---|
BILLING_BUNDLES_ENABLED=true |
Master switch — bundles are hidden unless set |
BILLING_BUNDLE_<ID>_MONTHLY / _ANNUAL |
Override a bundle’s price (cents) |
BILLING_BUNDLE_<ID>_GRANT |
Override the grant amount (single-dimension bundles only) |
BILLING_BUNDLE_<ID>_TIERS |
JSON array of tiers allowed to buy the bundle |
<ID> is the bundle id upper-cased: SEAT_PACK, PIPELINE_PACK, PLUGIN_PACK, API_PACK, AI_PACK, STORAGE_PACK, AUDIT_LOG, SSO.
AWS Marketplace: when the billing provider is
aws-marketplace, self-service bundle purchase is disabled — entitlements flow from Marketplace instead. See Environment Variables for the full billing configuration.