Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix a couple of broken links #12554

Merged
merged 1 commit into from
Aug 19, 2024
Merged

Fix a couple of broken links #12554

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions content/case-studies/sst.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,16 @@
title_tag: SST | Case Studies
title: "SST: Moving Away from CDK"
description: |
SST builds a new version of SST (Ion) on Pulumi instead of CDK because of its limitations around speed, error handling, leaky abstractions, non-AWS provider support, and more.
SST builds a new version of SST (Ion) on Pulumi instead of CDK because of its limitations around speed, error handling, leaky abstractions, non-AWS provider support, and more.
meta_desc: Read why SST switched to Pulumi and stopped using CDK because of its limitations around speed, error handling, leaky abstractions, non-AWS provider support, and more.

customer_name: SST
customer_logo: /logos/customers/sst-logo.svg
customer_url: https://sst.dev/blog/moving-away-from-cdk.html
redirect_to: https://sst.dev/blog/moving-away-from-cdk.html
customer_url: https://sst.dev/blog/moving-away-from-cdk
redirect_to: https://sst.dev/blog/moving-away-from-cdk

---

## Read the Blog

SST is working on a new version of SST called Ion. The current iteration of SST is based off of AWS CDK and CloudFormation. There are significant limitations to SST because of its dependencies on CDK and CloudFormation. CloudFormation is a proprietary cloud-based service that is opaque and CDK is only transpiling down to CloudFormation and doesn't create any infrastructure. This creates issues around speed, error handling, leaky abstractions, and state management. For Ion, SST uses Pulumi's engine underneath, which provides greater transparency and control over how the code executes and the infrastructure that is provisioned. Read Jay V's (Founder & CEO of SST) blog post on "[Moving away from CDK](https://sst.dev/blog/moving-away-from-cdk.html)".

4 changes: 2 additions & 2 deletions content/tutorials/pulumi-deployments-click-to-deploy/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Next, the [Pulumi GitHub App](/docs/using-pulumi/continuous-delivery/github-app/

## Create a New Project with the New Project Wizard

To create a new Pulumi project, commit its code, and deploy it entirely from your browser, you will use the [New Project Wizard](/docs/pulumi-cloud/developer-portals/new-project-wizard/). The wizard allows you to start from one of Pulumi’s public templates, your [Organization Templates](/docs/pulumi-cloud/developer-portals/templates), or even generate a custom project using the cloud resources and your preferred language of choice with [Pulumi AI](link).
To create a new Pulumi project, commit its code, and deploy it entirely from your browser, you will use the [New Project Wizard](/docs/pulumi-cloud/developer-portals/new-project-wizard/). The wizard allows you to start from one of Pulumi’s public templates, your [Organization Templates](/docs/pulumi-cloud/developer-portals/templates), or even generate a custom project using the cloud resources and your preferred language of choice with [Pulumi AI](/ai).

First, navigate to the **New Project** tab in the Pulumi Cloud console. Choose your source template from Pulumi, then you can optionally choose your cloud and language to filter the results or search all templates.

Expand All @@ -63,7 +63,7 @@ These values populate the `config` section in the `Pulumi.<stack>.yaml` file, sp

### Environment

If you've configured [environments](/docs/pulumi-cloud/esc) with your organization, you can specify one to use with the resulting stack. Environments enable teams to define and share collections of configuration and secrets across multiple Pulumi projects and stacks, such as your `AWS_SECRET_ACCESS_KEY` which will be needed to configure your deployment settings.
If you've configured [environments](/docs/pulumi-cloud/esc) with your organization, you can specify one to use with the resulting stack. Environments enable teams to define and share collections of configuration and secrets across multiple Pulumi projects and stacks, such as your `AWS_SECRET_ACCESS_KEY` which will be needed to configure your deployment settings.

### Repository

Expand Down
Loading