AWS CloudTrail is a web service that records AWS API calls for your account and delivers log files to you. The recorded information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by the AWS service.
With CloudTrail, you can get a history of AWS API calls for your account, including API calls made via the AWS Management Console, AWS SDKs, command line tools, and higher-level AWS services (such as AWS CloudFormation). The AWS API call history produced by CloudTrail enables security analysis, resource change tracking, and compliance auditing.
Millions of users globally rely on Atlassian products every day for improving software development, project management, collaboration, and code quality. Atlassian products include: JIRA Software, JIRA Service Desk, JIRA Core, StatusPage, Confluence, HipChat, Bitbucket, SourceTree, Bamboo, Cover, FishEye, Crucible.
Popular Use Cases
Bring all your CloudTrail data to Amazon Redshift
Load your CloudTrail data to Google BigQuery
ETL all your CloudTrail data to Snowflake
Move your CloudTrail data to MySQL
Bring all your Atlassian data to Amazon Redshift
Load your Atlassian data to Google BigQuery
ETL all your Atlassian data to Snowflake
Move your Atlassian data to MySQL
Atlassian's End Points
Request information about your service desk instance, including its version number, how long the instance has been running and what build it is. Accessing this data will, among other things, allow you to more successfully integrate your service desk with other relevant data sources.
Create a customer entity in JIRA Service Desk by providing Atlassian with the customer’s name, email and display name. Then, use this data in other endpoints to track service requests for a specific customer or integrate it with customer service data from other sources to provide a more comprehensive view of a customer’s journey.
Retrieve data on organizations that are engaging with your service desk, including the organizations’ names, IDs, properties and associated users. Then, access this endpoint to track those organizations, their users and their service requests so that you can have a better understanding of your service interactions with them.
Track any and all customer service requests and get relevant data, such as the customer’s contact info, the reason for the request, and the status of the request (what step it is on in your customer service process). Use this data to evaluate how well your company is responding to these requests and/or monitor customer service trends.