Release v1.36.33 (2021-01-27) (#3757)

Release v1.36.33 (2021-01-27)
===

### Service Client Updates
* `service/accessanalyzer`: Updates service API and documentation
* `service/customer-profiles`: Updates service API
* `service/elasticache`: Updates service API and documentation
  * Add support to pass ParameterGroup name as part updating Engine Version of Global Datastore.
* `service/es`: Updates service API and documentation
  * Amazon Elasticsearch Service adds support for node-to-node encryption and encryption at rest for existing domains running Elasticsearch version 6.7 and above
* `service/lightsail`: Updates service documentation
  * Documentation updates for Lightsail
* `service/sesv2`: Updates service API and documentation

Author: aws-sdk-go-automation

CHANGELOG.md

@@ -1,3 +1,17 @@
+Release v1.36.33 (2021-01-27)
+===
+
+### Service Client Updates
+* `service/accessanalyzer`: Updates service API and documentation
+* `service/customer-profiles`: Updates service API
+* `service/elasticache`: Updates service API and documentation
+  * Add support to pass ParameterGroup name as part updating Engine Version of Global Datastore.
+* `service/es`: Updates service API and documentation
+  * Amazon Elasticsearch Service adds support for node-to-node encryption and encryption at rest for existing domains running Elasticsearch version 6.7 and above
+* `service/lightsail`: Updates service documentation
+  * Documentation updates for Lightsail
+* `service/sesv2`: Updates service API and documentation
+
 Release v1.36.32 (2021-01-26)
 ===
 

aws/endpoints/defaults.go

@@ -5,4 +5,4 @@ package aws
 const SDKName = "aws-sdk-go"
 
 // SDKVersion is the version of this SDK
-const SDKVersion = "1.36.32"
+const SDKVersion = "1.36.33"

aws/version.go

@@ -1002,7 +1002,8 @@
         "AWS::SQS::Queue",
         "AWS::Lambda::Function",
         "AWS::Lambda::LayerVersion",
-        "AWS::KMS::Key"
+        "AWS::KMS::Key",
+        "AWS::SecretsManager::Secret"
       ]
     },
     "ServiceQuotaExceededException":{

models/apis/accessanalyzer/2019-11-01/api-2.json

@@ -5,7 +5,7 @@
     "ApplyArchiveRule": "<p>Retroactively applies the archive rule to existing findings that meet the archive rule criteria.</p>",
     "CreateAnalyzer": "<p>Creates an analyzer for your account.</p>",
     "CreateArchiveRule": "<p>Creates an archive rule for the specified analyzer. Archive rules automatically archive new findings that meet the criteria you define when you create the rule.</p>",
-    "DeleteAnalyzer": "<p>Deletes the specified analyzer. When you delete an analyzer, Access Analyzer is disabled for the account in the current or specific Region. All findings that were generated by the analyzer are deleted. You cannot undo this action.</p>",
+    "DeleteAnalyzer": "<p>Deletes the specified analyzer. When you delete an analyzer, Access Analyzer is disabled for the account or organization in the current or specific Region. All findings that were generated by the analyzer are deleted. You cannot undo this action.</p>",
     "DeleteArchiveRule": "<p>Deletes the specified archive rule.</p>",
     "GetAnalyzedResource": "<p>Retrieves information about a resource that was analyzed.</p>",
     "GetAnalyzer": "<p>Retrieves information about the specified analyzer.</p>",
@@ -71,7 +71,7 @@
     "AnalyzerStatus": {
       "base": null,
       "refs": {
-        "AnalyzerSummary$status": "<p>The status of the analyzer. An <code>Active</code> analyzer successfully monitors supported resources and generates new findings. The analyzer is <code>Disabled</code> when a user action, such as removing trusted access for IAM Access Analyzer from AWS Organizations, causes the analyzer to stop generating new findings. The status is <code>Creating</code> when the analyzer creation is in progress and <code>Failed</code> when the analyzer creation has failed. </p>"
+        "AnalyzerSummary$status": "<p>The status of the analyzer. An <code>Active</code> analyzer successfully monitors supported resources and generates new findings. The analyzer is <code>Disabled</code> when a user action, such as removing trusted access for AWS IAM Access Analyzer from AWS Organizations, causes the analyzer to stop generating new findings. The status is <code>Creating</code> when the analyzer creation is in progress and <code>Failed</code> when the analyzer creation has failed. </p>"
       }
     },
     "AnalyzerSummary": {
@@ -568,7 +568,7 @@
       "base": null,
       "refs": {
         "AnalyzerSummary$type": "<p>The type of analyzer, which corresponds to the zone of trust chosen for the analyzer.</p>",
-        "CreateAnalyzerRequest$type": "<p>The type of analyzer to create. Only ACCOUNT analyzers are supported. You can create only one analyzer per account per Region.</p>",
+        "CreateAnalyzerRequest$type": "<p>The type of analyzer to create. Only ACCOUNT and ORGANIZATION analyzers are supported. You can create only one analyzer per account per Region. You can create up to 5 analyzers per organization per Region.</p>",
         "ListAnalyzersRequest$type": "<p>The type of analyzer.</p>"
       }
     },

models/apis/accessanalyzer/2019-11-01/docs-2.json

@@ -620,7 +620,10 @@
     },
     "DeleteIntegrationRequest":{
       "type":"structure",
-      "required":["DomainName"],
+      "required":[
+        "DomainName",
+        "Uri"
+      ],
       "members":{
         "DomainName":{
           "shape":"name",
@@ -805,7 +808,10 @@
     },
     "GetIntegrationRequest":{
       "type":"structure",
-      "required":["DomainName"],
+      "required":[
+        "DomainName",
+        "Uri"
+      ],
       "members":{
         "DomainName":{
           "shape":"name",

models/apis/customer-profiles/2020-08-15/api-2.json

@@ -2982,6 +2982,7 @@
         "ApplyImmediately":{"shape":"Boolean"},
         "CacheNodeType":{"shape":"String"},
         "EngineVersion":{"shape":"String"},
+        "CacheParameterGroupName":{"shape":"String"},
         "GlobalReplicationGroupDescription":{"shape":"String"},
         "AutomaticFailoverEnabled":{"shape":"BooleanOptional"}
       }