Skip to content

Connect your AWS account to Ownkube in two minutes

Connecting AWS to Ownkube is zero-input: no account ID to paste, no region to pick. The whole flow, plus where to find your AWS account ID.

Abhishek Jaiswal

3 min Updated

On this page 3 sections

Your AWS account ID is a 12 digit number, something like 1234-5678-9012. To find it: sign in to the AWS console, click your name in the top right corner, and read the number at the top of the menu that opens. You don’t need the command line.

Find it in the console

  1. Go to console.aws.amazon.com and sign in.
  2. Click your name in the top right corner. A menu drops down.
  3. The Account ID sits at the top of that menu, with a copy button next to it.

Illustration of the AWS console top navigation bar with the account menu open, showing the 12 digit account ID

The account ID is always 12 digits. AWS shows it with dashes (1234-5678-9012) or without (123456789012), and either way it is the same number. It is not a secret: AWS does not treat account IDs as sensitive, so you can paste yours into a setup form without rotating anything. It does not change, and it is the same for everyone in the account.

If you do not see it (you might be signed in as an IAM user), open the search bar, type IAM, and the account ID shows on the IAM dashboard too. If you have more than one account, the number always reflects the one you are currently signed in to, so check the account name next to it.

Connecting to Ownkube (you do not type it in)

Ownkube never asks you to paste your account ID. You start the connection from Ownkube, approve a setup page in your own AWS account, and Ownkube detects the account automatically. Knowing your account ID is still handy for confirming you are connecting the right one, but you will not type it anywhere.

The whole flow takes about two minutes and never touches a terminal.

  1. Start the connection in Ownkube. You don’t fill in an account ID or pick a region. Ownkube opens a CloudFormation setup page in your own AWS account in a new tab.
  2. Approve the grant in AWS. That page creates a scoped role that lets Ownkube manage resources inside your account, on your behalf. You do two things on it.

First, tick the box that lets the template create the access role:

AWS CloudFormation acknowledgment box, with an arrow pointing to the checkbox that permits creating the IAM access role

Then click Create stack. That is the last click on your side:

AWS CloudFormation action bar, with an arrow pointing to the orange Create stack button

  1. Leave the rest to Ownkube. It detects the account the moment the stack finishes and verifies the connection, then you are ready to create your first cluster. You can revoke access anytime by deleting the stack from AWS.

Ownkube runs in your AWS account. You pay AWS directly for the infrastructure, and your data and infrastructure stay under your control.

Ownkube is built for deploying without standing up a platform team first. Start free on a single-instance cluster and scale up when you are ready. See Ownkube pricing for the per-minute wallet model, from $5 a month. Deploy my first app.

Abhishek Jaiswal · Founder and Engineer

Abhishek Jaiswal is the founder and engineer behind Ownkube, a cloud for personal software. He builds the platform and writes here about cloud cost, migrations, and running production infrastructure in your own AWS account without a DevOps team.

Share

More posts

All posts

Ship my first app in the next five minutes.

Push a repo and get a live URL, with no cloud account or config.

Top up from $5, billed per minute with no subscription.