Jskenglish 16 views

Tentang Perusahaan

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

Today, we are delighted 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 model, DeepSeek-R1, together with the distilled variations varying from 1.5 to 70 billion parameters to build, experiment, and properly scale your generative AI ideas on AWS.

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

Overview of DeepSeek-R1

DeepSeek-R1 is a big language model (LLM) developed by DeepSeek AI that uses reinforcement finding out to improve thinking capabilities through a multi-stage training process from a DeepSeek-V3-Base foundation. A crucial identifying function is its support learning (RL) action, which was utilized to improve the model’s responses beyond the standard pre-training and tweak procedure. By including RL, DeepSeek-R1 can adapt more successfully to user feedback and goals, eventually enhancing both importance and yewiki.org clearness. In addition, DeepSeek-R1 employs a chain-of-thought (CoT) method, meaning it’s equipped to break down complex questions and reason through them in a detailed manner. This directed reasoning process enables the design to produce more accurate, transparent, and detailed answers. This design integrates RL-based fine-tuning with CoT abilities, aiming to create structured reactions while concentrating on interpretability and user interaction. With its wide-ranging capabilities DeepSeek-R1 has caught the industry’s attention as a versatile text-generation design that can be integrated into numerous workflows such as agents, sensible reasoning and data interpretation tasks.

DeepSeek-R1 uses a Mix of Experts (MoE) architecture and is 671 billion parameters in size. The MoE architecture allows activation of 37 billion parameters, making it possible for efficient inference by routing questions to the most appropriate professional “clusters.” This method permits the design to concentrate on different issue domains while maintaining overall performance. DeepSeek-R1 requires at least 800 GB of HBM memory in FP8 format for reasoning. In this post, we will use an ml.p5e.48 xlarge circumstances 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 reasoning capabilities of the main R1 model to more efficient architectures based upon popular open models like Qwen (1.5 B, 7B, 14B, and gratisafhalen.be 32B) and Llama (8B and 70B). Distillation describes a process of training smaller, more efficient designs to simulate the habits and reasoning patterns of the larger DeepSeek-R1 model, utilizing it as a teacher design.

You can deploy DeepSeek-R1 model 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 utilize Amazon Bedrock Guardrails to present safeguards, avoid harmful content, and assess designs against crucial security criteria. At the time of composing this blog, for DeepSeek-R1 implementations on SageMaker JumpStart and Bedrock Marketplace, Bedrock Guardrails supports just the ApplyGuardrail API. You can develop multiple guardrails tailored to various use cases and apply them to the DeepSeek-R1 model, enhancing user experiences and standardizing security controls throughout your generative AI applications.

Prerequisites

To release the DeepSeek-R1 design, you need access to an ml.p5e circumstances. To examine if you have quotas for P5e, wiki.snooze-hotelsoftware.de open the Service Quotas console and under AWS Services, pick Amazon SageMaker, and verify you’re utilizing ml.p5e.48 xlarge for . 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, create a limitation boost request and reach out to your account team.

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) permissions to use Amazon Bedrock Guardrails. For guidelines, see Set up authorizations to use guardrails for content filtering.

Implementing guardrails with the ApplyGuardrail API

Amazon Bedrock Guardrails allows you to present safeguards, prevent damaging material, and assess models against key security criteria. You can implement precaution for the DeepSeek-R1 design using the Amazon Bedrock ApplyGuardrail API. This enables you to use guardrails to evaluate user inputs and design responses 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 develop the guardrail, see the GitHub repo.

The basic flow includes the following steps: engel-und-waisen.de 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 design for inference. After getting the model’s output, another guardrail check is applied. If the output passes this last check, it’s returned as the outcome. However, if either the input or output is intervened by the guardrail, a message is returned indicating 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 models (FMs) through Amazon Bedrock. To gain access to DeepSeek-R1 in Amazon Bedrock, total the following actions:

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 utilize the InvokeModel API to invoke the model. It doesn’t support Converse APIs and other Amazon Bedrock tooling.
2. Filter for DeepSeek as a service provider and select the DeepSeek-R1 design.

The design detail page provides necessary details about the design’s capabilities, pricing structure, and implementation guidelines. You can discover detailed use directions, consisting of sample API calls and code snippets for combination. The model supports different text generation tasks, including content creation, code generation, and concern answering, utilizing its reinforcement learning optimization and CoT reasoning abilities.
The page likewise consists of implementation alternatives and licensing details to help you begin with DeepSeek-R1 in your applications.
3. To start utilizing DeepSeek-R1, select Deploy.

You will be triggered to configure the implementation details for DeepSeek-R1. The design ID will be pre-populated.
4. For Endpoint name, enter an endpoint name (in between 1-50 alphanumeric characters).
5. For Variety of instances, go into a number of circumstances (in between 1-100).
6. For Instance type, pick your circumstances type. For optimal efficiency with DeepSeek-R1, a GPU-based circumstances type like ml.p5e.48 xlarge is suggested.
Optionally, you can configure advanced security and infrastructure settings, consisting of virtual personal cloud (VPC) networking, service role consents, and encryption settings. For many utilize cases, the default settings will work well. However, for production implementations, you may wish to examine these settings to line up with your organization’s security and compliance requirements.
7. Choose Deploy to start using the design.

