This page explains how buying from CloudAccSale.com actually works, what arrives, and what becomes your responsibility the moment it does. If something here is unclear, support would rather answer before you buy than after.
Choosing a configuration
Each platform has its own product page listing every configuration supplied for it, with the price for each. The configuration name describes what differentiates it, such as a credit amount, a vCPU ceiling, a droplet or server limit, or whether outbound port 25 is open. Pick the one that matches the workload you have in mind. If two look similar, ask support rather than guessing.
A small number of configurations are priced on request rather than listed. Those show an On request state and a quote link instead of an add-to-cart button. That is deliberate: a price is never shown unless it is a real supplied price.
Ordering
Add the configuration you want to the cart, review the cart, then complete checkout. The selected configuration travels with the cart line, so what you checked out with is what is recorded on the order.
Delivery
Credentials and supporting information are provided after payment confirmation, within the window stated for that product. Delivery windows differ between configurations, so read the one on the product page you are buying rather than assuming a single sitewide figure.
The first ten minutes after delivery
Do these immediately, before deploying anything. They are not optional and they are the difference between a clean account and an expensive incident:
- Change the primary password.
- Enable multi-factor authentication on the root or primary identity.
- Review and rotate any existing access keys or API credentials.
- Create least-privilege users for day-to-day work and stop using the primary identity.
- Configure billing alerts and a spend threshold.
- Review the account for resources or access methods you did not create, and remove them.
What stays your responsibility
- Security. Hardening after delivery, and everything that follows from it.
- Cost. Billing alerts, usage monitoring and deleting unused resources. Cloud spend accrues whether or not anyone is watching.
- Compliance. Each provider terms of service and acceptable-use policy apply to you as the account holder.
- Availability and quotas. Uptime, performance and service limits are governed by the cloud provider, not by this marketplace.
- Credits. Where a configuration includes promotional credit, its amount, expiry and eligibility rules are set by the provider.
These are the same realities that apply to an account you create directly with a provider. Being explicit about them is part of how this marketplace prefers to operate.
Still stuck?
Contact support with the platform name, the configuration name and what you are trying to do.