Cursor on Bedrock Guided Migration

Your developers keep Cursor. Your prompts, code context, and AI spend stays in your AWS account. We set it all up, move your rules and skills across, and guide your team through the adoption.

Request private offer

Overview

Try agent mode

Create proposal

Ask question

Your security team asks where the code goes when a developer opens Cursor chat. Today, the answer is vendor-hosted models on a vendor's bill, with no IAM in the path and no audit trail. This migration points Cursor at a model running in your Bedrock account. Prompts and code context stay inside the AWS network. Access runs through IAM and SSO. Spend lands on the AWS bill, tagged by team and project.

Model access, region pinning, and least-privilege IAM roles for developer credentials
VPC endpoints via PrivateLink when traffic has to stay off the public internet
Application inference profiles and cost-allocation tags for per-team and per-project spend
Content and PII filters in Bedrock Guardrails
Invocation logging in CloudWatch and S3

Highlights

Runs on your AWS account, your IAM roles, your Region
Feature-parity limits documented at kickoff, before a single developer switches
Rollback path defined and tested, so the pilot can fail safely

Details

Sold by

New Math Data

Introducing multi-product solutions

You can now purchase comprehensive solutions tailored to use cases and industries.

Learn more

Explore multi-product solutions

Pricing

Custom pricing options

Request private offer

Pricing is based on your specific requirements and eligibility. To get a custom quote for your needs, request a private offer.

How can we make this page better?

Tell us how we can improve this page, or report an issue with this product.

Legal

Content disclaimer

Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.