> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/guides/configure-rds-to-have-public-access.md).

# Configure RDS to have public access

Usually, RDS instances do not have public access. You would also need to allow your RDS instance to accept connections from Humanic server IP, 44.241.14.240 Please refer below for how to do that on your AWS console

## Identify VPC for your RDS instance

1. Go to **AWS console > RDS > your-instance-name** 
2. Locate VPC name under ***Connectivity & Security > Networking***

## Create a new Security Group

Go to **EC2 > Security Groups** and click on **Create New** button

#### Add basic details

* Security group name: **HumanicRDSSecurityGroup**
* Description: Allow RDS access to Humanic servers 
* VPC: select the one that we located in the last step

#### Inbound Rule 

* Type: ***MYSQL/Aurora*** 
* Source: **44.241.14.240/32** 
* Description: Humanic server 

#### Outbound rule

* Type: ***All TCP*** 
* Destination: ***44.241.14.240/32*** 
* Description: Humanic server 

Add tags as required, and create the security group.

## Modify RDS instance

1. Go to you RDS instance ***AWS console > RDS > your-instance-name*** 
2. Click on ***Modify*** button towards top right
3. Go to the ***Connectivity*** section. Select the *newly created security group* from the dropdown.
4. Go to ***Connectivity > Additional Configuration*** and make sure it's publicly accessible
5. Click on ***Continue***, review your changes and apply them. 

Now your RDS instance is ready to accept connections from Humanic Servers


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://humanic.gitbook.io/humanic/guides/configure-rds-to-have-public-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.