Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tryardent.com/llms.txt

Use this file to discover all available pages before exploring further.

Want Claude to handle this? Paste this into Claude Code or Cursor: 
Check if my AWS RDS Postgres database is ready to connect to Ardent.
My connection string: [paste here]

Verify:
1. The host is reachable and credentials work
2. Logical replication is enabled (rds.logical_replication = 1 in the parameter group)
3. The user has the rds_replication role granted
4. The security group allows inbound connections on port 5432

Tell me exactly what to fix if anything fails, then run:
ardent connector create postgresql '<connection-string>'
1

Enable logical replication

Create or modify a parameter group with rds.logical_replication = 1 and apply it to your RDS instance.
This requires a reboot of your RDS instance. Plan accordingly.
2

Grant replication permissions

Connect to your RDS instance and grant the replication role to your user:
GRANT rds_replication TO your_user;
3

Get your connection string

Your RDS connection string looks like:
postgresql://user:password@your-instance.region.rds.amazonaws.com:5432/mydb
You can find the hostname in the RDS Console > Databases > your instance > Connectivity & security.
4

Connect your database

ardent connector create postgresql 'postgresql://user:password@your-instance.region.rds.amazonaws.com:5432/mydb'
Use single quotes around the URL so the shell does not treat special characters in the password or host as syntax.Ardent will verify your setup and begin replicating your database. This may take a few minutes depending on data size.
5

Create your first branch

ardent branch create my-feature
Done. You now have an isolated copy of your RDS database — schema, data, and all. The CLI returns a connection URL you can use anywhere.