Bedrock FMs Overview
- Choosing an adequate FM depends on a lot of factors!
- Model types, performance requirements, capabilities, constraints, compliance
- Level of customization, model size, inference options, licensing agreements, context windows, latency
- Multimodal models (varied types of input and outputs)
- Multimodal models can do e.g. both text and image
- 💡 Smaller models: more cost-effective & more limited in outputs
- Amazon Titan
- High-performing FM from AWS
- Image, text, multimodal model choices via fully-managed APIs
- Can be customized with your own data
Comparison table of important FMs
- Stable Diffusion used mainly for image generation
- Cheapness: Titan > Llama > Claude
- Input tokens: Claude > Titan > Llama
- i.e. how big/long can the prompt be
- ‼️ Remember features and use cases!!
- 💡 The FMs are slowly converging to the same thing, but right now there are differences between them
Demo
- Can compare outputs of different FMs for same prompts
- Custom Models → Influence an FM with your own data:
- Fine-tuning job: applied once
- Continued Pre-training job: applied continuously
- Fine-tuning an FM
- S3 used → Bedrock needs a service role with S3 permissions
- Training data
- Validation data (if existent)
- Output data
- Hyperparameters: present in ML jobs
- configurations on how the algorithm should behave
- very useful for data scientists
- Must purchase provisioned throughput
- Very expensive!!
- Screenshot
Fine-Tuning a Model