ORACLE CLOUD

Bastion actions

10 actions you can wire into a flow, alongside everything else in the Oracle Cloud integration.

Every Bastion action

  • OCI Bastion: Change Bastion CompartmentMove a bastion into a different compartment: the bastion keeps its OCID, only its compartment placement changes.
  • OCI Bastion: Create BastionCreate a standard bastion in a target subnet. Optionally set a name, a client CIDR allow-list and a maximum session TTL. Returns a work-request id: poll Get Bastion until ACTIVE.
  • OCI Bastion: Create SessionOpen a managed SSH bastion session to a target host on a private subnet. Returns the session in a CREATING state plus a work-request id: poll Get Session until ACTIVE, then connect with the matching private key.
  • OCI Bastion: Delete BastionDelete an OCI Bastion by its OCID: returns a work-request OCID to poll for completion.
  • OCI Bastion: Delete SessionDelete a Bastion session by its OCID: it tears down the brokered SSH access.
  • OCI Bastion: Get BastionFetch a single OCI Bastion by its OCID: its type, target network, session limits and lifecycle state.
  • OCI Bastion: Get SessionFetch a single Bastion session by its OCID: its target-resource details, TTL, key type and lifecycle state.
  • OCI Bastion: List BastionsList the bastions in a compartment. Optionally filter by lifecycle state, exact name, or a specific bastion OCID. Walks pagination up to a safe cap.
  • OCI Bastion: List SessionsList the sessions on a bastion. Optionally filter by lifecycle state or exact display name and cap the page size. Walks pagination up to a safe limit.
  • OCI Bastion: Update BastionPartially update a bastion: change only the maximum session time-to-live or the client CIDR allow-list you supply; blank fields are left unchanged. Returns a work-request id to poll.

Also in Oracle Cloud

Put Bastion in a flow

These actions sit on the same canvas as every other integration, so a Bastion step can follow a form, a schedule or a message without any glue code.