Armor Anywhere | Armor Agent for Servers
| Armor Toolbox Bug Fix
We have addressed an issue affecting the AMP Toolbox page that was causing delays and errors when loading scheduled tasks. This update improves the performance and reliability of the Toolbox page, ensuring that users can access their scheduled tasks without encountering timeouts or errors.
Enhanced Page Loading:
The Toolbox page now loads more efficiently, significantly reducing the time it takes to retrieve and display scheduled task data.
Users will no longer encounter the “Endpoint request timed out” error when navigating to the Toolbox page.
Improved Query Performance: We have optimized the database query responsible for fetching scheduled tasks. The query now specifically targets registered virtual machines (VMs), ensuring that only relevant data is retrieved and reducing the likelihood of timeouts.
This change results in faster page load times and a smoother user experience.
...
We are excited to introduce a new feature that allows Armor customers to remotely update the Armor Agent using the AMP Toolbox. This enhancement is designed to streamline the update process, reduce downtime, and ensure that all users have the latest features and security patches without the need for manual intervention.
...
An issue was identified where certain steps in the Armor Agent update script were not executing when triggered from the AMP Toolbox.
...
Armor customers and support teams can now schedule and execute Armor Agent updates directly from the AMP Toolbox for Linux VM’s.
...
| Automatic Kernel Compatibility Listing for Trend Sub-Agent
Overview:
We are pleased to announce a significant enhancement to the Armor Knowledge Base (KB), designed to simplify the process of identifying compatible kernels for the Trend sub-agent across different operating systems. This update provides Armor customers and users with easy access to up-to-date compatibility information, ensuring successful installation and optimal performance of the Armor Agent for Servers.
Key Enhancements:
Automated Kernel Compatibility Listing: The Armor Knowledge Base now automatically lists the available kernels for the Trend sub-agent per compatible Operating System (OS), helping users quickly identify the supported kernels for each OS version.
This update includes detailed information for both ARM64 and x64 architectures, making it easier to determine compatibility with your infrastructure.
Enhanced ARM64 Support Information: The compatibility table in the KB has been updated to clearly specify ARM64 support under operating systems such as Amazon Linux 2 and Amazon Linux 2023.
Users can now easily see which kernels are supported for ARM64, helping them make informed decisions about their infrastructure and reducing potential installation issues.
Comprehensive Kernel Support Details: The KB now lists the minimal kernel version support required for each OS, such as
6.1.84-99.169.amzn2023for Amazon Linux 2023.Additional requirements, such as the need to install ‘cronie’ for Amazon Linux 2023, are also noted to ensure smooth installation and operation of the Armor Agent.
Regular Updates to Compatibility Information: A new process has been implemented to ensure that the compatibility table in the KB is regularly updated with the latest supported kernels and OS versions.
How to Access:
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.
...
| 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.