# Monitoring Amazon FSx for OpenZFS file systems
Monitoring file systems

Monitoring is an important part of maintaining the reliability, availability, and performance of your FSx for OpenZFS file system and your other AWS solutions. Collecting monitoring data from all parts of your AWS solution allows you to more easily debug a multi-point failure if one occurs. You can monitor your FSx for OpenZFS file system, report when something is wrong, and take action automatically when appropriate using the following tools:
+ **Amazon CloudWatch** – Monitors your AWS resources and the applications that you run on AWS in real time. You can collect and track metrics, create customized dashboards, and set alarms that notify you when a specified metric reaches a threshold that you specify. For example, you can have CloudWatch track storage capacity or other metrics for your Amazon FSx instances and automatically launch new instances when needed.
+ **AWS CloudTrail** – Captures API calls and related events made by or on behalf of your AWS account and delivers the log files to an Amazon S3 bucket that you specify. You can identify which users and accounts called AWS, the source IP address from which the calls were made, and when the calls occurred.

The following sections provide information on how to use both Amazon CloudWatch and AWS CloudTrail with your FSx for OpenZFS file systems.

**Topics**
+ [

# Monitoring with Amazon CloudWatch
](monitoring-cloudwatch.md)
+ [

# Logging FSx for OpenZFS API calls with AWS CloudTrail
](logging-using-cloudtrail-win.md)

# Monitoring with Amazon CloudWatch
Monitoring with CloudWatch

You can monitor Amazon FSx using CloudWatch, which collects raw data and processes it into readable, near real-time metrics. These statistics are kept for 15 months so that you can access historical information and gain a better perspective on how your application or service is performing. You can also set alarms that watch for certain thresholds and send notifications or take actions when those thresholds are met. For more information about CloudWatch, see [What is Amazon CloudWatch?](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html) in the *Amazon CloudWatch User Guide*.

FSx for OpenZFS publishes CloudWatch metrics in the following domains:
+ **Network I/O metrics** – Measure activity between clients that access the file system and the file server.
+ **File server metrics** – Measure network throughput utilization, file server CPU and memory, and file server disk throughput and IOPS utilization.
+ **Disk metrics** – Measure activity between the file server and the SSD storage.
+ **Storage capacity metrics** – Measure storage usage.

The following diagram illustrates an FSx for OpenZFS file system, its components, and its metric domains.

