help.nops.io Open in urlscan Pro
2606:50c0:8001::153  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Toggle navigation   Documentation Site
   
   
   
 * GitHub
   
   
 * nOps
   * Website
   * Blogs
   * Login
 * Feedback
   
 * 

 * 
 * Home
   * Connecting to nOps
 * Getting Started
   * Onboarding
     * Onboarding with Automatic Setup
     * Onboarding with Manual Setup
     * Onboarding Linked Accounts
     * Onboarding Accounts with Terraform
     * Onboarding Accounts with CloudFormation
     * Generate an AWS Cost and Usage Report
   * IAM
     * nOps platform IAM permissions
     * nSwitch IAM permissions
     * YAML file for ShareSave Setup
   * SSO
     * SSO Integration
     * SSO integration with Okta
     * SSO integration with OneLogin
     * SSO integration with AWS
 * ShareSave
   * Savings on Auto-Pilot
   * Configure Risk-Free Commitment Management
 * Agents and Integrations
   * Agents
     * Cloudwatch Agent
     * Kubernetes Agent
     * Lambda Forwarder Agent
   * Integrations
     * Eventbridge Integration
     * Jira Integration
     * PagerDuty Integration
     * Slack Integration
     * Webhook Integration
 * User Guides
   * Cost
     * Commitment Management - Working with Reserved Instances
     * Cost Reporting for Cloud Resources
     * Resource Rightsizing
     * Spot Advisor
     * Tag Explorer
   * Dashboards
     * The nOps Dashboard
     * nOps DSL
   * Data Explorer
     * The nOps Data Explorer
   * Reports
     * Weekly Reports
   * Rules
     * Custom Rules
     * View Underutilized EBS Volumes
     * View Underutlized Network Resources
     * View IAM Violations
   * Security
     * View Security Violations
     * Check Multi-Factor Authentication
   * Settings
     * Adding Users to nOps
     * Change Your Password
     * Customize Settings
     * Data Purge
     * Disable Notifications
     * Notifications Center
 * Workload
   * Workloads
     * Add Resources to Workloads
     * Workload API
     * Attach Documents to Workloads
     * Create Workloads
     * Evaluate Risk for a Workload
     * View and Manage Workloads
   * Well Architected Framework
     * Export a WAFR Report
     * WAFR Report
     * WAFR Review
   * MAP
     * Automated Taging for AWS MAP
     * Backfill a CUR for AWS MAP
   * FTR
     * The AWS Foundational Technical Review
     * The FTR Report
     * FTR Question Descriptions
 * Solutions
   * Cost Optimization Recommendations
   * NAT Gateway Visibility
   * Evaluating the Cost Impact of a Changeset
   * Using EventBridge with nSwitch to Reduce Costs
 * Developer
   * Getting Started with the nOps API
   * nSwitch Slackbot "How To" Guide
   * nOps Application API Swagger File
   * Notification APIs
   * Recommendations API Swagger
   


ONBOARDING MULTIPLE AWS LINKED ACCOUNTS WITH CLOUDFORMATION

 * Onboarding Multiple AWS Linked Accounts to nOps with CloudFormation
 * Prerequisites
 * Adding Multiple AWS Accounts (CloudFormation)
   * Generate your API key
 * Enable Stacksets
 * Create a Stackset for the Linked Accounts
   * Step 1 (Choose a template)
   * Step 2 (Specify Stackset details)
   * Step 3 (Configure Stackset options)
   * Step 4 (Set deployment options)
   * Step 5 (Review), review and create the stackset.
 * Fetching

Edit me


ONBOARDING MULTIPLE AWS LINKED ACCOUNTS TO NOPS WITH CLOUDFORMATION

nOps requires safe, secure, and AWS-approved access to your AWS accounts in
order to give you the analysis, dashboards, and reports that you need. We only
see what you want us to see in order to provide our services, no more, and we
need you to give us permission first.

In order to credential and register multiple accounts, we leverage AWS
Organizations, CloudFormation, Stack, StackSets, and Lambda.

