Integrating with AWS Bedrock Cohere in Orkes Conductor

To effectively utilize AI and LLM tasks in Orkes Conductor, it's essential to integrate your Orkes Conductor cluster with the necessary AI and LLM models.

AWS Bedrock Cohere offers a range of models that can be incorporated into the Orkes Conductor cluster. The choice of model depends on your unique use case, the functionalities you require, and the specific natural language processing tasks you intend to tackle.

This guide will provide the steps for integrating the AWS Bedrock Cohere provider with Orkes Conductor.

Steps to integrate with AWS Bedrock Cohere

Before beginning the integration process in Orkes Conductor, you must get specific configuration credentials from your AWS account.

• AWS account ID & region where the resource is located.
• Amazon Resource Name (ARN) to set up the connection.
• External ID - When you assume a role belonging to another account in AWS, you need to provide the external ID, which can be used in an IAM role trust policy to designate the person to assume the role. Learn more.
• Access key and secret from AWS account.

Integrating with AWS Bedrock Cohere as a model provider

Let’s integrate AWS Bedrock Cohere with Orkes Conductor.

1. Navigate to Integrations from the left menu on your Orkes Conductor cluster.
2. Click +New integration button from the top-right corner.
3. Under the AI/LLM section, choose AWS Bedrock Cohere.
4. Click +Add and provide the following parameters:

Parameters	Description
Integration name	A name for the integration.
Connection type	Select the required connection type. Depending upon how the connection is to be established, it can take the following values: Current Conductor Role - Choose this if you are using the current Conductor role to establish the connection. Assume External Role - Choose this if you are assuming a role belonging to another AWS account. Learn more. Access Key/Secret - Choose this if you are establishing the connection using the access key and secret.
Region	The valid AWS region where the resource is located.
Account ID	Your AWS account ID. This field is optional.
Role ARN	The Amazon Resource Name (ARN) required to set up the connection. Note: This field is applicable only if the Connection Type is chosen as Assume External Role.
External ID	If applicable, provide the external ID to assume the role. Note: This field is applicable only if the Connection Type is chosen as Assume External Role.
Access key	The AWS access key. Note: This field is applicable only if the Connection Type is chosen as Access Key/Secret.
Access secret	The AWS access secret. Note: This field is applicable only if the Connection Type is chosen as Access Key/Secret.
Description	A description of your integration.

5. You can toggle-on the Active button to activate the integration instantly.
6. Click Save.

Adding AWS Bedrock Cohere models to integration

You have now integrated your Orkes Conductor cluster with the AWS Bedrock Cohere provider. The next step is to integrate with the specific models. AWS Bedrock Cohere has different models: Command, Command Light, Command R, Embed English and more. Each model is intended for different use cases, such as text completion and generating embeddings.

Depending on your use case, you must configure the required model within your AWS Bedrock Cohere configuration.

To add a new model to the AWS Bedrock Cohere integration:

1. Navigate to the integrations page and click the '+' button next to the integration created.

2. Click +New model.
3. Provide the model name and an optional description. The complete list of models in AWS Bedrock Cohere is available here.

4. Toggle-on the Active button to enable the model immediately.
5. Click Save.

This ensures the integration model is saved for future use in LLM tasks within Orkes Conductor.

RBAC - Governance on who can use Integrations

The integration with the required models is now ready. Next, we should determine the access control to these models.

The permission can be granted to applications/groups within the Orkes Conductor cluster.

To provide explicit permission to Groups:

1. Navigate to Access Control > Groups from the left menu on your Orkes Conductor cluster.
2. Create a new group or choose an existing group.
3. Under the Permissions section, click +Add Permission.
4. Under the Integrations tab, select the required integrations with the required permissions.

5. Click Add Permissions. This ensures that all the group members can access these integration models in their workflows.

Similarly, you can also provide permissions to applications.

note

Once the integration is ready, start creating workflows with LLM tasks.