feat(client-config-service): Add resourceType enums for AWS::EMR::SecurityConfiguration and AWS::SageMaker::CodeRepository

Author: awstools

clients/client-config-service/src/ConfigService.ts

@@ -2975,11 +2975,11 @@ export class ConfigService extends ConfigServiceClient {
   /**
    * <p>Adds or updates an Config rule for evaluating whether your
    * 			Amazon Web Services resources comply with your desired configurations.</p>
-   * 		       <p>You can use this action for custom Config rules and Config
-   * 			managed rules. A custom Config rule is a rule that you
+   * 		       <p>You can use this action for Config custom rules and Config
+   * 			managed rules. A Config custom rule is a rule that you
    * 			develop and maintain. An Config managed rule is a customizable,
    * 			predefined rule that Config provides.</p>
-   * 		       <p>If you are adding a new custom Config rule, you must first
+   * 		       <p>If you are adding a new Config custom rule, you must first
    * 			create the Lambda function that the rule invokes to evaluate
    * 			your resources. When you use the <code>PutConfigRule</code> action
    * 			to add the rule to Config, you must specify the Amazon Resource
@@ -3295,8 +3295,8 @@ export class ConfigService extends ConfigServiceClient {
    * 			Config verifies the existence of role with <code>GetRole</code> action.</p>
    * 		       <p>To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization
    * 			<code>register-delegated-administrator</code> for <code>config-multiaccountsetup.amazonaws.com</code>. </p>
-   * 		       <p>You can use this action to create both custom Config rules and Config managed rules.
-   * 			If you are adding a new custom Config rule, you must first create Lambda function in the master account or a delegated
+   * 		       <p>You can use this action to create both Config custom rules and Config managed rules.
+   * 			If you are adding a new Config custom rule, you must first create Lambda function in the master account or a delegated
    * 			administrator that the rule invokes to evaluate your resources. You also need to create an IAM role in the managed-account that can be assumed by the Lambda function.
    * 			When you use the <code>PutOrganizationConfigRule</code> action to add the rule to Config, you must
    * 			specify the Amazon Resource Name (ARN) that Lambda assigns to the function.

clients/client-config-service/src/commands/PutConfigRuleCommand.ts

@@ -24,11 +24,11 @@ export interface PutConfigRuleCommandOutput extends __MetadataBearer {}
 /**
  * <p>Adds or updates an Config rule for evaluating whether your
  * 			Amazon Web Services resources comply with your desired configurations.</p>
- * 		       <p>You can use this action for custom Config rules and Config
- * 			managed rules. A custom Config rule is a rule that you
+ * 		       <p>You can use this action for Config custom rules and Config
+ * 			managed rules. A Config custom rule is a rule that you
  * 			develop and maintain. An Config managed rule is a customizable,
  * 			predefined rule that Config provides.</p>
- * 		       <p>If you are adding a new custom Config rule, you must first
+ * 		       <p>If you are adding a new Config custom rule, you must first
  * 			create the Lambda function that the rule invokes to evaluate
  * 			your resources. When you use the <code>PutConfigRule</code> action
  * 			to add the rule to Config, you must specify the Amazon Resource

clients/client-config-service/src/commands/PutOrganizationConfigRuleCommand.ts

@@ -33,8 +33,8 @@ export interface PutOrganizationConfigRuleCommandOutput extends PutOrganizationC
  * 			Config verifies the existence of role with <code>GetRole</code> action.</p>
  * 		       <p>To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization
  * 			<code>register-delegated-administrator</code> for <code>config-multiaccountsetup.amazonaws.com</code>. </p>
- * 		       <p>You can use this action to create both custom Config rules and Config managed rules.
- * 			If you are adding a new custom Config rule, you must first create Lambda function in the master account or a delegated
+ * 		       <p>You can use this action to create both Config custom rules and Config managed rules.
+ * 			If you are adding a new Config custom rule, you must first create Lambda function in the master account or a delegated
  * 			administrator that the rule invokes to evaluate your resources. You also need to create an IAM role in the managed-account that can be assumed by the Lambda function.
  * 			When you use the <code>PutOrganizationConfigRule</code> action to add the rule to Config, you must
  * 			specify the Amazon Resource Name (ARN) that Lambda assigns to the function.

clients/client-config-service/src/models/models_0.ts

@@ -643,6 +643,7 @@ export enum ResourceType {
   EFSFileSystem = "AWS::EFS::FileSystem",
   EIP = "AWS::EC2::EIP",
   EKSCluster = "AWS::EKS::Cluster",
+  EMRSecurityConfiguration = "AWS::EMR::SecurityConfiguration",
   EgressOnlyInternetGateway = "AWS::EC2::EgressOnlyInternetGateway",
   EncryptionConfig = "AWS::XRay::EncryptionConfig",
   Environment = "AWS::ElasticBeanstalk::Environment",
@@ -696,6 +697,7 @@ export enum ResourceType {
   Rule = "AWS::WAF::Rule",
   RuleGroup = "AWS::WAF::RuleGroup",
   RuleGroupV2 = "AWS::WAFv2::RuleGroup",
+  SageMakerCodeRepository = "AWS::SageMaker::CodeRepository",
   ScalingPolicy = "AWS::AutoScaling::ScalingPolicy",
   ScheduledAction = "AWS::AutoScaling::ScheduledAction",
   Secret = "AWS::SecretsManager::Secret",

codegen/sdk-codegen/aws-models/config-service.json

@@ -8583,7 +8583,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>Adds or updates an Config rule for evaluating whether your\n\t\t\tAmazon Web Services resources comply with your desired configurations.</p>\n\t\t       <p>You can use this action for custom Config rules and Config\n\t\t\tmanaged rules. A custom Config rule is a rule that you\n\t\t\tdevelop and maintain. An Config managed rule is a customizable,\n\t\t\tpredefined rule that Config provides.</p>\n\t\t       <p>If you are adding a new custom Config rule, you must first\n\t\t\tcreate the Lambda function that the rule invokes to evaluate\n\t\t\tyour resources. When you use the <code>PutConfigRule</code> action\n\t\t\tto add the rule to Config, you must specify the Amazon Resource\n\t\t\tName (ARN) that Lambda assigns to the function. Specify the ARN\n\t\t\tfor the <code>SourceIdentifier</code> key. This key is part of the\n\t\t\t\t<code>Source</code> object, which is part of the\n\t\t\t\t<code>ConfigRule</code> object. </p>\n\t\t       <p>If you are adding an Config managed rule, specify the\n\t\t\trule's identifier for the <code>SourceIdentifier</code> key. To\n\t\t\treference Config managed rule identifiers, see <a href=\"https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_use-managed-rules.html\">About Config managed rules</a>.</p>\n\t\t       <p>For any new rule that you add, specify the\n\t\t\t\t<code>ConfigRuleName</code> in the <code>ConfigRule</code>\n\t\t\tobject. Do not specify the <code>ConfigRuleArn</code> or the\n\t\t\t<code>ConfigRuleId</code>. These values are generated by Config for new rules.</p>\n\t\t       <p>If you are updating a rule that you added previously, you can\n\t\t\tspecify the rule by <code>ConfigRuleName</code>,\n\t\t\t\t<code>ConfigRuleId</code>, or <code>ConfigRuleArn</code> in the\n\t\t\t\t<code>ConfigRule</code> data type that you use in this\n\t\t\trequest.</p>\n\t\t       <p>The maximum number of rules that Config supports is 150.</p>\n\n\t\t       <p>For information about requesting a rule limit increase, see\n\t\t\t\t<a href=\"http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html#limits_config\">Config Limits</a> in the <i>Amazon Web Services General\n\t\t\t\tReference Guide</i>.</p>\n\n\t\t       <p>For more information about developing and using Config\n\t\t\trules, see <a href=\"https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html\">Evaluating Amazon Web Services resource Configurations with Config</a>\n\t\t\tin the <i>Config Developer Guide</i>.</p>"
+        "smithy.api#documentation": "<p>Adds or updates an Config rule for evaluating whether your\n\t\t\tAmazon Web Services resources comply with your desired configurations.</p>\n\t\t       <p>You can use this action for Config custom rules and Config\n\t\t\tmanaged rules. A Config custom rule is a rule that you\n\t\t\tdevelop and maintain. An Config managed rule is a customizable,\n\t\t\tpredefined rule that Config provides.</p>\n\t\t       <p>If you are adding a new Config custom rule, you must first\n\t\t\tcreate the Lambda function that the rule invokes to evaluate\n\t\t\tyour resources. When you use the <code>PutConfigRule</code> action\n\t\t\tto add the rule to Config, you must specify the Amazon Resource\n\t\t\tName (ARN) that Lambda assigns to the function. Specify the ARN\n\t\t\tfor the <code>SourceIdentifier</code> key. This key is part of the\n\t\t\t\t<code>Source</code> object, which is part of the\n\t\t\t\t<code>ConfigRule</code> object. </p>\n\t\t       <p>If you are adding an Config managed rule, specify the\n\t\t\trule's identifier for the <code>SourceIdentifier</code> key. To\n\t\t\treference Config managed rule identifiers, see <a href=\"https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_use-managed-rules.html\">About Config managed rules</a>.</p>\n\t\t       <p>For any new rule that you add, specify the\n\t\t\t\t<code>ConfigRuleName</code> in the <code>ConfigRule</code>\n\t\t\tobject. Do not specify the <code>ConfigRuleArn</code> or the\n\t\t\t<code>ConfigRuleId</code>. These values are generated by Config for new rules.</p>\n\t\t       <p>If you are updating a rule that you added previously, you can\n\t\t\tspecify the rule by <code>ConfigRuleName</code>,\n\t\t\t\t<code>ConfigRuleId</code>, or <code>ConfigRuleArn</code> in the\n\t\t\t\t<code>ConfigRule</code> data type that you use in this\n\t\t\trequest.</p>\n\t\t       <p>The maximum number of rules that Config supports is 150.</p>\n\n\t\t       <p>For information about requesting a rule limit increase, see\n\t\t\t\t<a href=\"http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html#limits_config\">Config Limits</a> in the <i>Amazon Web Services General\n\t\t\t\tReference Guide</i>.</p>\n\n\t\t       <p>For more information about developing and using Config\n\t\t\trules, see <a href=\"https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html\">Evaluating Amazon Web Services resource Configurations with Config</a>\n\t\t\tin the <i>Config Developer Guide</i>.</p>"
       }
     },
     "com.amazonaws.configservice#PutConfigRuleRequest": {
@@ -8989,7 +8989,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>Adds or updates organization Config rule for your entire organization evaluating whether your Amazon Web Services resources comply with your \n\t\t\tdesired configurations.</p>\n\t        <p> Only a master account and a delegated administrator can create or update an organization Config rule.\n\t\tWhen calling this API with a delegated administrator, you must ensure Organizations \n\t\t<code>ListDelegatedAdministrator</code> permissions are added. </p>\n\t\t       <p>This API enables organization service access through the <code>EnableAWSServiceAccess</code> action and creates a service linked \n\t\t\trole <code>AWSServiceRoleForConfigMultiAccountSetup</code> in the master or delegated administrator account of your organization. \n\t\t\tThe service linked role is created only when the role does not exist in the caller account. \n\t\t\tConfig verifies the existence of role with <code>GetRole</code> action.</p>\n\t\t       <p>To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization\n\t\t\t<code>register-delegated-administrator</code> for <code>config-multiaccountsetup.amazonaws.com</code>. </p>\n\t\t       <p>You can use this action to create both custom Config rules and Config managed rules. \n\t\t\tIf you are adding a new custom Config rule, you must first create Lambda function in the master account or a delegated \n\t\t\tadministrator that the rule invokes to evaluate your resources. You also need to create an IAM role in the managed-account that can be assumed by the Lambda function.\n\t\t\tWhen you use the <code>PutOrganizationConfigRule</code> action to add the rule to Config, you must \n\t\t\tspecify the Amazon Resource Name (ARN) that Lambda assigns to the function. \n\t\t\tIf you are adding an Config managed rule, specify the rule's identifier for the <code>RuleIdentifier</code> key.</p>\n\t\t       <p>The maximum number of organization Config rules that Config supports is 150 and 3 delegated administrator per organization. </p>\n\t\t       <note>\n            <p>Prerequisite: Ensure you call <code>EnableAllFeatures</code> API to enable all features in an organization.</p>\n\t\t\t         <p>Specify either <code>OrganizationCustomRuleMetadata</code> or <code>OrganizationManagedRuleMetadata</code>.</p>\n\t\t\t      </note>"
+        "smithy.api#documentation": "<p>Adds or updates organization Config rule for your entire organization evaluating whether your Amazon Web Services resources comply with your \n\t\t\tdesired configurations.</p>\n\t        <p> Only a master account and a delegated administrator can create or update an organization Config rule.\n\t\tWhen calling this API with a delegated administrator, you must ensure Organizations \n\t\t<code>ListDelegatedAdministrator</code> permissions are added. </p>\n\t\t       <p>This API enables organization service access through the <code>EnableAWSServiceAccess</code> action and creates a service linked \n\t\t\trole <code>AWSServiceRoleForConfigMultiAccountSetup</code> in the master or delegated administrator account of your organization. \n\t\t\tThe service linked role is created only when the role does not exist in the caller account. \n\t\t\tConfig verifies the existence of role with <code>GetRole</code> action.</p>\n\t\t       <p>To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization\n\t\t\t<code>register-delegated-administrator</code> for <code>config-multiaccountsetup.amazonaws.com</code>. </p>\n\t\t       <p>You can use this action to create both Config custom rules and Config managed rules. \n\t\t\tIf you are adding a new Config custom rule, you must first create Lambda function in the master account or a delegated \n\t\t\tadministrator that the rule invokes to evaluate your resources. You also need to create an IAM role in the managed-account that can be assumed by the Lambda function.\n\t\t\tWhen you use the <code>PutOrganizationConfigRule</code> action to add the rule to Config, you must \n\t\t\tspecify the Amazon Resource Name (ARN) that Lambda assigns to the function. \n\t\t\tIf you are adding an Config managed rule, specify the rule's identifier for the <code>RuleIdentifier</code> key.</p>\n\t\t       <p>The maximum number of organization Config rules that Config supports is 150 and 3 delegated administrator per organization. </p>\n\t\t       <note>\n            <p>Prerequisite: Ensure you call <code>EnableAllFeatures</code> API to enable all features in an organization.</p>\n\t\t\t         <p>Specify either <code>OrganizationCustomRuleMetadata</code> or <code>OrganizationManagedRuleMetadata</code>.</p>\n\t\t\t      </note>"
       }
     },
     "com.amazonaws.configservice#PutOrganizationConfigRuleRequest": {
@@ -10695,6 +10695,14 @@
           {
             "value": "AWS::GuardDuty::Detector",
             "name": "GuardDutyDetector"
+          },
+          {
+            "value": "AWS::EMR::SecurityConfiguration",
+            "name": "EMRSecurityConfiguration"
+          },
+          {
+            "value": "AWS::SageMaker::CodeRepository",
+            "name": "SageMakerCodeRepository"
           }
         ]
       }