Logging calls with CloudTrail

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

If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Deadline Cloud. 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 Deadline Cloud, 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.

Deadline Cloud information in CloudTrail

CloudTrail is enabled on your AWS account when you create the account. When activity occurs in Deadline Cloud, 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.

CloudTrail also records events when users sign in to the Deadline Cloud monitor and receive AWS credentials. When a user signs in, there is a CloudTrail event with the source signin.amazonaws.com and the name UserAuthentication. There is a second event when the signed-in user is given AWS credentials from the source sts.amazonaws.com and the name AssumeRole. The user's ID is recorded in second event inside the role session name.

For an ongoing record of events in your AWS account, including events for Deadline Cloud, 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 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:

Overview for creating a trail

CloudTrail supported services and integrations

Configuring Amazon SNS notifications for CloudTrail

Receiving CloudTrail log files from multiple Regions

Receiving CloudTrail log files from multiple accounts

Deadline Cloud supports logging the following actions as events in CloudTrail log files:

• associate-member-to-farm

• associate-member-to-fleet

• associate-member-to-job

• associate-member-to-queue

• assume-fleet-role-for-read

• assume-fleet-role-for-worker

• assume-queue-role-for-read

• assume-queue-role-for-user

• assume-queue-role-for-worker

• create-budget

• create-farm

• create-fleet

• create-license-endpoint

• create-monitor

• create-queue

• create-queue-environment

• create-queue-fleet-association

• create-storage-profile

• create-worker

• delete-budget

• delete-farm

• delete-fleet

• delete-license-endpoint

• delete-metered-product

• delete-monitor

• delete-queue

• delete-queue-environment

• delete-queue-fleet-association

• delete-storage-profile

• delete-worker

• disassociate-member-from-farm

• disassociate-member-from-fleet

• disassociate-member-from-job

• disassociate-member-from-queue

• get-application-version

• get-budget

• get-farm

• get-feature-map

• get-fleet

• get-license-endpoint

• get-monitor

• get-queue

• get-queue-environment

• get-queue-fleet-association

• get-sessions-statistics-aggregation

• get-storage-profile

• get-storage-profile-for-queue

• list-available-metered-products

• list-budgets

• list-farm-members

• list-farms

• list-fleet-members

• list-fleets

• list-job-members

• list-license-endpoints

• list-metered-products

• list-monitors

• list-queue-environments

• list-queue-fleet-associations

• list-queue-members

• list-queues

• list-storage-profiles

• list-storage-profiles-for-queue

• list-tags-for-resource

• put-metered-product

• start-sessions-statistics-aggregation

• tag-resource

• untag-resource

• update-budget

• update-farm

• update-fleet

• update-monitor

• update-queue

• update-queue-environment

• update-queue-fleet-association

• update-storage-profile

• update-worker

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 AWS Identity and Access Management (IAM) user credentials.

• Whether the request was made with temporary security credentials for a role or federated user.

• Whether the request was made by another service.

For more information, see the CloudTrail user Identity element.

Understanding Deadline Cloud 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.

This JSON example shows the log generated by a call to the CreateFarm API:

{
    "eventVersion": "0",
    "userIdentity": {
        "type": "AssumedRole",
        "principalId": "EXAMPLE-PrincipalID:EXAMPLE-Session",
        "arn": "arn:aws:sts::111122223333:assumed-role/EXAMPLE-UserName/EXAMPLE-Session",
        "accountId": "111122223333",
        "accessKeyId": "EXAMPLE-accessKeyId",
        "sessionContext": {
            "sessionIssuer": {
                "type": "Role",
                "principalId": "EXAMPLE-PrincipalID",
                "arn": "arn:aws:iam::111122223333:role/EXAMPLE-UserName",
                "accountId": "111122223333",
                "userName": "EXAMPLE-UserName"
            },
            "webIdFederationData": {},
            "attributes": {
                "mfaAuthenticated": "false",
                "creationDate": "2021-03-08T23:25:49Z"
            }
        }
    },
    "eventTime": "2021-03-08T23:25:49Z",
    "eventSource": "deadline.amazonaws.com",
    "eventName": "CreateFarm",
    "awsRegion": "us-west-2",
    "sourceIPAddress": "192.0.2.0",
    "userAgent": "EXAMPLE-userAgent",
    "requestParameters": {
        "displayName": "example-farm",
        "kmsKeyArn": "arn:aws:kms:us-west-2:111122223333:key/111122223333",
        "X-Amz-Client-Token": "12abc12a-1234-1abc-123a-1a11bc1111a",
        "description": "example-description",
        "tags": {
            "purpose_1": "e2e"
            "purpose_2": "tag_test"
        }
    },
    "responseElements": {
        "farmId": "EXAMPLE-farmID"
    },
    "requestID": "EXAMPLE-requestID",
    "eventID": "EXAMPLE-eventID",
    "readOnly": false,
    "eventType": "AwsApiCall",
    "managementEvent": true,
    "recipientAccountId": "111122223333"
    "eventCategory": "Management",
}  
            

The example shows the AWS Region, IP address, and other "requestParameters" such as the "displayName" and "kmsKeyArn" that can help you identify the event.