Amazon RDS IP Address
-
I have a database set up in Amazon RDS and I can reach that from my web application using the endpoint address without a problem. However, I have just had to switch web host and the new one only allows outbound requests through a static IP address. I have, temporarily, inferred the IP address by pinging the endpoint address and that works. However, the IP address can change without warning which is why Amazon uses an endpoint address. The new web host has told me that Amazon RDS have a range of IP addresses and if I can get them, they will set that up for me. However, from what I've read, that does not appear to be the case. So, am I incorrect and, if so, how do I get the range of addresses or a single, static IP address? Or is there another way of overcoming this? I would ask Amazon but at the account level I am at, do not have access to technical support. Thank you.
-
I have a database set up in Amazon RDS and I can reach that from my web application using the endpoint address without a problem. However, I have just had to switch web host and the new one only allows outbound requests through a static IP address. I have, temporarily, inferred the IP address by pinging the endpoint address and that works. However, the IP address can change without warning which is why Amazon uses an endpoint address. The new web host has told me that Amazon RDS have a range of IP addresses and if I can get them, they will set that up for me. However, from what I've read, that does not appear to be the case. So, am I incorrect and, if so, how do I get the range of addresses or a single, static IP address? Or is there another way of overcoming this? I would ask Amazon but at the account level I am at, do not have access to technical support. Thank you.
1. Maybe you are on a different VPC? 2. When created the DB you had to provide a security group. If you followed the basic Amazon instruction, you linked it to the VM you had...You may have to extend/change that group... 3. Subnet of the new VM? 4. The availability zone of the DB and the VM may be different...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
1. Maybe you are on a different VPC? 2. When created the DB you had to provide a security group. If you followed the basic Amazon instruction, you linked it to the VM you had...You may have to extend/change that group... 3. Subnet of the new VM? 4. The availability zone of the DB and the VM may be different...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Thanks - I'll check that out.
