-
Notifications
You must be signed in to change notification settings - Fork 145
Conversation
Your site preview for commit e9a0550 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-e9a0550a.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 325d7fc is ready! 🎉 http://pulumi-hugo-origin-pr-3533-325d7fc8.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 60661e0 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-60661e03.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 5a302c4 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-5a302c43.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 2495131 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-2495131e.s3-website.us-west-2.amazonaws.com. |
themes/default/content/blog/esc-env-run-aws/show-trust-policy.png
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check comments :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, Torian! I agree w/ a couple of Diana's comments (I replied to her existing comments where applicable), but fantastic work otherwise.
Your site preview for commit f045d96 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-f045d96f.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit f9b8cf6 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-f9b8cf61.s3-website.us-west-2.amazonaws.com. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Your site preview for commit 9a7a771 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-9a7a771b.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit ec94783 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-ec947838.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 1300724 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-13007248.s3-website.us-west-2.amazonaws.com. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, this is really comprehensive! Thank you for writing it 🙌
I think we could more or less ship this content as is (with edits and feedback of course) as it really is a full overview and pitch of ESC.
I think there is an opportunity for a slightly different style of content (maybe that is a completely separate post, maybe it is a set of edits to this post) that instead of leading with a pitch, leads with a clear concrete problem to be solved that might get picked up better by SEO and folks who aren't familiar with Pulumi and ESC.
For instance, what about changing the title to something like:
- How to Configure the AWS CLI
- Secure, Short-term Credentials for every AWS CLI command
- Acquiring credentials for
aws s3 ls
This is more "user problem" oriented. If I was a person struggling to set up or administer AWS access, I think I'd be more likely to click on content with this title rather than something with ESC in the name that I'd never heard of.
I would suggest moving the pitch and "power of ESC" sections to the end. I think the following structure would work really well:
- clearly and briefly introduce the user problem
- Simply state what ESC can do in one sentence
- solve the user problem (this is your comprehensive walk through
- pitch the broader benefits of ESC
- CTA/next steaps
Users will be far more receptive to the pitch if it comes after we've already solved a problem for them. For (1) and (2) I think we could say something like:
How do I get credentials for the AWS CLI? How do I securely share these credentials with teammates? I want to make sure everyone can easily and safely run
aws s3 ls
without needing to be a security wizard. I don't want to use static AWS key pairs due to the risks associated with long-lived, highly privileged credentials including copy-paste errors, and accidental VCS check-ins.// [Animated GIF showing someone running
aws s3 ls
and subsequent failure, and thenesc run ... -- aws s3 ls
and success]We'll learn how to use Pulumi ESC with the AWS CLI so that every command you run uses security best practices including short-term, scoped credentials issued via OIDC. Once we're up and running with ESC, it is easy to share these credentials across your team and org with Pulumi's comprehensive RBAC model."
Your site preview for commit 71340bb is ready! 🎉 http://pulumi-hugo-origin-pr-3533-71340bb7.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit af8deb2 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-af8deb2c.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 6044d99 is ready! 🎉 http://pulumi-hugo-origin-pr-3533-6044d990.s3-website.us-west-2.amazonaws.com. |
Requested edits have been made.
Site previews for this pull request have been removed. ✨ |
Description
This PR holds the content for the
esc run
blog.As this is my first blog, I am looking for overall feedback on the flow and voice of the content as well as validation that the steps included are clear and working as expected.
Review path:
/blog/esc-env-run-aws/
Checklist: