{"id":47198,"date":"2020-08-17T09:00:00","date_gmt":"2020-08-17T15:00:00","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=47198"},"modified":"2024-11-08T17:34:08","modified_gmt":"2024-11-08T22:34:08","slug":"aws-serverless-app-directory-insights","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/aws-serverless-app-directory-insights","title":{"rendered":"Using AWS Serverless Architecture to Collect JumpCloud Directory Insights Data"},"content":{"rendered":"\n

With the release of Directory Insights<\/a>\u2122, JumpCloud\u00ae<\/sup> provided administrators with visibility into the everyday happenings of their cloud-based directory. Directory Insights is a premium JumpCloud feature that returns event logs and authentications across JumpCloud endpoints.<\/p>\n\n\n\n

Now, we\u2019ve released the JumpCloud Directory Insights Serverless application<\/a> to further empower JumpCloud administrators to expand the use and duration of their Directory Insights data. Using the power of Amazon Web Services’ Serverless architecture<\/a>, we\u2019ve provided a quick and easy way for JumpCloud admins to deploy the infrastructure required to automatically collect and store their Directory Insights data within their own AWS account.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

What Does the Serverless App Do?<\/h2>\n\n\n\n

Once you provide the application with your JumpCloud API key<\/a>, how often you’d like your data to be collected (and an Organization ID for our MSP clients out there who use the Multi-Tenant Portal), you’ll be able to hit the \u201cDeploy\u201d button. After the application has been deployed, you can sit back and relax with the knowledge that AWS will put in all the heavy lifting by provisioning the required resources. At the end of the deployment process, you will have:<\/p>\n\n\n\n