Amazon Bedrock: Pioneering AI with Foundational Models

Introduction

Creating an AWS Cloud9 Environment

• Click the Create environment button located in one of the following places:
  • If you do not have any AWS Cloud9 environments yet, this button is displayed on the welcome page.
  • If you already have AWS Cloud9 environments, the button appears as follows.

• On the Create environment page, fill in:
  • Name: The name for your environment.
  • Description: A description of the environment. Example: “This environment is for AWS Cloud9 tutorials.”

• Choose Environment type:
  • New EC2 instance: Create a new EC2 instance that AWS Cloud9 can directly connect to via SSH.
  • Existing compute: Use an existing EC2 instance, requiring SSH login information.

Note: Auto-off is not available for AWS Cloud9 environments created from existing EC2 instances.

Warning: Creating an EC2 instance may incur charges on your AWS account.* In the New EC2 instance section, keep the default settings for Instance type.

Warning: Choosing an instance type with more RAM and CPU can lead to additional costs.* Select Platform: Amazon Linux 2 or Ubuntu 22.04 LTS. AWS Cloud9 will create the instance and connect the environment to it.

Important: We recommend selecting Amazon Linux 2. Choose a duration for Timeout.

Warning: Selecting a longer duration may lead to additional costs.

• In the Network settings section, choose how to access the environment: through AWS System Manager (SSM) or Secure Shell (SSH).
• Select VPC Settings to display Amazon Virtual Private Cloud and Subnet for your environment.
• Add up to 50 tags by providing Key and Value for each tag.

Warning: Updating tags after creation will not be reflected on the underlying resources.* Click Create to make the environment.* If the account is successfully created, a green notification bar will appear at the top of the AWS Cloud9 console.* If the account creation fails, a red notification bar will appear.

• After about 3 minutes of creation, click Open

• In the AWS Cloud9 interface:
• Select Preferences
• Select AWS Settings
• In the Credentials section, toggle off AWS managed temporary credentials

Creating an IAM Policy for Amazon Bedrock

• Log in to AWS Management Console
  • Access the AWS Management Console and log in with your account.
• Open the IAM Dashboard
  • On the AWS toolbar, select “Services” and search for IAM to open the IAM Dashboard.
• Create a New IAM Policy
  • In the IAM Dashboard, select the Policies tab.
  • Click on Create policy.

• Enter Policy Details
  • Switch to the JSON tab.
  • Copy and paste the following JSON snippet into the input field:
• {
  "Version": "2012-10-17",
  "Statement": [
  {
  "Sid": "Statement1",
  "Effect": "Allow",
  "Action": "bedrock:*",
  "Resource": "*"
  }
  ]
  }

• Confirm and Create the Policy
  • Double-check the information entered.
  • Click on Review policy, name the policy, and click Create policy to complete.

• With the above steps, you should be able to successfully create an IAM Policy for managing access to Amazon Bedrock’s APIs.

Creating an IAM Role for Amazon Bedrock

• Log in to the AWS Management Console
  • Navigate to AWS Management Console and log in with your account.
• Open the IAM Dashboard
  • On the AWS toolbar, select “Services” and search for IAM to open the IAM Dashboard.
• Create a New IAM Role
  • In the IAM Dashboard, select the Roles tab.
  • Click the Create role button.

• 

• Choose Entity Type and Use Case
  • Select AWS service in the entity type section.
  • Choose the appropriate use case for the role (e.g., EC2 if you want this role for EC2 instances).
  • Click Next: Permissions.

• 

  • 

• Attach Policy to Role
  • In the Attach permissions policies section, find and select the policy you created for Bedrock (BedrockAccessPolicy if you named it so).
  • Find and select AdministratorAccess to provide administrator privileges.
  • Click Next: Tags (you can add tags if needed).
  • Click Next: Review.

• 

  • 

• Name and Create the Role
  • Name the role (e.g., BedrockAdminRole).
  • Review the configuration and click Create role to complete.
    

    

Attaching IAM Role to AWS Cloud9

• Log in to the AWS Management Console
  • Access the AWS Management Console and log in with your account.
• Open the EC2 Dashboard
  • On the AWS toolbar, select “Services” and search for EC2 to open the EC2 Dashboard.
• Select Instances
  • In the EC2 Dashboard, select Instances from the left menu.
• Choose the Instance to Attach the Role
  • Find the EC2 instance you wish to attach the IAM Role to (this instance should be used in AWS Cloud9).
  • Click on that instance to select it.
    

    

