Skip to content

Commit a53775a

Browse files
author
AWS
committed
Amazon Elastic Compute Cloud Update: 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.
1 parent 88ac745 commit a53775a

File tree

4 files changed

+18
-2
lines changed

4 files changed

+18
-2
lines changed
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
{
2+
"type": "feature",
3+
"category": "Amazon Elastic Compute Cloud",
4+
"contributor": "",
5+
"description": "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."
6+
}

services/ec2/src/main/resources/codegen-resources/paginators-1.json

100755100644
File mode changed.

services/ec2/src/main/resources/codegen-resources/service-2.json

100755100644
Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -994,7 +994,7 @@
994994
},
995995
"input":{"shape":"CreateTrafficMirrorTargetRequest"},
996996
"output":{"shape":"CreateTrafficMirrorTargetResult"},
997-
"documentation":"<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>"
997+
"documentation":"<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>"
998998
},
999999
"CreateTransitGateway":{
10001000
"name":"CreateTransitGateway",
@@ -12775,6 +12775,10 @@
1277512775
"shape":"String",
1277612776
"documentation":"<p>Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Run_Instance_Idempotency.html\">How to ensure idempotency</a>.</p>",
1277712777
"idempotencyToken":true
12778+
},
12779+
"GatewayLoadBalancerEndpointId":{
12780+
"shape":"VpcEndpointId",
12781+
"documentation":"<p>The ID of the Gateway Load Balancer endpoint.</p>"
1277812782
}
1277912783
}
1278012784
},
@@ -47661,6 +47665,11 @@
4766147665
"shape":"TagList",
4766247666
"documentation":"<p>The tags assigned to the Traffic Mirror target.</p>",
4766347667
"locationName":"tagSet"
47668+
},
47669+
"GatewayLoadBalancerEndpointId":{
47670+
"shape":"String",
47671+
"documentation":"<p>The ID of the Gateway Load Balancer endpoint.</p>",
47672+
"locationName":"gatewayLoadBalancerEndpointId"
4766447673
}
4766547674
},
4766647675
"documentation":"<p>Describes a Traffic Mirror target.</p>"
@@ -47684,7 +47693,8 @@
4768447693
"type":"string",
4768547694
"enum":[
4768647695
"network-interface",
47687-
"network-load-balancer"
47696+
"network-load-balancer",
47697+
"gateway-load-balancer-endpoint"
4768847698
]
4768947699
},
4769047700
"TrafficMirroringMaxResults":{

services/ec2/src/main/resources/codegen-resources/waiters-2.json

100755100644
File mode changed.

0 commit comments

Comments
 (0)