Skip to main content

probes

Creates, updates, deletes, gets or lists a probes resource.

Overview

Nameprobes
TypeResource
Idaws.networkmonitor.probes

Fields

The following fields are returned by SELECT queries:

NameDatatypeDescription
address_familystringIndicates whether the IP address is IPV4 or IPV6. (IPV4, IPV6)
created_atstring (date-time)The time and date that the probe was created.
destinationstringThe destination IP address for the monitor. This must be either an IPv4 or IPv6 address.
destination_portintegerThe port associated with the destination. This is required only if the protocol is TCP and must be a number between 1 and 65536.
modified_atstring (date-time)The time and date that the probe was last modified.
packet_sizeintegerThe size of the packets sent between the source and destination. This must be a number between 56 and 8500.
probe_arnstringThe ARN of the probe. (pattern: <code>arn:.*</code>)
probe_idstringThe ID of the probe for which details are returned. (pattern: <code>probe-[a-z0-9A-Z-]{21,64}</code>)
protocolstringThe protocol used for the network traffic between the source and destination. This must be either TCP or ICMP. (TCP, ICMP)
source_arnstringThe ARN of the probe. (pattern: <code>arn:.*</code>)
statestringThe state of the probe. (PENDING, ACTIVE, INACTIVE, ERROR, DELETING, DELETED)
tagsobjectThe list of key-value pairs assigned to the probe.
vpc_idstringThe ID of the source VPC or subnet. (pattern: <code>vpc-[a-zA-Z0-9]{8,32}</code>)

Methods

The following methods are available for this resource:

NameAccessible byRequired ParamsOptional ParamsDescription
get_probeselectmonitor_name, probe_id, regionReturns the details about a probe. This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs.
create_probeinsertmonitor_name, region, probeCreate a probe within a monitor. Once you create a probe, and it begins monitoring your network traffic, you'll incur billing charges for that probe. This action requires the monitorName parameter. Run ListMonitors to get a list of monitor names. Note the name of the monitorName you want to create the probe for.
update_probeupdatemonitor_name, probe_id, regionUpdates a monitor probe. This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs. You can update the following para create a monitor with probes using this command. For each probe, you define the following: state—The state of the probe. destination— The target destination IP address for the probe. destinationPort—Required only if the protocol is TCP. protocol—The communication protocol between the source and destination. This will be either TCP or ICMP. packetSize—The size of the packets. This must be a number between 56 and 8500. (Optional) tags —Key-value pairs created and assigned to the probe.
delete_probedeletemonitor_name, probe_id, regionDeletes the specified probe. Once a probe is deleted you'll no longer incur any billing fees for that probe. This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs. You can only delete a single probe at a time using this action.

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

NameDatatypeDescription
monitor_namestringThe name of the monitor to delete.
probe_idstringThe ID of the probe to delete.
regionstringAWS region (default: us-east-1)

SELECT examples

Returns the details about a probe. This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs.

SELECT
address_family,
created_at,
destination,
destination_port,
modified_at,
packet_size,
probe_arn,
probe_id,
protocol,
source_arn,
state,
tags,
vpc_id
FROM aws.networkmonitor.probes
WHERE monitor_name = '{{ monitor_name }}' -- required
AND probe_id = '{{ probe_id }}' -- required
AND region = '{{ region }}' -- required
;

INSERT examples

Create a probe within a monitor. Once you create a probe, and it begins monitoring your network traffic, you'll incur billing charges for that probe. This action requires the monitorName parameter. Run ListMonitors to get a list of monitor names. Note the name of the monitorName you want to create the probe for.

INSERT INTO aws.networkmonitor.probes (
probe,
clientToken,
tags,
monitor_name,
region
)
SELECT
'{{ probe }}' /* required */,
'{{ clientToken }}',
'{{ tags }}',
'{{ monitor_name }}',
'{{ region }}'
RETURNING
address_family,
created_at,
destination,
destination_port,
modified_at,
packet_size,
probe_arn,
probe_id,
protocol,
source_arn,
state,
tags,
vpc_id
;

UPDATE examples

Updates a monitor probe. This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs. You can update the following para create a monitor with probes using this command. For each probe, you define the following: state—The state of the probe. destination— The target destination IP address for the probe. destinationPort—Required only if the protocol is TCP. protocol—The communication protocol between the source and destination. This will be either TCP or ICMP. packetSize—The size of the packets. This must be a number between 56 and 8500. (Optional) tags —Key-value pairs created and assigned to the probe.

UPDATE aws.networkmonitor.probes
SET
state = '{{ state }}',
destination = '{{ destination }}',
destinationPort = {{ destinationPort }},
protocol = '{{ protocol }}',
packetSize = {{ packetSize }}
WHERE
monitor_name = '{{ monitor_name }}' --required
AND probe_id = '{{ probe_id }}' --required
AND region = '{{ region }}' --required
RETURNING
address_family,
created_at,
destination,
destination_port,
modified_at,
packet_size,
probe_arn,
probe_id,
protocol,
source_arn,
state,
tags,
vpc_id;

DELETE examples

Deletes the specified probe. Once a probe is deleted you'll no longer incur any billing fees for that probe. This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs. You can only delete a single probe at a time using this action.

DELETE FROM aws.networkmonitor.probes
WHERE monitor_name = '{{ monitor_name }}' --required
AND probe_id = '{{ probe_id }}' --required
AND region = '{{ region }}' --required
;