amazon web services - Access RDS from Lambda function -


i have aurora cluster in rds , lambda function.

  • both assigned same vpc.
  • both have same subnets (us-east-1 a-f)
  • both have same security group assigned
  • lambda assigned role amazonrdsfullaccess, amazonvpcfullaccess, awslambdavpcaccessexecutionrole

when run lambda instance, connection timeout when trying connect aurora. i'm able access aurora locally (with access key added aws configure).

any ideas else can check why lambda wouldn't have access instance? thank you

update: subnets each have following configuration: enter image description here route table

both have same security group assigned

it's common misconception members of same security group can communicate each other virtue of being members of same group. not case. being members of same group means follow same set of rules.

members of security group can access other members of group if group allows access itself.

instances associated security group can't talk each other unless add rules allowing (exception: default security group has these rules default).

http://docs.aws.amazon.com/amazonvpc/latest/userguide/vpc_securitygroups.html

add rule group "mysql/aurora" traffic, instead of entering ip address, enter sg-xxxxxxxx identifier of security group.


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -