Creating a Commitment

Create a continuous consumption discount (CCD) commitment from an eligible pricing offer using the Console, CLI, or API. Before creating the commitment, review the offer's terms, confirm the configuration and start time, and obtain any required financial approval.

  • Sign in as an authorized tenancy administrator or delegated commitment manager in the parent tenancy associated with the subscription, or in the standalone tenancy. For permissions, see Required IAM Policy to View and Accept Offers.

    An eligible, valid offer must be associated with the intended subscription. Review existing commitments for the same subscription and products, expected demand, all billable components, and capacity arrangements. Obtain your organization's required financial approval before accepting an obligation.

    For contract-defined commitments, review the record created from the signed contract rather than creating another commitment. See CCD Commitment Offer Sources.

    1. On the Continuous Consumption Discounts page, select Create commitment.

      For help finding the page, see Listing Commitments.

    2. On the Create commitment page, enter a commitment name.
      Avoid entering confidential information.
    3. In the Tags section, optionally add one or more tags to the commitment.
      If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.
    4. Select an eligible offer and review its details.

      Confirm the intended subscription. Review the offer's products, region, price, term, usage basis, quantity limits, validity, and capacity arrangements. Select only permitted values.

    5. Select Next to review the commitment configuration.

      The selected offer determines which values you can configure:

      • For a configurable contract offer or OCI-generated offer, enter the permitted primary SKU quantity. Review every bundled component. Change a component quantity only when allowed; fixed-ratio quantities are derived from the primary quantity.
      • For a fixed offer, including Flex and fixed OCI-generated offers, review the predefined configuration without changing its commercial terms.

      For information about sources and bundles, see CCD Commitment Offer Sources and Understanding What a CCD Offer Covers.

    6. Review the default start time and, if the offer allows it, select a supported future whole-hour start.
    7. Select Next to review the offer and commitment values.

      Check the subscription, selected offer, all component quantities and units, prices, currency, total obligation, billing basis, eligibility scope, effective start, duration or minimum period, end conditions, and capacity terms.

      Read How CCD Usage and Pricing Determine Charges and When a Commitment Ends if you need help interpreting the obligation. A minimum-period boundary isn't necessarily the actual end.

    8. Select Create commitment.
    The commitment appears on the Continuous Consumption Discounts page.
    Note

    After a CCD has been accepted, you can't cancel the commitment. If you need to cancel the commitment, contact Oracle Support as soon as possible.

    After commitment creation, you can review its details. Verify the subscription, products, component quantities, price, effective start, and end condition against the accepted terms.

    Successful commitment creation doesn't necessarily mean pricing or billing is already active. For delivery-dependent terms, verify the qualifying handover event and effective timestamp. See When a Commitment Begins.

    Once billing starts, use Reviewing and Reconciling CCD Charges to check that CCD charges match the terms you accepted.

    You can also manage tags. Tags don't change quantity, price, duration, or the financial obligation. See Listing Commitments.

  • Use the oci ccd-offers ccd-commitments ccd-commitment create command and required parameters to create a CCD commitment:

    oci ccd-offers ccd-commitments ccd-commitment create --ccd-offer-id --compartment-id, -c --display-name --quantity --subscription-id --time-ccd-commitment-starts [OPTIONS]

    For a complete list of parameters and variable options for CLI commands, see the Command Line Reference.

  • API acceptance creates the same financial obligation as Console acceptance.

    Use an authenticated caller with offer-read and commitment-management authority. See Required IAM Policy to View and Accept Offers.

    Run the CreateCcdCommitment operation to create a commitment.

    For fixed offers, accept the offered terms. For configurable offers, submit only permitted selections.

    1. Use ListCcdOffers and GetCcdOffer to find and review an eligible offer.

      Check the offer identifier, subscription, scope, products, quantities, prices, usage basis, start policy, term, and end condition. Review existing commitments before creating an additional obligation.

    2. Use the offered fixed quantity or an allowed configurable value. For bundles, follow the component quantity rules.
    3. Set the start from the offer's rule.

      Contract offers default to the rounded-up hour or a permitted future hour. Flex offers use the rounded-up hour plus one. Recheck the time before sending. See When a Commitment Begins.

    4. Call CreateCcdCommitment with the offer identifier and required fields.

      Sign the HTTPS request using OCI request signing or a supported signing client. Include a retry token.

    5. Retain the returned commitment and request identifiers, then use GetCcdCommitment to verify the accepted terms and effective timestamps.

    The API returns the commitment record. Verify the returned term-based end rather than calculating it from the request alone.

    For example, assume the offer permits 100 units and a fixed-time start. Acceptance on 1 November 2026 at 10:40 UTC defaults to 11:00 UTC.

    • Replace the OCID placeholders and use the published CCD endpoint for your location. This is a request-body and route example, not a complete signed HTTP request.
    • For an otherwise equivalent fixed-time Flex acceptance at 10:40 UTC, the start would be 12:00 UTC and the quantity must equal the fixed offered quantity.
    • For OCI-generated offers, use the offer's specified start rule.
    POST /20240601/ccdCommitments?ccdOfferId=<offer_ocid> 
     Content-Type: application/json
     opc-retry-token: <unique_retry_token> 
    
    { 
       "quantity": 100, 
       "subscriptionId": "<subscription_ocid>", 
       "displayName": "compute-baseline", 
       "compartmentId": "<parent_or_standalone_tenancy_ocid>", 
       "timeCcdCommitmentStarts": "2026-11-01T11:00:00Z" 
    }

    The API requires quantity, subscription, display name, root compartment, and start timestamp. The offer ID is a query parameter. Verify the returned term-based end rather than assuming it from the request.

    In case of a timeout, retry the identical request with the same retry token and check for the existing commitment. Resolve invalid starts, expired offers, insufficient authority, or quantities outside bounds. Don't create a second obligation to work around an uncertain response.

    Additional notes:

    • Tags don't change quantity, price, or duration.
    • Commercial changes and termination depend on governing terms and supported rules.
    • Stopping a workload doesn't release the obligation.
    • After a CCD has been accepted, you can't cancel the commitment. If you need to cancel the commitment, contact Oracle Support as soon as possible.