AWS Deployment using terraform | all nodes have SSH open to the world
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
**Is your enhancement request related to a problem? Please describe.**
A clear and concise description of what the enhancement is.
I am referring to https://github.com/apache/pulsar/blob/master/deployment/terraform-ansible/aws/security.tf. The default security group (SG) opens SSH to the world and this SG gets applied to all the nodes. This is not a right practice. I would recommend opening only the proxy for SSH from anywhere. You can allow SSH from the default SG elsewhere.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
I am referring to https://github.com/apache/pulsar/blob/master/deployment/terraform-ansible/aws/security.tf. Create 3 SGs. 1) ELB 2) Proxy and 3) default. Open only Proxy for SSH. Apply Proxy and default to proxy server. Apply default to all other nodes. Also in the instructions ask to use private IP everywhere. `TF_STATE=./ TF_KEY_NAME=private_ip ansible-playbook --user='ec2-user' --inventory=~/environment/terraform-inventory ../deploy-pulsar.yaml
` , this is useful as now servers are connecting to each other using private IP.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
Start with deployment/terraform-ansible/aws/security.tf and review how its security groups are assigned to nodes. Use the documented TF_STATE, TF_KEY_NAME=private_ip, and ansible-playbook command to inspect the deployment flow. Done means SSH is not open to the world on every node, proxy and default groups are assigned as requested, and the instructions use private IPs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, aws, terraform
- Domain
- cloud, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100