Deploying the SBC on Cloud Infrastructures in Standalone Mode

Deploying the SBC in standalone mode on public clouds consists of deploying a single SBC. Standalone deployments are significantly less complex to configure and maintain. Although some object types are not required for standalone mode, you can use them for other purposes, if desired.

Differences between standalone and HA deployment include:

• EC2
  • The IAM role is not required for the SBC
  • Only a single management interface is required
  • No Elastic IP addressing is required
  • No Place Group is required
• OCI
  • No Instance Principal Authorization is required
  • No Dynamic Group is required
  • Only a single management interface is required
  • No Secondary Private addressing is required
• Azure
  • The IAM Network Contributor role is not required for the SBC
  • No Fault Domain is required
  • No Availability Set is required
  • Only a single management interface is required
  • No Elastic IP addressing is required

Although the procedures in this document include steps that are used to support HA, you use the same procedures without the HA steps to deploy the SBC in standalone mode. Procedure documentation indicates when a step applies to HA deployments.