Skip to content

Latest commit

 

History

History
37 lines (20 loc) · 2.82 KB

ce-ipaddresses.md

File metadata and controls

37 lines (20 loc) · 2.82 KB
copyright lastupdated keywords subcollection
years
2023, 2023
2023-11-09
code engine, functions, stateless code snippet, code snippet, stateless
codeengine

{{site.data.keyword.attribute-definition-list}}

{{site.data.keyword.codeengineshort}} public and private IP addresses

{: #network-addresses}

When you deploy your {{site.data.keyword.codeengineshort}} app, job, or function, the workload is deployed to a known list of possible network addresses, depending on the deployment region. You can add these IP addresses to an allowlist in your firewall; however, you must accept the drawbacks and risks that are involved in this action. {: shortdesc}

  • When {{site.data.keyword.codeengineshort}} runs an application, job, or function, it selects an arbitrary system from a large pool of systems for running the workload. Load conditions and system health influence the system selection. Systems are also dynamically added and removed from this pool without warning, making the list of potential network addresses large and dynamic. Your allowlist might not be stable and work reliably.
  • These network addresses are not exclusive to a single tenant and by granting access to these network addresses, you are also granting access for all other workloads, which might be owned by other tenants that are running on {{site.data.keyword.codeengineshort}}.

Because of these reasons, this approach is not recommended. However, if you accept these risks, then follow these steps to find the network addresses that are used by your {{site.data.keyword.codeengineshort}} workload.

Depending on your scenario, you can send requests to a third-party proxy service. Proxy services provide static IP addresses that you can add to your allowlist. For more information, see How can I add my {{site.data.keyword.codeengineshort}} application to an allowlist? {: tip}

You can list all egress IP addresses, both public and private that are used by {{site.data.keyword.codeengineshort}} workloads in a specific project with the {{site.data.keyword.codeengineshort}} API. For more information, see List egress IP addresses.

When you are working with a component in {{site.data.keyword.codeengineshort}} from the console such as apps, jobs, or functions, or their related entities such as access, bindings, or subscriptions, you can view details about the associated project. From the page of the particular {{site.data.keyword.codeengineshort}} entity, click Details to learn more about the associated project. Use this page to view details of the associated project, which includes information such as the region, CRN (Cloud Resource Name), GUID (globally unique identifier), network addresses (public and private), and more! {: note}