DeepSeek-R1 Model now Available in Amazon Bedrock Marketplace And Amazon SageMaker JumpStart

Today, we are delighted to reveal that DeepSeek R1 distilled Llama and Qwen designs are available through Amazon Bedrock Marketplace and Amazon SageMaker JumpStart. With this launch, you can now release DeepSeek AI‘s first-generation frontier model, DeepSeek-R1, together with the distilled versions varying from 1.5 to 70 billion criteria to develop, experiment, and properly 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 deploy the distilled versions of the models also.

Overview of DeepSeek-R1

DeepSeek-R1 is a big language design (LLM) developed by DeepSeek AI that uses reinforcement discovering to boost thinking abilities through a multi-stage training procedure from a DeepSeek-V3-Base structure. An essential distinguishing function is its reinforcement knowing (RL) action, which was used to refine the design’s responses beyond the standard pre-training and tweak procedure. By including RL, DeepSeek-R1 can adjust more successfully to user feedback and objectives, ultimately improving both importance and clearness. In addition, DeepSeek-R1 utilizes a chain-of-thought (CoT) method, meaning it’s geared up to break down intricate queries and reason through them in a detailed manner. This assisted thinking process enables the model to produce more precise, transparent, and detailed answers. This model combines RL-based fine-tuning with CoT capabilities, aiming to produce structured actions while focusing on interpretability and user interaction. With its comprehensive abilities DeepSeek-R1 has actually captured the industry’s attention as a versatile text-generation design that can be incorporated into various workflows such as representatives, rational thinking and information analysis tasks.

DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion specifications in size. The MoE architecture permits activation of 37 billion criteria, allowing effective inference by routing inquiries to the most appropriate expert “clusters.” This method enables the design to concentrate on different issue domains while maintaining total performance. DeepSeek-R1 requires 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 offering 1128 GB of GPU memory.

DeepSeek-R1 distilled designs bring the thinking capabilities of the main R1 model to more efficient architectures based on popular open designs 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 simulate the behavior and reasoning patterns of the bigger DeepSeek-R1 design, utilizing it as a teacher design.

You can deploy DeepSeek-R1 design either through SageMaker JumpStart or Bedrock Marketplace. Because DeepSeek-R1 is an emerging model, we recommend deploying this design with guardrails in place. In this blog site, we will use Amazon Bedrock Guardrails to introduce safeguards, prevent hazardous content, and examine designs against essential safety requirements. At the time of composing this blog site, fishtanklive.wiki for DeepSeek-R1 deployments on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports only the ApplyGuardrail API. You can produce numerous guardrails tailored to different usage cases and apply them to the DeepSeek-R1 design, enhancing user experiences and standardizing security controls throughout your generative AI applications.

Prerequisites

To deploy the DeepSeek-R1 design, you require access to an ml.p5e instance. To examine if you have quotas for wiki.dulovic.tech 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 releasing. To request a limit boost, create a limit increase request and connect to your account team.

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

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to introduce safeguards, avoid damaging content, and evaluate designs against essential safety criteria. You can implement security procedures for the DeepSeek-R1 design utilizing the Amazon Bedrock ApplyGuardrail API. This enables you to apply guardrails to assess user inputs and model reactions deployed 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 flow involves the following actions: First, the system receives 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 reasoning. After getting the model’s output, another guardrail check is used. If the output passes this last check, it’s returned as the result. However, if either the input or output is intervened by the guardrail, a message is returned showing the nature of the intervention and whether it took place at the input or output phase. The examples showcased in the following sections show reasoning utilizing this API.

Deploy DeepSeek-R1 in Amazon Bedrock Marketplace

Amazon Bedrock Marketplace provides 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 steps:

1. On the Amazon Bedrock console, select Model catalog under Foundation designs in the navigation pane.
At the time of composing this post, you can use 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 provider and pick the DeepSeek-R1 model.

The design detail page offers necessary details about the design’s abilities, pricing structure, and implementation guidelines. You can find detailed use guidelines, consisting of sample API calls and code bits for integration. The design supports various text generation tasks, including content development, code generation, and question answering, utilizing its support discovering optimization and CoT thinking capabilities.
The page likewise consists of release options and licensing details to assist you begin with DeepSeek-R1 in your applications.
3. To begin using DeepSeek-R1, choose Deploy.

You will be prompted to configure the implementation details for DeepSeek-R1. The model ID will be pre-populated.
4. For Endpoint name, go into an endpoint name (in between 1-50 alphanumeric characters).
5. For links.gtanet.com.br Number of instances, enter a variety of instances (in between 1-100).
6. For Instance type, pick your circumstances type. For ideal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is advised.
Optionally, you can configure sophisticated security and facilities settings, including virtual personal cloud (VPC) networking, service function consents, and file encryption settings. For the majority of utilize cases, the default settings will work well. However, for production deployments, you might wish to review these settings to line up with your company’s security and compliance requirements.
7. Choose Deploy to start using the model.

