13 docs tagged with "onboarding"

How to use AWS SSO for nOps

This topic is for Clients who log in using an Administrator Role. It assumes that you have nOps configured on your Microsoft Entra ID (This was formerly known as Azure AD).

In order to get started with nOps, the first step is to subscribe to nOps on the AWS marketplace. Next, you'll create an nOps login and set up your AWS payer account. We've made the setup process as easy as possible for you while complying with AWS security best practices.

Prerequisites

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.

Essentials resource scheduler IAM permissions

nOps requires safe, secure, and AWS-approved cross account 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.

IAM Policy Permissions for the nOps Platform ##

How to use Okta SSO for nOps

Steps to configure Onelogin SSO integration with nOps :

As cloud security becomes more of a concern, the adoption of Control Tower and Service Control Policies (SCP) has increased substantially. Because of their nature, SCPs can inhibit nOps from viewing necessary resource information to make cost optimization recommendations. It can also impact visibility capabilities, such as looking at resource tags.

How to Integrate with SSO for nOps access

Use nOps custom Terraform provider and module to easily integrate your AWS accounts. Manage project lifecycles and use your CICD pipelines