Reputation
245
Top tag
Next privilege 250 Rep.
View close votes
Badges
3 14
Impact
~28k people reached

7h
awarded  Popular Question
Sep
1
awarded  Caucus
Aug
1
awarded  Tumbleweed
Jul
28
awarded  Notable Question
Jul
25
asked AWS + KeepAliveD: Not able to Ping or Telnet Virtual IP from remote hosts
Mar
30
awarded  Popular Question
Jan
27
awarded  Yearling
Dec
10
awarded  Self-Learner
Dec
8
awarded  Notable Question
Oct
21
awarded  Popular Question
Sep
24
awarded  Autobiographer
Sep
10
accepted AWS VPC + IPtables + NAT: Port Forwarding is not working
Aug
26
awarded  Popular Question
May
28
comment Software VPN connection to Amazon AWS VPC private instance
@MohyedeenN, I am going through similar thoughts. I have a question. Apart from what you have suggested above, Do I have to configure VPC security groups rules to allow traffic from VPN Server (in pub subnet) to other resources (In Private subnet). And, also security group rules in Private subnet to accept traffic from VPN server in Pub subnet ? It sound logical to me though. Thanks. and +1.
Mar
7
revised Amazon AWS: Can I attach volumes at runtime?
added 81 characters in body
Mar
7
answered Accessing Amazon S3 from a private VPC subnet
Mar
7
answered Amazon AWS: Can I attach volumes at runtime?
Jan
31
comment AWS VPC + IPtables + NAT: Port Forwarding is not working
Thanks. +1 for your efforts. Your MASQUERADE command is not helpful in my case. May be I am missing something. The Only MASQUERADE command that gets me flying is the the one I have mentioned in my answer.
Jan
31
awarded  Teacher
Jan
30
comment Iptables MASQUERADE: What is the advantage/disadvantage between these two commands?
I have dumped whatever I could regarding the VPC setup in the question I linked in my post. Regarding the routing info, AWS VPC handles that and I have no control over it neither I know how it works behind the curtains. I highly appreciate your time and explanation. I am researching further and if I fail to find anything meaningful, I shall be accepting this answer.