Skip to content

/AWS1/CL_BDK=>CREATECUSTOMMODELDEPLOYMENT()

About CreateCustomModelDeployment

Deploys a custom model for on-demand inference in Amazon Bedrock. After you deploy your custom model, you use the deployment's Amazon Resource Name (ARN) as the modelId parameter when you submit prompts and generate responses with model inference.

For more information about setting up on-demand inference for custom models, see Set up inference for a custom model.

The following actions are related to the CreateCustomModelDeployment operation:

Method Signature

IMPORTING

Required arguments:

iv_modeldeploymentname TYPE /AWS1/BDKMODELDEPLOYMENTNAME /AWS1/BDKMODELDEPLOYMENTNAME

The name for the custom model deployment. The name must be unique within your Amazon Web Services account and Region.

iv_modelarn TYPE /AWS1/BDKCUSTOMMODELARN /AWS1/BDKCUSTOMMODELARN

The Amazon Resource Name (ARN) of the custom model to deploy for on-demand inference. The custom model must be in the Active state.

Optional arguments:

iv_description TYPE /AWS1/BDKCUSTMDELDEPLOYMENTDSC /AWS1/BDKCUSTMDELDEPLOYMENTDSC

A description for the custom model deployment to help you identify its purpose.

it_tags TYPE /AWS1/CL_BDKTAG=>TT_TAGLIST TT_TAGLIST

Tags to assign to the custom model deployment. You can use tags to organize and track your Amazon Web Services resources for cost allocation and management purposes.

iv_clientrequesttoken TYPE /AWS1/BDKIDEMPOTENCYTOKEN /AWS1/BDKIDEMPOTENCYTOKEN

A unique, case-sensitive identifier to ensure that the operation completes no more than one time. If this token matches a previous request, Amazon Bedrock ignores the request, but does not return an error. For more information, see Ensuring idempotency.

RETURNING

oo_output TYPE REF TO /aws1/cl_bdkcrecustmdeldeplo01 /AWS1/CL_BDKCRECUSTMDELDEPLO01

Domain /AWS1/RT_ACCOUNT_ID
Primitive Type NUMC

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->/aws1/if_bdk~createcustommodeldeployment(
  it_tags = VALUE /aws1/cl_bdktag=>tt_taglist(
    (
      new /aws1/cl_bdktag(
        iv_key = |string|
        iv_value = |string|
      )
    )
  )
  iv_clientrequesttoken = |string|
  iv_description = |string|
  iv_modelarn = |string|
  iv_modeldeploymentname = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_custommodeldeploymentar = lo_result->get_custommodeldeploymentarn( ).
ENDIF.