Chapter 1. Use Case Considerations

Because Amazon Web Services is an image-only service, there are common Satellite use cases that do not work, or require extra configuration in an Amazon Web Service environment. If you plan to use Satellite on AWS, ensure that the use case scenarios that you want to use are available in an AWS environment.

1.1. Use Cases Known to Work

You can perform the following Red Hat Satellite use cases on AWS:

Subscriptions

Not all Red Hat subscriptions are eligible to run in public cloud environments. For more information about subscription eligibility, see the Red Hat Cloud Access Page. You can create additional organizations and then import additional manifests to the organizations. For more information, see Creating an Organization in Administering Red Hat Satellite.

Multi-homed Satellite and Capsule

Multi-homed Satellite is not supported.

Multi-homed Capsule is supported, to implement this, you can configure Capsules with a load balancer. For more information, see Configuring Capsules with a Load Balancer.

You must do this when Satellite Server or Capsule Server has different internal and external DNS host names and there is no site-to-site VPN connection between the locations where you deploy Satellite Server and Capsule Server.

On demand content sources

You can use the On demand download policy to reduce the storage footprint of the server that runs Satellite. When you set the download policy to On Demand, content syncs to Satellite Server or Capsule Server when a content host requests it.

For more information, see Importing Content in Managing Content.

1.2. Use Cases that Do Not Work

In AWS, you cannot manage the DHCP. Because of this, most of Satellite Server’s kickstart and PXE provisioning models are unusable. This includes:

  • PXE Provisioning
  • Discovery and Discovery Rules

  • ISO Provisioning methods.

    • PXE-Less Discovery (iPXE)
    • Per-host ISO
    • Generic ISO
    • Full-host ISO