aws · awstools · Aug 8, 2018 · Aug 8, 2018
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,12 @@
+Release v1.15.8 (2018-08-08)
+===
+
+### Service Client Updates
+* `service/secretsmanager`: Updates service API and documentation
+ * This release introduces a ForceDeleteWithoutRecovery parameter to the DeleteSecret API enabling customers to force the deletion of a secret without any recovery window
+* `service/ssm`: Updates service API and documentation
+ * AWS Systems Manager Automation is launching two new features for Automation Execution Rate Control based on tags and customized parameter maps. With the first feature, customer can target their resources by specifying a Tag with Key/Value. With the second feature, Parameter maps rate control, customers can benefit from customization of input parameters.
+
 Release v1.15.7 (2018-08-07)
 ===
 

diff --git a/aws/version.go b/aws/version.go
@@ -5,4 +5,4 @@ package aws
 const SDKName = "aws-sdk-go"
 
 // SDKVersion is the version of this SDK
-const SDKVersion = "1.15.7"
+const SDKVersion = "1.15.8"
diff --git a/models/apis/secretsmanager/2017-10-17/api-2.json b/models/apis/secretsmanager/2017-10-17/api-2.json
@@ -372,6 +372,10 @@
  "RecoveryWindowInDays":{
  "shape":"RecoveryWindowInDaysType",
  "box":true
+ },
+ "ForceDeleteWithoutRecovery":{
+ "shape":"BooleanType",
+ "box":true
  }
  }
  },

diff --git a/models/apis/secretsmanager/2017-10-17/docs-2.json b/models/apis/secretsmanager/2017-10-17/docs-2.json
diff --git a/models/apis/ssm/2014-11-06/api-2.json b/models/apis/ssm/2014-11-06/api-2.json
@@ -1962,6 +1962,7 @@
  "CurrentAction":{"shape":"String"},
  "TargetParameterName":{"shape":"AutomationParameterKey"},
  "Targets":{"shape":"Targets"},
+ "TargetMaps":{"shape":"TargetMaps"},
  "ResolvedTargets":{"shape":"ResolvedTargets"},
  "MaxConcurrency":{"shape":"MaxConcurrency"},
  "MaxErrors":{"shape":"MaxErrors"},
@@ -2039,6 +2040,7 @@
  "FailureMessage":{"shape":"String"},
  "TargetParameterName":{"shape":"AutomationParameterKey"},
  "Targets":{"shape":"Targets"},
+ "TargetMaps":{"shape":"TargetMaps"},
  "ResolvedTargets":{"shape":"ResolvedTargets"},
  "MaxConcurrency":{"shape":"MaxConcurrency"},
  "MaxErrors":{"shape":"MaxErrors"},
@@ -2194,20 +2196,17 @@
  "enum":[
  "InvokedAfter",
  "InvokedBefore",
- "Status",
- "ExecutionStage",
- "DocumentName"
+ "Status"
  ]
  },
  "CommandFilterList":{
  "type":"list",
  "member":{"shape":"CommandFilter"},
- "max":5,
+ "max":3,
  "min":1
  },
  "CommandFilterValue":{
  "type":"string",
- "max":128,
  "min":1
  },
  "CommandId":{
@@ -6840,6 +6839,7 @@
  "Mode":{"shape":"ExecutionMode"},
  "TargetParameterName":{"shape":"AutomationParameterKey"},
  "Targets":{"shape":"Targets"},
+ "TargetMaps":{"shape":"TargetMaps"},
  "MaxConcurrency":{"shape":"MaxConcurrency"},
  "MaxErrors":{"shape":"MaxErrors"}
  }
@@ -7038,6 +7038,35 @@
  "min":1,
  "pattern":"^[\\p{L}\\p{Z}\\p{N}_.:/=\\-@]*$"
  },
+ "TargetMap":{
+ "type":"map",
+ "key":{"shape":"TargetMapKey"},
+ "value":{"shape":"TargetMapValueList"},
+ "max":20,
+ "min":1
+ },
+ "TargetMapKey":{
+ "type":"string",
+ "max":50,
+ "min":1
+ },
+ "TargetMapValue":{
+ "type":"string",
+ "max":50,
+ "min":1
+ },
+ "TargetMapValueList":{
+ "type":"list",
+ "member":{"shape":"TargetMapValue"},
+ "max":25,
+ "min":0
+ },
+ "TargetMaps":{
+ "type":"list",
+ "member":{"shape":"TargetMap"},
+ "max":300,
+ "min":0
+ },
  "TargetParameterList":{
  "type":"list",
  "member":{"shape":"ParameterValue"}

diff --git a/models/apis/ssm/2014-11-06/docs-2.json b/models/apis/ssm/2014-11-06/docs-2.json
@@ -766,7 +766,7 @@
  "CommandFilterValue": {
  "base": null,
  "refs": {
- "CommandFilter$value": "<p>The filter value. Valid values for each filter key are as follows:</p> <ul> <li> <p> <b>InvokedAfter</b>: Specify a timestamp to limit your results. For example, specify <code>2018-07-07T00:00:00Z</code> to see a list of command executions occurring July 7, 2018, and later.</p> </li> <li> <p> <b>InvokedBefore</b>: Specify a timestamp to limit your results. For example, specify <code>2018-07-07T00:00:00Z</code> to see a list of command executions from before July 7, 2018.</p> </li> <li> <p> <b>Status</b>: Specify a valid command status to see a list of all command executions with that status. Status values you can specify include:</p> <ul> <li> <p> <code>Pending</code> </p> </li> <li> <p> <code>InProgress</code> </p> </li> <li> <p> <code>Success</code> </p> </li> <li> <p> <code>Cancelled</code> </p> </li> <li> <p> <code>Failed</code> </p> </li> <li> <p> <code>TimedOut</code> </p> </li> <li> <p> <code>Cancelling</code> </p> </li> </ul> </li> <li> <p> <b>DocumentName</b>: Specify name of the SSM document for which you want to see command execution results. For example, specify <code>AWS-RunPatchBaseline</code> to see command executions that used this SSM document to perform security patching operations on instances. </p> </li> <li> <p> <b>ExecutionStage</b>: Specify one of the following values:</p> <ul> <li> <p> <code>Executing</code>: Returns a list of command executions that are currently still running.</p> </li> <li> <p> <code>Complete</code>: Returns a list of command exeuctions that have already completed. </p> </li> </ul> </li> </ul>"
+ "CommandFilter$value": "<p>The filter value. </p>"
  }
  },
  "CommandId": {
@@ -5001,9 +5001,9 @@
  "GetMaintenanceWindowTaskResult$ServiceRoleArn": "<p>The IAM service role to assume during task execution.</p>",
  "MaintenanceWindowRunCommandParameters$ServiceRoleArn": "<p>The IAM service role to assume during task execution.</p>",
  "MaintenanceWindowTask$ServiceRoleArn": "<p>The role that should be assumed when executing the task</p>",
- "RegisterTaskWithMaintenanceWindowRequest$ServiceRoleArn": "<p>The role that should be assumed when executing the task.</p>",
+ "RegisterTaskWithMaintenanceWindowRequest$ServiceRoleArn": "<p>The role to assume when running the Maintenance Window task.</p> <p>If you do not specify a service role ARN, Systems Manager will use your account's service-linked role for Systems Manager by default. If no service-linked role for Systems Manager exists in your account, it will be created when you run <code>RegisterTaskWithMaintenanceWindow</code> without specifying a service role ARN.</p> <p>For more information, see <a href=\"http:https://docs.aws.amazon.com/systems-manager/latest/userguide/using-service-linked-roles.html#slr-permissions\">Service-Linked Role Permissions for Systems Manager</a> and <a href=\"http:https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-maintenance-permissions.html#maintenance-window-tasks-service-role\">Should I Use a Service-Linked Role or a Custom Service Role to Run Maintenance Window Tasks? </a> in the <i>AWS Systems Manager User Guide</i>.</p>",
  "SendCommandRequest$ServiceRoleArn": "<p>The IAM role that Systems Manager uses to send notifications. </p>",
- "UpdateMaintenanceWindowTaskRequest$ServiceRoleArn": "<p>The IAM service role ARN to modify. The system assumes this role during task execution. </p>",
+ "UpdateMaintenanceWindowTaskRequest$ServiceRoleArn": "<p>The IAM service role ARN to modify. The system assumes this role during task execution.</p> <p>If you do not specify a service role ARN, Systems Manager will use your account's service-linked role for Systems Manager by default. If no service-linked role for Systems Manager exists in your account, it will be created when you run <code>RegisterTaskWithMaintenanceWindow</code> without specifying a service role ARN.</p> <p>For more information, see <a href=\"http:https://docs.aws.amazon.com/systems-manager/latest/userguide/using-service-linked-roles.html#slr-permissions\">Service-Linked Role Permissions for Systems Manager</a> and <a href=\"http:https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-maintenance-permissions.html#maintenance-window-tasks-service-role\">Should I Use a Service-Linked Role or a Custom Service Role to Run Maintenance Window Tasks? </a> in the <i>AWS Systems Manager User Guide</i>.</p>",
  "UpdateMaintenanceWindowTaskResult$ServiceRoleArn": "<p>The updated service role ARN value.</p>"
  }
  },
@@ -5353,6 +5353,38 @@
  "Target$Key": "<p>User-defined criteria for sending commands that target instances that meet the criteria. Key can be tag:&lt;Amazon EC2 tag&gt; or InstanceIds. For more information about how to send commands that target instances using Key,Value parameters, see <a href=\"http:https://docs.aws.amazon.com/systems-manager/latest/userguide/send-commands-multiple.html#send-commands-targeting\">Targeting Multiple Instances</a> in the <i>AWS Systems Manager User Guide</i>.</p>"
  }
  },
+ "TargetMap": {
+ "base": null,
+ "refs": {
+ "TargetMaps$member": null
+ }
+ },
+ "TargetMapKey": {
+ "base": null,
+ "refs": {
+ "TargetMap$key": null
+ }
+ },
+ "TargetMapValue": {
+ "base": null,
+ "refs": {
+ "TargetMapValueList$member": null
+ }
+ },
+ "TargetMapValueList": {
+ "base": null,
+ "refs": {
+ "TargetMap$value": null
+ }
+ },
+ "TargetMaps": {
+ "base": null,
+ "refs": {
+ "AutomationExecution$TargetMaps": "<p>The specified key-value mapping of document parameters to target resources.</p>",
+ "AutomationExecutionMetadata$TargetMaps": "<p>The specified key-value mapping of document parameters to target resources.</p>",
+ "StartAutomationExecutionRequest$TargetMaps": "<p>A key-value mapping of document parameters to target resources. Both Targets and TargetMaps cannot be specified together.</p>"
+ }
+ },
  "TargetParameterList": {
  "base": null,
  "refs": {

diff --git a/service/secretsmanager/api.go b/service/secretsmanager/api.go