Skip to main content

Onboarding to nOps

Welcome to the nOps onboarding guide! This guide will help you quickly set up and onboard your AWS accounts into our platform, allowing you to monitor, manage, and optimize your AWS expenses effectively.

Overview​

Our platform provides a comprehensive view of your AWS resource usage and associated costs, enabling insights into cost-saving opportunities across various AWS services. By integrating your AWS accounts, you can leverage powerful cost analysis tools and automated recommendations to enhance cost efficiency within your cloud environment.

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 we need, no more, and we need you to give us permission first.

Pre-requisites for nOps Integration​

To successfully integrate and onboard your AWS environment with the nOps platform, ensure the following requirements are met:

  1. AWS Organizations must Be enabled

nOps requires AWS Organizations to be enabled if you intend to enroll products such as cost optimization or governance features. Learn how to enable AWS Organizations

  1. Administrator Access to the Master Payer AWS Account.

The user performing the setup must have administrator access to the AWS master payer account with permissions to:

  • Deploy AWS CloudFormation stacks
  • Create IAM roles
  • Create Lambda functions
  • Create S3 buckets
  • Configure and access the AWS Cost and Usage Report (CUR)
  1. AWS StackSets Must Be Enabled (Optional but Recommended)

If you want to onboard all linked (child) accounts under your AWS Organization into the nOps platform, ensure that AWS StackSets is enabled in the master payer account. Enable AWS StackSets

  1. Sign Up for nOps

You must sign up for the nOps platform using your administrator email. You will receive a verification email and complete your account setup before proceeding with AWS integration.

Onboarding Methods​

You can onboard your AWS accounts to nOps using either Terraform or CloudFormation.

  • Terraform: Use our own Terraform module to configure and deploy resources on both AWS and nOps, in order to manage their lifecycle with HCL.
  • CloudFormation: Use AWS's native CloudFormation service to deploy the necessary resources and configurations with minimal manual intervention, we provide the necessary templates for a succesful integration.
Onboard with Terraform (Preferred method)
Onboard with Terraform (Preferred method)
  1. Automatic detection of existing nOps projects for the AWS accounts
  2. Creation and verification of new nOps projects
  3. Integration with nOps APIs for project lifecycle management using a custom nOps Terraform provider
  4. Can be integrated into your own IaC codebase and CICD
  5. Secure nOps API key management through environment variables
Onboard with Cloudformation
Onboard with Cloudformation
  1. Integration with nOps APIs using AWS Lambda
  2. Fast and automatic onboarding of all child accounts in an organization
  3. Use Cloudformation quick links to deploy the infrastructure and integration resources
  4. Code free deployments

Support​

For additional help, please contact our support team for troubleshooting steps and more information on the platform's capabilities.

Welcome onboard!