The Helm charts are provided as a reference that can be used to build deployments in AWS. The Helm charts are undergoing continual development and improvement and should not be used "as-is" for a production deployment. If you're a System administrator, ensure that data persistence, backups, log storage, and other system-level functions have been configured to meet your needs.
Since we need to use private (Enterprise-only) Docker images from Quay.io, you need credentials to be able to pull those images from Quay.io. Alfresco customers can request their credentials by logging a ticket with Alfresco Support.
Here's a summary of the steps required for the EKS deployment:
- Set up an EKS cluster on AWS.
- Prepare the cluster for Alfresco Content Services, including creating a hosted zone in Route 53, and an Elastic File System (EFS) for storage.
- Deploy Alfresco Content Services on the Kubernetes cluster, including creating a namespace.
- To access the images in Quay.io, you'll need to generate a pull secret and apply it to your cluster.
- Check the status of your deployment.
See the detailed project documentation in GitHub: Deploying Helm charts on AWS EKS
In this project, you can use the Helm charts following the documentation for standard installations.
Any customization of your environment, including major configuration changes, should be done inside a Docker image, resulting in the creation of a new image with a new tag. This approach allows changes to be tracked in the source code (i.e. Dockerfile) and rolling updates to the deployment in the Kubernetes cluster. See the Customization Guidelines for more.