Getting started

Prerequisites

Creating an Organization

Creating Audit and Log Archive AWS Accounts

Management

Creating an AWS Account

Initial Setup

Billing Alerts

Configuring AWS SSO (IAM Identity Center)

Generating As-Built Documentation

Alliance Mode

Environments

Environments

Configuring AWS Client VPN

Configuring Private Bastion

Deleting an Environment

Domains

Service Roles

Compliance

Compliance standards

Compliance status

Configuring a standard

Reference

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 account

Troubleshooting

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 Error

Fixing the problem when Network Access is connecting to RDS

This troubleshooting will explain how to fix the problem when the Network Access (AWS Client VPN or Private Bastion) connection is not connecting to a RDS.

Checking if the AWS Client VPN is enabled

1. Go to https://app.nx1.io;
2. Select Environments on the menu;
3. On the Environment page, select the environment you want to check;
4. Select Network Access; and
5. Check if the AWS Client VPN is enabled.

Checking if the Private Bastion is enabled

1. Go to https://app.nx1.io;
2. Select Environments on the menu;
3. On the Environment page, select the environment you want to check;
4. Select Network Access; and
5. Check if the AWS Client VPN is enabled.

Configuring the connection between RDS and Network Access

1. Go to the AWS Console and log in with a role that allows you to change the AWS Security Group;
2. Go to the RDS service;
3. Go to Databases and select the instance RDS you need to connect;
4. In Connectivity & security, find the VPC security groups and click on it;
5. In the “Security groups” page, select Inbounds rules;
6. Select “Edit inbound rules”;
7. Add a new rule by selecting the Add rule button;
8. Leave the custom field as it is and add the service of the Network Access service ID you want to use to connect your RDS (AWS Client VPN or Private Bastion).

You can find it on the Security Group page. Look for the the Security Group prefix name: citadel-workload-network-access-private-bastion-SecurityGroup or citadel-workload-network-access-client-vpn-SecurityGroup;

9. Click and “Save rules”.

You should be able to connect to your RDS throughout AWS Client VPN or Private Bastion.