When the release is total, you can evaluate DeepSeek-R1’s capabilities straight in the Amazon Bedrock playground.
8. Choose Open in playground to access an interactive interface where you can explore various prompts and adjust design parameters like temperature and optimum length.
When using R1 with Bedrock’s InvokeModel and Playground Console, use DeepSeek’s chat template for optimal outcomes. For example, content for inference.

This is an outstanding way to check out the model’s thinking and text generation abilities before integrating it into your applications. The play area provides instant feedback, assisting you understand how the model responds to numerous inputs and letting you tweak your prompts for optimal outcomes.

You can quickly evaluate 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 using guardrails with the released DeepSeek-R1 endpoint

The following code example shows how to perform reasoning utilizing a released DeepSeek-R1 design 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 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, sets up reasoning specifications, and sends out a demand to create text based on a user prompt.

Deploy DeepSeek-R1 with SageMaker JumpStart

SageMaker JumpStart is an artificial intelligence (ML) hub with FMs, integrated algorithms, and prebuilt ML options that you can deploy with just a few clicks. With SageMaker JumpStart, you can tailor pre-trained models to your use case, with your information, and deploy them into production utilizing either the UI or SDK.

Deploying DeepSeek-R1 model through SageMaker JumpStart offers two practical methods: utilizing the instinctive SageMaker JumpStart UI or executing programmatically through the SageMaker Python SDK. Let’s check out both methods to help you choose the technique that finest fits your requirements.

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 create a domain.
3. On the SageMaker Studio console, choose JumpStart in the navigation pane.

The model web browser displays available designs, with details like the company name and model capabilities.

4. Search for DeepSeek-R1 to view the DeepSeek-R1 model card.
Each model card shows key details, including:

– Model name
– Provider name
– Task classification (for example, Text Generation).
Bedrock Ready badge (if appropriate), indicating that this design can be registered with Amazon Bedrock, permitting you to use Amazon Bedrock APIs to conjure up the model

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

The model details page includes the following details:

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

The About tab consists of crucial details, such as:

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

Before you deploy the model, it’s recommended to evaluate the design details and license terms to verify compatibility with your usage case.

6. Choose Deploy to proceed with implementation.

7. For Endpoint name, use the automatically produced name or develop a custom-made one.
8. For Instance type ¸ choose an instance type (default: ml.p5e.48 xlarge).
9. For Initial circumstances count, go into the variety of circumstances (default: 1).
Selecting proper instance types and counts is crucial for hb9lc.org cost and efficiency optimization. Monitor your implementation 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 configurations for accuracy. For this design, we strongly recommend sticking to SageMaker JumpStart default settings and making certain that network isolation remains in location.
11. Choose Deploy to release the model.

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

When implementation is complete, your endpoint status will alter to InService. At this moment, the model is all set to accept inference demands through the endpoint. You can keep an eye on the deployment progress on the SageMaker console Endpoints page, which will display appropriate metrics and status details. When the release 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 going with DeepSeek-R1 using the SageMaker Python SDK, you will require to install the SageMaker Python SDK and garagesale.es make certain you have the essential 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 note pad 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 utilize the ApplyGuardrail API with your SageMaker JumpStart predictor. You can develop a guardrail using the Amazon Bedrock console or fishtanklive.wiki the API, and implement it as displayed in the following code:

Tidy up

To avoid unwanted charges, finish the steps in this area to tidy 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 designs in the navigation pane, choose Marketplace deployments.
2. In the Managed deployments area, find the endpoint you want to delete.
3. Select the endpoint, and on the Actions menu, choose Delete.
4. Verify the endpoint details to make certain you’re deleting the right release: 1. Endpoint name.
2. Model name.
3. 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 explored how you can access and release the DeepSeek-R1 model using Bedrock Marketplace and SageMaker JumpStart. Visit SageMaker JumpStart in SageMaker Studio or Amazon Bedrock Marketplace now to get started. For more details, describe Use Amazon Bedrock tooling with Amazon SageMaker JumpStart models, SageMaker JumpStart pretrained models, 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 construct ingenious services using AWS services and sped up compute. Currently, he is concentrated on developing strategies for fine-tuning and enhancing the reasoning performance of big language models. In his spare time, Vivek enjoys treking, watching movies, and attempting various cuisines.

Niithiyn Vijeaswaran is a Generative AI Specialist Solutions Architect with the Third-Party Model Science team 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 an Expert Solutions Architect working on generative AI with the Third-Party Model Science team at AWS.

Banu Nagasundaram leads product, engineering, and tactical partnerships for Amazon SageMaker JumpStart, SageMaker’s artificial intelligence and generative AI hub. She is enthusiastic about developing options that assist clients accelerate their AI journey and unlock service worth.