Add details and links for FIPS ingest

deploy-manage/security/fips-ingest.md

@@ -14,7 +14,7 @@ applies_to:
 
 # FIPS mode for Ingest tools [fips-ingest]
 
-{{agent}}, {{fleet}}, {{filebeat}}, {{metricbeat}}, and {{apm-server}} binaries are built and can be configured to use FIPS 140-2 compliant cryptography.
+{{agent}}, {{fleet}}, {{filebeat}}, {{metricbeat}}, and {{apm-server}} binaries are built and configured to use FIPS 140-2 compliant cryptography.
 Generally speaking FIPS 140-2 requirements can be summarized as:
 - linking against a FIPS certified cryptographic library
 - using only FIPS approved cryptographic functions
@@ -89,6 +89,7 @@ When you use {{agent}} and {{fleet-server}}, these limitations apply:
 
   - [Azure Logs Integration (v2 preview)](integration-docs://reference/azure/events.md)
   - [Azure Event Hub Input](integration-docs://reference/azure/eventhub.md)
+  - [SQL Input](integration-docs://reference/sql.md) 
   - [PostgreSQL Integration](integration-docs://reference/postgresql.md)
   - [MongoDB Integration](integration-docs://reference/mongodb.md)
   - [MySQL Integration](integration-docs://reference/mysql.md)

reference/fleet/install-elastic-agents.md

@@ -21,6 +21,16 @@ Note the following restrictions when installing {{agent}} on your system:
 ::::
 
 
+
+
+::::{admonition} New FIPS compatible install packages
+:class: note
+
+{applies_to}`stack: preview 9.1` FIPS compatible binaries for {{agent}}, {{fleet}}, and other ingest tools are available for download. Look for the `Linux 64-bit (FIPS)` or `Linux aarch64 (FIPS)` platform option on the product [download page](https://www.elastic.co/downloads). Get more details about FIPS compatibility for {{agent}}, {{fleet}} and other ingest tools in [FIPS mode for Ingest tools](/deploy-manage/security/fips-ingest.md).
+
+::::
+
+
 You have a few options for installing and managing an {{agent}}:
 
 * **Install a {{fleet}}-managed {{agent}} (recommended)**

solutions/observability/apm/use-apm-securely.md

@@ -23,4 +23,5 @@ When setting up Elastic APM, it’s critical to ensure that application data is
 | **What kind of data is collected?** | Ensure that data doesn’t contain sensitive information like passwords,  credit card numbers, health data, or other identifiable information.<br>  Read more in [Secure data](/solutions/observability/apm/secure-data.md). |
 | **How do APM agents and {{agent}} communicate?** | Ensure that any communication between APM agents and {{agent}}  are both encrypted and authenticated.<br>  Read more in [Secure communication with APM agents](/solutions/observability/apm/secure-communication-with-apm-agents.md). |
 | **How do APM Server and the {{stack}} communicate?** | Use role-based access control to grant APM Server users access to secured resources. The roles that you set up depend on your organization’s security requirements and the  minimum privileges required to use specific features.<br>  Read more in [Secure communication with the {{stack}}](/solutions/observability/apm/secure-communication-with-elastic-stack.md). |
+| **Is FIPS compatibility available for APM Server?** | {applies_to}`stack: preview 9.1`Yes! FIPS compatible binaries are available for download. Look for the `Linux x86_64 (FIPS)` or `Linux aarch64 (FIPS)` platform option on the [APM Server download](https://www.elastic.co/downloads/apm) page.<br> Get more details about FIPS compatibility for APM Server and other ingest tools in [FIPS mode for Ingest tools](/deploy-manage/security/fips-ingest.md).|
 | **Who can use the Applications UI?** | Use role-based access control to grant users access to features of the Applications UI.<br>  Read more in [Secure access to the Applications UI](/solutions/observability/apm/secure-access-to-applications-ui.md). |