![\[FSx for Windows File Server reports metrics in CloudWatch.\]](http://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/images/metrics-overview-FSxZ.png)


By default, FSx for OpenZFS sends metric data to CloudWatch at 1-minute intervals. The following are exceptions to the default, and are sent at 5-minute intervals:
+ `FileServerDiskThroughputBalance`
+ `FileServerDiskIopsBalance`

**Note**  
Metrics might not be published during file system maintenance for Single-AZ (non-HA) file systems, or during failover and failback between the primary and secondary file servers for Single-AZ (HA) and Multi-AZ (HA) file systems.

**Topics**
+ [

# Using Amazon FSx for OpenZFS CloudWatch metrics
](how_to_use_metrics.md)
+ [

# Accessing CloudWatch metrics
](accessingmetrics.md)
+ [

# Amazon FSx for OpenZFS metrics and dimensions
](fsx-openzfs-metrics.md)
+ [

# Performance warnings and recommendations
](performance-insights-FSxZ.md)
+ [

# Creating CloudWatch alarms to monitor metrics
](creating_alarms.md)

# Using Amazon FSx for OpenZFS CloudWatch metrics
Using CloudWatch metrics

There are two primary architectural components of each Amazon FSx file system:
+ The **file server** that serves data to clients that access the file system.
+ The **storage volumes** that host the data in your file system.

FSx for OpenZFS reports metrics in CloudWatch that track performance and resource utilization for your file system's file server and storage volumes. The following diagram illustrates an Amazon FSx file system with its architectural components, and the performance and resource CloudWatch metrics that are available for monitoring. The key property for a set of metrics is the file system property that determines the capacity for those metrics. Adjusting that property modifies the file system's performance for that set of metrics.

![\[Diagram displaying the different types of FSx for OpenZFS Cloudwatch metrics.\]](http://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/images/file-server-metrics-FSxZ.png)


You can use the **Monitoring & performance** panel on your file system's dashboard in the Amazon FSx console to view the metrics that are described in the following table. For more information, see [Accessing CloudWatch metrics](accessingmetrics.md).

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/how_to_use_metrics.html)

**Note**  
We recommend that you provision throughput capacity so that the utilization of any performance-related dimension,—such as typical network, CPU, and memory utilization is less than 50%. This ensures that you have enough spare throughput capacity for unexpected spikes in your workload, as well as for background storage operations.

# Accessing CloudWatch metrics


You can access Amazon FSx metrics for CloudWatch in the following ways: 
+ The Amazon FSx console.
+ The CloudWatch console.
+ The CloudWatch command line interface (CLI).
+ The CloudWatch API.

The following procedures show you how to access the metrics using these tools.

## Using the Amazon FSx console


**To view metrics using the Amazon FSx console**

1. Open the Amazon FSx console at [https://console.aws.amazon.com/fsx/](https://console.aws.amazon.com/fsx/).

1. From the navigation pane, choose **File systems**, then choose the file system that has the metrics that you want to view.

1. Choose **Actions > View details**. 

1. On the **Summary** page, choose **Monitoring and performance** to see the metrics for your file system. 

## Using the CloudWatch console


**To view metrics using the CloudWatch console**

1. Open the [CloudWatch console](https://console.aws.amazon.com/cloudwatch).

1. In the navigation pane, choose **Metrics**. 

1. Select the **FSx** namespace.

1. (Optional) To view a metric, enter its name in the search field.

1. (Optional) To explore metrics, select the category that best matches your question. *File system metrics* and *Volume metrics* report summary-level metrics for individual file systems or volumes. *File system detailed metrics* and *Volume detailed metrics* report more granular metrics within a file system or volume. For example, storage capacity that's used by snapshots.

## Using the AWS CLI


**To access metrics from the AWS CLI**
+ Use the [https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/list-metrics.html](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/list-metrics.html) command with the `--namespace "AWS/FSx"` namespace. For more information, see the [AWS CLI Command Reference](https://docs.aws.amazon.com/cli/latest/reference/).

## Using the CloudWatch API


**To access metrics from the CloudWatch API**
+ Call `[GetMetricStatistics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html)`. For more information, see [Amazon CloudWatch API Reference](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/). 

# Amazon FSx for OpenZFS metrics and dimensions
Metrics and dimensions

Amazon FSx publishes the metrics described in the following tables in the `AWS/FSx` namespace in Amazon CloudWatch for all FSx for OpenZFS file systems:

**Topics**
+ [

## FSx for OpenZFS network I/O metrics
](#fsx-networkio-metrics)
+ [

## FSx for OpenZFS file server metrics
](#fsx-file-server-metrics)
+ [

## FSx for OpenZFS disk metrics
](#fsx-diskio-metrics)
+ [

## FSx for OpenZFS storage capacity metrics
](#fsx-storage-capacity-metrics)
+ [

## FSx for OpenZFS dimensions
](#fsx-dimensions)

## FSx for OpenZFS network I/O metrics


The `AWS/FSx` namespace includes the following network I/O metrics.


| Metric | Description | 
| --- | --- | 
| DataReadBytes |  The number of bytes for read operations for clients that access the file system. Unit: Bytes Valid statistic: `Sum`  | 
| DataWriteBytes |  The number of bytes for write operations for clients that access the file system. Unit: Bytes Valid statistic: `Sum`  | 
| DataReadOperations |  The number of read operations for clients that access the file system. Unit: Count Valid statistic: `Sum`  | 
| DataWriteOperations |  The number of write operations for clients that access the file system. Unit: Count Valid statistic: `Sum`  | 
| ClientConnections | The number of active connections between clients and the file server. Unit: Count Valid statistics: `Average`, `Maximum`  | 
| MetadataOperations |  The number of metadata operations for clients that access the file system. Unit: Count Valid statistic: `Sum`  | 
| NfsBadCalls |  The number of calls rejected by the NFS server remote procedure call (RPC) mechanism. Unit: Count Valid statistic: `Sum`  | 

## FSx for OpenZFS file server metrics


The `AWS/FSx` namespace includes the following file server metrics.


| Metric | Description | 
| --- | --- | 
| NetworkThroughputUtilization | The network throughput for clients that access the file system, as a percentage of the provisioned limit. For Multi-AZ file systems, this metric includes replication traffic. Note that this metric reflects the direction - i.e. inbound or outbound - that has the higher traffic flow. Unit: Percent Valid statistics: `Average`, `Maximum`  | 
| CPUUtilization | The percentage utilization of your file server’s CPU resources. Unit: Percent Valid statistics: `Average`, `Maximum`  | 
| FileServerDiskThroughputUtilization |  The disk throughput between your file server and its storage volumes. Listed as a percentage of the provisioned limit, which is determined by throughput capacity. Unit: Percent Valid statistics: `Average`, `Maximum`  | 
| FileServerDiskThroughputBalance | The percentage of available burst credits for disk throughput between your file server and its storage volumes. Unit: Percent Valid statistics: `Average`, `Minimum`  | 
| FileServerDiskIopsUtilization | The disk IOPS between your file server and storage volumes, as a percentage of the provisioned limit, which is determined by throughput capacity. Unit: Percent Valid statistics: `Average`, `Maximum`  | 
| FileServerDiskIopsBalance | The percentage of available burst credits for disk IOPS between your file server and its storage volumes. Unit: Percent Valid statistics: `Average`, `Minimum`  | 
| MemoryUtilization | The percentage of your file server’s memory resources that are utilized. Unit: Percent Valid statistics: `Average`, `Maximum`  | 
| FileServerCacheHitRatio | The percentage of cache hits. For Single-AZ 2 (non-HA and HA) file systems, this metric reports the cache hit ratio for both the in-memory (ARC) and NVMe (L2ARC) caches. For Single-AZ 1 (non-HA and HA) file systems, this metric reports only the cache hit ratio for the ARC cache. Unit: Percent Valid statistics: `Average`, `Minimum`  | 

## FSx for OpenZFS disk metrics


The `AWS/FSx` namespace includes the following disk metrics.


| Metric | Description | 
| --- | --- | 
| DiskReadBytes | The number of bytes for read operations that access storage volumes. Unit: Bytes Valid statistic: `Sum`  | 
| DiskWriteBytes | The number of bytes for write operations that access storage volumes. Unit: Bytes Valid statistic: `Sum`  | 
| DiskReadOperations |  The number of read operations for the file server that accesses storage volumes. Unit: Count Valid statistic: `Sum`  | 
| DiskWriteOperations |  The number of write operations for the file server that accesses storage volumes. Unit: Count Valid statistic: `Sum`  | 
| DiskThroughputBalance | The percentage of available burst credits for disk throughput for the storage volumes. Unit: Percent Valid statistics: `Average`, `Minimum`  | 
| DiskIopsUtilization | The disk IOPS between your file server and storage volumes, as a percentage of the provisioned IOPS limit that has been determined by the storage volumes. Unit: Percent Valid statistics: `Average`, `Maximum`  | 

## FSx for OpenZFS storage capacity metrics


The `AWS/FSx` namespace includes the following storage capacity metrics.


| Metric | Description | 
| --- | --- | 
| StorageCapacity |  The total storage capacity, equal to the sum of used and available storage capacity. Unit: Bytes Valid statistics: `Average`, `Minimum`  | 
| UsedStorageCapacity |  The amount of storage that's used. Unit: Bytes Valid statistics: `Average`, `Minimum`  | 
| CompressionRatio |  The ratio of compressed storage usage to uncompressed storage usage. Valid statistics: `Average`, `Minimum`  | 

## FSx for OpenZFS dimensions


FSx for OpenZFS provides additional dimensions to further refine the metrics listed in the previous table. FSx for OpenZFS metrics use the `FSx` namespace and provide metrics at the file system or volume granularity by using the `FileSystemId` or `VolumeId`. 


| Dimension | Description | 
| --- | --- | 
| `FileSystemId` | This dimension filters the metrics that you request to an individual file system. | 
| `VolumeId` | This dimension filters the metrics that you request to an individual volume within a file system. This dimension must be used in combination with `FileSystemId`. | 
| `CacheType` | This dimension filters the metrics that you request by the type of cache used, either ARC for in-memory caching or L2ARC for SSD and NVMe caching. This dimension must be used in combination with `FileSystemId`. | 
| `DataType` | This dimension filters the metrics that you requested to a specific type of stored data. Metrics with `DataType` set to `Snapshot` report information about the snapshots within the volume. Metrics without a `DataType` dimension report aggregated information from the volume, which includes any child volumes and snapshots within the volume.  | 

FSx for OpenZFS metrics use the `FSx` namespace and provide metrics for the dimensions that are listed in the table above.

# Performance warnings and recommendations


FSx for OpenZFS displays a warning for CloudWatch metrics when one of these metrics approaches or crosses a predetermined threshold for multiple consecutive data points. These warnings provide you with actionable recommendations that you can use to optimize your file system's performance.

Warnings are accessible in several areas of the **Monitoring & performance** dashboard on the Amazon FSx console. All active or recent Amazon FSx performance warnings and CloudWatch alarms configured for the file system that are in an alarm state appear in the **Monitoring & performance** panel in the **Summary** section. The warning also appears in the section of the dashboard where the metric graph is displayed.

You can create CloudWatch alarms for any of the Amazon FSx metrics. For more information, see [Creating CloudWatch alarms to monitor metrics](creating_alarms.md).

## Use performance warnings to improve file system performance
Improve file system performance

Amazon FSx provides actionable recommendations that you can use to optimize your file system's performance. You can take the recommended action if you expect the issue to continue, or if it's causing an impact to your file system's performance. Depending on which metric has triggered a warning, you can resolve it by increasing the file system's throughput capacity or storage capacity, as described in the following table.

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/performance-insights-FSxZ.html)

For more information about file system performance, see [Performance for Amazon FSx for OpenZFSPerformance](performance.md).

# Creating CloudWatch alarms to monitor metrics
Creating CloudWatch alarms

You can create a CloudWatch alarm that sends an Amazon SNS message when the alarm changes state. An alarm watches a single metric over a time period that you specify and performs one or more actions based on the value of the metric relative to a given threshold over a specified period of time. The action is a notification that's sent to an Amazon SNS topic or Auto Scaling policy.

Alarms invoke actions for sustained state changes only. CloudWatch alarms don't invoke actions because they are in a particular state. The state must change and remain changed for a specified period of time. You can create an alarm on the Amazon FSx console or the CloudWatch console.

The following procedures describe how to create alarms for Amazon FSx using the console, AWS CLI, and API.

## To set alarms using the Amazon FSx console


1. Open the Amazon FSx console at [https://console.aws.amazon.com/fsx/](https://console.aws.amazon.com/fsx/).

1. From the navigation pane, choose **File systems**, and then choose the file system that you want to create the alarm for.

1. Choose **Actions > View details**. 

1. On the **Summary** page, choose **Monitoring and performance**. 

1. Choose **Create CloudWatch alarm**. You are redirected to the CloudWatch console.

1. Choose **Select metrics**, and choose **Next**.

1. In the **Metrics** section, choose **FSX**.

1. Choose **File System Metrics**, choose the metric that you want to set the alarm for, and then choose **Select metric**.

1. In the **Conditions** section, choose the conditions for the alarm, and choose **Next**.
**Note**  
Metrics might not be published during file system maintenance. To prevent unnecessary and misleading alarm condition changes and to configure your alarms so that they are resilient to missing data points, see [Configuring how CloudWatch alarms treat missing data](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html#alarms-and-missing-data) in the *Amazon CloudWatch User Guide*.

1. If you want CloudWatch to send you an email or SNS notification when the alarm state triggers the action, choose **Whenever this alarm state is**. 

   For **Select an SNS topic**, choose an existing SNS topic. If you select **Create topic**, you can set the name and email addresses for a new email subscription list. This list is saved and appears in the field for future alarms. Choose **Next**.
**Warning**  
If you use **Create topic** to create a new Amazon SNS topic, the email addresses must be verified before they receive notifications. Emails are only sent when the alarm enters an alarm state. If this alarm state change happens before the email addresses are verified, they do not receive a notification.

1. Fill in the **Name**, **Description**, and **Whenever** values for the metric, and choose **Next**. 

1. On the **Preview and create** page, review the alarm and choose **Create Alarm**. 

## To set alarms using the CloudWatch console


1. Sign in to the AWS Management Console and open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/).

1. Choose **Create Alarm** to start the **Create Alarm Wizard**. 

1. Choose **FSx Metrics** to locate a metric. To narrow the results, you can search for your file system ID. Select the metric that you want to create an alarm for and choose **Next**.

1.  Enter a **Name** and a **Description**, and choose a **Whenever** value for the metric. 

1. If you want CloudWatch to send you an email when the alarm state is reached, choose **State is ALARM** for **Whenever this alarm**. For **Send notification to**, choose an existing SNS topic. If you select **Create topic**, you can set up the names and email addresses for a new email subscription list. This list is saved and appears in the field for future alarms.
**Warning**  
If you use **Create topic** to create a new Amazon SNS topic, the email addresses must be verified before they receive notifications. Emails are only sent when the alarm enters an alarm state. If this alarm state change happens before the email addresses are verified, they do not receive a notification.

1. View the **Alarm Preview** and then choose **Create Alarm** or go back to make changes. 

## To set an alarm using the AWS CLI

+ Call `[put-metric-alarm](https://docs.aws.amazon.com/cli/latest/reference/put-metric-alarm.html)`. For more information, see *[AWS CLI Command Reference](https://docs.aws.amazon.com/cli/latest/reference/)*.

## To set an alarm using the CloudWatch

+ Call `[PutMetricAlarm](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutMetricAlarm.html)`. For more information, see *[Amazon CloudWatch API Reference](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/)*. 

# Logging FSx for OpenZFS API calls with AWS CloudTrail
Logging API calls with AWS CloudTrail

Amazon FSx is integrated with AWS CloudTrail, a service that provides a record of actions taken by a user, role, or an AWS service in Amazon FSx. CloudTrail captures all API calls for Amazon FSx as events. Captured calls include calls from the Amazon FSx console and from code calls to Amazon FSx API operations.

If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Amazon FSx. If you don't configure a trail, you can still view the most recent events in the CloudTrail console in **Event history**. Using the information collected by CloudTrail, you can determine the request that was made to Amazon FSx. You can also determine the IP address from which the request was made, who made the request, when it was made, and additional details. 

To learn more about CloudTrail, see the [AWS CloudTrail User Guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/).

## Amazon FSx Information in CloudTrail


CloudTrail is enabled on your AWS account when you create the account. When API activity occurs in Amazon FSx, that activity is recorded in a CloudTrail event along with other AWS service events in **Event history**. You can view, search, and download recent events in your AWS account. For more information, see [Viewing events with CloudTrail Event history](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events.html). 

For an ongoing record of events in your AWS account, including events for Amazon FSx, create a trail. A *trail* enables CloudTrail to deliver log files to an Amazon S3 bucket. By default, when you create a trail in the console, the trail applies to all AWS Regions. The trail logs events from all AWS Regions in the AWS partition and delivers the log files to the Amazon S3 bucket that you specify. Additionally, you can configure other AWS services to further analyze and act upon the event data collected in CloudTrail logs. For more information, see the following topics in the *AWS CloudTrail User Guide:* 
+ [Creating a trail for your AWS account](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-create-and-update-a-trail.html)
+ [AWS service integrations with CloudTrail Logs](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-aws-service-specific-topics.html#cloudtrail-aws-service-specific-topics-integrations)
+ [Configuring Amazon SNS notifications for CloudTrail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/configure-sns-notifications-for-cloudtrail.html)
+ [Receiving CloudTrail log files from multiple regions](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html) and [Receiving CloudTrail log files from multiple accounts](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-receive-logs-from-multiple-accounts.html)

All Amazon FSx [API calls](fsx/latest/APIReference/welcome.html) are logged by CloudTrail. For example, calls to the `CreateFileSystem` and `TagResource` operations generate entries in the CloudTrail log files. 

Every event or log entry contains information about who generated the request. The identity information helps you determine the following: 
+ Whether the request was made with root or user credentials.
+ Whether the request was made with temporary security credentials for a role or federated user.
+ Whether the request was made by another AWS service.

For more information, see the [CloudTrail userIdentity element](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-user-identity.html) in the *AWS CloudTrail User Guide.*

## Understanding Amazon FSx Log File Entries


A *trail* is a configuration that enables delivery of events as log files to an Amazon S3 bucket that you specify. CloudTrail log files contain one or more log entries. An *event* represents a single request from any source and includes information about the requested action, the date and time of the action, request parameters, and so on. CloudTrail log files aren't an ordered stack trace of the public API calls, so they don't appear in any specific order. 

The following example shows a CloudTrail log entry that demonstrates the `TagResource` operation when a tag for a file system is created from the console.

```
{
    "eventVersion": "1.05",
    "userIdentity": {
        "type": “Root”,
        "principalId": “111122223333”,
        "arn": "arn:aws:sts::111122223333:root”,
        "accountId": “111122223333”,
        "accessKeyId": "AKIAIOSFODNN7EXAMPLE”,
        "sessionContext": {
            "attributes": {
                "mfaAuthenticated": "false",
                "creationDate": "2018-11-14T22:36:07Z"
            }
        }
    },
    "eventTime": "2018-11-14T22:36:07Z",
    "eventSource": "fsx.amazonaws.com",
    "eventName": "TagResource",
    "awsRegion": "us-east-1",
    "sourceIPAddress": “192.0.2.0”,
    "userAgent": “console.amazonaws.com”,
    "requestParameters": {
        "resourceARN": "arn:aws:fsx:us-east-1:111122223333:file-system/fs-ab12cd34ef56gh789”
    },
    "responseElements": null,
    "requestID": “aEXAMPLE-abcd-1234-56ef-b4cEXAMPLE51”,
    "eventID": “bEXAMPLE-gl12-3f5h-3sh4-ab6EXAMPLE9p”,
    "eventType": "AwsApiCall",
    "apiVersion": "2018-03-01",
    "recipientAccountId": “111122223333”
}
```

The following example shows a CloudTrail log entry that demonstrates the `UntagResource` action when a tag for a file system is deleted from the console.

```
{
    "eventVersion": "1.05",
    "userIdentity": {
        "type": “Root”,
        "principalId": "111122223333",
        "arn": "arn:aws:sts::111122223333:root",
        "accountId": "111122223333",
        "accessKeyId": "AKIAIOSFODNN7EXAMPLE",
        "sessionContext": {
            "attributes": {
                "mfaAuthenticated": "false",
                "creationDate": "2018-11-14T23:40:54Z"
            }
        }
    },
    "eventTime": "2018-11-14T23:40:54Z",
    "eventSource": "fsx.amazonaws.com",
    "eventName": "UntagResource",
    "awsRegion": "us-east-1",
    "sourceIPAddress": "192.0.2.0",
    "userAgent": "console.amazonaws.com",
    "requestParameters": {
        "resourceARN": "arn:aws:fsx:us-east-1:111122223333:file-system/fs-ab12cd34ef56gh789"
    },
    "responseElements": null,
    "requestID": "aEXAMPLE-abcd-1234-56ef-b4cEXAMPLE51",
    "eventID": "bEXAMPLE-gl12-3f5h-3sh4-ab6EXAMPLE9p",
    "eventType": "AwsApiCall",
    "apiVersion": "2018-03-01",
    "recipientAccountId": "111122223333"
}
```