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
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 Citadel Access from AWS Accounts
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.
Before proceeding, make sure your
AWS Client VPN
and Private Bastion
are correctly configured in the environment in which you are working.Checking if the AWS Client VPN is enabled
- Go to the Citadel Run site;
- Select Environments on the menu;
- On the Environment page, select the environment you want to check;
- Select Network Access; and
- Check if the
AWS Client VPN
is enabled.
Checking if the Private Bastion is enabled
- Go to the Citadel Run site;
- Select Environments on the menu;
- On the Environment page, select the environment you want to check;
- Select Network Access; and
- Check if the
AWS Client VPN
is enabled.
Configuring the connection between RDS and Network Access
- Go to the AWS Console and log in with a role that allows you to change the AWS Security Group;
- Go to the RDS service;
- Go to Databases and select the instance RDS you need to connect;
- In
Connectivity & security
, find theVPC security groups
and click on it; - In the “Security groups” page, select Inbounds rules;
- Select “Edit inbound rules”;
- Add a new rule by selecting the Add rule button;
- 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).
- Click and “Save rules”.
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
;
You should be able to connect to your RDS throughout AWS Client VPN or Private Bastion.
On this page