create_lag ¶

def create_lag(
    self,
    number_of_connections: "capo_direct_connect.types.count.Count",
    location: "capo_direct_connect.types.location_code.LocationCode",
    connections_bandwidth: "capo_direct_connect.types.bandwidth.Bandwidth",
    lag_name: "capo_direct_connect.types.lag_name.LagName",
    *,
    config_overrides: Optional[DirectConnectClientConfig] = None,
    connection_id: Optional[
        "capo_direct_connect.types.connection_id.ConnectionId"
    ] = None,
    tags: Optional["capo_direct_connect.types.tag_list.TagList"] = None,
    child_connection_tags: Optional[
        "capo_direct_connect.types.tag_list.TagList"
    ] = None,
    provider_name: Optional[
        "capo_direct_connect.types.provider_name.ProviderName"
    ] = None,
    request_mac_sec: Optional[
        "capo_direct_connect.types.request_mac_sec.RequestMACSec"
    ] = None,
    billing_mode: Optional[
        "capo_direct_connect.types.request_billing_mode.RequestBillingMode"
    ] = None,
) -> "capo_direct_connect.types.lag.Lag":
    """<p>Creates a link aggregation group (LAG) with the specified number of bundled physical dedicated connections between the customer network and a specific Direct Connect location. A LAG is a logical interface that uses the Link Aggregation Control Protocol (LACP) to aggregate multiple interfaces, enabling you to treat them as a single interface.</p> <p>All connections in a LAG must use the same bandwidth (either 1Gbps, 10Gbps, 100Gbps, or 400Gbps) and must terminate at the same Direct Connect endpoint.</p> <p>You can have up to 10 dedicated connections per location. Regardless of this limit, if you request more connections for the LAG than Direct Connect can allocate on a single endpoint, no LAG is created..</p> <p>You can specify an existing physical dedicated connection or interconnect to include in the LAG (which counts towards the total number of connections). Doing so interrupts the current physical dedicated connection, and re-establishes them as a member of the LAG. The LAG will be created on the same Direct Connect endpoint to which the dedicated connection terminates. Any virtual interfaces associated with the dedicated connection are automatically disassociated and re-associated with the LAG. The connection ID does not change.</p> <p>If the Amazon Web Services account used to create a LAG is a registered Direct Connect Partner, the LAG is automatically enabled to host sub-connections. For a LAG owned by a partner, any associated virtual interfaces cannot be directly configured.</p>

    Args:
        number_of_connections: <p>The number of physical dedicated connections initially provisioned and bundled by the LAG. You can have a maximum of four connections when the port speed is 1Gbps or 10Gbps, or two when the port speed is 100Gbps or 400Gbps.</p>
        location: <p>The location for the LAG.</p>
        connections_bandwidth: <p>The bandwidth of the individual physical dedicated connections bundled by the LAG. The possible values are 1Gbps,10Gbps, 100Gbps, and 400Gbps. </p>
        lag_name: <p>The name of the LAG.</p>
        connection_id: <p>The ID of an existing dedicated connection to migrate to the LAG.</p>
        tags: <p>The tags to associate with the LAG.</p>
        child_connection_tags: <p>The tags to associate with the automtically created LAGs.</p>
        provider_name: <p>The name of the service provider associated with the LAG.</p>
        request_mac_sec: <p>Indicates whether the connection will support MAC Security (MACsec).</p> <note> <p>All connections in the LAG must be capable of supporting MAC Security (MACsec). For information about MAC Security (MACsec) prerequisties, see <a href="https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-mac-sec-getting-started.html#mac-sec-prerequisites">MACsec prerequisties</a> in the <i>Direct Connect User Guide</i>.</p> </note>
        billing_mode: <p>The billing mode for the LAG.</p>

    Raises:
        capo_direct_connect.errors.direct_connect_client_exception.DirectConnectClientException: <p>One or more parameters are not valid.</p>
        capo_direct_connect.errors.direct_connect_server_exception.DirectConnectServerException: <p>A server-side error occurred.</p>
        capo_direct_connect.errors.duplicate_tag_keys_exception.DuplicateTagKeysException: <p>A tag key was specified more than once.</p>
        capo_direct_connect.errors.too_many_tags_exception.TooManyTagsException: <p>You have reached the limit on the number of tags that can be assigned.</p>
        capo_direct_connect.errors.UnknownServiceError: The service returned an error code this client does not model.
    """

    def _handler(
        req: "OperationRequest[capo_direct_connect.types.create_lag_request.CreateLagRequest]",
    ) -> OperationResponse["capo_direct_connect.types.lag.Lag"]:
        import capo_direct_connect._operations.overture_service.create_lag

        output, http_response = (
            capo_direct_connect._operations.overture_service.create_lag.create_lag(
                req.options, req.input
            )
        )
        return OperationResponse(output=output, response=http_response)

    interceptors_, options_ = self.operation_options(
        config_overrides, OperationLogging("CreateLag")
    )
    input_: capo_direct_connect.types.create_lag_request.CreateLagRequest = {
        "number_of_connections": number_of_connections,
        "location": location,
        "connections_bandwidth": connections_bandwidth,
        "lag_name": lag_name,
    }
    if connection_id is not None:
        input_["connection_id"] = connection_id
    if tags is not None:
        input_["tags"] = tags
    if child_connection_tags is not None:
        input_["child_connection_tags"] = child_connection_tags
    if provider_name is not None:
        input_["provider_name"] = provider_name
    if request_mac_sec is not None:
        input_["request_mac_sec"] = request_mac_sec
    if billing_mode is not None:
        input_["billing_mode"] = billing_mode

    response = execute_pipeline(
        OperationRequest(input=input_, options=options_),
        handler=_handler,
        interceptors=list(interceptors_),
    )
    response.response.close()
    return response.output