Amazon EC2 Security Group with Host / Dynamic IP / DNS -


i seeking guidance on best approach take ec2 security groups , services dynamic ip's. want make use of services such sendgrid, elastic cloud etc use dyanmic ip's on port 80/443. access port 80/443 closed exception of whitelisted ips. far solutions have found are:

  1. cron job ping service, take ip's , update ec2 security group via ec2 api.
  2. create new ec2 act proxy port 80/443 open. new server communicates sendgrid/elasticcloud, inspects responses , returns parts main server.

are there other better solutions?

firstly, please bear in mind security groups in aws stateful, meaning that, example, if open ports 80 , 443 destinations (0.0.0.0/0) in outbound rules, ec2 machines able connect remote hosts , response if there no inbound rules given ip.

however, approach works if connection initiated ec2 instance , remote services responding. if require connections ec2 instances initiated outside, need specify inbound rules in security group(s). if know cidr block of public ip addresses, can solve problem can specify destination in security group rule. if don't know ip range of hosts going reach machines, access restriction @ network level not feasible , need implement form of authorisation of requester.

p.s. please bear in mind there soft default limit of 50 inbound or outbound rules per security group.


Comments

Popular posts from this blog

inversion of control - Autofac named registration constructor injection -

verilog - Systemverilog dynamic casting issues -

ios - Change Storyboard View using Seague -