Create a PD AWS EC2 package in Blesta
Configure the AWS account and instance specification a customer will receive. Saving the offering itself does not launch a server; the intended activation process creates real, chargeable AWS resources.
Configure the offering
- Open Packages → Packages → Add Package.
- Choose PD AWS EC2 and the intended saved AWS account.
- Set Region, Instance type, Image (OS) and Root disk size (GB) in the module fields. Review Startup script (user data) if needed.
- Review the client controls below. Set the terms and your own prices, then save it in the intended package group.
- When ready for sale, add that group to the appropriate order form under Packages → Order Forms.
Start with the package’s fixed resource settings. The module’s option-generation action is unavailable for Blesta in the release covered by this guide. Use the fixed package settings for this procedure rather than attempting to generate or manually recreate customer-selectable dimensions.
Review service activation. Eligible paid pending services use Provision Paid Pending Services automation, or staff activation if the package holds them for manual review. Keep the normal cron and automation running. Saving the package or receiving payment alone does not establish that an instance is ready.
Match region, instance type and image
Review the actual launch region, instance type and image together. Catalogue choices come from the module’s default region and can be cached; they do not reserve capacity or establish every combination’s availability elsewhere.
An OS family is resolved to an AMI for the launch region when provisioning. A specific AMI is region-specific and must be accessible to the selected account. Check image architecture and instance compatibility instead of treating a family label as a deployment test.
Root disk size (GB) governs the boot disk. Leaving the image-default choice uses the image’s own size. Do not confuse this with the separate Extra storage checkout option, which adds a data volume. Review any initialisation script before it runs, and keep provider secrets out of it.
Review client controls and allowances
Review Client: Start, Client: Stop, Client: Reboot, Client: Snapshots, Client: Firewall, Client: Volumes, Client: Connection details and Client: Usage graphs. Enable the intended actions and review how the offering covers provider costs rather than assuming a switch prices those resources.
Review any included or purchased backup allowance separately from automatic backup-retention days. These are different controls: one concerns how many backups the customer can keep, while the other concerns the automatic-retention process.
Client: Console also depends on the module-wide browser-console setting and the server’s actual support for that access method. Leave global console, scheduling and transfer-metering changes for separate deliberate setup. Client Area Section text must not expose provider credentials.
Review the full customer price
Set your own prices after considering compute, root disk, additional storage, addresses, backups, transfer and applicable OS costs. A generated suggestion based on Linux On-Demand compute in the default region is not the complete cost of this offering, especially when its region or operating system differs.
Verify an intended activation
Preview the form, effective selected choices and your own prices. When ready, use your normal authorised provisioning test and inspect Clients & Services, Activity, the actual instance and its intended access. Keep the normal cron running for finishing work such as address and extra-storage setup.
A running instance, saved offering or passed connection check does not prove that every finishing operation or guest login succeeded. Open the affected service under PD Modules → PD EC2 → Clients & Services and read Activity. Compare the selected account, region, instance type and image with the instance and related resources you can see in your own AWS account. Record any missing or unfinished step before requesting another activation.
See the PD AWS EC2 Blesta guide for related setup, or explore PD AWS EC2.
