1. Platform Preparation and Installation Guide
  2. Public Cloud Platforms
  3. Deploying the SBC on Cloud Infrastructures in HA Mode
  4. Cloud-Specific HA Deployment Considerations
  5. HA over AWS Overview

HA over AWS Overview

AWS uses Identity and Access Management (IAM) roles to provide instances access to the infrastructure services. Configure an IAM role with required policies and associate the IAM role with SBC instances during creation. The instances can then obtain the credentials through the metadata and authenticate itself while invoking the API.

As you deploy, follow these guidelines:

  1. Create both SBC instances in the same Availability Zone.
  2. Oracle recommends that you use Place Groups of type Spread for launching both SBC instances.

As you configure, follow these guidelines:

  1. On the primary instance of SBC, and through the AWS console, configure Secondary Private IPs to be used as SBC virtual IPs.
  2. When required, map Secondary Private IP addressing with Elastic IP addressing.

AWS uses its Access key ID and Secret access key as security credentials. Since these credentials change periodically, the SBC does not cache the information. Instead, the SBC always retrieves and uses the latest information from the metadata. In addition, the SBC retries the API by refreshing the latest security credentials if it receives any error response indicating the authentication failed.