« blib/lib/Paws/AppStream/CreateUsageReportSubscription.pm
↑ Summary
blib/lib/Paws/AppStream/CreateUser.pm »
| 1 | |||
| 2 | package Paws::AppStream::CreateUsageReportSubscriptionResult; | ||
| 3 | use Moose; | ||
| 4 | has S3BucketName => (is => 'ro', isa => 'Str'); | ||
| 5 | has Schedule => (is => 'ro', isa => 'Str'); | ||
| 6 | |||
| 7 | has _request_id => (is => 'ro', isa => 'Str'); | ||
| 8 | |||
| 9 | ### main pod documentation begin ### | ||
| 10 | |||
| 11 | =head1 NAME | ||
| 12 | |||
| 13 | Paws::AppStream::CreateUsageReportSubscriptionResult | ||
| 14 | |||
| 15 | =head1 ATTRIBUTES | ||
| 16 | |||
| 17 | |||
| 18 | =head2 S3BucketName => Str | ||
| 19 | |||
| 20 | The Amazon S3 bucket where generated reports are stored. | ||
| 21 | |||
| 22 | If you enabled on-instance session scripts and Amazon S3 logging for | ||
| 23 | your session script configuration, AppStream 2.0 created an S3 bucket | ||
| 24 | to store the script output. The bucket is unique to your account and | ||
| 25 | Region. When you enable usage reporting in this case, AppStream 2.0 | ||
| 26 | uses the same bucket to store your usage reports. If you haven't | ||
| 27 | already enabled on-instance session scripts, when you enable usage | ||
| 28 | reports, AppStream 2.0 creates a new S3 bucket. | ||
| 29 | |||
| 30 | |||
| 31 | =head2 Schedule => Str | ||
| 32 | |||
| 33 | The schedule for generating usage reports. | ||
| 34 | |||
| 35 | Valid values are: C<"DAILY"> | ||
| 36 | =head2 _request_id => Str | ||
| 37 | |||
| 38 | |||
| 39 | =cut | ||
| 40 | |||
| 41 | 1; |