GSP
Quick Navigator
Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Paws::Lightsail::InstancePortInfo(3) User Contributed Perl Documentation Paws::Lightsail::InstancePortInfo(3)

Paws::Lightsail::InstancePortInfo

This class represents one of two things:

Arguments in a call to a service

Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object.

As an example, if Att1 is expected to be a Paws::Lightsail::InstancePortInfo object:

  $service_obj->Method(Att1 => { AccessDirection => $value, ..., ToPort => $value  });

Results returned from an API call

Use accessors for each attribute. If Att1 is expected to be an Paws::Lightsail::InstancePortInfo object:

  $result = $service_obj->Method(...);
  $result->Att1->AccessDirection

Describes information about ports for an Amazon Lightsail instance.

The access direction ("inbound" or "outbound").

Lightsail currently supports only "inbound" access direction.

The location from which access is allowed. For example, "Anywhere (0.0.0.0/0)", or "Custom" if a specific IP address or range of IP addresses is allowed.

The type of access ("Public" or "Private").

An alias that defines access for a preconfigured range of IP addresses.

The only alias currently supported is "lightsail-connect", which allows IP addresses of the browser-based RDP/SSH client in the Lightsail console to connect to your instance.

The IPv4 address, or range of IPv4 addresses (in CIDR notation) that are allowed to connect to an instance through the ports, and the protocol.

The "ipv6Cidrs" parameter lists the IPv6 addresses that are allowed to connect to an instance.

For more information about CIDR block notation, see Classless Inter-Domain Routing (https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation) on Wikipedia.

The common name of the port information.

The first port in a range of open ports on an instance.

Allowed ports:

  • TCP and UDP - 0 to 65535
  • ICMP - The ICMP type for IPv4 addresses. For example, specify 8 as the "fromPort" (ICMP type), and -1 as the "toPort" (ICMP code), to enable ICMP Ping. For more information, see Control Messages (https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol#Control_messages) on Wikipedia.
  • ICMPv6 - The ICMP type for IPv6 addresses. For example, specify 128 as the "fromPort" (ICMPv6 type), and 0 as "toPort" (ICMPv6 code). For more information, see Internet Control Message Protocol for IPv6 (https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol_for_IPv6).

The IPv6 address, or range of IPv6 addresses (in CIDR notation) that are allowed to connect to an instance through the ports, and the protocol. Only devices with an IPv6 address can connect to an instance through IPv6; otherwise, IPv4 should be used.

The "cidrs" parameter lists the IPv4 addresses that are allowed to connect to an instance.

For more information about CIDR block notation, see Classless Inter-Domain Routing (https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation) on Wikipedia.

The IP protocol name.

The name can be one of the following:

  • "tcp" - Transmission Control Protocol (TCP) provides reliable, ordered, and error-checked delivery of streamed data between applications running on hosts communicating by an IP network. If you have an application that doesn't require reliable data stream service, use UDP instead.
  • "all" - All transport layer protocol types. For more general information, see Transport layer (https://en.wikipedia.org/wiki/Transport_layer) on Wikipedia.
  • "udp" - With User Datagram Protocol (UDP), computer applications can send messages (or datagrams) to other hosts on an Internet Protocol (IP) network. Prior communications are not required to set up transmission channels or data paths. Applications that don't require reliable data stream service can use UDP, which provides a connectionless datagram service that emphasizes reduced latency over reliability. If you do require reliable data stream service, use TCP instead.
  • "icmp" - Internet Control Message Protocol (ICMP) is used to send error messages and operational information indicating success or failure when communicating with an instance. For example, an error is indicated when an instance could not be reached. When you specify "icmp" as the "protocol", you must specify the ICMP type using the "fromPort" parameter, and ICMP code using the "toPort" parameter.

The last port in a range of open ports on an instance.

Allowed ports:

  • TCP and UDP - 0 to 65535
  • ICMP - The ICMP code for IPv4 addresses. For example, specify 8 as the "fromPort" (ICMP type), and -1 as the "toPort" (ICMP code), to enable ICMP Ping. For more information, see Control Messages (https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol#Control_messages) on Wikipedia.
  • ICMPv6 - The ICMP code for IPv6 addresses. For example, specify 128 as the "fromPort" (ICMPv6 type), and 0 as "toPort" (ICMPv6 code). For more information, see Internet Control Message Protocol for IPv6 (https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol_for_IPv6).

This class forms part of Paws, describing an object used in Paws::Lightsail

The source code is located here: <https://github.com/pplu/aws-sdk-perl>

Please report bugs to: <https://github.com/pplu/aws-sdk-perl/issues>

2022-06-01 perl v5.40.2
Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.