cloudConnect

Retry creation of an expired TGW breakout

<Info icon="fa-light fa-lock" className="permission-callout"> <div className="permission-callout__header"><span className="permission-callout__title"><span className="permission-callout__label">Required permissions</span> <span className="fern-docs-badge small blue subtle rounded-full permission-callout__beta">Beta</span></span> <span className="permission-callout__learn-more">[Learn more](/developers/api-guidelines/permissions#how-permissions-work)</span></div>

CloudConnect.Breakout + Create

<div className="permission-callout__roles"><span className="permission-callout__roles-label">Roles:</span> <Badge intent="info">Administrator</Badge> <Badge intent="info">User</Badge></div> </Info>

Retries the creation of a Transit Gateway breakout where the accept attachment state has expired, meaning the attachment on the customer's side has not been created in time.

Retry is only allowed if:

  • The breakout is of type Transit Gateway (type_id: 1)
  • The breakout is in status Pending AWS Activation (status_id: 2)
  • The accept attachment state has expired (7 days after creation)
patch/api/v1/cnc/breakout/{cloudconnect_attachment_id}

Request

  • Base URL: https://cdn.emnify.net
  • URL: https://cdn.emnify.net/api/v1/cnc/breakout/{cloudconnect_attachment_id}
  • Auth: HTTP bearer

Path parameters

cloudconnect_attachment_idnumber double required

Numerical ID of a Cloud Connect attachment

Response

Response to a successful GET, also used for a POST if it does not result in a creation

CloudConnectRetryCloudConnectAttachmentResponse200 required

Empty response body

Changes

No recorded changes to this operation across all 1 revision of this API.