Skip to Content

Amazon Bedrock (Beta) Prompt activity

Introduction

An Amazon Bedrock (Beta) Prompt activity, using its Amazon Bedrock (Beta) connection, sends a prompt to the specified model in Amazon Bedrock and is intended to be used as a target in an operation.

Note

For beta access and to provide feedback, contact the Jitterbit Product Team.

Prerequisites

To successfully use this activity, you must have the following AWS IAM account permissions:

  • bedrock:ListFoundationModels
  • bedrock:GetFoundationModel
  • bedrock:InvokeModel

Create an Amazon Bedrock (Beta) Prompt activity

An instance of an Amazon Bedrock (Beta) Prompt activity is created from an Amazon Bedrock (Beta) connection using its Prompt activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing Amazon Bedrock (Beta) Prompt activity can be edited from these locations:

Configure an Amazon Bedrock (Beta) Prompt activity

Follow these steps to configure an Amazon Bedrock (Beta) Prompt activity:

Step 1: Enter a name and specify settings

In this step, provide a name for the activity, select a model, and specify a prompt and optional settings. Each user interface element of this step is described below.

Amazon Bedrock Prompt activity configuration step 1

  • Name: Enter a name to identify the activity. The name must be unique for each Amazon Bedrock (Beta) Prompt activity and must not contain forward slashes / or colons :.

  • List all models: Select this option to choose from a list of models retrieved from Amazon Bedrock:

    • Select a model: This section displays models available in the Amazon Bedrock (Beta) endpoint.

      • Selected model: After a model is selected, it is listed here.

      • Search: Enter any column's value into the search box to filter the list of models. The search is not case-sensitive. If models are already displayed within the table, the table results are filtered in real time with each keystroke. To reload models from the endpoint when searching, enter search criteria and then refresh, as described below.

      • Refresh: Click the refresh icon or the word Refresh to reload models from the Amazon Bedrock (Beta) endpoint. This may be useful if models have been added to Amazon Bedrock. This action refreshes all metadata used to build the table of models displayed in the configuration.

      • Selecting a model: Within the table, click anywhere on a row to select a model. Only one model can be selected. The information available for each model is fetched from the Amazon Bedrock (Beta) endpoint:

        • Model Identifier: The model ID.

        • Model Provider: The provider of the model.

        • Model Name: The name of the model.

      Tip

      If the table does not populate with available models, the Amazon Bedrock (Beta) connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

  • Enter model identifier: Select this option to manually enter the name of a model in Amazon Bedrock:

    Amazon Bedrock activity model ID

    • Model identifier: Enter the model ID.

  • Prompt: Enter the text to prompt the model with.

  • Optional Settings: Click to expand additional optional settings:

    Amazon Bedrock Prompt activity configuration step 1 optional

    • Randomness and Diversity:

    • Length:

    • Continue on Error: Select to continue the activity execution if an error is encountered for a dataset in a batch request. If any errors are encountered, they are written to the operation log.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

Amazon Bedrock Prompt activity configuration step 2

  • Data schema: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    The Amazon Bedrock (Beta) connector uses the Amazon Bedrock API. Refer to the API documentation for information on the schema nodes and fields.

  • Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Amazon Bedrock (Beta) endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring an Amazon Bedrock (Beta) Prompt activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

Amazon Bedrock (Beta) Prompt activities can be used as a target with these operation patterns:

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.