When the release is complete, you can test DeepSeek-R1’s abilities straight in the Amazon Bedrock play area.
8. Choose Open in play area to access an interactive interface where you can experiment with different triggers and adjust model specifications like temperature and optimum length.
When using R1 with Bedrock’s InvokeModel and Playground Console, use DeepSeek’s chat design template for optimum outcomes. For instance, content for inference.

This is an excellent way to explore the design’s thinking and text generation capabilities before incorporating it into your applications. The play area offers instant feedback, assisting you comprehend how the model responds to numerous inputs and letting you tweak your prompts for ideal outcomes.

You can rapidly check the model in the playground through the UI. However, to invoke the deployed design programmatically with any Amazon Bedrock APIs, you need to get the endpoint ARN.

Run inference using guardrails with the released DeepSeek-R1 endpoint

The following code example shows how to perform inference using a deployed DeepSeek-R1 model through Amazon Bedrock using the invoke_model and ApplyGuardrail API. You can produce a guardrail using the Amazon Bedrock console or the API. For the example code to develop the guardrail, see the GitHub repo. After you have created the guardrail, utilize the following code to implement guardrails. The script initializes the bedrock_runtime customer, sets up reasoning specifications, and sends a demand to create text based upon a user prompt.

Deploy DeepSeek-R1 with SageMaker JumpStart

SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, integrated 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 information, and release them into production using either the UI or SDK.

Deploying DeepSeek-R1 design through SageMaker JumpStart offers 2 convenient techniques: utilizing the instinctive SageMaker JumpStart UI or carrying out programmatically through the SageMaker Python SDK. Let’s explore both approaches to assist you choose the method that best fits your requirements.

Deploy DeepSeek-R1 through SageMaker JumpStart UI

Complete the following steps to deploy DeepSeek-R1 using SageMaker JumpStart:

1. On the SageMaker console, select Studio in the navigation pane.
2. First-time users will be triggered to create a domain.
3. On the SageMaker Studio console, select JumpStart in the navigation pane.

The model internet browser displays available designs, with details like the service provider name and bio.rogstecnologia.com.br model abilities.

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

– Model name
– Provider name
– Task classification (for example, Text Generation).
Bedrock Ready badge (if relevant), suggesting that this design can be signed up with Amazon Bedrock, enabling you to use Amazon Bedrock APIs to conjure up the design

5. Choose the design card to view the design details page.

The design details page consists of 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 important details, such as:

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

Before you release the design, it’s advised to examine the model details and license terms to verify compatibility with your use case.

6. Choose Deploy to continue with deployment.

7. For Endpoint name, utilize the automatically created name or produce a custom one.
8. For example type ¸ pick a circumstances type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, enter the variety of instances (default: 1).
Selecting suitable circumstances types and counts is vital for expense and efficiency optimization. Monitor your deployment to adjust these settings as needed.Under Inference type, Real-time reasoning is chosen by default. This is optimized for sustained traffic and low latency.
10. Review all configurations for accuracy. For this design, we strongly suggest adhering to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to deploy the design.

The deployment process can take a number of minutes to finish.

When implementation is total, your endpoint status will change to InService. At this point, the design is prepared to accept inference demands through the endpoint. You can keep an eye on the implementation progress on the SageMaker console Endpoints page, which will display pertinent metrics and status details. When the release is complete, you can invoke the design 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 utilizing the SageMaker Python SDK, you will require to set up the SageMaker Python SDK and make certain you have the needed AWS permissions 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 additional 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 create a guardrail using the Amazon Bedrock console or the API, and implement it as shown in the following code:

Tidy up

To avoid undesirable 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 models in the navigation pane, select Marketplace releases.
2. In the Managed deployments 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 erasing the proper release: 1. Endpoint name.
2. Model name.
3. Endpoint status

Delete the SageMaker JumpStart predictor

The SageMaker JumpStart design you released 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 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 get going. For more details, refer to Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained models, Amazon SageMaker JumpStart Foundation Models, Amazon Bedrock Marketplace, and Beginning with Amazon SageMaker JumpStart.

About the Authors

Vivek Gangasani is a Lead Specialist Solutions Architect for Inference at AWS. He assists emerging generative AI companies develop innovative solutions using AWS services and accelerated calculate. Currently, he is focused on establishing methods for fine-tuning and optimizing the inference efficiency of large language designs. In his leisure time, Vivek delights in hiking, seeing films, and attempting various cuisines.

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 Science and Bioinformatics.

Jonathan Evans is an Expert Solutions Architect working on generative AI with the Third-Party Model Science team at AWS.

Banu Nagasundaram leads item, engineering, and strategic partnerships for Amazon SageMaker JumpStart, SageMaker’s artificial intelligence and generative AI center. She is enthusiastic about developing solutions that assist clients accelerate their AI journey and unlock organization worth.