feat(client-oam): This release adds support for sharing AWS::ApplicationSignals::Service and AWS::ApplicationSignals::ServiceLevelObjective resources.

Author: awstools

clients/client-oam/README.md

@@ -10,13 +10,17 @@ AWS SDK for JavaScript OAM Client for Node.js, Browser and React Native.
 monitoring accounts by using <i>CloudWatch cross-account observability</i>. 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, and Application Insights applications in any of the linked accounts without account boundaries.</p>
+logs, traces, Application Signals services, service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p>
 <p>Set up one or more Amazon Web Services accounts as <i>monitoring
 accounts</i> and link them with multiple <i>source accounts</i>. 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, and applications in Amazon CloudWatch Application Insights.</p>
+observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray,  Application Signals services, service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors
+in CloudWatch Internet Monitor.</p>
+<p>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.
+</p>
 
 ## Installing
 

clients/client-oam/src/OAM.ts

@@ -243,13 +243,17 @@ export interface OAM {
  *       monitoring accounts by using <i>CloudWatch cross-account observability</i>. 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, and Application Insights applications in any of the linked accounts without account boundaries.</p>
+ *       logs, traces, Application Signals services, service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p>
  *          <p>Set up one or more Amazon Web Services accounts as <i>monitoring
  *         accounts</i> and link them with multiple <i>source accounts</i>. 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, and applications in Amazon CloudWatch Application Insights.</p>
+ *       observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray,  Application Signals services, service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors
+ *        in CloudWatch Internet Monitor.</p>
+ *          <p>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.
+ *      </p>
  * @public
  */
 export class OAM extends OAMClient implements OAM {}

clients/client-oam/src/OAMClient.ts

@@ -317,13 +317,17 @@ export interface OAMClientResolvedConfig extends OAMClientResolvedConfigType {}
  *       monitoring accounts by using <i>CloudWatch cross-account observability</i>. 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, and Application Insights applications in any of the linked accounts without account boundaries.</p>
+ *       logs, traces, Application Signals services, service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p>
  *          <p>Set up one or more Amazon Web Services accounts as <i>monitoring
  *         accounts</i> and link them with multiple <i>source accounts</i>. 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, and applications in Amazon CloudWatch Application Insights.</p>
+ *       observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray,  Application Signals services, service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors
+ *        in CloudWatch Internet Monitor.</p>
+ *          <p>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.
+ *      </p>
  * @public
  */
 export class OAMClient extends __Client<

clients/client-oam/src/commands/CreateLinkCommand.ts

@@ -49,7 +49,7 @@ export interface CreateLinkCommandOutput extends CreateLinkOutput, __MetadataBea
  * const input = { // CreateLinkInput
  *   LabelTemplate: "STRING_VALUE", // required
  *   ResourceTypes: [ // ResourceTypesInput // required
- *     "AWS::CloudWatch::Metric" || "AWS::Logs::LogGroup" || "AWS::XRay::Trace" || "AWS::ApplicationInsights::Application" || "AWS::InternetMonitor::Monitor",
+ *     "AWS::CloudWatch::Metric" || "AWS::Logs::LogGroup" || "AWS::XRay::Trace" || "AWS::ApplicationInsights::Application" || "AWS::InternetMonitor::Monitor" || "AWS::ApplicationSignals::Service" || "AWS::ApplicationSignals::ServiceLevelObjective",
  *   ],
  *   SinkIdentifier: "STRING_VALUE", // required
  *   Tags: { // TagMapInput

clients/client-oam/src/commands/UpdateLinkCommand.ts

@@ -43,7 +43,7 @@ export interface UpdateLinkCommandOutput extends UpdateLinkOutput, __MetadataBea
  * const input = { // UpdateLinkInput
  *   Identifier: "STRING_VALUE", // required
  *   ResourceTypes: [ // ResourceTypesInput // required
- *     "AWS::CloudWatch::Metric" || "AWS::Logs::LogGroup" || "AWS::XRay::Trace" || "AWS::ApplicationInsights::Application" || "AWS::InternetMonitor::Monitor",
+ *     "AWS::CloudWatch::Metric" || "AWS::Logs::LogGroup" || "AWS::XRay::Trace" || "AWS::ApplicationInsights::Application" || "AWS::InternetMonitor::Monitor" || "AWS::ApplicationSignals::Service" || "AWS::ApplicationSignals::ServiceLevelObjective",
  *   ],
  *   LinkConfiguration: { // LinkConfiguration
  *     LogGroupConfiguration: { // LogGroupConfiguration

clients/client-oam/src/index.ts

@@ -5,13 +5,17 @@
  *       monitoring accounts by using <i>CloudWatch cross-account observability</i>. 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, and Application Insights applications in any of the linked accounts without account boundaries.</p>
+ *       logs, traces, Application Signals services, service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p>
  *          <p>Set up one or more Amazon Web Services accounts as <i>monitoring
  *         accounts</i> and link them with multiple <i>source accounts</i>. 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, and applications in Amazon CloudWatch Application Insights.</p>
+ *       observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray,  Application Signals services, service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors
+ *        in CloudWatch Internet Monitor.</p>
+ *          <p>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.
+ *      </p>
  *
  * @packageDocumentation
  */

clients/client-oam/src/models/models_0.ts

@@ -183,6 +183,8 @@ export interface LinkConfiguration {
  */
 export const ResourceType = {
   AWS_APPLICATIONINSIGHTS_APPLICATION: "AWS::ApplicationInsights::Application",
+  AWS_APPLICATION_SIGNALS_SERVICE: "AWS::ApplicationSignals::Service",
+  AWS_APPLICATION_SIGNALS_SLO: "AWS::ApplicationSignals::ServiceLevelObjective",
   AWS_CLOUDWATCH_METRIC: "AWS::CloudWatch::Metric",
   AWS_INTERNETMONITOR_MONITOR: "AWS::InternetMonitor::Monitor",
   AWS_LOGS_LOGGROUP: "AWS::Logs::LogGroup",

codegen/sdk-codegen/aws-models/oam.json

@@ -1317,6 +1317,18 @@
           "traits": {
             "smithy.api#enumValue": "AWS::InternetMonitor::Monitor"
           }
+        },
+        "AWS_APPLICATION_SIGNALS_SERVICE": {
+          "target": "smithy.api#Unit",
+          "traits": {
+            "smithy.api#enumValue": "AWS::ApplicationSignals::Service"
+          }
+        },
+        "AWS_APPLICATION_SIGNALS_SLO": {
+          "target": "smithy.api#Unit",
+          "traits": {
+            "smithy.api#enumValue": "AWS::ApplicationSignals::ServiceLevelObjective"
+          }
         }
       }
     },
@@ -1763,7 +1775,7 @@
         "smithy.api#cors": {
           "additionalAllowedHeaders": ["Content-Type", "X-Amz-Requested-Operation"]
         },
-        "smithy.api#documentation": "<p>Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and\n      monitoring accounts by using <i>CloudWatch cross-account observability</i>. With\n        CloudWatch cross-account observability, you can monitor and troubleshoot applications that span\n      multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics,\n      logs, traces, and Application Insights applications in any of the linked accounts without account boundaries.</p>\n         <p>Set up one or more Amazon Web Services accounts as <i>monitoring\n        accounts</i> and link them with multiple <i>source accounts</i>. A\n      monitoring account is a central Amazon Web Services account that can view and interact with\n      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.\n      Source accounts share their observability data with the monitoring account. The shared\n      observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray, and applications in Amazon CloudWatch Application Insights.</p>",
+        "smithy.api#documentation": "<p>Use Amazon CloudWatch Observability Access Manager to create and manage links between source accounts and\n      monitoring accounts by using <i>CloudWatch cross-account observability</i>. With\n        CloudWatch cross-account observability, you can monitor and troubleshoot applications that span\n      multiple accounts within a Region. Seamlessly search, visualize, and analyze your metrics,\n      logs, traces, Application Signals services, service level objectives (SLOs), Application Insights applications, and internet monitors in any of the linked accounts without account boundaries.</p>\n         <p>Set up one or more Amazon Web Services accounts as <i>monitoring\n        accounts</i> and link them with multiple <i>source accounts</i>. A\n      monitoring account is a central Amazon Web Services account that can view and interact with\n      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.\n      Source accounts share their observability data with the monitoring account. The shared\n      observability data can include metrics in Amazon CloudWatch, logs in Amazon CloudWatch Logs, traces in X-Ray,  Application Signals services, service level objectives (SLOs), applications in Amazon CloudWatch Application Insights, and internet monitors\n       in CloudWatch Internet Monitor.</p>\n         <p>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. \n       And for CloudWatch Logs, you can choose to share all log groups with the monitoring account, or filter to a subset of log groups.\n     </p>",
         "smithy.api#title": "CloudWatch Observability Access Manager",
         "smithy.rules#endpointRuleSet": {
           "version": "1.0",