Setting up nOps (Manual Setup)

Adding your AWS account with the manual setup feature. The following will need to be created in AWS before you proceed in nOps.

Step 1. Create S3 billing bucket

Step 2. Create IAM Policy

Step 3. Create IAM Role

Step 4. Go to nOps to complete Manual Setup

Things you will want to save that will be used in nOps to finish the process while creating the IAM Policy and S3 billing bucket:

• ARN for IAM Policy that was created in IAM Policy

• External ID in the IAM Role

• Report name created for the Cost and Usage Report

• Report path prefix in the S3 billing bucket creation

Step 1. Setup Cost & Report Usage

Login in to your AWS Account.

Go to: Billing & Cost Management Dashboard

On the left-hand side select Cost & Usage Report

or,

Go here: https://console.aws.amazon.com/billing/home?#/reports

Click on Create Report

Create a report name

Tick the Include resource IDs checkbox. (required)

Suggestion:
Report name: nopsbilling-daily-gzip
Tick: Include resource IDs
Tick: Automatically refresh your Cost & Usage Report when charges are detected for previous months with closed bills.

Create the S3 billing bucket

Click Configure

Click Next

On this page scroll to the bottom of the default policy

Copy the ARN this will be used later for the IAM Policy creation

Check the "I have confirmed that this policy is correct"

Click Save

  • Enter the S3 bucket to deliver the report. Click on verify. (Make sure the S3 bucket has an appropriate Policy for delivery report, check section II. )

  • Enter the report path prefix (Optional) - Suggestion: nopsbilling

  • Choose Daily (required) for Time granularity

  • Choose the Report versioning (Optional) - Suggestion: Overwrite existing report

  • Choose GZIP as Compression type (Required)

You will need the Report Path Prefix name later when you are adding the AWS Account in nOps

Click Next

Then, Click Review and Complete

Step 2. Creating the IAM policy

  1. On the AWS Management Console, go to the ‘Identity and Access Management’ screen.

  2. From the left navigation panel choose ‘Policies’

  3. Click on ‘Create Policy’.

  4. Choose ‘Json Tab’

  5. Replace the existing Json script with the script given below and click on ‘Review Policy’. Make sure you replace [bucket_name] with your billing bucket name to ensure policy efficacy.

IAM policy for nOps Last Updated: 20 March 2020

JSON:

"Version":"2012-10-17",
"Statement":[
{
"Action":[
"autoscaling:DescribeAutoScalingGroups",
"ce:GetCostAndUsage",
"ce:GetReservationPurchaseRecommendation",
"ce:GetRightsizingRecommendation",
"ce:GetSavingsPlansPurchaseRecommendation",
"cloudformation:DescribeStackResources",
"cloudformation:DescribeStacks",
"cloudformation:GetTemplate",
"cloudtrail:GetTrailStatus",
"cloudtrail:DescribeTrails",
"cloudtrail:LookupEvents",
"cloudwatch:GetMetricStatistics",
"cloudwatch:ListMetrics",
"config:DescribeConfigurationRecorderStatus",
"config:DescribeConfigurationRecorders",
"config:DescribeDeliveryChannelStatus",
"config:DescribeDeliveryChannels",
"cur:DescribeReportDefinitions",
"cur:PutReportDefinition",
"dynamodb:DescribeContinuousBackups",
"dynamodb:DescribeTable",
"dynamodb:ListTables",
"ec2:DescribeAddresses",
"ec2:DescribeInstanceStatus",
"ec2:DescribeInstances",
"ec2:DescribeNatGateways",
"ec2:DescribeNetworkInterfaces",
"ec2:DescribeRouteTables",
"ec2:DescribeSecurityGroups",
"ec2:DescribeSnapshots",
"ec2:DescribeSubnets",
"ec2:DescribeVolumes",
"ec2:DescribeVpcs",
"ecs:DescribeClusters",
"ecs:ListClusters",
"eks:ListClusters",
"elasticache:DescribeCacheClusters",
"elasticache:DescribeCacheSubnetGroups",
"elasticfilesystem:DescribeFileSystems",
"elasticloadbalancing:DescribeLoadBalancers",
"es:DescribeElasticsearchDomains",
"iam:GetAccessKeyLastUsed",
"iam:GetAccountSummary",
"iam:GetLoginProfile",
"iam:GetRole",
"iam:ListAccessKeys",
"iam:ListAccountAliases",
"iam:ListAttachedGroupPolicies",
"iam:ListAttachedUserPolicies",
"iam:ListGroupsForUser",
"iam:ListMFADevices",
"iam:ListRoles",
"iam:ListUserPolicies",
"iam:ListUsers",
"lambda:GetFunction",
"lambda:ListFunctions",
"rds:DescribeDBInstances",
"rds:DescribePendingMaintenanceActions",
"rds:ListTagsForResource",
"s3:GetBucketAcl",
"s3:GetBucketLogging",
"s3:GetBucketPolicy",
"s3:GetBucketPolicyStatus",
"s3:GetBucketPublicAccessBlock",
"s3:GetBucketVersioning",
"s3:GetEncryptionConfiguration",
"s3:HeadBucket",
"s3:ListAllMyBuckets",
"support:DescribeTrustedAdvisorCheckRefreshStatuses",
"support:DescribeTrustedAdvisorCheckResult",
"support:DescribeTrustedAdvisorChecks",
"tag:getResources",
"tag:getTagKeys",
"tag:getTagValues"
],
"Effect": "Allow",
"Resource": "*"
},
{
"Sid": "nOpsCurBucketStatement",
"Action": "s3:*",
"Effect": "Allow",
"Resource": [
"arn:aws:s3:::curtestjlw060821",
"arn:aws:s3:::curtestjlw060821/*"
]
}
]
}

