Add additional Bedrock Knowedlge Base supported regions

[sleepwithcoffee]

Issue #, if available:

#652

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[maryamkhidir]

can you add a screenshot of this change in the cli?

[sleepwithcoffee]

[sleepwithcoffee]

added support for the following regions:

export enum SupportedBedrockKnowledgeBaseRegion {
  AP_NORTHEAST_1 = "ap-northeast-1",
  AP_NORTHEAST_2 = "ap-northeast-2",
  AP_SOUTH_1 = "ap-south-1",
  AP_SOUTHEAST_1 = "ap-southeast-1",
  AP_SOUTHEAST_2 = "ap-southeast-2",
  CA_CENTRAL_1 = "ca-central-1",
  EU_CENTRAL_1 = "eu-central-1",
  EU_CENTRAL_2 = "eu-central-2",
  EU_NORTH_1 = "eu-north-1",
  EU_WEST_1 = "eu-west-1",
  EU_WEST_2 = "eu-west-2",
  EU_WEST_3 = "eu-west-3",
  US_EAST_1 = "us-east-1",
  US_EAST_2 = "us-east-2",
  US_WEST_2 = "us-west-2",
  SA_EAST_1 = "sa-east-1",
}

[Rob-Powell]

The problem with just adding more bedrock regions is that not all functions are currently supported in all regions for example instance types used by batch not available consistently in all regions. #488
We should check that if we are enabling more regions the solution actually works in those regions

[sleepwithcoffee]

hi @Rob-Powell this is Bedrock Knowledge Base region, isn't it different and should not impact in any way?

[Rob-Powell]

hi @Rob-Powell this is Bedrock Knowledge Base region, isn't it different and should not impact in any way?

no, as batch is how the documents get into the knowledge base via the solution. I don't think it makes sense to enable more knowledge base bedrock regions, if we know they wont work for core use cases of the solution.

[sleepwithcoffee]

thanks, that makes sense. Let me cross check and align with the list of existing regions for Bedrock