Delay in Streamlit Application Startup due to checkip.amazonaws.com

Using Streamlit
1

I’m experiencing an issue with the startup time of my Streamlit application, which is running inside a Kubernetes pod on Amazon EKS. The application takes a significant amount of time to start, and it seems that the delay is due to Streamlit attempting to retrieve the external IP address by hitting checkip.amazonaws.com.

Unfortunately, my company’s security policies do not allow whitelisting this URL, resulting in a prolonged startup time.

Debugging Info:

  1. Deployment: The app is deployed.
  2. Hosting Platform:
    a. It is deployed on Amazon EKS.
    b. (N/A - Internal deployment, no public link available)
  3. GitHub Repository:
  4. Error Message:
  5. Versions:
    • Streamlit Version: 1.35.0

Additional Details:

  • Environment: Kubernetes on Amazon EKS
  • Problem: The Streamlit application startup is delayed because it tries to fetch the external IP from checkip.amazonaws.com, which is not permitted by our company’s security policies.

Questions:

  1. Is there a way to make the external IP address check optional in Streamlit?
  2. Are there any configuration settings or environment variables that can bypass this check to avoid the startup delay?
  3. Has anyone else faced a similar issue, and if so, how did you resolve it?

Any help or suggestions would be greatly appreciated. Thank you!

2

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.