Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Commit

Permalink
updated front matter
Browse files Browse the repository at this point in the history
  • Loading branch information
toriancrane committed Oct 26, 2023
1 parent ec94783 commit 1300724
Showing 1 changed file with 10 additions and 4 deletions.
14 changes: 10 additions & 4 deletions themes/default/content/blog/esc-env-run-aws/index.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,16 @@
---
title: "From Zero to esc run"
authors: ["torian-crane"]
tags: ["aws", "secrets", "credentials-management"]
meta_desc: "From Zero to esc run placeholder area for blog content."
title: "Enhancing Credential Management with Pulumi ESC: A Step-by-Step Guide to 'esc run'"
allow_long_title: true
date: "2023-10-26"
draft: false
meta_desc: "Learn more about reducing the overhead of credentials management with the 'esc run' command of Pulumi ESC."
meta_image: "meta.png"
authors:
- torian-crane
tags:
- aws
- secrets
- credentials-management
---

In a world where cloud computing is the backbone of modern applications, managing environments and secrets is of the utmost importance. Earlier this month we released a new service called [Pulumi ESC (Environments, Secrets, and Configuration)](/product/esc/), the focus of which is to help alleviate the burden of managing cloud configuration and secrets by providing a centralized way to handle these critical aspects of cloud development. It’s like having a Swiss Army knife in your toolkit, ready to tackle the challenges of cloud infrastructure. This post will highlight the specific challenge of **credentials management**, and we’ll specifically dive into how using the `esc run` functionality of Pulumi ESC will make that easier.
Expand Down

0 comments on commit 1300724

Please sign in to comment.