Modifiable Container Profiles are only available on the Enterprise plan.

Container Profiles provide flexibility and cost-optimization by allowing users to select the workload-appropriate Profile. Aptible offers three Container Profiles with unique CPU-to-RAM ratios and sizes:

  • General Purpose: The default Container Profile, which works well for most use cases.
  • CPU Optimized: For CPU-constrained workloads, this Profile provides high-performance CPUs and more CPU per GB of RAM.
  • RAM Optimized: For memory-constrained workloads, this Profile provides more RAM for each CPU allocated to the Container.

The General Purpose Container Profile is available by default on all Stacks. Whereas CPU and RAM Optimized Container Profiles are only available on Dedicated Stacks.

All new Apps & Databases are default created with the General Purpose Container Profile. This applies to Database Backups and Database Replicas.

Specifications per Container Profile

Container ProfileDefaultAvailable StacksCPU:RAM RatioRAM per CPUContainer SizesCost
General Purpose✔️Shared & Dedicated1/4 CPU:1GB RAM4GB/CPU512MB-240GB$0.08/GB/Hour
RAM OptimizedDedicated1/8 CPU:1GB RAM8GB/CPU4GB-752GB$0.05/GB/Hour
CPU OptimizedDedicated1/2 CPU:1GB RAM2GB/CPU2GB-368GB$0.10/GB/Hour

Supported Availability Zones

It is important to note that not all container profiles are available in every AZ, whether for app or database containers. In the event that this occurs during a scaling operation:

  • App Containers: Aptible will handle the migration of app containers to an AZ that supports the desired container profile seamlessly and with zero downtime, requiring no additional action from the user.
  • Database Containers: However, for database containers, Aptible will prevent the scaling operation and log an error message, indicating that it is necessary to move the database to a new AZ that supports the desired container profile. This process requires a full disk backup and restore but can be easily accomplished using Aptible’s 1-click “Database Restart + Backup + Restore.” It is important to note that this operation will result in longer downtime and completion time than typical scaling operations. For more information on resolving this error, including expected downtime, please refer to our troubleshooting guide.