[blog] "Zero to esc run <env> aws s3 ls"

[EvanBoyle]

Details

It should briefly cover:

1. configuring an OIDC provider
2. the companion environment definition
3. running commands

Note: Add K8s once supported

Resources

• ESC 1k Users Plan
• Draft PR

Tasks

Preview Give feedback

1. [Task] Write "From Zero to ESC - AWS" blog post #10107
   area/blog resolution/fixed +2
   
2. [Task] Update Azure OIDC guide #10125
   area/docs docs/content docs/guides kind/task +4
   
3. [Task] Update GCP OIDC guide #10126
   area/docs docs/guides +2
   
4. [Task] Update AWS OIDC guide #10204
   area/docs docs/guides +2
   
5. [Task] Write OIDC(?) Vault guide #10193
   area/docs docs/guides resolution/fixed +3
   

[aaronkao]

Ad copy

aws s3 ls without InvalidAccessKey

[arunkumar611]

updated the list of providers

[toriancrane]

Feedback from Slack: One thing to call out. Luke wanted us to have all of the individual cloud provider zero to esc run guides in the docs section similar to how we have for Pulumi IaC. We'd want 1 single blog post showing one scenario and have a call to action that points the user to checkout the docs for more scenarios. We do not want to have 7 separate blogs for each provider!"

[toriancrane]

Per the latest update from James, we are now pivoting this project to focus on creating step by step docs for OIDC configuration between Pulumi and relevant providers, similar to how it is done on this site.

The goal now is to bring our current OIDC documentation up one level so that it does not live underneath deployments and to update them so that they accommodate for multiple services.

Removing the focus on dynamic credentials for CLI commands unblocks me from the Azure and GCP tasks.

[toriancrane]

Draft PR available for updating/reorganizing our existing OIDC content so that it accommodates for more than one service (right now it is very Deployments flavored).

At the moment, I have done the following:

• Move OIDC content from under Deployments to Pulumi Cloud
• Updated OIDC hub page content
• Updated Azure OIDC page content

Posted in #team-docs channel for early round of reviews.

[toriancrane]

Latest update from SEO meeting:

• prioritize AWS OIDC content page including existing gifs/images from blog
• Azure and GCP will be text for now
• update ESC providers page to direct users to OIDC page

Next week will be dedicated towards figuring out how to do OIDC(?) with Vault

[pulumi-bot]

Cannot close issue:

• does not have required labels: kind/

Please fix these problems and try again.