OamClient
Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and monitoring accounts by using CloudWatch cross-account observability. With CloudWatch cross-account observability, you can monitor and troubleshoot applications that span multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics, logs, traces, Application Signals services and service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.
Set up one or more Amazon Web Services accounts as monitoring accounts and link them with multiple source accounts. A monitoring account is a central Amazon Web Services account that can view and interact with observability data generated from source accounts. A source account is an individual Amazon Web Services account that generates observability data for the resources that reside in it. Source accounts share their observability data with the monitoring account. The shared observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray, Application Signals services and service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors in CloudWatch Internet Monitor.
When you set up a link, you can choose to share the metrics from all namespaces with the monitoring account, or filter to a subset of namespaces. And for CloudWatch Logs, you can choose to share all log groups with the monitoring account, or filter to a subset of log groups.
Functions
Creates a link between a source account and a sink that you have created in a monitoring account. After the link is created, data is sent from the source account to the monitoring account. When you create a link, you can optionally specify filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account.
Use this to create a sink in the current account, so that it can be used as a monitoring account in CloudWatch cross-account observability. A sink is a resource that represents an attachment point in a monitoring account. Source accounts can link to the sink to send observability data.
Deletes a link between a monitoring account sink and a source account. You must run this operation in the source account.
Deletes a sink. You must delete all links to a sink before you can delete that sink.
Returns complete information about one link.
Returns complete information about one monitoring account sink.
Returns the current sink policy attached to this sink. The sink policy specifies what accounts can attach to this sink as source accounts, and what types of data they can share.
Returns a list of source account links that are linked to this monitoring account sink.
Use this operation in a source account to return a list of links to monitoring account sinks that this source account has.
Use this operation in a monitoring account to return the list of sinks created in that account.
Displays the tags associated with a resource. Both sinks and links support tagging.
Creates or updates the resource policy that grants permissions to source accounts to link to the monitoring account sink. When you create a sink policy, you can grant permissions to all accounts in an organization or to individual accounts.
Assigns one or more tags (key-value pairs) to the specified resource. Both sinks and links can be tagged.
Removes one or more tags from the specified resource.
Use this operation to change what types of data are shared from a source account to its linked monitoring account sink. You can't change the sink or change the monitoring account with this operation.
Inherited functions
Creates a link between a source account and a sink that you have created in a monitoring account. After the link is created, data is sent from the source account to the monitoring account. When you create a link, you can optionally specify filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account.
Use this to create a sink in the current account, so that it can be used as a monitoring account in CloudWatch cross-account observability. A sink is a resource that represents an attachment point in a monitoring account. Source accounts can link to the sink to send observability data.
Deletes a link between a monitoring account sink and a source account. You must run this operation in the source account.
Deletes a sink. You must delete all links to a sink before you can delete that sink.
Returns complete information about one link.
Returns complete information about one monitoring account sink.
Returns the current sink policy attached to this sink. The sink policy specifies what accounts can attach to this sink as source accounts, and what types of data they can share.
Returns a list of source account links that are linked to this monitoring account sink.
Paginate over ListAttachedLinksResponse results.
Use this operation in a source account to return a list of links to monitoring account sinks that this source account has.
Paginate over ListLinksResponse results.
Use this operation in a monitoring account to return the list of sinks created in that account.
Paginate over ListSinksResponse results.
Displays the tags associated with a resource. Both sinks and links support tagging.
Creates or updates the resource policy that grants permissions to source accounts to link to the monitoring account sink. When you create a sink policy, you can grant permissions to all accounts in an organization or to individual accounts.
Assigns one or more tags (key-value pairs) to the specified resource. Both sinks and links can be tagged.
Removes one or more tags from the specified resource.
Use this operation to change what types of data are shared from a source account to its linked monitoring account sink. You can't change the sink or change the monitoring account with this operation.
Create a copy of the client with one or more configuration values overridden. This method allows the caller to perform scoped config overrides for one or more client operations.