Today, we are thrilled to reveal that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now deploy DeepSeek AI's first-generation frontier design, DeepSeek-R1, along with the distilled variations varying from 1.5 to 70 billion criteria to develop, experiment, and responsibly scale your generative AI ideas on AWS.
In this post, we demonstrate how to get going with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar actions to release the distilled variations of the models as well.
Overview of DeepSeek-R1
DeepSeek-R1 is a big language model (LLM) established by DeepSeek AI that uses reinforcement discovering to enhance thinking abilities through a multi-stage training process from a DeepSeek-V3-Base structure. A key identifying feature is its reinforcement learning (RL) action, which was utilized to refine the design's responses beyond the basic pre-training and fine-tuning process. By including RL, DeepSeek-R1 can adapt more effectively to user feedback and objectives, ultimately enhancing both significance and clearness. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) method, meaning it's geared up to break down intricate inquiries and factor through them in a detailed manner. This assisted thinking process permits the design to produce more accurate, transparent, and detailed answers. This model combines RL-based fine-tuning with CoT abilities, aiming to generate structured reactions while focusing on interpretability and user interaction. With its wide-ranging abilities DeepSeek-R1 has actually caught the market's attention as a flexible text-generation design that can be integrated into various workflows such as agents, rational thinking and data analysis jobs.
DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture permits activation of 37 billion criteria, enabling effective reasoning by routing queries to the most pertinent professional "clusters." This technique allows the design to concentrate on various issue domains while maintaining total efficiency. DeepSeek-R1 requires at least 800 GB of HBM memory in FP8 format for inference. In this post, we will use an ml.p5e.48 xlarge instance to release the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs supplying 1128 GB of GPU memory.
DeepSeek-R1 distilled designs bring the thinking capabilities of the main R1 model to more effective architectures based on popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a process of training smaller sized, more effective designs to mimic the behavior and thinking patterns of the larger DeepSeek-R1 design, using it as a teacher model.
You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we suggest deploying this model with guardrails in place. In this blog site, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid hazardous content, and evaluate designs against key safety criteria. At the time of writing this blog, for DeepSeek-R1 releases on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can produce multiple guardrails tailored to different usage cases and apply them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls throughout your generative AI applications.
Prerequisites
To release the DeepSeek-R1 design, you require access to an ml.p5e circumstances. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and confirm you're utilizing ml.p5e.48 xlarge for endpoint usage. Make certain that you have at least one ml.P5e.48 xlarge circumstances in the AWS Region you are deploying. To ask for a limitation boost, develop a limit boost request and reach out to your account group.
Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the appropriate AWS Identity and Gain Access To Management (IAM) authorizations to use Amazon Bedrock Guardrails. For instructions, see Establish consents to use guardrails for content filtering.
Implementing guardrails with the ApplyGuardrail API
Amazon Bedrock Guardrails allows you to present safeguards, avoid damaging material, and assess designs against key safety criteria. You can carry out security procedures for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This enables you to use guardrails to evaluate user inputs and design reactions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can develop a guardrail using the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo.
The general circulation includes the following steps: First, the system gets an input for the model. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent to the design for inference. After getting the design's output, another guardrail check is used. If the output passes this final check, it's returned as the result. However, if either the input or output is stepped in by the guardrail, a message is returned showing the nature of the intervention and whether it took place at the input or output stage. The examples showcased in the following sections demonstrate inference using this API.
Deploy DeepSeek-R1 in Amazon Bedrock Marketplace
Amazon Bedrock Marketplace offers you access to over 100 popular, emerging, and specialized structure models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following actions:
1. On the Amazon Bedrock console, choose Model brochure under Foundation designs in the navigation pane.
At the time of writing this post, you can use the InvokeModel API to invoke the model. It does not support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and choose the DeepSeek-R1 model.
The design detail page provides essential details about the design's capabilities, rates structure, setiathome.berkeley.edu and execution guidelines. You can discover detailed use instructions, including sample API calls and code snippets for combination. The model supports numerous text generation jobs, including material development, code generation, and question answering, using its support learning optimization and CoT thinking capabilities.
The page also includes deployment alternatives and licensing details to assist you begin with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, choose Deploy.
You will be triggered to configure the implementation details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (in between 1-50 alphanumeric characters).
5. For Variety of circumstances, get in a variety of circumstances (between 1-100).
6. For Instance type, choose your . For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is recommended.
Optionally, you can set up advanced security and facilities settings, consisting of virtual private cloud (VPC) networking, service function approvals, and file encryption settings. For most use cases, the default settings will work well. However, for production releases, you may wish to examine these settings to line up with your organization's security and compliance requirements.
7. Choose Deploy to begin utilizing the model.
When the deployment is complete, you can test DeepSeek-R1's capabilities straight in the Amazon Bedrock play ground.
8. Choose Open in play ground to access an interactive user interface where you can explore different triggers and adjust design specifications like temperature and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for optimum outcomes. For example, content for inference.
This is an excellent way to explore the design's reasoning and text generation abilities before integrating it into your applications. The play ground provides immediate feedback, helping you understand how the model reacts to numerous inputs and letting you tweak your prompts for optimum results.
You can quickly check the model in the playground through the UI. However, to invoke the released model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.
Run inference using guardrails with the deployed DeepSeek-R1 endpoint
The following code example shows how to carry out reasoning using a deployed DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to create the guardrail, see the GitHub repo. After you have developed the guardrail, use the following code to carry out guardrails. The script initializes the bedrock_runtime customer, configures reasoning parameters, and sends a request to produce text based upon a user prompt.
Deploy DeepSeek-R1 with SageMaker JumpStart
SageMaker JumpStart is an artificial intelligence (ML) center with FMs, built-in algorithms, and prebuilt ML services that you can release with just a few clicks. With SageMaker JumpStart, you can tailor pre-trained models to your usage case, with your data, and deploy them into production using either the UI or SDK.
Deploying DeepSeek-R1 design through SageMaker JumpStart uses two convenient approaches: utilizing the intuitive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's check out both approaches to help you select the technique that best fits your needs.
Deploy DeepSeek-R1 through SageMaker JumpStart UI
Complete the following actions to release DeepSeek-R1 utilizing SageMaker JumpStart:
1. On the SageMaker console, select Studio in the navigation pane.
2. First-time users will be prompted to develop a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.
The design internet browser shows available designs, with details like the company name and model capabilities.
4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each design card reveals crucial details, consisting of:
- Model name
- Provider name
- Task category (for instance, Text Generation).
Bedrock Ready badge (if suitable), indicating that this model can be registered with Amazon Bedrock, enabling you to utilize Amazon Bedrock APIs to conjure up the model
5. Choose the model card to view the design details page.
The design details page consists of the following details:
- The model name and company details. Deploy button to deploy the model. About and Notebooks tabs with detailed details
The About tab includes important details, such as:
- Model description. - License details.
- Technical specifications.
- Usage standards
Before you release the model, it's suggested to evaluate the model details and license terms to confirm compatibility with your usage case.
6. Choose Deploy to continue with implementation.
7. For Endpoint name, utilize the instantly created name or create a customized one.
- For example type ¸ pick an instance type (default: ml.p5e.48 xlarge).
- For Initial instance count, enter the variety of instances (default: 1). Selecting proper instance types and counts is important for cost and performance optimization. Monitor your release to adjust these settings as needed.Under Inference type, Real-time inference is picked by default. This is optimized for sustained traffic and low latency.
- Review all configurations for accuracy. For this design, we strongly advise sticking to SageMaker JumpStart default settings and making certain that network isolation remains in location.
- Choose Deploy to deploy the design.
The implementation process can take a number of minutes to finish.
When implementation is complete, your endpoint status will change to InService. At this moment, the design is prepared to accept inference demands through the endpoint. You can keep track of the deployment development on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the deployment is total, you can conjure up the design utilizing a SageMaker runtime client and incorporate it with your applications.
Deploy DeepSeek-R1 using the SageMaker Python SDK
To get going with DeepSeek-R1 utilizing the SageMaker Python SDK, you will need to install the SageMaker Python SDK and make certain you have the necessary AWS authorizations and environment setup. The following is a detailed code example that demonstrates how to deploy and utilize DeepSeek-R1 for reasoning programmatically. The code for deploying the design is provided in the Github here. You can clone the notebook and run from SageMaker Studio.
You can run extra demands against the predictor:
Implement guardrails and run reasoning with your SageMaker JumpStart predictor
Similar to Amazon Bedrock, you can also utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can produce a guardrail utilizing the Amazon Bedrock console or the API, and execute it as displayed in the following code:
Tidy up
To avoid undesirable charges, finish the actions in this section to clean up your resources.
Delete the Amazon Bedrock Marketplace implementation
If you released the design using Amazon Bedrock Marketplace, total the following actions:
1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace implementations. - In the Managed implementations area, locate the endpoint you wish to delete.
- Select the endpoint, and on the Actions menu, choose Delete.
- Verify the endpoint details to make certain you're erasing the appropriate release: 1. Endpoint name.
- Model name.
- Endpoint status
Delete the SageMaker JumpStart predictor
The SageMaker JumpStart design you released will sustain costs if you leave it running. Use the following code to erase the endpoint if you wish to stop sustaining charges. For more details, see Delete Endpoints and Resources.
Conclusion
In this post, we checked out how you can access and release the DeepSeek-R1 design using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to begin. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting going with Amazon SageMaker JumpStart.
About the Authors
Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He helps emerging generative AI business build innovative solutions utilizing AWS services and accelerated calculate. Currently, he is focused on establishing techniques for fine-tuning and enhancing the reasoning performance of large language designs. In his free time, Vivek delights in treking, seeing motion pictures, and attempting different cuisines.
Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model Science group at AWS. His location of focus is AWS AI accelerators (AWS Neuron). He holds a Bachelor's degree in Computer Science and Bioinformatics.
Jonathan Evans is a Specialist Solutions Architect working on generative AI with the Third-Party Model Science group at AWS.
Banu Nagasundaram leads product, engineering, and strategic collaborations for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI center. She is passionate about constructing options that assist clients accelerate their AI journey and unlock business value.