Search Results

All Results 7008
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Configuring Externally Managed Services
Official Documentation
Configuring Externally Managed Services Externally managed services are created, configured, and managed outside the Liferay Helm chart. Database Configuring an external database for Liferay in...
Auto-Scaling in AWS
Official Documentation
Auto-Scaling in AWS Liferay's auto-scaling feature automatically creates and destroys replicas (nodes) in the Liferay cluster to optimize performance. You can choose the minimum and maximum number...
AWS Managed Resources Reference
Official Documentation
AWS Managed Resources Reference By default, Liferay uses several managed services to run background operations when hosting in AWS. These resources facilitate the provisioning and continued use of...
Configuring Internally Managed Services
Official Documentation
Configuring Internally Managed Services Internally managed services are configured and managed within the chart. These services are defined using the dependencies property: dependencies: : ...
Configuring Liferay in AWS
Official Documentation
Configuring Liferay in AWS Since Liferay installations hosted in AWS use Helm, you must configure and customize Liferay using the Helm CLI. You can write as many .yaml files as you need. To update...
Installing Liferay in Amazon Web Services
Official Documentation
Installing Liferay in Amazon Web Services You can run Liferay DXP on AWS using a new or an existing EKS cluster; a plain installation or Liferay's offering on AWS Marketplace. Either installation...
Viewing Metrics from Kubernetes
Official Documentation
Viewing Metrics from Kubernetes It is important to track resource usage in the Kubernetes cluster. To view your resource usage, you must use a collector and an exporter. Before you can view...
Viewing Metrics with Prometheus
Viewing Metrics with Prometheus The Liferay Helm chart is prepared to set up the Prometheus JMX Exporter project agent out-of-the-box. Set the JMX_AGENT_YAML environment variable to the following...