The Ports tab provides you with a general information on managing container ports at CirrusGrid PaaS.
The following ports are opened by default:
Tip: Use the table below as a reference:
Additional ports can be opened using:
Depending on the way chosen, just bind your service (application listener) to the received internal or external address.
CirrusGrid PaaS automatically redirects incoming requests to the application hosted within a container.
During a node creation, the platform detects the ports which are listened on the TCP level. The commonly used for standard services (e.g. SSH, mail, databases, etc.) are automatically filtered. The first among the remaining ports becomes the container entry point so that all incoming requests are forwarded to it.
This process is performed on each container launch, so the corresponding application becomes available over the embedded Shared Load Balancer just after being deployed, without any manual intervention required.
However, in case you need to disable or adjust this functionality (e.g. if it exposes application admin panel), you can manually change the auto-redirect settings during the container creation. For that, switch to the Variables section, add the dedicated JELASTIC_EXPOSE parameter and set its value based on your needs:
Alternatively, a comma-separated list of ports can be provided via the JELASTIC_PRIORITY_PORTS variable. The platform checks them one by one, configuring the entry point redirect to the first active service discovered. This option can speed up container startup time compared to the all ports analysis during the default auto-redirect flow.
To get even greater flexibility over the node accessibility, you can customize your container firewall settings.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.