For multi-account setup, nOps recommends the use of CloudFormation (this setup)
instead of Terraform (intended for advanced users with specific requirements).

Watch the video on how to configure linked accounts with CloudFormation:

Open in a new window


PREREQUISITES

 * You must have Admin role permissions in AWS before you can add multiple AWS
   accounts to nOps using CloudFormation.

 * Access to the nOps public Github repository nOps Cloud Account Registration.

 * You have configured your Payer account.

 * Enable Stackset in AWS Organizations and AWS CloudFormation within AWS.

Once you’ve taken care of the prerequisites, the next steps are simple and
straightforward.


ADDING MULTIPLE AWS ACCOUNTS (CLOUDFORMATION)

Pull the nOps Member Account Registration YAML file down as a local YAML file.
You will need this CloudFormation YAML file as a template for your StackSet. You
will also need the nOps API key.


GENERATE YOUR API KEY

To generate your API key for use with CloudFormation Stacksets, log into the
nOps platform.

 1. Click on your email address to the top right of the platform
 2. Navigate to Organization Settings > API Key
 3. Click “Let’s Generate Your API Key”
 4. Enter a key name and a description.
 5. When you click Save a pop-up box will display with a 1 time key. Copy the
    key to a notepad/text editor.


ENABLE STACKSETS

To enable CloudFormation StackSets in AWS Organizations, go to AWS Organizations
> Services. If you see Access disabled for CloudFormation StackSets, you will
need to enable it.

Once enabled, you should see Access enabled:



Also ensure Trusted Access is enabled for CloudFormation > StackSets.


CREATE A STACKSET FOR THE LINKED ACCOUNTS

CloudFormation Stacksets can be multi-account and multi-regional. To create and
deploy a stackset for the linked accounts, make sure that you are logged into
your Management Account.

From within AWS Console > CloudFormation > Stacksets page, click Create
Stackset.

The creation of a Stackset is divided into 5 steps:


STEP 1 (CHOOSE A TEMPLATE)

 1. In the Specify template section, choose Upload a template file option.

 2. Click Choose file.

 3. AWS will open a navigation window for you to navigate and select the YAML
    template in your local machine. In your local copy of the repository
    navigate to
    nops-cloud-account-registration/nops-aws-account-register/cloudformation-org-member-accounts-register/
    and select the member_consolidated_aws_acc_nops_register.yaml file.
    
    

 4. Click Next.


STEP 2 (SPECIFY STACKSET DETAILS)



 1. Provide a StackSet name.

 2. (Optional) Add a Description for the StackSet.

 3. Provide the nOpsAPIKey you copied earlier.

 4. Click Next.


STEP 3 (CONFIGURE STACKSET OPTIONS)



 1. (Optional) enter any tags for the StackSet.

 2. In the Execution configuration section, leave the Inactive option selected.

 3. Click Next.


STEP 4 (SET DEPLOYMENT OPTIONS)

 1. In the Add stacks to stack set section, select the Deploy new stacks option.

 2. In the Deploy targets section, select the Deploy stacks in organizational
    units option.

 3. Provide the organizational unit ID.

 4. In the Specify regions section, select your desired region.

 5. In the Deployment options section, select the Parallel option (optional).

 6. Click Next


STEP 5 (REVIEW), REVIEW AND CREATE THE STACKSET.


FETCHING

It might take several hours for nOps to fetch the data from your AWS accounts.

After the data is fetched, the setup process is now complete.

Note: It can take up to 24 hours before you start seeing the different nOps
dashboards and compliance views populated with data from your workloads.

If you have any questions, please contact us at help@nops.io.

On initial ingestion, nOps will pull the data from AWS accounts based on the
following durations:

 * Cost data: 6 months look back + current month.

 * Rules: Current date.

 * CloudTrail Events: 14 day look back.

Back to top
Tags: getting_started onboarding

--------------------------------------------------------------------------------

©2023 nOps. All rights reserved.
Site last generated: Jun 26, 2023