Today, we are excited to announce that DeepSeek R1 distilled Llama and Qwen models are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek AI's first-generation frontier design, DeepSeek-R1, together with the distilled variations varying from 1.5 to 70 billion criteria to construct, experiment, and properly scale your generative AI ideas on AWS.


In this post, we show how to start with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow comparable steps to deploy the distilled versions of the models too.


Overview of DeepSeek-R1


DeepSeek-R1 is a large language design (LLM) established by DeepSeek AI that utilizes reinforcement finding out to improve reasoning capabilities through a multi-stage training procedure from a DeepSeek-V3-Base foundation. An essential differentiating function is its support learning (RL) step, which was used to refine the model's actions beyond the basic pre-training and tweak procedure. By integrating RL, DeepSeek-R1 can adapt more efficiently to user feedback and objectives, eventually improving both significance and clearness. In addition, DeepSeek-R1 uses a chain-of-thought (CoT) approach, suggesting it's geared up to break down complex questions and factor through them in a detailed manner. This assisted reasoning procedure enables the model to produce more precise, transparent, and detailed answers. This model integrates RL-based fine-tuning with CoT capabilities, aiming to create structured reactions while concentrating on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has actually caught the industry's attention as a versatile text-generation design that can be incorporated into various workflows such as representatives, logical reasoning and information analysis jobs.


DeepSeek-R1 utilizes a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture enables activation of 37 billion criteria, enabling effective reasoning by routing queries to the most relevant expert "clusters." This approach permits the design to focus on different problem domains while maintaining overall performance. DeepSeek-R1 needs a minimum of 800 GB of HBM memory in FP8 format for reasoning. In this post, we will utilize an ml.p5e.48 xlarge instance to deploy the design. ml.p5e.48 xlarge includes 8 Nvidia H200 GPUs providing 1128 GB of GPU memory.


DeepSeek-R1 distilled models bring the thinking capabilities of the main R1 design to more efficient architectures based on popular open models like Qwen (1.5 B, 7B, 14B, and 32B) and Llama (8B and 70B). Distillation refers to a procedure of training smaller, more efficient designs to imitate the habits and reasoning patterns of the larger DeepSeek-R1 design, using it as an instructor design.


You can release DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging design, we suggest releasing this model with guardrails in location. In this blog, we will utilize Amazon Bedrock Guardrails to introduce safeguards, prevent hazardous material, and assess models against essential safety requirements. At the time of composing this blog site, for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can develop numerous guardrails tailored to various usage cases and use them to the DeepSeek-R1 design, improving user experiences and standardizing security controls across your generative AI applications.


Prerequisites


To deploy the DeepSeek-R1 design, you require access to an ml.p5e circumstances. To inspect if you have quotas for P5e, open the Service Quotas console and under AWS Services, select 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 instance in the AWS Region you are releasing. To ask for a limit increase, produce a limitation increase request and connect to your account team.


Because you will be deploying this model with Amazon Bedrock Guardrails, make certain you have the right AWS Identity and Gain Access To Management (IAM) consents to use Amazon Bedrock Guardrails. For directions, see Establish authorizations to utilize guardrails for content filtering.


Implementing guardrails with the ApplyGuardrail API


Amazon Bedrock Guardrails enables you to introduce safeguards, prevent harmful content, and evaluate models against essential safety requirements. You can execute precaution for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This permits 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 basic 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 out to the model for inference. After getting the model's output, another guardrail check is applied. If the output passes this final check, it's returned as the last result. However, if either the input or output is stepped in by the guardrail, a message is returned suggesting the nature of the intervention and whether it happened at the input or output stage. The examples showcased in the following sections demonstrate reasoning utilizing this API.


Deploy DeepSeek-R1 in Amazon Bedrock Marketplace


