VPC Endpoints¶

Provider: AWS
Service ID: vpc_endpoints
Rendering: Standard table with expandable detail rows

Quick Example¶

<script>
var serviceDiscoveryRequests = serviceDiscoveryRequests || [];
serviceDiscoveryRequests.push({
    service: 'vpc_endpoints',
    provider: 'aws',
    region: 'eu-west-2',
    source: 'live',
    attributes: ['name', 'endpoint_id', 'service_name', 'vpc_id', 'type', 'state']
});
</script>

<div data-sd-service="vpc_endpoints" data-sd-source="live"></div>

Default Attributes¶

When no attributes array is specified, these columns are displayed:

attributes: ['name', 'endpoint_id', 'service_name', 'vpc_id', 'type', 'state']

All Attributes¶

Attribute	Display Name	Format	Description
`name`	Name	`text`	Resource display name (from tags or identifier)
`endpoint_id`	Endpoint ID	`text`	From API field: `VpcEndpointId`
`service_name`	Service Name	`text`	From API field: `ServiceName`
`vpc_id`	VPC ID	`text`	From API field: `VpcId`. Resolved to vpc name when available
`type`	Type	`text`	From API field: `VpcEndpointType`
`state`	State	`status_badge`	From API field: `State`
`subnet_ids`	Subnets	`tag_list`	From API field: `SubnetIds`
`route_table_ids`	Route Tables	`tag_list`	From API field: `RouteTableIds`
`private_dns`	Private DNS	`boolean`	From API field: `PrivateDnsEnabled`
`owner_id`	Owner ID	`text`	From API field: `OwnerId`
`creation_timestamp`	Created	`datetime`	From API field: `CreationTimestamp`
`tags`	Tags	`tags_table`	All tags/labels as a key-value table

= included in default view

Sort Order¶

Results are sorted by: name, endpoint_id