You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -30,12 +31,10 @@ export function getStaticProps(context) {
30
31
31
32
A foundation model is a large, general-purpose machine learning model that has been pre-trained on a vast amount of data. These models are trained in an unsupervised or self-supervised manner, meaning they learn patterns and representations from the unlabeled training data without being given specific instructions or labels.
32
33
33
-
Foundation models are useful because they are general-purpose and you don't need to train the models yourself, but are powerful enough to take on a range of applications.
34
+
Foundation models are useful because they are general-purpose and you don't need to train the models yourself, but are powerful enough to take on a range of applications.
34
35
35
36
Foundation Models, which Large Language Models are a part of, are inherently stateless. They take input in the form of text or images and generate text or images. They are also inherently non-deterministic. Providing the same input can generate different output.
36
37
37
-
38
-
39
38
## Getting model access
40
39
41
40
Before you can invoke a foundation model on Bedrock you will need to [request access to the models in the AWS console](https://console.aws.amazon.com/bedrock/home#/modelaccess).
@@ -44,51 +43,135 @@ Be sure to check the region you are building your Amplify app in!
44
43
45
44
## Pricing and Limits
46
45
47
-
Each foundation model in Amazon Bedrock has its own pricing and throughput limits for on-demand use. On-demand use is serverless, you don't need to provision any AWS resources to use and you only pay for what you use. The Amplify AI kit uses on-demand use for Bedrock.
46
+
Each foundation model in Amazon Bedrock has its own pricing and throughput limits for on-demand use. On-demand use is serverless, you don't need to provision any AWS resources to use and you only pay for what you use. The Amplify AI kit uses on-demand use for Bedrock.
48
47
49
-
The cost for using foundation models is calculated by token usage. A token in generative AI refers to chunks of data that were sent as input and how much data was generated. A token is roughly equal to a word, but depends on the model being used. Each foundation model in Bedrock has its own pricing based on input and output tokens used.
48
+
The cost for using foundation models is calculated by token usage. A token in generative AI refers to chunks of data that were sent as input and how much data was generated. A token is roughly equal to a word, but depends on the model being used. Each foundation model in Bedrock has its own pricing based on input and output tokens used.
50
49
51
50
When you use the Amplify AI Kit, inference requests are charged to your AWS account based on Bedrock pricing. There is no Amplify markup, you are just using AWS resources in your own account.
52
51
53
52
Always refer to [Bedrock pricing](https://aws.amazon.com/bedrock/pricing/) for the most up-to-date information on running generative AI with Amplify AI Kit.
54
53
54
+
Your Amplify project must be deployed to a region where the foundation model you specify is available. See [Bedrock model support](https://docs.aws.amazon.com/bedrock/latest/userguide/models-supported.html) for the supported regions per model.
55
55
56
56
## Supported Providers and Models
57
57
58
-
The Amplify AI Kit uses Bedrock's [Converse API](https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference.html) to leverage a unified API across models. Most models have different structures to how they best work with input and how they format their output. For example, ...
59
-
60
-
### AI21 Labs
61
-
* Jamba 1.5 Large
62
-
* Jamba 1.5 Mini
63
-
[Bedrock documentation about AI21 models](https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-ai21.html)
64
-
65
-
### Anthropic
66
-
* Claude 3 Haiku
67
-
* Claude 3.5 Haiku
68
-
* Claude 3 Sonnet
69
-
* Claude 3 Opus
70
-
* Claude 3.5 Sonnet
71
-
* Claude 3.5 Sonnet v2
72
-
[Bedrock documentation about Anthropic models](https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-claude.html)
73
-
74
-
### Cohere
75
-
* Command R
76
-
* Command R+
77
-
[Bedrock documentation about Cohere models](https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-cohere.html)
78
-
79
-
### Meta Llama
80
-
* Llama 3.1
81
-
[Bedrock documentation about Meta Llama models](https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-meta.html)
82
-
83
-
### Mistral AI
84
-
* Large
85
-
* Large 2
86
-
[Bedrock documentation about Mistral AI models](https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-mistral.html)
87
-
88
-
89
-
The Amplify AI Kit makes use of ["tools"](/[platform]/ai/concepts/tools) for both generation and conversation routes. [The models it supports must support tool use in the Converse API](https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference-supported-models-features.html).
90
-
91
-
Using the Converse API makes it easy to swap different models without having to drastically change how you interact with them.
58
+
The Amplify AI Kit uses Bedrock's [Converse API](https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference.html) to leverage a unified API across models.
59
+
60
+
<Table
61
+
caption="Table with supported models for Amplify AI kit"
Amplify AI Kit makes use of ["tools"](/[platform]/ai/concepts/tools) for both generation and conversation routes. [The models used must support tool use in the Converse API](https://docs.aws.amazon.com/bedrock/latest/userguide/conversation-inference-supported-models-features.html).
173
+
174
+
Most models have different structures to how they best work with input and how they format their output. Using the Converse API makes it easy to swap different models without having to drastically change how you interact with them.
92
175
93
176
## Choosing a model
94
177
@@ -100,17 +183,17 @@ Each model has its own context window size. The context window is how much infor
100
183
101
184
### Latency
102
185
103
-
Smaller models tend to have a lower latency than larger models, but can also sometimes be less powerful.
186
+
Smaller models tend to have a lower latency than larger models, but can also sometimes be less powerful.
104
187
105
188
### Cost
106
189
107
-
Each model has its own price and throughput.
190
+
Each model has its own price and throughput.
108
191
109
192
### Use-case fit
110
193
111
-
Some models are trained to be better at certain tasks or with certain languages.
194
+
Some models are trained to be better at certain tasks or with certain languages.
112
195
113
-
Choosing the right model for your use case is balancing latency, cost, and performance.
196
+
Choosing the right model for your use case is balancing latency, cost, and performance.
0 commit comments