> ## Documentation Index > Fetch the complete documentation index at: https://docs.megaport.com/llms.txt > Use this file to discover all available pages before exploring further. # AWS Interconnect from Megaport Features > This help topic describes the features of the AWS Interconnect from Megaport. > [!NOTE] > > AWS Interconnect from Megaport is in Preview. Features, supported locations, and connection speeds are limited during the Preview and are subject to change. For more information, see [Preview release](/aws-interconnect#preview-release). An AWS Interconnect from Megaport (AWS Interconnect) is a managed, routed connection to an AWS region. This topic describes the features of an AWS Interconnect, including the connections it accepts, its routing behavior, and its security options. For an introduction to the product, see [AWS Interconnect Overview](/aws-interconnect). **preview-limitations** ## Preview limitations > [!WARNING] > > Do not use a Preview AWS Interconnect for production traffic. These limits apply to the Preview release of AWS Interconnect. | Area | Limitation | | - | - | | Speed | The speed is fixed at 1 Gbps. Speed changes are not supported. | | Locations | AWS Interconnect is available in a limited set of metros. | | Connections | An AWS Interconnect supports up to 25 VXCs. | | Looking Glass | Looking Glass is not available for an AWS Interconnect. | | Telemetry | Traffic graphs are not available for an AWS Interconnect. | | Notifications | Email notifications are not sent for AWS Interconnect events. | | Activity logs | Some AWS Interconnect events are not written to the activity log. | | Terraform | The Megaport Terraform Provider does not manage AWS Interconnects. | | Service lifetime | Preview AWS Interconnects are not carried over to the general release. You need to reorder for production use. | | Encryption | MACsec is not supported during Preview. | **encryption** ## Encryption Media Access Control security (MACsec) is a security protocol that encrypts data traffic between Ethernet-connected devices. The MACsec protocol is defined by IEEE standard 802.1ae. When MACsec is enabled, a bi-directional secure link is established after an exchange and verification of security keys between the two connected devices. A combination of data integrity checks and encryption is used to safeguard the transmitted data. runs on each of the physical links between the Megaport network and AWS. Megaport configures and manages the MACsec keys. You do not provide them. For more information about MACsec, see [Using MACsec with Megaport](/encryption/macsec). **vxcs** ## VXC connections An AWS Interconnect connects your Ports, MCRs, MVEs, and NAT Gateways in the same metro to AWS through Virtual Cross Connects (VXCs). You configure the AWS Interconnect end of each attached VXC, with options similar to an MCR VXC. The AWS Interconnect manages the routing to AWS. These rules apply to VXCs on an AWS Interconnect: * You can attach a VXC after the AWS Interconnect is set up. An AWS Interconnect does not accept connections while it is being designed or deployed, or if it has failed to deploy. * Each VXC is limited to the speed of the AWS Interconnect. A single VXC cannot be faster than the AWS Interconnect connection you bought. **routing** ## Managed BGP routing An AWS Interconnect uses Border Gateway Protocol (BGP) is a standardized routing protocol designed to exchange route and reachability information among autonomous systems (AS) on the internet. to exchange routes with AWS. Megaport and AWS coordinate the BGP sessions, including the IP subnets and the VLANs that carry them. You do not create or configure these sessions. **asn** ## Autonomous system number (ASN) support An autonomous system (AS) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain. ASN refers to autonomous system number and is a unique numerical ID allocated to each AS for use in BGP routing. You choose the ASN for your side of the AWS Interconnect when you order it. The Portal suggests 133937 as a default. A small number of ASNs are reserved, and the Portal rejects them. If the Portal rejects an ASN, choose a different one. **ipmtu** ## IP MTU (Maximum Transmission Unit) IP MTU (Maximum Transmission Unit) refers to the largest size (in bytes) of an IP packet that can be sent over a network interface (VXC). Jumbo packets are larger than the standard 1500 bytes (MTU), and are typically used in high-performance networks to reduce overhead and improve efficiency. Megaport and AWS agree on an MTU for the AWS Interconnect when they set up the connection. A VXC attached to the AWS Interconnect cannot request an IP MTU larger than that agreed value, because a larger frame is dropped where the two networks meet. The supported range on a VXC interface is 1280 to 9074 bytes, capped by the agreed value for your AWS Interconnect. If you set an IP MTU above what the connection carries, the Portal rejects the change and reports the value the connection supports. **packet-filters** ## Packet filtering You can apply packet filters to an AWS Interconnect to permit or deny traffic based on its address and protocol details. A filter that you create on the AWS Interconnect is applied consistently across every path, so traffic is treated the same way regardless of which path it takes. A VXC can only reference packet filters configured on the AWS Interconnect to which it is attached. For more information about packet filters, see [Using Packet Filters with MCR](/mcr/packet-filters). **prefix-filters** ## Prefix filtering You can create prefix lists on an AWS Interconnect to control which routes are advertised and accepted. Like packet filters, prefix lists apply to all paths associated with the AWS Interconnect. For more information about prefix filtering, see [MCR Route Filtering](/mcr/route-filtering). **resiliency** ## Resiliency AWS Interconnect is designed for high resilience, with protection at both the physical layer and the routing layer. At the physical layer, Megaport delivers every AWS Interconnect over multiple link aggregation groups (LAGs), spread across separate locations in the metro, and across diversity zones within each location. At the routing layer, AWS Interconnect links its routers so that they share routes, and traffic continues over the remaining LAGs if any LAG goes down. These layers of redundancy work together, so an AWS Interconnect stays connected even if an entire location or diversity zone becomes unavailable. An AWS Interconnect is reported as live after all four of its routers are live and at least three of the four connections to AWS have been coordinated and are up. For more information, see [Resiliency](/aws-interconnect#resiliency) in the AWS Interconnect from Megaport Overview. **helpful-references** ## Helpful references * [AWS Interconnect from Megaport Overview](/aws-interconnect) * [Connecting to AWS Direct Connect](/cloud/megaport/aws) * [Creating a Private VXC](/connections/private-vxc) * [MCR Route Filtering](/mcr/route-filtering) * [Using MACsec with Megaport](/encryption/macsec) * [Using Packet Filters with MCR](/mcr/packet-filters) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.