Amazon Bedrock Marketplace offers you access to over 100 popular, emerging, and specialized foundation designs (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following steps:


1. On the Amazon Bedrock console, pick Model brochure under Foundation designs in the navigation pane.
At the time of writing this post, you can use the InvokeModel API to conjure up the model. It doesn't support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a supplier and pick the DeepSeek-R1 design.


The design detail page supplies important details about the model's abilities, prices structure, and execution standards. You can find detailed usage directions, consisting of sample API calls and code snippets for combination. The design supports numerous text generation tasks, including content creation, code generation, and question answering, utilizing its support finding out optimization and CoT thinking capabilities.
The page also includes release alternatives and licensing details to assist you get going with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, select Deploy.


You will be triggered to configure the deployment 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 instances, enter a variety of instances (in between 1-100).
6. For Instance type, choose your circumstances type. For optimum performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is advised.
Optionally, you can configure sophisticated security and infrastructure settings, including virtual personal cloud (VPC) networking, service role authorizations, and file encryption settings. For the majority of utilize cases, the default settings will work well. However, for production deployments, you might want to examine these settings to align with your company's security and compliance requirements.
7. Choose Deploy to begin utilizing the design.


When the deployment 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 experiment with different triggers and adjust model parameters like temperature level and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for ideal results. For example, <_begin_of_sentence_><_User_>material for reasoning<_Assistant_>.


This is an excellent method to explore the design's reasoning and text generation capabilities before integrating it into your applications. The play ground supplies instant feedback, assisting you comprehend how the model responds to various inputs and letting you fine-tune your prompts for optimum outcomes.


You can rapidly check the design in the play ground through the UI. However, to invoke the released design programmatically with any Amazon Bedrock APIs, you require to get the endpoint ARN.


Run reasoning using guardrails with the released DeepSeek-R1 endpoint


The following code example shows how to carry out reasoning using a released DeepSeek-R1 design through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can create a guardrail using the Amazon Bedrock console or the API. For the example code to produce the guardrail, see the GitHub repo. After you have developed the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime client, configures inference criteria, and sends out a demand to create text based upon a user timely.


Deploy DeepSeek-R1 with SageMaker JumpStart


SageMaker JumpStart is an artificial intelligence (ML) center with FMs, photorum.eclat-mauve.fr built-in algorithms, and prebuilt ML options that you can deploy with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained designs to your use case, with your information, and deploy them into production utilizing either the UI or SDK.


Deploying DeepSeek-R1 design through SageMaker JumpStart uses 2 hassle-free approaches: using the intuitive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let's explore both approaches to assist you pick the approach that best fits your needs.


Deploy DeepSeek-R1 through SageMaker JumpStart UI


Complete the following actions to release DeepSeek-R1 using SageMaker JumpStart:


1. On the SageMaker console, pick Studio in the navigation pane.
2. First-time users will be prompted to develop a domain.
3. On the SageMaker Studio console, pick JumpStart in the navigation pane.


The design browser displays available designs, with details like the supplier name and design abilities.


4. Look for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card reveals key details, consisting of:


- Model name
- Provider name
- Task category (for instance, Text Generation).
Bedrock Ready badge (if appropriate), showing that this model can be registered with Amazon Bedrock, allowing you to utilize Amazon Bedrock APIs to conjure up the design


5. Choose the design card to see the model details page.


The model details page includes the following details:


- The design name and company details.
Deploy button to deploy the model.
About and Notebooks tabs with detailed details


The About tab includes crucial details, such as:


- Model description.
- License details.
- Technical specifications.
- Usage standards


Before you release the design, it's recommended to evaluate the design details and license terms to validate compatibility with your use case.


6. Choose Deploy to proceed with deployment.


7. For Endpoint name, utilize the instantly produced name or develop a custom one.
8. For Instance type ¸ choose an instance type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, get in the number of circumstances (default: 1).
Selecting appropriate circumstances types and counts is important for expense and efficiency optimization. Monitor your deployment to change these settings as needed.Under Inference type, Real-time inference is picked by default. This is enhanced for sustained traffic and low latency.
10. Review all setups for precision. For this design, we highly recommend sticking to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to release the model.


The implementation procedure can take several minutes to finish.


When implementation is complete, your endpoint status will alter to InService. At this moment, the design is all set to accept reasoning demands through the endpoint. You can keep track of the implementation progress on the SageMaker console Endpoints page, which will show pertinent metrics and status details. When the release is complete, you can invoke the model using a SageMaker runtime customer and integrate it with your applications.


Deploy DeepSeek-R1 using the SageMaker Python SDK


To start with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to install the SageMaker Python SDK and make certain you have the needed AWS approvals and environment setup. The following is a detailed code example that demonstrates how to deploy and use DeepSeek-R1 for inference programmatically. The code for releasing the design is offered in the Github here. You can clone the notebook and range from SageMaker Studio.


You can run extra demands against the predictor:


Implement guardrails and run inference 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 shown in the following code:


Tidy up


To prevent unwanted charges, finish the actions in this area to clean up your resources.


Delete the Amazon Bedrock Marketplace release


If you released the model utilizing Amazon Bedrock Marketplace, complete the following steps:


1. On the Amazon Bedrock console, under Foundation models in the navigation pane, pick Marketplace implementations.
2. In the Managed implementations area, find the endpoint you desire to erase.
3. Select the endpoint, and on the Actions menu, select Delete.
4. Verify the endpoint details to make certain you're deleting the right deployment: 1. Endpoint name.
2. Model name.
3. Endpoint status


Delete the SageMaker JumpStart predictor


The SageMaker JumpStart model you released will sustain expenses 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 checked out how you can access and release the DeepSeek-R1 model utilizing Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get begun. 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 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 companies construct innovative options utilizing AWS services and sped up calculate. Currently, he is concentrated on establishing methods for fine-tuning and enhancing the inference efficiency of big language designs. In his downtime, Vivek takes pleasure in hiking, watching motion pictures, and trying various foods.


Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model Science team at AWS. His location of focus is AWS AI accelerators (AWS Neuron). He holds a Bachelor's degree in Computer technology and Bioinformatics.


Jonathan Evans is an Expert 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 enthusiastic about constructing solutions that assist consumers accelerate their AI journey and unlock business value.