Hot AI News

Claude Code and Cursor can now open an AWS sign-up and get credentials back

Developers without an AWS account can now sign up from inside Claude Code, Codex or Cursor and get short-lived credentials returned to the agent, which can then deploy.

Claude Code and Cursor can now open an AWS sign-up and get credentials back
Image: Amazon

Amazon Web Services announced on Nov. 17 that agentic coding harnesses can now open the new AWS sign-up flow for developers who have no account yet. The browser opens automatically, and short-lived credentials go back to the agent.

Sign-up moves inside the coding agent

According to AWS, developers working in tools such as Claude Code, Codex and Cursor previously had to leave the session, go to aws.amazon.com, create an account and configure credentials by hand before deploying anything. That step is now handled from the harness. The developer completes sign-up in the browser, which the agent opens, and the credentials return to the harness.

LoanPro AI servicing architecture on Amazon Bedrock and Amazon Bedrock AgentCore (LoanPro engineering, October 2026): API Gateway → Handler Lambda → SQS → Agent Interceptor → AgentCore runtime → Gateway → Parameter Store catalog → Loan Summary Tool → SSO/JWK → NLB/EC2 with RBAC
Image: Amazon

AWS says accounts created this way start on the new AWS experience. The first project arrives with a home Region, an IAM role manager and short-term credentials that refresh automatically, so the agent can begin deploying immediately. AWS describes the goal as going from an idea to a running application without interruption.

Four responsible AI challenges for agentic platforms: unpredictable runtime behavior, data boundaries, regulatory velocity, and team collaboration
Image: Amazon

To try it, developers install the AWS plugin or configure the AWS Agent Toolkit in their harness. AWS points to the AWS Agent Toolkit documentation and the AWS Account documentation for details.

Advertisements

What the announcement leaves out

The announcement page does not mention pricing, supported Regions or which harnesses beyond the three named are covered. It also does not say how the human sign-up step is verified, or what permissions the initial IAM role manager grants. Everything about the speed and smoothness of the flow is AWS’s own description; the page gives no measurements.

The human still has to finish sign-up in the browser. The agent opens the page and receives the credentials, but the account itself is created by a person, which is a sensible boundary for something that carries billing responsibility.

Closing the last manual gap in agent-driven deploys

The change targets a gap that AWS’s own agent tooling already exposed. When AWS launched its Agent Plugins in March, InfoQ reported that the first plugin, deploy-on-aws, supported Claude Code and Cursor and could analyze a codebase, recommend services, show projected monthly costs, generate CDK or CloudFormation code and deploy after confirmation. AWS claimed that took under 10 minutes in its example, against hours of manual work. But InfoQ also listed a requirement: the AWS CLI had to be configured with credentials already. New developers without an account could not get that far, and the new sign-up flow addresses exactly that.

Support has also widened since then. Search results for AWS’s Agent Toolkit page and documentation show plugins for Claude Code, Codex and Cursor, with other MCP-compatible agents able to connect to the AWS MCP Server manually. Sources differ on exact support details, so readers should check the toolkit documentation for their harness.

The credential design matters too. Short-lived credentials that refresh automatically avoid leaving long-lived access keys in an agent’s environment. A same-day AWS release, the IAM Access Troubleshooter, adds an identifier to access-denied messages so developers can retrieve which policies were evaluated. That is likely to help when an agent hits a permissions wall on a new account, though AWS does not link the two announcements.

The broader pattern is cloud providers competing to be the default target of coding agents. Our earlier coverage of how websites verify that an AI agent is who it claims to be shows the other side of the same shift: as agents act on behalf of people, identity and authorization become the hard part.

Sign Up for the Daily AI Pulse

One email a day. All the stories that matter.

Alex CarterAI News & Big Tech Correspondent

Alex Carter writes for Aiholics, keeping readers updated on the fast-paced world of AI and Big Tech.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may also like