Getting started
Prerequisites
Creating an Organization
Creating Audit and Log Archive AWS AccountsManagement
Creating an AWS Account
Initial Setup
Billing Alerts
Configuring AWS SSO (IAM Identity Center)
Generating As-Built Documentation
Alliance ModeEnvironments
Environments
Configuring AWS Client VPN
Configuring Private Bastion
Deleting an Environment
Domains
Service RolesCompliance
Compliance standards
Compliance status
Configuring a standardReference
Choosing Email Addresses for your AWS Accounts
Checklist end-of-deployment
Configuring SSO for Microsoft Azure
Configuring SSO for G-Suite
Deploying Applications
Notification History
Removing NX1 Access from AWS Accounts
Reduce permission access for NX1
What’s deployed in my accountTroubleshooting
Troubleshooting
Common Issues
Finding the Root Cause of a Failed Job
Creating new environment failed
Fixing Network Access is not connecting to RDS
SSO G-Suite - Deploy Lambda ErrorUnderstanding the Compliance Status
On the Environment Status page, you can see all the rules and guidelines that the system is following. This page will show you if there are any potential issues that you should be aware of.
The page has a visual representation of all the standards being used, which makes it easy to see what the system is complying with. Each standard has a card that shows a score check, indicating how many checks were done and how many passed. If there are any failed checks, the user can click on `View issues` to see more details about the issues.
For each failed check, there will be a level of risk assigned, Low, Medium, or High, along with a description of the check. The user can click on `View Details` to get more information about any failed checks.
The information detailed are:
- Resource Affected
- Description
- Remediation
← Previous
Compliance status