Skip to main content

Classic Onboarding

info

This page documents Classic Onboarding for AWS, reachable by selecting Switch to classic onboarding in the first step of the onboarding flow. Classic onboarding is still available for both AWS organizations and single AWS accounts. For the current flow, see Instructions.

Overview​

This article walks through connecting AWS to Upwind using the classic onboarding flow in the Upwind Management Console .

Select the tab for the entity you want to connect:

  • Connect AWS account: Connect a single AWS account. This flow does not require an AWS root ID or an AWS Organization ID.
  • Connect AWS organization: Connect an AWS Organization and its member accounts. You designate an orchestrator account and create the required IAM roles from the management account.

Within each entity, select the tab for your deployment method, CloudFormation or Terraform.

Use this flow to connect one AWS account to Upwind. You do not need an AWS root account for this flow.

warning

Single account onboarding does not support the SaaS Cloud Scanner deployment. For AWS, SaaS Cloud Scanners are supported only through organizational onboarding. Cloud Scanners for a single account are installed in your own AWS account, as described in Install a Cloud Scanner for a single account.

Generate credentials for Upwind​

In Step 1 : Generate Credentials for Upwind, choose one of the following:

  • In Use existing Cloud Account credentials, select credentials you already created.
  • Click Generate next to Or, generate new client credentials to create new credentials.

If you stored the credentials in AWS Secrets Manager, enter the ARN in the Upwind Client Credentials ARN field instead.

Deploy and configure permissions​

In Step 2 : Deploy and Configure Permissions, click Click here to log in to the AWS account you want to connect. Then click Run the AWS CloudFormation template to deploy the template in the AWS console.

Test connectivity and complete setup​

After the CloudFormation stack finishes deploying, return to the Upwind Management Console and click Test & save to validate the connection and save your configuration.

Install a Cloud Scanner for a single account​

After you connect the AWS account, you deploy a Cloud Scanner into that account. The Cloud Scanner is deployed in the AWS account and region where you run the template.

Open the Cloud Scanner setup from the Upwind Management Console, then complete the steps for your deployment method.

Select a region​

In Step 2 : Select a region, select the region where you want to deploy the Cloud Scanner.

Name the Cloud Scanner​

In Step 3 : Cloud Scanner name, enter a name for the Cloud Scanner and click Save to create the Auto Scaling group configurations. By default, all scanning capabilities are enabled, including vulnerabilities, secrets, and malware detections. To change these settings, open the Cloud Scanner's side panel and use edit mode.

Select Cloud Scanner credentials​

In Step 4 : Select Cloud Scanner Credentials, choose one of the following:

  • In Use existing Cloud Scanner credentials, select credentials you already created. If you select existing credentials, you must provide the ClientSecret parameter when you launch the CloudFormation stack.
  • Click Generate next to Or, generate new client credentials to create new credentials.

Log in to your AWS account​

In Step 5 : Log in to your desired AWS Account, log in to the AWS account and region where you want to deploy the Cloud Scanner.

Run the CloudFormation template​

In Step 6 : Run the following AWS CloudFormation template, click the template link to open the template in the AWS console. Copy the client secret and paste it into the template, then run the stack.

Test connectivity and complete setup​

After the CloudFormation stack finishes deploying, return to the Upwind Management Console and click Test & save to validate the connection and save your configuration.