At Kubox, we strive to make creating and managing a Kubox cluster as simple as possible. However, Kubox doesn’t operate in isolation, and it’s typically part of a larger system requiring setup and configuration on both in the cloud and on your local development machine.

​
Set Up an AWS account and Create a User

These steps walks you through the essential steps to get started, even if you’re new to AWS.
1

Sign up for an AWS account

If you’re a new AWS customer, you can get started for free. For more information, see AWS Free Usage Tier
  1. To sign up for an AWS account go to and follow the sign up instructions.
  2. When you sign up for an AWS account, a Root User is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform tasks that require root user access.
After you sign up for an AWS account, secure your AWS account root user, enable AWS IAM Identity Center, and create an administrative user so that you don’t use the root user for everyday tasks.
  1. Secure your AWS account root user Sign in to the AWS Management Console as the account owner by choosing Root User and entering your AWS account email address. On the next page, enter your password. For help signing in by using root user, see Signing in as the root user in the AWS Sign-In User Guide.
  2. Turn on multi-factor authentication (MFA) for your root user. For instructions, see Enable a virtual MFA device for your AWS account root user (console) in the IAM User Guide.
2

Create a user with administrative access

To create the first user with administrative access follow Configure user access with the default IAM Identity Center directory.
3

Configuring IAM Identity Center authentication with the AWS CLI

To download, configure and setup authentication with AWS CLI follow AWS IAM Identity Center concepts for the AWS CLI.
When logging with the aws configure sso sign in with you non-root user.
4

Verify AWS CLI is configured correctly 

aws sts get-caller-identity