At the bottom of the JSON, there is a section for the S3 Bucket permissions

This is for the ARN that was requested above in the creation of the Cost and Usage Report S3 bucket. You will need to replace the JSON with the S3 ARN.

Provide a name and description of the policy.

Click on ‘Create Policy’.

Step 3. Creating IAM roles

From the left navigation panel choose ‘Roles’

Click on ‘Create Role’

Select type of trusted identity: Choose

Specify accounts that can use this role: AWS will ask for Account ID and External ID. For Account ID enter the nOps account ID (202279780353) and for External ID, enter any unique string. The External ID adds an extra level of security for you. Please do not check ‘Require MFA’. Please save the External ID, you will have to use it while adding the project in nOps.

Click on ‘Next: Permissions’

Click on "Next:Tags" Add tags to be associated with this role.

On Next Step, we will attach the policy created in the earlier task and then click on ‘Next:Review’

Provide some name and description to the role and click on ‘Create Role’

You have now completed the Manual process in AWS console.

Step 4. Adding AWS account manually in nOps:

Setting up the AWS account is a 2-step process:

  1. Add AWS account details to fetch CloudTrail data and the other is adding a billing bucket to fetch billing data, you can add both at the same time (recommended).

Note: If you don’t add a billing bucket your billing stats pages in nOps will not show any data.

Select: Yes, I have access

Select the Manual Setup method on the Setup nOps page.

Add AWS Account Name.

Enter:

S3 bucket

nameReport

namePrefix path

For role-based access, we need ARN of the IAM role.

For External ID, use the same one you used when created the role earlier.

Add billing bucket name. Make sure the billing bucket name is the same as the S3 bucket you created for billing.

When adding the AWS account to nOps make sure you save the settings after filling all the fields as in the screenshot below.

Note: It’ll take about a day for billing data to populate and a couple of hours for CloudTrail data to populate. If you have any questions, please contact us at help@nops.io

Viewing Added AWS Accounts/ Projects:

You can view the list of all added projects in your project settings. To view go to UserName Dropdown (Top right) → Settings → AWS Accounts. where it shows the name of the billing bucket [If added] and also the “Last fetch” time of the billing bucket.

Editing an Existing AWS Account/Project:

Go to UserName Dropdown (Top right) → Settings → AWS Accounts

Click on any project you want to edit and it will open the edit “Account Details” page.

You can do changes as per your requirements and make sure to click the Update Account button in order to save changes.

Note: If you try to edit the billing bucket of an existing project it can cause changes in cost pages data or undesired results.

Related Articles:

How Child Accounts Work in nOps

Did this answer your question?