awscli 1.37.2__py3-none-any.whl → 1.37.4__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Potentially problematic release.
This version of awscli might be problematic. Click here for more details.
- awscli/__init__.py +1 -1
- awscli/examples/cloudfront/create-distribution-with-tags.rst +9 -13
- awscli/examples/cloudfront/get-distribution.rst +6 -10
- awscli/examples/cloudtrail/put-event-selectors.rst +2 -2
- awscli/examples/deploy/batch-get-deployments.rst +2 -2
- awscli/examples/deploy/create-deployment.rst +1 -1
- awscli/examples/deploy/get-application-revision.rst +2 -2
- awscli/examples/deploy/get-deployment.rst +1 -1
- awscli/examples/deploy/list-application-revisions.rst +3 -3
- awscli/examples/deploy/push.rst +2 -2
- awscli/examples/deploy/register-application-revision.rst +1 -1
- awscli/examples/ec2/accept-address-transfer.rst +1 -1
- awscli/examples/ec2/allocate-hosts.rst +55 -55
- awscli/examples/ec2/associate-address.rst +44 -35
- awscli/examples/ec2/authorize-security-group-egress.rst +56 -23
- awscli/examples/ec2/authorize-security-group-ingress.rst +15 -15
- awscli/examples/ec2/cancel-capacity-reservation.rst +14 -14
- awscli/examples/ec2/cancel-spot-fleet-requests.rst +43 -46
- awscli/examples/ec2/copy-snapshot.rst +2 -4
- awscli/examples/ec2/create-capacity-reservation.rst +95 -95
- awscli/examples/ec2/create-replace-root-volume-task.rst +1 -3
- awscli/examples/ec2/create-restore-image-task.rst +2 -2
- awscli/examples/ec2/create-spot-datafeed-subscription.rst +1 -1
- awscli/examples/ec2/create-tags.rst +43 -43
- awscli/examples/ec2/create-traffic-mirror-filter-rule.rst +32 -32
- awscli/examples/ec2/create-traffic-mirror-filter.rst +22 -12
- awscli/examples/ec2/create-traffic-mirror-session.rst +31 -31
- awscli/examples/ec2/create-traffic-mirror-target.rst +45 -35
- awscli/examples/ec2/create-transit-gateway-prefix-list-reference.rst +27 -27
- awscli/examples/ec2/create-verified-access-endpoint.rst +1 -1
- awscli/examples/ec2/create-vpc-endpoint-service-configuration.rst +67 -65
- awscli/examples/ec2/create-vpc-endpoint.rst +4 -4
- awscli/examples/ec2/describe-vpc-endpoint-service-configurations.rst +62 -62
- awscli/examples/ec2/describe-vpc-endpoint-services.rst +132 -134
- awscli/examples/ec2/describe-vpc-endpoints.rst +89 -89
- awscli/examples/eks/describe-cluster.rst +1 -1
- awscli/examples/emr/create-cluster-examples.rst +4 -4
- awscli/examples/emr/schedule-hbase-backup.rst +23 -23
- awscli/examples/importexport/create-job.rst +2 -2
- awscli/examples/importexport/get-shipping-label.rst +1 -1
- awscli/examples/importexport/get-status.rst +1 -1
- awscli/examples/rds/download-db-log-file-portion.rst +7 -3
- awscli/examples/resourcegroupstaggingapi/untag-resources.rst +1 -1
- awscli/examples/s3/cp.rst +7 -7
- awscli/examples/s3/ls.rst +2 -2
- awscli/examples/s3/mv.rst +5 -5
- awscli/examples/s3/sync.rst +5 -5
- awscli/examples/securitylake/create-subscriber.rst +83 -0
- {awscli-1.37.2.dist-info → awscli-1.37.4.dist-info}/METADATA +2 -2
- {awscli-1.37.2.dist-info → awscli-1.37.4.dist-info}/RECORD +62 -63
- awscli/examples/securitylake/create-subscriber-data-access.rst +0 -41
- awscli/examples/securitylake/create-subscriber-query-access.rst +0 -41
- /awscli/examples/securitylake/{create-aws-logsource.rst → create-aws-log-source.rst} +0 -0
- /awscli/examples/securitylake/{create-custom-logsource.rst → create-custom-log-source.rst} +0 -0
- /awscli/examples/securitylake/{delete-aws-logsource.rst → delete-aws-log-source.rst} +0 -0
- /awscli/examples/securitylake/{delete-custom-logsource.rst → delete-custom-log-source.rst} +0 -0
- {awscli-1.37.2.data → awscli-1.37.4.data}/scripts/aws +0 -0
- {awscli-1.37.2.data → awscli-1.37.4.data}/scripts/aws.cmd +0 -0
- {awscli-1.37.2.data → awscli-1.37.4.data}/scripts/aws_bash_completer +0 -0
- {awscli-1.37.2.data → awscli-1.37.4.data}/scripts/aws_completer +0 -0
- {awscli-1.37.2.data → awscli-1.37.4.data}/scripts/aws_zsh_completer.sh +0 -0
- {awscli-1.37.2.dist-info → awscli-1.37.4.dist-info}/LICENSE.txt +0 -0
- {awscli-1.37.2.dist-info → awscli-1.37.4.dist-info}/WHEEL +0 -0
- {awscli-1.37.2.dist-info → awscli-1.37.4.dist-info}/top_level.txt +0 -0
|
@@ -1,35 +1,45 @@
|
|
|
1
|
-
**To create a a Network Load Balancer Traffic Mirror target**
|
|
2
|
-
|
|
3
|
-
The following ``create-traffic-mirror-target`` example creates a Network Load Balancer Traffic Mirror target. ::
|
|
4
|
-
|
|
5
|
-
aws ec2 create-traffic-mirror-target \
|
|
6
|
-
--description "Example Network Load Balancer Target" \
|
|
7
|
-
--network-load-balancer-arn arn:aws:elasticloadbalancing:us-east-1:111122223333:loadbalancer/net/NLB/7cdec873EXAMPLE
|
|
8
|
-
|
|
9
|
-
Output::
|
|
10
|
-
|
|
11
|
-
{
|
|
12
1
|
"TrafficMirrorTarget": {
|
|
13
2
|
"Type": "network-load-balancer",
|
|
14
3
|
"Tags": [],
|
|
15
4
|
"Description": "Example Network Load Balancer Target",
|
|
16
5
|
"OwnerId": "111122223333",
|
|
17
6
|
"NetworkLoadBalancerArn": "arn:aws:elasticloadbalancing:us-east-1:724145273726:loadbalancer/net/NLB/7cdec873EXAMPLE",
|
|
18
7
|
"TrafficMirrorTargetId": "tmt-0dabe9b0a6EXAMPLE"
|
|
19
8
|
},
|
|
20
9
|
"ClientToken": "d5c090f5-8a0f-49c7-8281-72c796a21f72"
|
|
21
10
|
}
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
--
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
"Description": "Network
|
|
37
|
-
"
|
|
38
|
-
"
|
|
39
|
-
"
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
11
|
+
**To create a a Network Load Balancer traffic mirror target**
|
|
12
|
+
|
|
13
|
+
The following ``create-traffic-mirror-target`` example creates a Network Load Balancer traffic mirror target. ::
|
|
14
|
+
|
|
15
|
+
aws ec2 create-traffic-mirror-target \
|
|
16
|
+
--description 'Example Network Load Balancer Target' \
|
|
17
|
+
--network-load-balancer-arn arn:aws:elasticloadbalancing:us-east-1:111122223333:loadbalancer/net/NLB/7cdec873EXAMPLE
|
|
18
|
+
|
|
19
|
+
Output::
|
|
20
|
+
|
|
21
|
+
{
|
|
22
|
+
"TrafficMirrorTarget": {
|
|
23
|
+
"Type": "network-load-balancer",
|
|
24
|
+
"Tags": [],
|
|
25
|
+
"Description": "Example Network Load Balancer Target",
|
|
26
|
+
"OwnerId": "111122223333",
|
|
27
|
+
"NetworkLoadBalancerArn": "arn:aws:elasticloadbalancing:us-east-1:724145273726:loadbalancer/net/NLB/7cdec873EXAMPLE",
|
|
28
|
+
"TrafficMirrorTargetId": "tmt-0dabe9b0a6EXAMPLE"
|
|
29
|
+
},
|
|
30
|
+
"ClientToken": "d5c090f5-8a0f-49c7-8281-72c796a21f72"
|
|
31
|
+
}
|
|
32
|
+
|
|
33
|
+
**To create a network traffic mirror target**
|
|
34
|
+
|
|
35
|
+
The following ``create-traffic-mirror-target`` example creates a network interface Traffic Mirror target. ::
|
|
36
|
+
|
|
37
|
+
aws ec2 create-traffic-mirror-target \
|
|
38
|
+
--description 'Network interface target' \
|
|
39
|
+
--network-interface-id eni-eni-01f6f631eEXAMPLE
|
|
40
|
+
|
|
41
|
+
Output::
|
|
42
|
+
|
|
43
|
+
{
|
|
44
|
+
"ClientToken": "5289a345-0358-4e62-93d5-47ef3061d65e",
|
|
45
|
+
"TrafficMirrorTarget": {
|
|
46
|
+
"Description": "Network interface target",
|
|
47
|
+
"NetworkInterfaceId": "eni-01f6f631eEXAMPLE",
|
|
48
|
+
"TrafficMirrorTargetId": "tmt-02dcdbe2abEXAMPLE",
|
|
49
|
+
"OwnerId": "111122223333",
|
|
50
|
+
"Type": "network-interface",
|
|
51
|
+
"Tags": []
|
|
52
|
+
}
|
|
53
|
+
}
|
|
54
|
+
|
|
55
|
+
For more information, see `Create a traffic mirror target <https://docs.aws.amazon.com/vpc/latest/mirroring/create-traffic-mirroring-target.html>`__ in the *Traffic Mirroring Guide*.
|
|
@@ -1,27 +1,27 @@
|
|
|
1
|
-
**To create a reference to a prefix list**
|
|
2
|
-
|
|
3
|
-
The following ``create-transit-gateway-prefix-list-reference`` example creates a reference to the specified prefix list in the specified transit gateway route table. ::
|
|
4
|
-
|
|
5
|
-
aws ec2 create-transit-gateway-prefix-list-reference \
|
|
6
|
-
--transit-gateway-route-table-id tgw-rtb-0123456789abcd123 \
|
|
7
|
-
--prefix-list-id pl-11111122222222333 \
|
|
8
|
-
--transit-gateway-attachment-id tgw-attach-aaaaaabbbbbb11111
|
|
9
|
-
|
|
10
|
-
Output::
|
|
11
|
-
|
|
12
|
-
{
|
|
13
|
-
"TransitGatewayPrefixListReference": {
|
|
14
|
-
"TransitGatewayRouteTableId": "tgw-rtb-0123456789abcd123",
|
|
15
|
-
"PrefixListId": "pl-11111122222222333",
|
|
16
|
-
"PrefixListOwnerId": "123456789012",
|
|
17
|
-
"State": "pending",
|
|
18
|
-
"Blackhole": false,
|
|
19
|
-
"TransitGatewayAttachment": {
|
|
20
|
-
"TransitGatewayAttachmentId": "tgw-attach-aaaaaabbbbbb11111",
|
|
21
|
-
"ResourceType": "vpc",
|
|
22
|
-
"ResourceId": "vpc-112233445566aabbc"
|
|
23
|
-
}
|
|
24
|
-
}
|
|
25
|
-
}
|
|
26
|
-
|
|
27
|
-
For more information, see `
|
|
1
|
+
**To create a reference to a prefix list**
|
|
2
|
+
|
|
3
|
+
The following ``create-transit-gateway-prefix-list-reference`` example creates a reference to the specified prefix list in the specified transit gateway route table. ::
|
|
4
|
+
|
|
5
|
+
aws ec2 create-transit-gateway-prefix-list-reference \
|
|
6
|
+
--transit-gateway-route-table-id tgw-rtb-0123456789abcd123 \
|
|
7
|
+
--prefix-list-id pl-11111122222222333 \
|
|
8
|
+
--transit-gateway-attachment-id tgw-attach-aaaaaabbbbbb11111
|
|
9
|
+
|
|
10
|
+
Output::
|
|
11
|
+
|
|
12
|
+
{
|
|
13
|
+
"TransitGatewayPrefixListReference": {
|
|
14
|
+
"TransitGatewayRouteTableId": "tgw-rtb-0123456789abcd123",
|
|
15
|
+
"PrefixListId": "pl-11111122222222333",
|
|
16
|
+
"PrefixListOwnerId": "123456789012",
|
|
17
|
+
"State": "pending",
|
|
18
|
+
"Blackhole": false,
|
|
19
|
+
"TransitGatewayAttachment": {
|
|
20
|
+
"TransitGatewayAttachmentId": "tgw-attach-aaaaaabbbbbb11111",
|
|
21
|
+
"ResourceType": "vpc",
|
|
22
|
+
"ResourceId": "vpc-112233445566aabbc"
|
|
23
|
+
}
|
|
24
|
+
}
|
|
25
|
+
}
|
|
26
|
+
|
|
27
|
+
For more information, see `Create a prefix list reference <https://docs.aws.amazon.com/vpc/latest/tgw/create-prefix-list-reference.html>`__ in the *Transit Gateways Guide*.
|
|
@@ -48,4 +48,4 @@ Output::
|
|
|
48
48
|
}
|
|
49
49
|
}
|
|
50
50
|
|
|
51
|
-
For more information, see `Verified Access endpoints <https://docs.aws.amazon.com/verified-access/latest/ug/
|
|
51
|
+
For more information, see `Verified Access endpoints <https://docs.aws.amazon.com/verified-access/latest/ug/verified-access-endpoints.html>`__ in the *AWS Verified Access User Guide*.
|
|
@@ -1,65 +1,67 @@
|
|
|
1
|
-
**Example 1: To create an endpoint service configuration for an interface endpoint**
|
|
2
|
-
|
|
3
|
-
The following ``create-vpc-endpoint-service-configuration`` example creates a VPC endpoint service configuration using the Network Load Balancer ``nlb-vpce``. This example also specifies that requests to connect to the service through an interface endpoint must be accepted. ::
|
|
4
|
-
|
|
5
|
-
aws ec2 create-vpc-endpoint-service-configuration \
|
|
6
|
-
--network-load-balancer-arns arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/net/nlb-vpce/e94221227f1ba532 \
|
|
7
|
-
--acceptance-required
|
|
8
|
-
|
|
9
|
-
Output::
|
|
10
|
-
|
|
11
|
-
{
|
|
12
|
-
"ServiceConfiguration": {
|
|
13
|
-
"ServiceType": [
|
|
14
|
-
{
|
|
15
|
-
"ServiceType": "Interface"
|
|
16
|
-
}
|
|
17
|
-
],
|
|
18
|
-
"NetworkLoadBalancerArns": [
|
|
19
|
-
"arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/net/nlb-vpce/e94221227f1ba532"
|
|
20
|
-
],
|
|
21
|
-
"ServiceName": "com.amazonaws.vpce.us-east-1.vpce-svc-03d5ebb7d9579a2b3",
|
|
22
|
-
"ServiceState": "Available",
|
|
23
|
-
"ServiceId": "vpce-svc-03d5ebb7d9579a2b3",
|
|
24
|
-
"AcceptanceRequired": true,
|
|
25
|
-
"AvailabilityZones": [
|
|
26
|
-
"us-east-1d"
|
|
27
|
-
],
|
|
28
|
-
"BaseEndpointDnsNames": [
|
|
29
|
-
"vpce-svc-03d5ebb7d9579a2b3.us-east-1.vpce.amazonaws.com"
|
|
30
|
-
]
|
|
31
|
-
}
|
|
32
|
-
}
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
"
|
|
54
|
-
"
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
"
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
1
|
+
**Example 1: To create an endpoint service configuration for an interface endpoint**
|
|
2
|
+
|
|
3
|
+
The following ``create-vpc-endpoint-service-configuration`` example creates a VPC endpoint service configuration using the Network Load Balancer ``nlb-vpce``. This example also specifies that requests to connect to the service through an interface endpoint must be accepted. ::
|
|
4
|
+
|
|
5
|
+
aws ec2 create-vpc-endpoint-service-configuration \
|
|
6
|
+
--network-load-balancer-arns arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/net/nlb-vpce/e94221227f1ba532 \
|
|
7
|
+
--acceptance-required
|
|
8
|
+
|
|
9
|
+
Output::
|
|
10
|
+
|
|
11
|
+
{
|
|
12
|
+
"ServiceConfiguration": {
|
|
13
|
+
"ServiceType": [
|
|
14
|
+
{
|
|
15
|
+
"ServiceType": "Interface"
|
|
16
|
+
}
|
|
17
|
+
],
|
|
18
|
+
"NetworkLoadBalancerArns": [
|
|
19
|
+
"arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/net/nlb-vpce/e94221227f1ba532"
|
|
20
|
+
],
|
|
21
|
+
"ServiceName": "com.amazonaws.vpce.us-east-1.vpce-svc-03d5ebb7d9579a2b3",
|
|
22
|
+
"ServiceState": "Available",
|
|
23
|
+
"ServiceId": "vpce-svc-03d5ebb7d9579a2b3",
|
|
24
|
+
"AcceptanceRequired": true,
|
|
25
|
+
"AvailabilityZones": [
|
|
26
|
+
"us-east-1d"
|
|
27
|
+
],
|
|
28
|
+
"BaseEndpointDnsNames": [
|
|
29
|
+
"vpce-svc-03d5ebb7d9579a2b3.us-east-1.vpce.amazonaws.com"
|
|
30
|
+
]
|
|
31
|
+
}
|
|
32
|
+
}
|
|
33
|
+
|
|
34
|
+
For more information, see `Create an endpoint service <https://docs.aws.amazon.com/vpc/latest/privatelink/create-endpoint-service.html>`__ in the *AWS PrivateLink User Guide*.
|
|
35
|
+
|
|
36
|
+
**Example 2: To create an endpoint service configuration for a Gateway Load Balancer endpoint**
|
|
37
|
+
|
|
38
|
+
The following ``create-vpc-endpoint-service-configuration`` example creates a VPC endpoint service configuration using the Gateway Load Balancer ``GWLBService``. Requests to connect to the service through a Gateway Load Balancer endpoint are automatically accepted. ::
|
|
39
|
+
|
|
40
|
+
aws ec2 create-vpc-endpoint-service-configuration \
|
|
41
|
+
--gateway-load-balancer-arns arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/gwy/GWLBService/123123123123abcc \
|
|
42
|
+
--no-acceptance-required
|
|
43
|
+
|
|
44
|
+
Output::
|
|
45
|
+
|
|
46
|
+
{
|
|
47
|
+
"ServiceConfiguration": {
|
|
48
|
+
"ServiceType": [
|
|
49
|
+
{
|
|
50
|
+
"ServiceType": "GatewayLoadBalancer"
|
|
51
|
+
}
|
|
52
|
+
],
|
|
53
|
+
"ServiceId": "vpce-svc-123123a1c43abc123",
|
|
54
|
+
"ServiceName": "com.amazonaws.vpce.us-east-1.vpce-svc-123123a1c43abc123",
|
|
55
|
+
"ServiceState": "Available",
|
|
56
|
+
"AvailabilityZones": [
|
|
57
|
+
"us-east-1d"
|
|
58
|
+
],
|
|
59
|
+
"AcceptanceRequired": false,
|
|
60
|
+
"ManagesVpcEndpoints": false,
|
|
61
|
+
"GatewayLoadBalancerArns": [
|
|
62
|
+
"arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/gwy/GWLBService/123123123123abcc"
|
|
63
|
+
]
|
|
64
|
+
}
|
|
65
|
+
}
|
|
66
|
+
|
|
67
|
+
For more information, see `Create a Gateway Load Balancer endpoint service <https://docs.aws.amazon.com/vpc/latest/privatelink/create-gateway-load-balancer-endpoint-service.html>`__ in the *AWS PrivateLink User Guide*.
|
|
@@ -23,7 +23,7 @@ Output::
|
|
|
23
23
|
}
|
|
24
24
|
}
|
|
25
25
|
|
|
26
|
-
For more information, see `
|
|
26
|
+
For more information, see `Create a gateway endpoint <https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-s3.html#create-gateway-endpoint-s3>`__ in the *AWS PrivateLink User Guide*.
|
|
27
27
|
|
|
28
28
|
**Example 2: To create an interface endpoint**
|
|
29
29
|
|
|
@@ -82,11 +82,11 @@ Output::
|
|
|
82
82
|
}
|
|
83
83
|
}
|
|
84
84
|
|
|
85
|
-
For more information, see `
|
|
85
|
+
For more information, see `Create an interface VPC endpoint <https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html>`__ in the *AWS PrivateLink User Guide*.
|
|
86
86
|
|
|
87
87
|
**Example 3: To create a Gateway Load Balancer endpoint**
|
|
88
88
|
|
|
89
|
-
The following ``create-vpc-endpoint`` example creates a Gateway Load Balancer endpoint between VPC ``vpc-111122223333aabbc`` and a service that is configured using a Gateway Load Balancer. ::
|
|
89
|
+
The following ``create-vpc-endpoint`` example creates a Gateway Load Balancer endpoint between VPC ``vpc-111122223333aabbc`` and and a service that is configured using a Gateway Load Balancer. ::
|
|
90
90
|
|
|
91
91
|
aws ec2 create-vpc-endpoint \
|
|
92
92
|
--service-name com.amazonaws.vpce.us-east-1.vpce-svc-123123a1c43abc123 \
|
|
@@ -115,4 +115,4 @@ Output::
|
|
|
115
115
|
}
|
|
116
116
|
}
|
|
117
117
|
|
|
118
|
-
For more information, see `Gateway Load Balancer endpoints <https://docs.aws.amazon.com/vpc/latest/privatelink/
|
|
118
|
+
For more information, see `Gateway Load Balancer endpoints <https://docs.aws.amazon.com/vpc/latest/privatelink/gateway-load-balancer-endpoints.html>`__ in the *AWS PrivateLink User Guide*.
|
|
@@ -1,62 +1,62 @@
|
|
|
1
|
-
**To describe endpoint service configurations**
|
|
2
|
-
|
|
3
|
-
The following ``describe-vpc-endpoint-service-configurations`` example describes your endpoint service configurations. ::
|
|
4
|
-
|
|
5
|
-
aws ec2 describe-vpc-endpoint-service-configurations
|
|
6
|
-
|
|
7
|
-
Output::
|
|
8
|
-
|
|
9
|
-
{
|
|
10
|
-
"ServiceConfigurations": [
|
|
11
|
-
{
|
|
12
|
-
"ServiceType": [
|
|
13
|
-
{
|
|
14
|
-
"ServiceType": "GatewayLoadBalancer"
|
|
15
|
-
}
|
|
16
|
-
],
|
|
17
|
-
"ServiceId": "vpce-svc-012d33a1c4321cabc",
|
|
18
|
-
"ServiceName": "com.amazonaws.vpce.us-east-1.vpce-svc-012d33a1c4321cabc",
|
|
19
|
-
"ServiceState": "Available",
|
|
20
|
-
"AvailabilityZones": [
|
|
21
|
-
"us-east-1d"
|
|
22
|
-
],
|
|
23
|
-
"AcceptanceRequired": false,
|
|
24
|
-
"ManagesVpcEndpoints": false,
|
|
25
|
-
"GatewayLoadBalancerArns": [
|
|
26
|
-
"arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/gwy/GWLBService/123210844e429123"
|
|
27
|
-
],
|
|
28
|
-
"Tags": []
|
|
29
|
-
},
|
|
30
|
-
{
|
|
31
|
-
"ServiceType": [
|
|
32
|
-
{
|
|
33
|
-
"ServiceType": "Interface"
|
|
34
|
-
}
|
|
35
|
-
],
|
|
36
|
-
"ServiceId": "vpce-svc-123cabc125efa123",
|
|
37
|
-
"ServiceName": "com.amazonaws.vpce.us-east-1.vpce-svc-123cabc125efa123",
|
|
38
|
-
"ServiceState": "Available",
|
|
39
|
-
"AvailabilityZones": [
|
|
40
|
-
"us-east-1a"
|
|
41
|
-
],
|
|
42
|
-
"AcceptanceRequired": true,
|
|
43
|
-
"ManagesVpcEndpoints": false,
|
|
44
|
-
"NetworkLoadBalancerArns": [
|
|
45
|
-
"arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/net/NLBforService/1238753950b25123"
|
|
46
|
-
],
|
|
47
|
-
"BaseEndpointDnsNames": [
|
|
48
|
-
"vpce-svc-123cabc125efa123.us-east-1.vpce.amazonaws.com"
|
|
49
|
-
],
|
|
50
|
-
"PrivateDnsName": "example.com",
|
|
51
|
-
"PrivateDnsNameConfiguration": {
|
|
52
|
-
"State": "failed",
|
|
53
|
-
"Type": "TXT",
|
|
54
|
-
"Value": "vpce:qUAth3FdeABCApUiXabc",
|
|
55
|
-
"Name": "_1d367jvbg34znqvyefrj"
|
|
56
|
-
},
|
|
57
|
-
"Tags": []
|
|
58
|
-
}
|
|
59
|
-
]
|
|
60
|
-
}
|
|
61
|
-
|
|
62
|
-
For more information, see `
|
|
1
|
+
**To describe endpoint service configurations**
|
|
2
|
+
|
|
3
|
+
The following ``describe-vpc-endpoint-service-configurations`` example describes your endpoint service configurations. ::
|
|
4
|
+
|
|
5
|
+
aws ec2 describe-vpc-endpoint-service-configurations
|
|
6
|
+
|
|
7
|
+
Output::
|
|
8
|
+
|
|
9
|
+
{
|
|
10
|
+
"ServiceConfigurations": [
|
|
11
|
+
{
|
|
12
|
+
"ServiceType": [
|
|
13
|
+
{
|
|
14
|
+
"ServiceType": "GatewayLoadBalancer"
|
|
15
|
+
}
|
|
16
|
+
],
|
|
17
|
+
"ServiceId": "vpce-svc-012d33a1c4321cabc",
|
|
18
|
+
"ServiceName": "com.amazonaws.vpce.us-east-1.vpce-svc-012d33a1c4321cabc",
|
|
19
|
+
"ServiceState": "Available",
|
|
20
|
+
"AvailabilityZones": [
|
|
21
|
+
"us-east-1d"
|
|
22
|
+
],
|
|
23
|
+
"AcceptanceRequired": false,
|
|
24
|
+
"ManagesVpcEndpoints": false,
|
|
25
|
+
"GatewayLoadBalancerArns": [
|
|
26
|
+
"arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/gwy/GWLBService/123210844e429123"
|
|
27
|
+
],
|
|
28
|
+
"Tags": []
|
|
29
|
+
},
|
|
30
|
+
{
|
|
31
|
+
"ServiceType": [
|
|
32
|
+
{
|
|
33
|
+
"ServiceType": "Interface"
|
|
34
|
+
}
|
|
35
|
+
],
|
|
36
|
+
"ServiceId": "vpce-svc-123cabc125efa123",
|
|
37
|
+
"ServiceName": "com.amazonaws.vpce.us-east-1.vpce-svc-123cabc125efa123",
|
|
38
|
+
"ServiceState": "Available",
|
|
39
|
+
"AvailabilityZones": [
|
|
40
|
+
"us-east-1a"
|
|
41
|
+
],
|
|
42
|
+
"AcceptanceRequired": true,
|
|
43
|
+
"ManagesVpcEndpoints": false,
|
|
44
|
+
"NetworkLoadBalancerArns": [
|
|
45
|
+
"arn:aws:elasticloadbalancing:us-east-1:123456789012:loadbalancer/net/NLBforService/1238753950b25123"
|
|
46
|
+
],
|
|
47
|
+
"BaseEndpointDnsNames": [
|
|
48
|
+
"vpce-svc-123cabc125efa123.us-east-1.vpce.amazonaws.com"
|
|
49
|
+
],
|
|
50
|
+
"PrivateDnsName": "example.com",
|
|
51
|
+
"PrivateDnsNameConfiguration": {
|
|
52
|
+
"State": "failed",
|
|
53
|
+
"Type": "TXT",
|
|
54
|
+
"Value": "vpce:qUAth3FdeABCApUiXabc",
|
|
55
|
+
"Name": "_1d367jvbg34znqvyefrj"
|
|
56
|
+
},
|
|
57
|
+
"Tags": []
|
|
58
|
+
}
|
|
59
|
+
]
|
|
60
|
+
}
|
|
61
|
+
|
|
62
|
+
For more information, see `Concepts <https://docs.aws.amazon.com/vpc/latest/privatelink/concepts.html>`__ in the *AWS PrivateLink User Guide*.
|