Skip to content

Commit 00164b0

Browse files
committed
[#327] Update wiki content
1 parent f8cdd04 commit 00164b0

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

.github/wiki/Connect-to-Bastion-via-SSM.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,20 @@ Traditional SSH key pairs have several drawbacks:
1111
- **Rigid Access Control:** Revoking access requires deleting the entire key pair, affecting all users.
1212
- **Management Overhead:** AWS doesn't store key pairs after creation - if lost, recovery is impossible.
1313

14+
## Benefits of SSM
15+
16+
- **Centralized Access Control:** Manage access via IAM policies - grant/revoke access without touching the instance.
17+
- **Quick Response:** Immediately terminate all sessions in case of security incidents.
18+
- **No Public IP Required:** Connect to instances in private subnets via VPC Endpoints.
19+
- **Full Auditing:** Log every session and command to CloudWatch Logs or S3 for compliance.
20+
21+
## Considerations
22+
23+
- **Latency:** Session Manager tunnels traffic through AWS APIs, which may introduce slight lag compared to direct SSH connections.
24+
- **Logging Costs:** While SSM is free, storing session logs in CloudWatch or S3 incurs costs. Consider configuring lifecycle rules or retention periods to manage costs.
25+
26+
For more information, refer to the [AWS Session Manager documentation](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html).
27+
1428
## Prerequisites
1529

1630
Before connecting via SSM, ensure the following requirements are met:
@@ -69,17 +83,3 @@ aws ssm start-session \
6983
--document-name AWS-StartPortForwardingSessionToRemoteHost \
7084
--parameters '{"host":["your-rds-endpoint"],"portNumber":["5432"],"localPortNumber":["5432"]}'
7185
```
72-
73-
## Benefits of SSM
74-
75-
- **Centralized Access Control:** Manage access via IAM policies - grant/revoke access without touching the instance.
76-
- **Quick Response:** Immediately terminate all sessions in case of security incidents.
77-
- **No Public IP Required:** Connect to instances in private subnets via VPC Endpoints.
78-
- **Full Auditing:** Log every session and command to CloudWatch Logs or S3 for compliance.
79-
80-
## Considerations
81-
82-
- **Latency:** Session Manager tunnels traffic through AWS APIs, which may introduce slight lag compared to direct SSH connections.
83-
- **Logging Costs:** While SSM is free, storing session logs in CloudWatch or S3 incurs costs. Consider configuring lifecycle rules or retention periods to manage costs.
84-
85-
For more information, refer to the [AWS Session Manager documentation](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html).

0 commit comments

Comments
 (0)