Build Lightsail instance blueprint configurations with networking, add-ons, and user data scripts.
Build Lightsail instance blueprint configurations with networking, add-ons, and user data scripts.
Required Fields
InstanceNamesAvailabilityZoneBlueprintIdBundleIdOutput will appear here...Build an Amazon Lightsail instance definition from a Blueprint (an OS or application image like wordpress) and a Bundle (the fixed-price plan defining vCPU/RAM/storage/data-transfer allowance), Lightsail's simplified alternative to composing EC2, EBS, and a security group separately. Lightsail's flat-rate bundles include a fixed monthly data transfer allowance baked into the price, unlike EC2's pay-per-GB egress model, which means a Lightsail instance that exceeds its bundle's included transfer starts billing overage at a rate that can make it more expensive than an equivalent EC2 setup for a genuinely high-egress workload, the simplicity trades away EC2's more granular (and sometimes cheaper at scale) pricing model.
No, each bundle includes a specific data transfer allowance, going over it incurs overage charges per GB, it's not unlimited. For a workload with unpredictable or high egress (video, large file downloads), model the expected transfer against the bundle's allowance before assuming the flat monthly price is the total cost, a high-egress workload can end up costing more on Lightsail than on EC2 with its pay-per-GB (but no fixed floor) egress pricing.
You can change to a larger bundle for an existing instance, but downsizing to a smaller bundle isn't supported for a running instance, if you initially over-provisioned, moving to a smaller bundle typically means creating a new instance and migrating rather than an in-place downgrade.
No, deliberately simplified, Lightsail instances live in a Lightsail-managed VPC-like environment with a simpler port-based firewall (the Networking.Ports config) rather than full security groups, NACLs, and custom VPC topology. For a workload needing complex network segmentation, multiple subnets, or peering into an existing corporate VPC, plain EC2/VPC is the better fit, Lightsail intentionally trades that flexibility for simplicity.
The builder validates that InstanceNames, AvailabilityZone, BlueprintId, and BundleId all resolve before accepting the JSON as a valid CreateInstances request, the fields Lightsail needs to know what image, what plan, and where to launch; it can't verify the specific BlueprintId/BundleId combination is actually valid together, that's checked only against the live Lightsail API.
Always check a bundle's included data transfer against your workload's actual expected egress before committing, Lightsail's pricing advantage assumes you stay within the bundle, a workload that regularly exceeds it should be sized against EC2's actual pay-per-GB cost instead.
Lightsail bundle downsizing isn't supported in place, size conservatively upward if you're unsure, since scaling down later means a migration, not a quick resize.
The AutoSnapshot add-on's SnapshotTimeOfDay should be scheduled during your actual lowest-traffic window, not an arbitrary time, since snapshot creation has some I/O impact on the instance while it runs.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.