AWS CloudFormation vs Canonical Landscape

AWS CloudFormation models, provisions, and manages related AWS and third-party resources as infrastructure as code. YAML or JSON templates define AWS resources and their properties. StackSets deploy a common set of resources across multiple AWS accounts and Regions; Change Sets preview proposed stack updates, including possible deletion or replacement, and Drift Detection tracks changes made outside the service. For authoring, AWS CDK supports TypeScript, Python, Java, and .NET, while AWS SAM offers shorthand YAML for serverless resources that is converted during deployment. The CloudFormation Registry supports third-party resources and modules, and stacks can be updated from remote Git repositories. The service is available through API, Linux, macOS, web, and Windows, and manages state. CloudFormation itself has a free plan, with no additional charge for AWS and Alexa resource providers, but created AWS resources are billed at their standard rates. Third-party provider and custom hook operations may also incur charges. Access can be managed with IAM, and CloudTrail logs API calls.

Canonical Landscape manages Ubuntu desktops, servers, cloud instances, IoT devices, and other Ubuntu systems from a central portal. Administrators can handle updates, packages and repositories, run scripts remotely, set role-based access, and monitor machines. It can alert on updates and graph temperature, disk and memory use, system load, and custom metrics. One instance can manage up to 40,000 machines, with options to scale further. Deployment choices are Canonical-hosted SaaS, Managed Landscape, and self-hosted software; SaaS is bundled with Ubuntu Pro. A free SaaS account with Ubuntu Pro covers up to five machines. Managed Landscape costs $6,861 a year per physical machine on public clouds, VMware, OpenStack, or LXD, or $9,470 a year per physical machine on bare metal. No self-hosted price is listed; Ubuntu Pro is its main licensing mechanism. Landscape has a scriptable API and can integrate with configuration management, monitoring, and ticketing systems. Self-hosting requires the organization to install, host, and maintain it. SaaS does not currently offer repository mirroring or custom external identity-provider configuration.