• Attach IAM Role
  • With the selected instance, press the Actions button.
  • In the dropdown menu, choose Security and then Modify IAM role.
  • In the Modify IAM role window, select the IAM Role you created earlier from the dropdown list (e.g., BedrockAdminRole).
  • Click Save to apply the changes.
    

    

• Confirm and Use the Role
  • Double-check to ensure that the IAM Role has been correctly attached.
  • Now, your EC2 instance in Cloud9 has access rights according to the selected IAM Role.

Updating Security Group for EC2 in AWS Cloud9

• Log in to the AWS Management Console
  • Access AWS Management Console and log in with your account.
• Open EC2 Dashboard
  • On the AWS toolbar, select “Services” and search for EC2 to open the EC2 Dashboard.
• Select Security Groups
  • In the EC2 Dashboard, select Security Groups from the left-side menu.
• Choose the Security Group to Update
  • Locate the Security Group linked with the EC2 instance you are using in Cloud9.
  • Click on that Security Group to select it.
• Edit Inbound Rules
  • With the selected Security Group, click the Actions button.
  • Choose Edit inbound rules.
    

    

• Add Rules for the Necessary Ports
  • Click Add rule to add a new rule.
  • For each port (8080, 80, and 22), add a rule:
    • Type: Select Custom TCP for ports 8080 and 80, SSH for port 22.
    • Port Range: Enter the corresponding port number (8080, 80, or 22).
    • Source: Choose Anywhere or restrict to specific IP addresses if necessary.
  • Repeat for each required port.
    

    

• Save the Changes
  • After adding the rules, click Save rules to apply the changes.

Clone Repository from GitHub

• Install Git First, you need to make sure that Git is installed on your computer. If not, you can download and install it from Git’s homepage.
• Open Terminal or Command Prompt
  • On Windows, you can use Command Prompt or PowerShell.
  • On macOS or Linux, you can use Terminal.
  • On Cloud9, you can run directly.
• Navigate to Desired Folder Use the cd command to navigate to the directory where you want to save the repository. For example:

• Clone Repository Once in the desired directory, use the following command to clone the repository:

• Check Results After the cloning process is completed, use the ls or dir command to check if the repository has been cloned to your computer.
• Install the necessary libraries for the application

• Clone and Go to Project Folder

• Install Necessary Libraries
• Use pip3 to install necessary libraries from requirements.txt file:

Creating an Access Key

• Log into the AWS Management Console.
  • Use your AWS account to log in.
• Access IAM (Identity and Access Management).
  • In the AWS Management Console, find and select “IAM” to access Identity and Access Management.
• Create a new user or use an existing user.
  • If you don’t have a user, you need to create a new one.
  • If you already have one, you can use the existing user.
• Create an Access Key for the user.
  • In the user’s ‘Security credentials’ tab, find and select ‘Create access key’.
  • Save the ‘Access Key ID’ and ‘Secret Access Key’ when displayed.

Configuring Credentials for Cloud9

• Open AWS Cloud9 Environment.
  • In the AWS Management Console, find and select “Cloud9”.
  • Open your Cloud9 environment.
• Open a terminal in Cloud9.
  • In the Cloud9 environment, open a terminal or command window.
• Run the AWS Configure command.
  • In the terminal, enter the following command:aws configure
  • Enter the ‘Access Key ID’ and ‘Secret Access Key’ you saved in step 1.
  • Enter the region information and output format if needed.

Setting Up Amazon Bedrock

• In the AWS console interface, select the region where you wish to access Amazon Bedrock.At the time of writing this guide, the workshop will work best in the us-west-2 (Oregon) or us-east-1 (N. Virginia) regions.
  

  

• Find Amazon Bedrock by searching within the AWS console.
  

  

• Expand the side menu.
  

  

• From the side menu, select Model access.
  

  

• Click the Edit button.
  

  

• Use the checkboxes to select the models you want to activate. Most of the model providers listed will be used in the workshop. There is no cost to activate models - you only pay for what you use in the labs. Review applicable EULAs as needed. Click Save changes to activate the models in your account.
  

  

• Review the model access status.

 To run the application, use the following command on AWS Cloud9:

Application Experience

• Application 1: RAG with Document (Architecture - RAG with document)

• Application 2: Converting Text to SQL Query (Architecture - Text To SQL Query)

• Applications 3 and 4: ReAct and Agents (Architecture - ReAct and Agents)

Resource Cleanup

• In the Cloud9 admin interface.
  • Select the Cloud9 instance you created.
  • Click Delete.
• Type Delete to confirm.
  • Click Delete to remove the created Cloud9 instance.

Reference Materials

• Amazon Bedrock
• AI21
• Anthropic Claude

Installation References

• Install Python
• Set up Python Environment
• Install AWS CLI