...
You can view the updated compatibility information by visiting the Armor Knowledge Base. The table now includes detailed kernel support for both ARM64 and x64 architectures, along with any additional requirements for installation.
...
| Armor Agent Installation Enhancement for Linux Systems
Summary:
This update enhances the installation process for the Armor agent on Linux-based systems, including Amazon Linux 2023. Users are now guided through the installation and configuration of the required cronie service, ensuring that all subagents and security functions operate correctly.
Details:
Previously, when installing the Armor agent on certain Linux distributions where cronie was not pre-installed or properly configured, users encountered issues with agent functionality, such as the inability to run certain toolbox tasks (e.g., agent start, stop, and restart).
This enhancement addresses these issues by prompting users during the installation process to:
Install
cronie:
If cronie is not found, users will be prompted to install it using the command:
| Code Block |
|---|
sudo yum install cronie -y |
Enable and Start
cronie:
| Code Block |
|---|
sudo systemctl enable crond.service
sudo systemctl start crond.service |
Confirm
cronieis Running:
| Code Block |
|---|
sudo systemctl status crond | grep Active |
Technical Details:
The installation script now checks for the presence of the
/etc/cron.ddirectory to determine ifcronieis installed. If the directory is missing, a warning is displayed, and users are provided instructions for installing and configuringcronie.Without a properly running
cronieservice, certain agent tasks that require thecroncontext will fail to execute, impacting agent functionality.
Next Steps:
Documentation updates have been made to the Armor knowledge base to include these steps and ensure users are aware of the pre-installation requirements when using Amazon Linux 2023 or other distributions where
cronieis not pre-installed.
...
| Armor Agent Uninstallation Feature for VMs in AMP
Summary:
We have introduced a new UI feature that simplifies the uninstallation process of the Armor Agent on virtual machines (VMs). Users can now initiate the uninstallation directly from the VM management interface with just a few clicks, offering greater control and efficiency.
Details:
This update introduces an “Uninstall Armor Agent” button in the VM management UI. Users can now seamlessly remove the Armor Agent without needing to use CLI or external tools. The new feature is designed to improve the user experience by aligning with the goal of providing user-friendly, visible, and intuitive solutions.
Key Features:
Uninstall Button in UI:
A new button labeled “Uninstall Armor Agent” has been added to the VM management interface.
Clicking the button triggers the uninstallation of the Armor Agent by calling the
agent/uninstallAPI.
Confirmation Prompt:
Upon clicking the uninstall button, a confirmation popup will appear with the message:
Warning: This action will remove the Armor Agent from your device. Please confirm you wish to remove the Agent.
If sub-agents are still running on the VM, an additional warning will be shown:
There are sub-agents still running on this VM, proceeding will force uninstall the agents. Do you wish to proceed?
Options to Proceed:
Users can choose between “Yes” and “No” in the confirmation popup to proceed or cancel the uninstallation process.
Additional Removal Option:
An option to remove the Armor Agent is also included in the hamburger menu on the infrastructure page for easier access.
Business Impact:
This enhancement allows users to efficiently manage the Armor Agent on their virtual machines, providing a more streamlined approach to uninstallation. By simplifying the process and making it accessible directly from the UI, users gain better control over their infrastructure, reducing the need for manual interventions.
...
| Trend Sub-agent Status Display Fix
Issue Summary:
In some instances, the Trend sub-agent incorrectly displays the message “Disabled - The customer opted out of this service” despite the Trend agent being actively running and communicating. This issue occurs due to the lack of retry logic in the API call that fetches Trend installation details. If the API call fails within 30 seconds, the VM is incorrectly marked as unhealthy, leading to confusion and inaccurate status reports for customers.
Impact:
Affected customers may see an incorrect status for the Trend sub-agent, even though Trend is operating normally.
Resolution:
We have implemented a retry logic mechanism to ensure that even if the initial API call fails, the system will attempt to retry before marking the VM as unhealthy.
Expected Behavior:
With the fix, the Trend sub-agent will correctly reflect its active status, preventing the erroneous “Disabled - The customer opted out of this service” message. The system will accurately report the health of the Trend sub-agent, and VMs will no longer show an unhealthy status due to temporary API errors.