From 94b40b763cd6daa6507b55928a3032d5c1c270ae Mon Sep 17 00:00:00 2001 From: Gustavo Azevedo Date: Fri, 7 Nov 2025 12:13:53 -0300 Subject: [PATCH] Change Bedrock region from us-east-1 to us-west-2 To keep consistency with the rest of the course, this advises using the us-west-2 region as the Bedrock execution region. --- terraform/8_enterprise/terraform.tfvars.example | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/terraform/8_enterprise/terraform.tfvars.example b/terraform/8_enterprise/terraform.tfvars.example index 35d96a10..82788769 100644 --- a/terraform/8_enterprise/terraform.tfvars.example +++ b/terraform/8_enterprise/terraform.tfvars.example @@ -8,7 +8,7 @@ aws_region = "us-east-1" # Bedrock region where your models are deployed # IMPORTANT: This must match the BEDROCK_REGION in your Lambda functions # Check with: aws lambda get-function-configuration --function-name alex-planner --query "Environment.Variables.BEDROCK_REGION" -bedrock_region = "us-east-1" +bedrock_region = "us-west-2" # Bedrock model ID to monitor in dashboards # Common values: @@ -16,4 +16,4 @@ bedrock_region = "us-east-1" # - us.amazon.nova-pro-v1:0 (Cross-region Nova Pro) # - anthropic.claude-3-5-sonnet-20241022-v2:0 (Claude 3.5 Sonnet) # Check your CloudWatch metrics for the exact ModelId being used -bedrock_model_id = "amazon.nova-pro-v1:0" \ No newline at end of file +bedrock_model_id = "amazon.nova-pro-v1:0"