Feature/Parameterize Bedrock model ID in CloudFormation templates

[oussamahansal]

Description of changes:

• Replace hardcoded anthropic.claude-sonnet-4-6 model references with a configurable BedrockModelId parameter across CloudFormation templates.
• Users can now specify which Bedrock model to use without editing template source files.

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

[iansrobinson]

This doesn't work for the workshop, because the workshop ModelId parameter can also accept a profile, which already includes the prefix. We need this profile to carry all the way through, because a) Many models will now only work when invoked with a profile - sonnet-4-6, for example, b) the workshop's cached responses are keyed for the specific modelId/profile that is suplpied.

[acarbonetto]

I believe removing the *. would work, right?

[iansrobinson]

My preference would be for ModelId to accept a model ID or profile. Many models, sonnet-4-6 for example, have to be invoked via a profile. Therefore, I suspect the configuration of environment variables will fail unless supplied with a profile.

In the end, I liked the use of *.anthropic.* in the IAM profiles. It's not as locked to specific models as we'd like, but it works in the face of the inconsistencies in Bedrock.

[acarbonetto]

Suggested change

	"Description": "Bedrock model ID used for extraction, response, and evaluation LLMs",
	"Description": "Bedrock model ID or inference profile used for extraction, response, and evaluation LLMs",

[acarbonetto]

Suggested change

	"Description": "Bedrock model ID used for extraction, response, and evaluation LLMs",
	"Description": "Bedrock model ID or inference profile used for extraction, response, and evaluation LLMs",

[acarbonetto]

Suggested change

	"Description": "Bedrock model ID used for extraction, response, and evaluation LLMs",
	"Description": "Bedrock model ID or inference profile used for extraction, response, and evaluation LLMs",

[acarbonetto]

Suggested change

	"Description": "Bedrock model ID used for extraction, response, and evaluation LLMs",
	"Description": "Bedrock model ID or inference profile used for extraction, response, and evaluation LLMs",

[acarbonetto]

Suggested change

	"Description": "Bedrock model ID used for extraction, response, and evaluation LLMs",
	"Description": "Bedrock model ID or inference profile used for extraction, response, and evaluation LLMs",

[acarbonetto]

Suggested change

	"Description": "Bedrock model ID used for extraction, response, and evaluation LLMs",
	"Description": "Bedrock model ID or inference profile used for extraction, response, and evaluation LLMs",

[acarbonetto]

Suggested change

	"Fn::Sub": "arn:${AWS::Partition}:bedrock:*:${AWS::AccountId}:inference-profile/*.${BedrockModelId}"
	"Fn::Sub": "arn:${AWS::Partition}:bedrock:*:${AWS::AccountId}:inference-profile/*${BedrockModelId}"

[acarbonetto]

Suggested change

	"Fn::Sub": "arn:${AWS::Partition}:bedrock:*:${AWS::AccountId}:inference-profile/*.${BedrockModelId}"
	"Fn::Sub": "arn:${AWS::Partition}:bedrock:*:${AWS::AccountId}:inference-profile/*${BedrockModelId}"

[acarbonetto]

I believe removing the *. would work, right?

[acarbonetto]

Suggested change

	"Fn::Sub": "arn:${AWS::Partition}:bedrock:*:${AWS::AccountId}:inference-profile/*.${BedrockModelId}"
	"Fn::Sub": "arn:${AWS::Partition}:bedrock:*:${AWS::AccountId}:inference-profile/${BedrockModelId}"

[acarbonetto]

I don't think we need the wildcard for profiles, since the profile passed in would contain the prefix.

[acarbonetto]

We might need to go with something like *${BedrockModelId}*?