After everything is created, the application waits until your specified time increment passes and then gathers the JumpCloud Directory Insights data from the specified time period, puts it in a zipped JSON file, and sends it to the S3 bucket for storage. The application goes through this process until the CloudFormation template is deleted or the CloudWatch Event that triggers the Lambda function is disabled. <\/p>\n\n\n\n
If an entire increment goes by without any Directory Insights data, we place a data point in a CloudWatch Metric in the JumpCloudDirectoryInsights Namespace. This namespace isn’t created if you don’t experience increments without events. <\/p>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\"){kind=icon}
<\/p><\/div>
If your logs are not collected properly, you can increase the memory size of your application to mitigate the issue. See\u00a0Troubleshooting Issues in Lambda<\/a>\u00a0for more information.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Installing the Application<\/h2>\n\n\n\n
You can install the Directory Insights Serverless Application from the AWS Serverless Application Repository<\/a>. You can also manually install the application from GitHub<\/a>. You’ll need to provide the following when you install the Directory Insights Serverless Application:<\/p>\n\n\n\n
- \n
- Application Name<\/strong>: Many of the AWS resources this application generates for you base their name off the application name you provide.<\/li>\n\n\n\n
- Increment Amount and Increment Type<\/strong>: These parameters specify the cadence at which Directory Insights data is exported.<\/li>\n\n\n\n
- JumpCloud API Key<\/strong>: Your API Key is safely stored in the AWS Secrets Manager. <\/li>\n<\/ul>\n\n\n\n
Alternatively, You can create the Directory Insights Serverless Application for Google Cloud Platform (GCP) Service. Instructions can be found from GitHub<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"