Issue with ACS Deployment on AWS using CloudFormation template

[uvukasinovic]

Hi all,

I am following this guide: https://github.com/Alfresco/acs-deployment-aws …

When Stack is created, ACS is not available with error: 503 Service Temporarily Unavailable. In the background share and repo dockers are being recreated repeatedly.

Has anyone already tried this guide?

[sudattamawade]

Hi There,

I see that you have faced a similar issue which I am currently facing with Alfresco Installation. 

Similar to what you did,  I have done the installation using Helm Chart AWS EKS approach.

Could you please let me know if you were able to fix the issue or provide any help in the right direction. Your help is highly appreciated.

Steps:

I have followed the steps for Helm installation. I could see that the INGRESS release and ACS release are correctly deployed. However, when we try to access the below URLs:

We are getting the below issue nginx

503 Service Temporarily Unavailable

  Share: https://$EXTERNALHOST/share
  Content: https://$EXTERNALHOST/alfresco

Does this mean that the Alfresco Content Services are not correctly deployed or if there is an issue with the nginx ingress controller. Please point me in the right direction. 

Thank you and have a great day ahead.

Regards,

Sudatta Mawade

[EddieMay]

Hi @uvukasinovic & @sudattamawade,

I've asked one of our cloud engineers to take a look at your issues. I'll report back as soon as I can. 

[EddieMay]

Hi @sudattamawade,

Unfortunately, the only option here is to dig into the log files of each container/pod to look for the root cause of the pods being repeatedly recreated. Are you able to supply the log files? 

[sudattamawade]

Hi Eddie,

Thank you for your prompt responses.

I was able to figure out the solution to this. We are now using the stable version of the Helms chart (v 3.0.3) instead of the incubator. We have also increased the size of the worker nodes to accomodate the services.

We are now able to access the URLs for Share, alfresco and api explorer.

Now, I am looking to configure the S3 bucket with the ACS services. Is there any documentation available for this while installing the ACS services using the Helm Chart.

I see that in the below image it talks about applying S3 connector amp to the docker image. Does that mean I have to download the Helm Chart for ACS and modify the same to incorporate the docker compose file to include the S3 connector credentials. Are there any steps or documentation available to implement the same. Any help would be appreciated.

https://github.com/Alfresco/acs-deployment/blob/master/docs/helm-deployment-aws_kops.md#setting-up-a...

Thank you and have a great day ahead.

Regards,

Sudatta Mawade

[EddieMay]

Hi @sudattamawade,

Great news that you've made some progress. I've asked one of our engineers to take a look at the next stumbling block. I'll get back when I know more  

[EddieMay]

Hi @sudattamawade,

I've been told that reading a combination of https://github.com/Alfresco/acs-deployment/blob/master/docs/use-cases/acs-deployment-with-s3-connect... and https://docs.alfresco.com/s3connector/concepts/s3-contentstore-install-intro.html should help you resolve your problem.

HTH, 

[sudattamawade]

Hi Eddie,

We went through the steps. However, it is quite rough to understand. However, we are working on the steps to configure the S3 connector.

In the meanwhile, we are trying to apply the Enterprise License to ACS. We have uploaded the license through the Admin Console. However, we are not sure of how do we restart the PODs or the services. We have tried to use the kubectl stop pods, service commands but these are not working.

Can you please provide us any steps or provide any links which contains the documentation of how to restart services in AWS EKS cluster and also applying the licenses.

Thank you in advance for your help.

Regards,

Sudatta Mawade

[EddieMay]

Hi @sudattamawade,

Are these trial licences? 

[sudattamawade]

Hi Eddie,

No, we have enterprise license for ACS.

Regards,

Sudatta Mawade