Automic Workload Automation

 View Only

 Automic RA_Rest Agent installation on AWS - redshift

Srinivas Reddy's profile image
Srinivas Reddy posted Jan 08, 2024 10:54 AM

Hi Community,

Hope everyone doing well.

We have a requirement to install the containerized RA_Rest Agent on AWS redshift platform. Our environment is Automic V21 standard edition. 

is this possible to install & configure the containerized RA_Agent with standard edition? If possible, can you please share installation steps, pros&cons for this kind of installation.

Thanks in advance.

Regards,

Srinivas.

Mike Halliday's profile image
Broadcom Employee Mike Halliday

There is a document on the Broadcom Software Academy that covers this scenario in detail.

https://academy.broadcom.com/hubfs/ESD/ESD_Academy/ESD_FY22_Academy/ESD_FY22_Academy_Files/ESD_FY22_Academy_Files_Automation/How-to-build-and-run-a-container-hosting-an-Automic-Java-Based-Agent.pdf

Michael Dolinek's profile image
Broadcom Employee Michael Dolinek
Srinivas Reddy's profile image
Srinivas Reddy

Hi Mike, Michael,

Good Day.

Thank you for sharing the documents. We will go through them and get back to you if any help or clarification needed.

Regards,

Srinivas.

Srinivas Reddy's profile image
Srinivas Reddy

Hi Mike, Michael,

As per the documentation,

1. Containerized agents can connect to AE standard edition(on-premises) as well.

2. we can't use the service manager and CAU.

Is my understanding correct? do we have any other limitations if we follow this approach.

Regards,

Srinivas.

Michael Dolinek's profile image
Broadcom Employee Michael Dolinek

Hi Srinivas Reddy

  1. yes - as long as a network connection can be established, and the used certificates are in place
  2. no
    • you can install/use Service Manager in the Container (e.g. this allows you to start/stop the Agent from AWI, but keeps the container running)
    • CAU requires that the Agent is started by the Service Manager. Technical there is no blocker to perform a CAU in a container but as soon as the container is restarted the "old" Agent binaries are used again
    • In order to update/upgrade your Agent you have to build a new container.

Michael