---
schema_version: "1"
id: 7eb66d98c166ab1f49ca8512147e58018eab3f0698574f23937b7a91e1ccbaa9
title: Using Anypoint Studio to Configure Amazon Bedrock Connector 1.1
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/amazon-bedrock-connector/latest/amazon-bedrock-connector-studio.md
canonical_url: https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-studio
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 969a5e31ddac5dc7eec837eb298d6e2a62776fd9a82e2454ac141df8f99441df
description: MuleSoft Documentation Site
release: "1.1"
latest: true
---
---
product: Amazon Bedrock Connector
version: 1.1
is-latest-version: true
---

# Using Anypoint Studio to Configure Amazon Bedrock Connector 1.1

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).

2.  [Add the connector to your Mule project](#add-connector-to-project).

3.  [Configure a source for the connector’s flow](#configure-source).

4.  [Add a connector operation to the flow](#add-connector-operation).

5.  [Configure a global element for the connector](#configure-global-element).

6.  [Configure the other connector fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems in real time, as
described in [View the App Log](#view-app-log).

If you are new to configuring connectors in Studio, see
[Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio).
If, after reading this topic, you need additional information about the connector fields, see the
[Amazon Bedrock Connector Reference](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure Anypoint Connector for Amazon
Bedrock (Amazon Bedrock Connector):

1.  In Studio, select **File > New > Mule Project**.

2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add Amazon Bedrock Connector to your Mule project to automatically populate the XML code with the
connector’s namespace and schema location and add the required dependencies to the project’s
`pom.xml` file:

1.  In **Mule Palette**, click **(X) Search in Exchange**.

2.  In **Add Dependencies to Project**, type `amazon bedrock` in the search field.

3.  Click **Amazon Bedrock Connector** in **Available modules**.

4.  Click **Add**.

5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources
to use with Amazon Bedrock Connector:

- **HTTP > Listener**

  Initiates a flow each time it receives a request on the configured host and port

- **Scheduler**

  Initiates a flow when a time-based condition is met

For example, to configure an **HTTP > Listener** source, follow these steps:

1.  In **Mule Palette**, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  On the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.

4.  Specify a value for the **Path** field.

5.  Click the plus sign (**+**) next to the **Connector configuration** field to configure a global
    element that can be used by all instances of the **HTTP > Listener** source in the app.

6.  On the **General** tab, specify the connection information for the connector.

7.  On the **TLS** tab, optionally specify the TLS information for the connector.

8.  On the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

9.  Click **Test Connection** to confirm that Mule can connect with the specified server.

10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to
perform.

To add an operation for Amazon Bedrock Connector, follow these steps:

1.  In **Mule Palette**, select **Amazon Bedrock Connector** and then select the operation to add.

2.  Drag the operation onto the Studio canvas, next to the source.

## Configure a Global Element for the Connector

When you configure a connector, configure a global element that all instances of that connector in
the app can use. In addition to the required access key and secret key fields, you can enable the
default AWS credentials provider chain to obtain credentials from the AWS environment.

To configure the global element for Amazon Bedrock Connector, follow these steps:

1.  Select the operation in the Studio canvas.

2.  In the **General** configuration screen for the operation, click the **Add** icon to access the
    global element configuration fields.

3.  In the **General** tab, in **Connection**, select the authentication method to configure:

    - [Basic](#basic)

    - [Role](#role)

    You can reference a configuration file that contains ANT-style property placeholders
    (recommended) or enter your authorization credentials in the global configuration properties.
    You can also enable **Try Default AWSCredentials Provider Chain** to obtain credentials from the
    AWS environment. For information about the benefits of using property placeholders and how to
    configure them, refer to
    [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

4.  In the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

### Basic

Enter the following information in the **General** tab of the **Global Element Properties** screen
to configure Basic Authentication:

<table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>User Action</th></tr></thead><tbody><tr><td><p><strong>Name</strong></p></td><td><div><div><p>Enter the configuration name.</p></div></div></td></tr><tr><td><p><strong>Connection</strong></p></td><td><div><div><p>Select <strong>Basic</strong>.</p></div></div></td></tr><tr><td><p><strong>Access Key</strong></p></td><td><div><div><p>Enter the access key provided by Amazon.</p></div></div></td></tr><tr><td><p><strong>Secret Key</strong></p></td><td><div><div><p>Enter the secret key provided by Amazon.</p></div></div></td></tr><tr><td><p><strong>Session Token</strong></p></td><td><div><div><p>Optionally enter the session token provided by Amazon Security Token Service (AWS STS).</p></div></div></td></tr><tr><td><p><strong>Try Default AWSCredentials Provider Chain</strong></p></td><td><div><div><p>Enable this field to obtain credentials from the AWS environment. The default is <code>false</code>.</p></div></div></td></tr><tr><td><p><strong>Region Endpoint</strong></p></td><td><div><div><p>Enter the AWS region endpoint. The default is <code>us-east-1</code>.</p></div></div></td></tr></tbody></table>

### Role

Enter the following information in the **General** tab of the **Global Element Properties** screen
to configure Role Authentication:

<table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>User Action</th></tr></thead><tbody><tr><td><p><strong>Name</strong></p></td><td><div><div><p>Enter the configuration name.</p></div></div></td></tr><tr><td><p><strong>Connection</strong></p></td><td><div><div><p>Select <strong>Role</strong>.</p></div></div></td></tr><tr><td><p><strong>Role ARN</strong></p></td><td><div><div><p>Enter the role to assume to gain cross-account access.</p></div></div></td></tr><tr><td><p><strong>Access Key</strong></p></td><td><div><div><p>Enter the access key provided by Amazon.</p></div></div></td></tr><tr><td><p><strong>Secret Key</strong></p></td><td><div><div><p>Enter the secret key provided by Amazon.</p></div></div></td></tr><tr><td><p><strong>Try Default AWSCredentials Provider Chain</strong></p></td><td><div><div><p>Enable this field to obtain credentials from the AWS environment. The default is <code>false</code>.</p></div></div></td></tr><tr><td><p><strong>Region Endpoint</strong></p></td><td><div><div><p>Enter the AWS region endpoint. The default is <code>us-east-1</code>.</p></div></div></td></tr></tbody></table>

## Configure Additional Connector Fields

After you configure a global element for the connector, configure the other required fields. The
required fields vary depending on which connector operation you use.

For detailed configuration information for each operation type, see
[Amazon Bedrock Connector - Additional Configuration Information](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-additional-config).

## View the App Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the app log output is visible on the Anypoint
  Studio console window.

- If you’re running the app using Mule from the command line, the app log output is visible in your
  operating system console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`. You can configure the location of
the log path in the app log file `log4j2.xml`.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Using Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio)

- [Amazon Bedrock Connector Reference](https://docs.mulesoft.com/amazon-bedrock-connector/latest/amazon-bedrock-connector-reference)

- [Salesforce Help](https://help.salesforce.com)