Account Management

This article covers how to manage your Cyber Ranges profile — including your display name, password, and MFA settings — and how to connect, configure, and disconnect an AWS account for Community Edition users and connected-platform users.

Your Cyber Ranges profile

To manage your user profile, select the Settings icon in the bottom left of the dashboard. From there, you can edit your Cyber Ranges display name, enable or disable MFA, and change your password.

Password management

To change your current password, select Change, enter your current password, and choose a new one for the application.

If you've forgotten your password, select "Forgot your password?" from the login page and enter the email address registered with Cyber Ranges. We'll send you a temporary password, which you'll be required to change upon logging in.

Note: Password Requirements
Make sure to select a strong password. At a minimum, your password must be eight characters long and include the following:

Uppercase letter
Lowercase letter
Number
Special character

Multifactor authentication

Cyber Ranges supports MFA. To enable it, select Enable from the Account Settings page and scan the QR code in your preferred authenticator application (such as Google Authenticator, Duo, or Authy). Then enter the TOTP to confirm your MFA setup.

You may also disable MFA at any time.

Deleting your account

To delete your account, select "Delete Account" and confirm your intent to delete your Cyber Ranges account.

Warning: Community Account Deletion
Upon account deletion, Cyber Ranges will attempt to clean up all the resources deployed into your connected AWS account. This includes all deployed range environments and templates.

AWS account

Community Edition users and users connected to the Immersive platform can connect their own AWS account to take advantage of the range deployment and management capabilities of Cyber Ranges. You only pay AWS directly for the range infrastructure you actually use.

We recommend creating a dedicated AWS account for use with the Cyber Ranges platform. This lets you:

Monitor your billing easily and accurately
Segment your Cyber Ranges infrastructure from personal or company infrastructure
Clean up range resources more easily if you choose to disconnect your account from the Cyber Ranges platform

To sign up for a free AWS account, check out the AWS Free Tier.

Note: EC2 Limits
For newly created accounts, the Running Instances limit may be quite small (five vCPUs). Most range templates will require more than this, so we recommend requesting a limit increase as soon as you set up your AWS account.

You can request a service limit increase here. We deploy ranges into the US-East-1 region currently, so make sure to request the increase in that region.

Request an increase for "Running On-Demand Standard (A, C, D, H, I, M, R, T, Z) instances". We recommend at least 120 vCPUs to allow running multiple range environments simultaneously.

Other limits you might run into include:

VPC Limits (one per range)
Elastic IP Address (one per range)
Public AMIs (one per system when sharing a template)

Connecting your AWS account to Cyber Ranges

If you already have an AWS account, you can be up and running in just a couple of minutes. Follow the instructions in the AWS Connection Wizard to connect your accounts in a few clicks. Behind the scenes, Cyber Ranges will:

Deploy a CloudFormation Stack
Create an IAM Role with the required permissions
Automatically detect when your accounts are connected
Assume this IAM Role to deploy and manage ranges within your own account

Cyber Ranges IAM Permission Requirements

The Cyber Ranges platform needs certain permissions within your AWS account to deploy and manage your range systems. We do not need full administrative access. The IAM role we create has the minimal permissions required for the platform to function.

We require most permissions to interact with EC2, including permissions to create, modify, and delete resources like EC2 instances, EBS volumes, and snapshots. For a full list of the specific permissions required, review the CloudFormation stack created when connecting your AWS and Cyber Ranges accounts.

Disconnecting your AWS account

To disconnect your account, go to the Account Settings page and select Disconnect.

Warning: Stranded Cyber Ranges Resources
Be careful when disconnecting your AWS account from Cyber Ranges. You should delete your deployed ranges first.

Upon disconnecting your account, Cyber Ranges will lose the ability to manage resources on your behalf. If you disconnect before deleting your existing ranges, there may be resources left in your AWS account — including running EC2 instances — that could significantly affect your monthly bill.

If you choose to leave ranges deployed but disconnect your account, you can identify Cyber Ranges-managed resources for future cleanup by the CyberRanges tag.

Design test internal Admin