MongoByte
Welcome to the new MongoDB Feedback Portal!
{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.
Welcome to the new MongoDB Feedback Portal!
{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.
What problem are you trying to solve? |
We are experiencing a failure in the lambda process, which is occurring due to a change in the host IP address. This issue arises because we utilize Route53 DNS in AWS to establish connectivity to Mongo Atlas from AWS lambda. |
|
What would you like to see happen? |
We are seeking a notification regarding any advance changes to the host's IP address if it becomes dynamic. Is there a method to configure a static IP address at the host level instead of using a dynamic one? |
|
Why is this important to you or your team? |
The production process is being affected, which is crucial from a business perspective. |
|
What steps, if any, are you taking today to manage this problem? |
We would update the DNS record with the new IP address immediately following any communication failure in the lambda process. Typically, this issue arises only when there is a change in the IP address. This concern has been brought up previously as well. |
Hi there! Thank you for sharing your feedback. Out of curiosity, have you seen our documentation on "Do Atlas cluster's public IPs ever change?" Typically, they change when you are making topology changes. Alternatively, have you considered leveraging AWS PrivateLink with Lambda? That may also be a way to avoid needing to continuously allowlist new IPs. Hopefully this helps!