Setting up nOps (Automated Setup)
This is the first step to set up the AWS account in nOps. The simplest way is to use the Wizard/Automatic Setup. We create the IAM Policy and CloudFormation for the account.
Pro Tip: If you link only the child account, nOps won’t be able to pull the cost details. Though you will be able to see other details except for the cost details.
The account that you use to log in must have the below-mentioned permissions in order to set up the account properly.
The following are the minimum set of permissions the AWS user needs to successfully set up the AWS project
Access to the master payer account if you are using AWS Organizations.
Permission to create and run an AWS CloudFormation stack.
Permission to create AWS Identity and Access Management (IAM) roles in your account.
Friendly account name.
The name of an Amazon S3 bucket where your AWS Cost and Usage Reports (CURs) will be written. (We will create one if one does not exist.)
CURs enabled in the account.
How far back is data pulled from AWS accounts on initial ingestion:
Cost data: 6 months back + current month.
Rules: Current date
CloudTrail Events: 14 days back
IAM and CloudFormation:
The IAM and CloudFormation are read and write permissions only
Lambda automates all the configuration for role and billing bucket for nOps setup.
Code for this lambda is fully available for review.
In case you are not comfortable with the automated setup, you can use manual steps for setup.
View the latest IAM Policy here
Steps to set up a project in nOps:
Check the steps below:
Upon signing in for the first time, a pop-up will appear that instructs on how to add your AWS account.
Selecting Yes, I have access will take you to the Link AWS Account
Selecting No, Invite Member will take you to the Invite User page. Select this option if another person has access to an AWS account.
The nOps Wizard Setup will automatically create the AWS account IAM Policy and CloudFormation.
The Manual Setup will be the responsibility of the user to create the IAM Policy and CloudFormations. View Help Article for Manual Setup
After selecting nOps wizard Setup the Auto AWS Account Setup appears.
AWS Account Name will be a unique name for the nOps setup. i.e, nops_businessname
S3 Bucket Name will be a unique name for the S3 bucket that is created for the CloudFormation. Use a name in all lowercase and numbers to distinguish this in your Cost and Usage Report.
Click Setup Account
If the pop-up was closed follow these steps:
Go to “Settings → AWS Accounts” from top right user avatar drop-down. In “AWS Accounts” page, click on “Add new AWS Account”.
On the AWS console, the user will be asked to log in using user credentials that have rights defined as per the prerequisite section.
Once logged in, the user will be redirected to the “Create Stack” screen. All the fields on this page will be pre-populated.
Mark the checkbox for “I acknowledge that AWS CloudFormation might create IAM resources” and click on “Create” button.
If you have all required permissions, as mentioned at the top in the prerequisites section, then the setup will start creating the stack with the status “CREATE_IN_PROGRESS”. Once the stack is created then “Status” will be “CREATE_COMPLETE”. You can click the browser refresh button to check progress. Normally it takes 1 to 2 minutes to complete the process.
If you don’t have proper permissions then you will see errors like in the screenshot below and the stack will not be created. You can assign the necessary permissions and rerun the setup.
Log in to https://www.nops.io after the nOps integration (stack) create process completes.
Note: It can take up to 24 hours before you start seeing the different nOps dashboards and compliances views populated with data from your workload. If you have any questions, please contact us at firstname.lastname@example.org, or by phone at +1 866-673-9330.
Do you have a pop-up blocker on your browser? A pop-up blocker on your browser will stop nOps from redirecting you to an AWS account to create a stack.
There may have been a disconnect when creating the S3 stack causing the stack to have an error of Rollback_Error, please re-try the automatic setup, then delete the first one.
Is it pulling in incorrect data? Make sure that you are logging into the correct account. When you have multiple access to AWS accounts, it can import the wrong data.
If you belong to an Organization ( multiple accounts linked to a Master Account) ensure you are logged into the Master account before running the wizard (so the billing data is populated)
The Master account must be added first before you can credential the child account.