Access logging

Open the MediaPackage console at https://console.aws.amazon.com/mediapackage/.

Select your channel group from the list of channel groups.

Under Access Logging, do the following:

1. For Log deliveries – Egress Access Logs or Log deliveries – Ingress Access Logs, choose Add, and then do the following:

2. Choose one of the following logging destinations.

   • Amazon CloudWatch Logs

   • Amazon S3

   • Firehose

   Tip

   • If you choose Amazon S3 or Firehose, you can deliver your logs to a Cross account or In current account.

   • To enable cross-account delivery, both AWS accounts must have the required permissions. For more information, see the Cross-account delivery example in the Amazon CloudWatch Logs User Guide.

For the Delivery destination ARN, choose or enter the ARN. If you don't have one already, follow the prompts to create one.

For Additional settings - optional, choose the following:

1. For Field selection, select the log fields to include in each log record.

2. For Output format, choose the output format for the log.

3. For Field delimiter, choose how to separate each log field.

4. (Amazon S3) For Suffix, specify the suffix path to partition your data. You can use the following fields: {accountid}, {region}, {channel_group_id}, {yyyy}, {MM}, {dd}, {HH}

5. (Amazon S3) For Hive-compatible, choose Enable if you want to use Hive-compatible S3 paths.

To apply your changes to all log types, choose Apply to all log types.

To create another log destination, repeat steps 3 – 5.

Follow the prompts to update your channel group.

After you a create a channel group by using either the MediaPackage v2 API or the MediaPackage v2 console, get the Amazon Resource Name (ARN) of the channel group.

You can find the ARN from the Channel groups page in the MediaPackage console or you can use the GetChannel API operation. A channel group ARN follows this format: arn:aws:mediapackagev2:region:123456789012:channelGroup/channelGroupName

Next, use the CloudWatch PutDeliverySource API operation to create a delivery source for the channel group.

1. Pass the resourceArn.

2. For logType, specify ACCESS_LOGS as the type of logs that are collected. ACCESS_LOGS track the current status of files during an ingestion job.

{
    "logType": "ACCESS_LOGS",
    "name": "my-channel-group-source",
    "resourceArn": "arn:aws:mediapackagev2:region:123456789012:channelGroup/channelGroupName"
}

Use the PutDeliveryDestination API operation to configure where to store your logs. You can choose either CloudWatch Logs, Amazon S3, or Firehose as the destination. You must specify the ARN of one of the destination options for where your logs will be stored. You can choose the outputFormat of the logs to be one of the following: json, plain, w3c, raw, parquet.

The following is an example of configuring logs to store in an Amazon S3 bucket and in JSON format.

{
   "deliveryDestinationConfiguration": { 
      "destinationResourceArn": "arn:aws:s3:::amzn-s3-demo-bucket-name"
   },
   "name": "string",
   "outputFormat": "json",
   "tags": { 
      "key" : "value" 
   }
}

Use the CreateDelivery API operation to link the delivery source to the destination that you created in the previous steps. This API operation associates the delivery source with the end destination.

{
   "deliveryDestinationArn": "string",
   "deliverySourceName": "string",
   "tags": { 
      "string" : "string" 
   }
}

Open the MediaPackage console at https://console.aws.amazon.com/mediapackage/.

Select your channel group from the list of channel groups.

In the Access Logging section, select the destination and choose Edit.

Modify the log configuration as needed and then choose Update.

Open the MediaPackage console at https://console.aws.amazon.com/mediapackage/.

Select your channel group from the list of channel groups.

In the Access Logging section, select the destination to disable and choose Remove.

Review your changes and then choose Delete.