Today, we are thrilled to announce that DeepSeek R1 distilled Llama and Qwen designs 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 versions 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 steps to release the distilled versions of the designs too.
Overview of DeepSeek-R1
DeepSeek-R1 is a big language model (LLM) established by DeepSeek AI that utilizes reinforcement discovering to boost reasoning abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. An essential identifying function is its support knowing (RL) step, which was used to improve the model's reactions beyond the basic pre-training and fine-tuning procedure. By incorporating RL, DeepSeek-R1 can adapt better to user feedback and goals, ultimately improving both relevance and clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) approach, suggesting it's geared up to break down complicated inquiries and reason through them in a detailed manner. This guided reasoning process allows the design to produce more accurate, transparent, and detailed responses. This design integrates RL-based fine-tuning with CoT abilities, aiming to generate structured responses while focusing on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has caught the market's attention as a flexible text-generation model that can be integrated into various workflows such as agents, sensible reasoning and information interpretation jobs.
DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture permits activation of 37 billion criteria, enabling effective inference by routing questions to the most appropriate specialist "clusters." This approach permits the design to specialize in various issue domains while maintaining overall performance. DeepSeek-R1 needs at least 800 GB of HBM memory in FP8 format for reasoning. In this post, we will utilize an ml.p5e.48 xlarge instance to release the model. ml.p5e.48 xlarge features 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.
DeepSeek-R1 distilled models bring the reasoning abilities of the main R1 design to more effective architectures based on popular open designs like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation describes a procedure of training smaller sized, more efficient designs to imitate the behavior and reasoning patterns of the bigger DeepSeek-R1 design, utilizing it as an instructor model.
You can release DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we advise releasing this model with guardrails in place. In this blog, we will use Amazon Bedrock Guardrails to introduce safeguards, avoid hazardous material, and examine designs against crucial safety requirements. At the time of composing this blog, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can produce numerous guardrails tailored to various use cases and apply them to the DeepSeek-R1 model, enhancing user experiences and standardizing security controls across your generative AI applications.
Prerequisites
To deploy the DeepSeek-R1 model, you require access to an ml.p5e instance. To examine if you have quotas for P5e, open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and verify you're using ml.p5e.48 xlarge for endpoint use. 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 increase, produce a limitation increase request and connect to your account team.
Because you will be deploying this design with Amazon Bedrock Guardrails, make certain you have the proper AWS Identity and Gain Access To Management (IAM) permissions to utilize Amazon Bedrock Guardrails. For wavedream.wiki instructions, see Establish permissions to utilize guardrails for content filtering.
Implementing guardrails with the ApplyGuardrail API
Amazon Bedrock Guardrails enables you to introduce safeguards, prevent damaging content, and examine designs against crucial security criteria. You can carry out safety procedures for the DeepSeek-R1 model utilizing the Amazon Bedrock ApplyGuardrail API. This permits you to apply guardrails to examine user inputs and model reactions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo.
The general flow includes the following steps: First, the system receives an input for the design. This input is then processed through the ApplyGuardrail API. If the input passes the guardrail check, it's sent out to the model for reasoning. After getting the model's output, another guardrail check is used. If the output passes this final check, it's returned as the last outcome. However, if either the input or output is intervened by the guardrail, a message is returned suggesting the nature of the intervention and whether it took place at the input or output phase. 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 catalog under Foundation models in the navigation pane.
At the time of composing this post, you can utilize the InvokeModel API to invoke the model. It does not support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a supplier and select the DeepSeek-R1 design.
The design detail page offers important details about the design's capabilities, rates structure, and implementation standards. You can find detailed use instructions, consisting of sample API calls and code snippets for combination. The model supports numerous text generation jobs, including content production, code generation, and question answering, utilizing its support discovering optimization and CoT thinking capabilities.
The page likewise consists of implementation alternatives and licensing details to assist you get started with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, pick Deploy.
You will be triggered to configure the deployment details for DeepSeek-R1. The design ID will be pre-populated.
4. For Endpoint name, go into an endpoint name (between 1-50 alphanumeric characters).
5. For Number of circumstances, enter a variety of circumstances (in between 1-100).
6. For Instance type, choose your instance type. For ideal efficiency with DeepSeek-R1, a GPU-based instance type like ml.p5e.48 xlarge is suggested.
Optionally, you can configure innovative security and facilities settings, including virtual personal cloud (VPC) networking, service function approvals, and file encryption settings. For most utilize cases, the default settings will work well. However, for production deployments, you might want to evaluate these settings to align with your company's security and compliance requirements.
7. Choose Deploy to begin utilizing the design.
When the release is total, you can check DeepSeek-R1's capabilities straight in the Amazon Bedrock play ground.
8. Choose Open in play area to access an interactive interface where you can explore different prompts and change model parameters like temperature level and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, utilize DeepSeek's chat template for optimal results. For example, content for inference.
This is an outstanding method to check out the design's thinking and text generation capabilities before integrating it into your applications. The play ground supplies immediate feedback, assisting you comprehend how the model reacts to different inputs and letting you tweak your triggers for ideal results.
You can rapidly test the model in the play area through the UI. However, to conjure up the deployed model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.
Run inference utilizing guardrails with the released DeepSeek-R1 endpoint
The following code example shows how to perform reasoning using a released DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can create a guardrail utilizing the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have actually produced the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, sets up reasoning specifications, and sends out a request to produce text based upon a user timely.
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 deploy with just a few clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your data, and deploy them into production using either the UI or SDK.
Deploying DeepSeek-R1 model through SageMaker JumpStart uses 2 hassle-free approaches: utilizing the intuitive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's check out both methods to help you pick the method that best matches your needs.
Deploy DeepSeek-R1 through SageMaker JumpStart UI
Complete the following steps to release DeepSeek-R1 using SageMaker JumpStart:
1. On the SageMaker console, select Studio in the navigation pane.
2. First-time users will be triggered to develop a domain.
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.
The design web browser shows available models, with details like the name and model capabilities.
4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card reveals essential details, consisting of:
- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if suitable), indicating that this model can be registered with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to invoke the design
5. Choose the model card to view the design details page.
The design details page includes the following details:
- The design name and service provider 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 requirements.
- Usage guidelines
Before you deploy the design, it's advised to review the design details and license terms to verify compatibility with your use case.
6. Choose Deploy to continue with release.
7. For Endpoint name, use the instantly created name or develop a custom-made one.
- For Instance type ¸ choose a circumstances type (default: ml.p5e.48 xlarge).
- For Initial circumstances count, enter the variety of circumstances (default: 1). Selecting suitable circumstances types and counts is vital for expense and performance optimization. Monitor your deployment to change these settings as needed.Under Inference type, Real-time inference is selected by default. This is optimized for sustained traffic and low latency.
- Review all setups for precision. For this model, we strongly recommend adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
- Choose Deploy to deploy the model.
The deployment process can take several minutes to complete.
When implementation is total, your endpoint status will alter to InService. At this moment, the design is all set to accept reasoning requests through the endpoint. You can keep an eye on the deployment progress on the SageMaker console Endpoints page, which will display relevant metrics and status details. When the deployment is complete, you can invoke the model utilizing a SageMaker runtime client and incorporate it with your applications.
Deploy DeepSeek-R1 using the SageMaker Python SDK
To get begun with DeepSeek-R1 using the SageMaker Python SDK, you will need to install the SageMaker Python SDK and make certain you have the required AWS authorizations and environment setup. The following is a detailed code example that demonstrates how to deploy and use DeepSeek-R1 for reasoning programmatically. The code for releasing the model is supplied in the Github here. You can clone the notebook and range from SageMaker Studio.
You can run additional demands against the predictor:
Implement guardrails and run reasoning with your SageMaker JumpStart predictor
Similar to Amazon Bedrock, you can likewise utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can create a guardrail utilizing the Amazon Bedrock console or the API, and implement it as shown in the following code:
Clean up
To avoid unwanted charges, complete the actions in this section to tidy up your resources.
Delete the Amazon Bedrock Marketplace deployment
If you deployed the model using Amazon Bedrock Marketplace, total the following steps:
1. On the Amazon Bedrock console, under Foundation models in the navigation pane, select Marketplace deployments. - In the Managed releases section, find the endpoint you desire to erase.
- Select the endpoint, and on the Actions menu, select Delete.
- Verify the endpoint details to make certain you're deleting the correct implementation: 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 delete the endpoint if you wish to stop sustaining charges. For more details, see Delete Endpoints and Resources.
Conclusion
In this post, we explored how you can access and deploy the DeepSeek-R1 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get started. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart designs, SageMaker JumpStart pretrained designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Starting 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 develop ingenious services utilizing AWS services and sped up calculate. Currently, he is focused on establishing techniques for fine-tuning and optimizing the reasoning performance of large language designs. In his leisure time, Vivek enjoys treking, viewing movies, and attempting different foods.
Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model Science group at AWS. His area of focus is AWS AI accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology 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 tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI hub. She is passionate about developing solutions that assist customers accelerate their AI journey and unlock business value.