Georgi Milanov
01/31/2024, 7:59 AMMarvin
01/31/2024, 7:59 AMHTTPS_PROXY
and SSL_CERT_FILE
, as this may be necessary for communication through proxies.
For more detailed information on proxy configuration and the necessary settings for Prefect Cloud communication, you can refer to the Prefect Discourse and appropriate documentation pages.
Lastly, keep in mind that the specifics may vary depending on updates to Prefect services or your particular infrastructure setup. If you wish to get more up-to-date or detailed data, you might need to explore Prefect's changelog or further documentation.Georgi Milanov
01/31/2024, 8:00 AMMarvin
01/31/2024, 8:01 AMPREFECT_API_URL
and should point to <https://api.prefect.cloud/api/>...
. The exact endpoint would depend on the specific API method being used.
The IP addresses for these services are not directly provided as they may vary and could be subject to change. These services are accessed over HTTPS, and depending on your organization's network policies, might require whitelisting the DNS names.
If you need to whitelist IP addresses for a firewall or other security-minded network configurations and you cannot resolve this with DNS names, it is recommended to contact Prefect support for the current range of IP addresses that they use.
For security and privacy reasons, companies often don't publicly disclose their IP ranges, so reaching out directly to Prefect is the preferred approach to ensure you have accurate and current information.
To view or set the active workspace for your Prefect Cloud interactions, you can use the CLI command prefect cloud workspace ls
. To configure the Prefect server instance API URL, you could set PREFECT_API_URL
in your configuration to the correct endpoint.
Please note that if you are running Prefect inside a containerized environment, such as Docker, you must set the API server address to ensure proper communication between your Prefecture instance and the Prefect Cloud services.