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, in addition to the distilled variations varying from 1.5 to 70 billion specifications to construct, experiment, and responsibly scale your generative AI concepts on AWS.
In this post, we show how to get begun with DeepSeek-R1 on Amazon Bedrock Marketplace and SageMaker JumpStart. You can follow similar actions to deploy the distilled versions of the designs too.
Overview of DeepSeek-R1
DeepSeek-R1 is a big language design (LLM) established by DeepSeek AI that uses support finding out to boost thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. A key identifying feature is its reinforcement knowing (RL) action, which was used to refine the model's actions beyond the standard pre-training and fine-tuning procedure. By incorporating RL, DeepSeek-R1 can adjust more efficiently to user feedback and objectives, eventually enhancing both relevance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) method, meaning it's geared up to break down complicated questions and factor through them in a detailed manner. This directed thinking procedure permits the model to produce more precise, transparent, and detailed responses. This design integrates RL-based fine-tuning with CoT capabilities, aiming to produce structured reactions while concentrating on interpretability and user interaction. With its comprehensive capabilities DeepSeek-R1 has recorded the market's attention as a flexible text-generation model that can be incorporated into numerous workflows such as representatives, sensible reasoning and data analysis jobs.
DeepSeek-R1 uses a Mixture of Experts (MoE) architecture and is 671 billion criteria in size. The MoE architecture permits activation of 37 billion criteria, allowing effective inference by routing questions to the most pertinent expert "clusters." This technique enables the model to specialize in different issue domains while maintaining general effectiveness. DeepSeek-R1 needs at least 800 GB of HBM memory in FP8 format for inference. In this post, we will use an ml.p5e.48 xlarge circumstances to deploy the model. ml.p5e.48 xlarge comes with 8 Nvidia H200 GPUs offering 1128 GB of GPU memory.
DeepSeek-R1 distilled designs bring the reasoning 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 process of training smaller sized, more efficient models to mimic the behavior and reasoning patterns of the larger DeepSeek-R1 design, utilizing it as an instructor design.
You can deploy DeepSeek-R1 model either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we suggest deploying this design with guardrails in place. In this blog, we will utilize Amazon Bedrock Guardrails to present safeguards, avoid harmful material, and examine designs against essential safety requirements. At the time of composing this blog site, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can create several guardrails tailored to different use cases and use them to the DeepSeek-R1 model, improving user experiences and standardizing safety controls throughout your generative AI applications.
Prerequisites
To deploy the DeepSeek-R1 model, you need access to an ml.p5e circumstances. To inspect if you have quotas for P5e, open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and validate you're utilizing ml.p5e.48 xlarge for endpoint use. Make certain that you have at least one ml.P5e.48 xlarge instance in the AWS Region you are releasing. To request a limitation boost, develop a limit boost demand and reach out to your account team.
Because you will be releasing this model with Amazon Bedrock Guardrails, make certain you have the proper AWS Identity and genbecle.com Gain Access To Management (IAM) consents to utilize Amazon Bedrock Guardrails. For guidelines, see Establish permissions to use guardrails for material filtering.
Implementing guardrails with the ApplyGuardrail API
Amazon Bedrock Guardrails allows you to present safeguards, avoid hazardous material, and evaluate designs against crucial safety requirements. You can carry out precaution for the DeepSeek-R1 model using the Amazon Bedrock ApplyGuardrail API. This permits you to use guardrails to examine user inputs and model reactions released on Amazon Bedrock Marketplace and SageMaker JumpStart. You can create a guardrail using the Amazon Bedrock console or the API. For the example code to develop 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 out to the design for inference. After getting the design's output, another guardrail check is applied. 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 occurred at the input or output stage. The examples showcased in the following areas show reasoning using this API.
Deploy DeepSeek-R1 in Amazon Bedrock Marketplace
Amazon Bedrock Marketplace gives you access to over 100 popular, emerging, and specialized structure models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, complete the following actions:
1. On the Amazon Bedrock console, choose Model brochure under Foundation designs in the navigation pane.
At the time of composing this post, you can utilize the InvokeModel API to conjure up the model. It does not support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a company and pick the DeepSeek-R1 model.
The model detail page offers essential details about the design's capabilities, pricing structure, and application standards. You can discover detailed usage directions, including sample API calls and code snippets for integration. The model supports numerous text generation tasks, including material development, code generation, and question answering, utilizing its support finding out optimization and CoT reasoning abilities.
The page likewise consists of deployment choices and licensing details to help you begin with DeepSeek-R1 in your applications.
3. To start using DeepSeek-R1, choose Deploy.
You will be prompted to configure the deployment details for DeepSeek-R1. The design ID will be pre-populated.
4. For Endpoint name, get in an endpoint name (in between 1-50 alphanumeric characters).
5. For Variety of circumstances, go into a number of instances (in between 1-100).
6. For example type, choose your instance type. For optimal performance with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is advised.
Optionally, you can set up sophisticated security and facilities settings, consisting of virtual personal cloud (VPC) networking, service role permissions, and encryption settings. For the majority of use cases, the default settings will work well. However, for production releases, you may want to evaluate these settings to align with your organization's security and compliance requirements.
7. Choose Deploy to start using the design.
When the release is complete, you can test DeepSeek-R1's capabilities straight in the Amazon Bedrock play ground.
8. Choose Open in playground to access an interactive interface where you can experiment with different triggers and adjust model criteria like temperature level and optimum length.
When using R1 with Bedrock's InvokeModel and Playground Console, use DeepSeek's chat design template for optimal outcomes. For example, content for reasoning.
This is an outstanding method to check out the design's reasoning and text generation abilities before incorporating it into your applications. The playground supplies instant feedback, assisting you comprehend how the design responds to numerous inputs and letting you tweak your prompts for optimal outcomes.
You can quickly check the model in the play area through the UI. However, to conjure up the released model programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.
Run reasoning using guardrails with the deployed DeepSeek-R1 endpoint
The following code example shows how to carry out inference utilizing a deployed DeepSeek-R1 design through Amazon Bedrock utilizing the invoke_model and ApplyGuardrail API. You can develop 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, use the following code to implement guardrails. The script initializes the bedrock_runtime customer, configures inference criteria, and sends a request to produce text based on a user timely.
Deploy DeepSeek-R1 with SageMaker JumpStart
SageMaker JumpStart is an artificial intelligence (ML) center with FMs, integrated algorithms, and prebuilt ML options that you can deploy with simply a couple of clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your information, and release them into production using either the UI or SDK.
Deploying DeepSeek-R1 model through SageMaker JumpStart provides two convenient methods: utilizing the instinctive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let's check out both approaches to assist you select the method that best matches your needs.
Deploy DeepSeek-R1 through SageMaker JumpStart UI
Complete the following steps to deploy DeepSeek-R1 using SageMaker JumpStart:
1. On the SageMaker console, choose Studio in the navigation pane.
2. First-time users will be triggered to develop a domain.
3. On the SageMaker Studio console, select JumpStart in the navigation pane.
The design web browser displays available models, with details like the company name and design capabilities.
4. Search for DeepSeek-R1 to view the DeepSeek-R1 design card.
Each model card shows essential details, including:
- Model name
- Provider name
- Task classification (for example, Text Generation).
Bedrock Ready badge (if relevant), indicating that this model can be registered with Amazon Bedrock, permitting you to utilize Amazon Bedrock APIs to conjure up the design
5. Choose the design card to view the design details page.
The design details page includes the following details:
- The design name and supplier details. Deploy button to release the design. About and Notebooks tabs with detailed details
The About tab includes important details, such as:
- Model description. - License details.
- Technical specs.
- Usage standards
Before you deploy the model, it's recommended to review the model details and license terms to verify compatibility with your usage case.
6. Choose Deploy to continue with deployment.
7. For Endpoint name, use the instantly created name or produce a custom-made one.
- For example type ¸ select an instance type (default: ml.p5e.48 xlarge).
- For Initial circumstances count, enter the variety of instances (default: 1). Selecting appropriate instance types and counts is crucial for cost and efficiency optimization. Monitor your implementation 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 . For this model, we highly advise adhering to SageMaker JumpStart default settings and making certain that network seclusion remains in location.
- Choose Deploy to deploy the model.
The deployment procedure can take numerous minutes to complete.
When deployment is complete, your endpoint status will alter to InService. At this moment, the design is ready to accept reasoning requests through the endpoint. You can monitor the release progress on the SageMaker console Endpoints page, which will show relevant metrics and status details. When the deployment is total, you can conjure up the design using a SageMaker runtime customer and integrate it with your applications.
Deploy DeepSeek-R1 using the SageMaker Python SDK
To get begun with DeepSeek-R1 utilizing the SageMaker Python SDK, you will require to set up 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 utilize DeepSeek-R1 for inference programmatically. The code for releasing the design is supplied in the Github here. You can clone the notebook and range from SageMaker Studio.
You can run extra requests against the predictor:
Implement guardrails and run inference with your SageMaker JumpStart predictor
Similar to Amazon Bedrock, you can also use the ApplyGuardrail API with your SageMaker JumpStart predictor. You can develop a guardrail using the Amazon Bedrock console or the API, and execute it as revealed in the following code:
Tidy up
To avoid unwanted charges, complete the actions in this section to clean up your resources.
Delete the Amazon Bedrock Marketplace deployment
If you released the design utilizing Amazon Bedrock Marketplace, complete the following steps:
1. On the Amazon Bedrock console, under Foundation designs in the navigation pane, pick Marketplace implementations. - In the Managed implementations area, find the endpoint you desire to erase.
- Select the endpoint, and on the Actions menu, pick Delete.
- Verify the endpoint details to make certain you're deleting the proper implementation: 1. Endpoint name.
- Model name.
- Endpoint status
Delete the SageMaker JumpStart predictor
The SageMaker JumpStart model you deployed will sustain expenses if you leave it running. Use the following code to erase the endpoint if you desire to stop sustaining charges. For more details, see Delete Endpoints and Resources.
Conclusion
In this post, we checked out how you can access and deploy the DeepSeek-R1 design utilizing 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 designs, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Getting begun 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 services utilizing AWS services and accelerated compute. Currently, he is focused on establishing strategies for fine-tuning and optimizing the reasoning efficiency of large language designs. In his leisure time, Vivek delights in treking, watching motion pictures, 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 Science and Bioinformatics.
Jonathan Evans is a Professional Solutions Architect dealing with generative AI with the Third-Party Model Science team at AWS.
Banu Nagasundaram leads item, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker's artificial intelligence and generative AI center. She is passionate about developing services that help customers accelerate their AI journey and unlock organization value.