Skip to content

Commit 13ac6d6

Browse files
committed
chore(bastion-host): fix docs
1 parent f453486 commit 13ac6d6

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

lib/bastion-host/index.ts

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,6 @@ import {
88
import { Construct } from "constructs";
99

1010
/**
11-
* ## Bastion Host
12-
*
1311
* The database is located in an isolated subnet, meaning that it is not accessible from the public internet. As such, to interact with the database directly, a user must tunnel through a bastion host.
1412
*
1513
* ### Configuring
@@ -29,7 +27,7 @@ import { Construct } from "constructs";
2927
*
3028
* #### Tips & Tricks when using the Bastion Host
3129
*
32-
* ##### Connecting to RDS Instance via SSM
30+
* **Connecting to RDS Instance via SSM**
3331
*
3432
* ```sh
3533
* aws ssm start-session --target $INSTANCE_ID \
@@ -58,7 +56,7 @@ import { Construct } from "constructs";
5856
* aws ssm start-session --target $INSTANCE_ID --profile $AWS_PROFILE
5957
* ```
6058
*
61-
* ##### Setting up an SSH tunnel
59+
* **Setting up an SSH tunnel**
6260
*
6361
* In your `~/.ssh/config` file, add an entry like:
6462
*
@@ -80,7 +78,7 @@ import { Construct } from "constructs";
8078
* psql -h 127.0.0.1 -p 5433 -U {username} -d {database}
8179
* ```
8280
*
83-
* ##### Handling `REMOTE HOST IDENTIFICATION HAS CHANGED!` error
81+
* **Handling `REMOTE HOST IDENTIFICATION HAS CHANGED!` error**
8482
*
8583
* If you've redeployed a bastion host that you've previously connected to, you may see an error like:
8684
*

0 commit comments

Comments
 (0)