Skip to content

(aws-logs): Incorrect descriptions for involvement of CrossAccountDestination #36585

@taesungh

Description

@taesungh

Describe the issue

Related to #6884, pointed out before in incomplete PR #20582:

Previously in #2655, constructs for CloudWatch Logs Subscription Destinations were moved to aws-logs-destinations, but there's some leftover inaccurate descriptions of using CrossAccountDestination: the docs indicate the constructs for Kinesis handle cross-account usage and suggestion consumers shouldn't need to use said construct, but there are no remaining supporting code references for such.

Would appreciate the construct itself being fixed, but that's out of scope.

Links

aws-cdk-lib.aws_logs module Overview

If the Kinesis stream lives in a different account, a CrossAccountDestination object needs to be added in the destination account which will act as a proxy for the remote Kinesis stream. This object is automatically created for you if you use the CDK Kinesis library.

class CrossAccountDestination (construct)

Consumers will hardly ever need to use this class. Instead, directly subscribe a Kinesis stream using the integration class in the aws-cdk-lib/aws-logs-destinations package; if necessary, a CrossAccountDestination will be created automatically.

Metadata

Metadata

Assignees

No one assigned

    Labels

    @aws-cdk/aws-logsRelated to Amazon CloudWatch LogsdocumentationThis is a problem with documentation.effort/smallSmall work item – less than a day of effortgood first issueRelated to contributions. See CONTRIBUTING.mdp3

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions