Skip to content

Commit

Permalink
Release v1.44.13 (2022-05-12) (#4400)
Browse files Browse the repository at this point in the history
Release v1.44.13 (2022-05-12)
===

### Service Client Updates
* `service/ec2`: Updates service API and documentation
  * This release introduces a target type Gateway Load Balancer Endpoint for mirrored traffic. Customers can now specify GatewayLoadBalancerEndpoint option during the creation of a traffic mirror target.
* `service/finspace-data`: Updates service documentation
* `service/iot`: Updates service documentation
  * Documentation update for China region ListMetricValues for IoT
* `service/ivschat`: Updates service API and documentation
* `service/kendra`: Updates service API and documentation
  * Amazon Kendra now provides a data source connector for Jira. For more information, see https://docs.aws.amazon.com/kendra/latest/dg/data-source-jira.html
* `service/lambda`: Updates service API and documentation
  * Lambda releases NodeJs 16 managed runtime to be available in all commercial regions.
* `service/lightsail`: Updates service API and documentation
  * This release adds support to include inactive database bundles in the response of the GetRelationalDatabaseBundles request.
* `service/outposts`: Updates service documentation
* `service/ssm-incidents`: Updates service API and documentation
* `service/transfer`: Updates service documentation
  * AWS Transfer Family now accepts ECDSA keys for server host keys
* `service/workspaces`: Updates service API
  * Increased the character limit of the login message from 600 to 850 characters.
  • Loading branch information
aws-sdk-go-automation committed May 12, 2022
1 parent ec3763d commit 0c7296c
Show file tree
Hide file tree
Showing 30 changed files with 989 additions and 162 deletions.
23 changes: 23 additions & 0 deletions CHANGELOG.md
@@ -1,3 +1,26 @@
Release v1.44.13 (2022-05-12)
===

### Service Client Updates
* `service/ec2`: Updates service API and documentation
* This release introduces a target type Gateway Load Balancer Endpoint for mirrored traffic. Customers can now specify GatewayLoadBalancerEndpoint option during the creation of a traffic mirror target.
* `service/finspace-data`: Updates service documentation
* `service/iot`: Updates service documentation
* Documentation update for China region ListMetricValues for IoT
* `service/ivschat`: Updates service API and documentation
* `service/kendra`: Updates service API and documentation
* Amazon Kendra now provides a data source connector for Jira. For more information, see https://docs.aws.amazon.com/kendra/latest/dg/data-source-jira.html
* `service/lambda`: Updates service API and documentation
* Lambda releases NodeJs 16 managed runtime to be available in all commercial regions.
* `service/lightsail`: Updates service API and documentation
* This release adds support to include inactive database bundles in the response of the GetRelationalDatabaseBundles request.
* `service/outposts`: Updates service documentation
* `service/ssm-incidents`: Updates service API and documentation
* `service/transfer`: Updates service documentation
* AWS Transfer Family now accepts ECDSA keys for server host keys
* `service/workspaces`: Updates service API
* Increased the character limit of the login message from 600 to 850 characters.

Release v1.44.12 (2022-05-11)
===

Expand Down
2 changes: 1 addition & 1 deletion aws/version.go
Expand Up @@ -5,4 +5,4 @@ package aws
const SDKName = "aws-sdk-go"

// SDKVersion is the version of this SDK
const SDKVersion = "1.44.12"
const SDKVersion = "1.44.13"
10 changes: 8 additions & 2 deletions models/apis/ec2/2016-11-15/api-2.json
Expand Up @@ -10343,7 +10343,8 @@
"ClientToken":{
"shape":"String",
"idempotencyToken":true
}
},
"GatewayLoadBalancerEndpointId":{"shape":"VpcEndpointId"}
}
},
"CreateTrafficMirrorTargetResult":{
Expand Down Expand Up @@ -36870,6 +36871,10 @@
"Tags":{
"shape":"TagList",
"locationName":"tagSet"
},
"GatewayLoadBalancerEndpointId":{
"shape":"String",
"locationName":"gatewayLoadBalancerEndpointId"
}
}
},
Expand All @@ -36892,7 +36897,8 @@
"type":"string",
"enum":[
"network-interface",
"network-load-balancer"
"network-load-balancer",
"gateway-load-balancer-endpoint"
]
},
"TrafficMirroringMaxResults":{
Expand Down
4 changes: 3 additions & 1 deletion models/apis/ec2/2016-11-15/docs-2.json
Expand Up @@ -100,7 +100,7 @@
"CreateTrafficMirrorFilter": "<p>Creates a Traffic Mirror filter.</p> <p>A Traffic Mirror filter is a set of rules that defines the traffic to mirror.</p> <p>By default, no traffic is mirrored. To mirror traffic, use <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateTrafficMirrorFilterRule.htm\">CreateTrafficMirrorFilterRule</a> to add Traffic Mirror rules to the filter. The rules you add define what traffic gets mirrored. You can also use <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifyTrafficMirrorFilterNetworkServices.html\">ModifyTrafficMirrorFilterNetworkServices</a> to mirror supported network services.</p>",
"CreateTrafficMirrorFilterRule": "<p>Creates a Traffic Mirror filter rule.</p> <p>A Traffic Mirror rule defines the Traffic Mirror source traffic to mirror.</p> <p>You need the Traffic Mirror filter ID when you create the rule.</p>",
"CreateTrafficMirrorSession": "<p>Creates a Traffic Mirror session.</p> <p>A Traffic Mirror session actively copies packets from a Traffic Mirror source to a Traffic Mirror target. Create a filter, and then assign it to the session to define a subset of the traffic to mirror, for example all TCP traffic.</p> <p>The Traffic Mirror source and the Traffic Mirror target (monitoring appliances) can be in the same VPC, or in a different VPC connected via VPC peering or a transit gateway. </p> <p>By default, no traffic is mirrored. Use <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateTrafficMirrorFilter.htm\">CreateTrafficMirrorFilter</a> to create filter rules that specify the traffic to mirror.</p>",
"CreateTrafficMirrorTarget": "<p>Creates a target for your Traffic Mirror session.</p> <p>A Traffic Mirror target is the destination for mirrored traffic. The Traffic Mirror source and the Traffic Mirror target (monitoring appliances) can be in the same VPC, or in different VPCs connected via VPC peering or a transit gateway.</p> <p>A Traffic Mirror target can be a network interface, or a Network Load Balancer.</p> <p>To use the target in a Traffic Mirror session, use <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateTrafficMirrorSession.htm\">CreateTrafficMirrorSession</a>.</p>",
"CreateTrafficMirrorTarget": "<p>Creates a target for your Traffic Mirror session.</p> <p>A Traffic Mirror target is the destination for mirrored traffic. The Traffic Mirror source and the Traffic Mirror target (monitoring appliances) can be in the same VPC, or in different VPCs connected via VPC peering or a transit gateway.</p> <p>A Traffic Mirror target can be a network interface, a Network Load Balancer, or a Gateway Load Balancer endpoint.</p> <p>To use the target in a Traffic Mirror session, use <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateTrafficMirrorSession.htm\">CreateTrafficMirrorSession</a>.</p>",
"CreateTransitGateway": "<p>Creates a transit gateway.</p> <p>You can use a transit gateway to interconnect your virtual private clouds (VPC) and on-premises networks. After the transit gateway enters the <code>available</code> state, you can attach your VPCs and VPN connections to the transit gateway.</p> <p>To attach your VPCs, use <a>CreateTransitGatewayVpcAttachment</a>.</p> <p>To attach a VPN connection, use <a>CreateCustomerGateway</a> to create a customer gateway and specify the ID of the customer gateway and the ID of the transit gateway in a call to <a>CreateVpnConnection</a>.</p> <p>When you create a transit gateway, we create a default transit gateway route table and use it as the default association route table and the default propagation route table. You can use <a>CreateTransitGatewayRouteTable</a> to create additional transit gateway route tables. If you disable automatic route propagation, we do not create a default transit gateway route table. You can use <a>EnableTransitGatewayRouteTablePropagation</a> to propagate routes from a resource attachment to a transit gateway route table. If you disable automatic associations, you can use <a>AssociateTransitGatewayRouteTable</a> to associate a resource attachment with a transit gateway route table.</p>",
"CreateTransitGatewayConnect": "<p>Creates a Connect attachment from a specified transit gateway attachment. A Connect attachment is a GRE-based tunnel attachment that you can use to establish a connection between a transit gateway and an appliance.</p> <p>A Connect attachment uses an existing VPC or Amazon Web Services Direct Connect attachment as the underlying transport mechanism.</p>",
"CreateTransitGatewayConnectPeer": "<p>Creates a Connect peer for a specified transit gateway Connect attachment between a transit gateway and an appliance.</p> <p>The peer address and transit gateway address must be the same IP address family (IPv4 or IPv6).</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/vpc/latest/tgw/tgw-connect.html#tgw-connect-peer\">Connect peers</a> in the <i>Transit Gateways Guide</i>.</p>",
Expand Down Expand Up @@ -18032,6 +18032,7 @@
"TrafficMirrorTarget$NetworkLoadBalancerArn": "<p>The Amazon Resource Name (ARN) of the Network Load Balancer.</p>",
"TrafficMirrorTarget$Description": "<p>Information about the Traffic Mirror target.</p>",
"TrafficMirrorTarget$OwnerId": "<p>The ID of the account that owns the Traffic Mirror target.</p>",
"TrafficMirrorTarget$GatewayLoadBalancerEndpointId": "<p>The ID of the Gateway Load Balancer endpoint.</p>",
"TransitGateway$TransitGatewayId": "<p>The ID of the transit gateway.</p>",
"TransitGateway$TransitGatewayArn": "<p>The Amazon Resource Name (ARN) of the transit gateway.</p>",
"TransitGateway$OwnerId": "<p>The ID of the Amazon Web Services account that owns the transit gateway.</p>",
Expand Down Expand Up @@ -20300,6 +20301,7 @@
"base": null,
"refs": {
"CreateRouteRequest$VpcEndpointId": "<p>The ID of a VPC endpoint. Supported for Gateway Load Balancer endpoints only.</p>",
"CreateTrafficMirrorTargetRequest$GatewayLoadBalancerEndpointId": "<p>The ID of the Gateway Load Balancer endpoint.</p>",
"CreateVpcEndpointConnectionNotificationRequest$VpcEndpointId": "<p>The ID of the endpoint.</p>",
"ModifyVpcEndpointRequest$VpcEndpointId": "<p>The ID of the endpoint.</p>",
"ReplaceRouteRequest$VpcEndpointId": "<p>The ID of a VPC endpoint. Supported for Gateway Load Balancer endpoints only.</p>",
Expand Down
2 changes: 1 addition & 1 deletion models/apis/finspace-data/2020-07-13/docs-2.json
Expand Up @@ -713,7 +713,7 @@
}
},
"ResourcePermission": {
"base": "<p>Resource permission for a dataset. When you create a dataset, all the other members of the same user group inherit access to the dataset. You can only create a dataset if your user group has application permission for Create Datasets.</p> <p>The following is a list of valid dataset permissions that you can apply: </p> <ul> <li> <p> <code>ViewDatasetDetails</code> </p> </li> <li> <p> <code>ReadDatasetDetails</code> </p> </li> <li> <p> <code>AddDatasetData</code> </p> </li> <li> <p> <code>CreateSnapshot</code> </p> </li> <li> <p> <code>EditDatasetMetadata</code> </p> </li> <li> <p> <code>DeleteDataset</code> </p> </li> </ul> <p>For more information on the dataset permissions, see <a href=\"https://docs.aws.amazon.com/finspace/latest/userguide/managing-user-permissions.html#supported-dataset-permissions\">Supported Dataset Permissions</a> in the FinSpace User Guide.</p>",
"base": "<p>Resource permission for a dataset. When you create a dataset, all the other members of the same user group inherit access to the dataset. You can only create a dataset if your user group has application permission for Create Datasets.</p> <p>The following is a list of valid dataset permissions that you can apply: </p> <ul> <li> <p> <code>ViewDatasetDetails</code> </p> </li> <li> <p> <code>ReadDatasetDetails</code> </p> </li> <li> <p> <code>AddDatasetData</code> </p> </li> <li> <p> <code>CreateDataView</code> </p> </li> <li> <p> <code>EditDatasetMetadata</code> </p> </li> <li> <p> <code>DeleteDataset</code> </p> </li> </ul> <p>For more information on the dataset permissions, see <a href=\"https://docs.aws.amazon.com/finspace/latest/userguide/managing-user-permissions.html#supported-dataset-permissions\">Supported Dataset Permissions</a> in the FinSpace User Guide.</p>",
"refs": {
"ResourcePermissionsList$member": null
}
Expand Down

0 comments on commit 0c7296c

Please sign in to comment.