[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1773040572837.jpg (172.06 KB, 1080x720, img_1773040564698_4ynmhojl.jpg)ImgOps Exif Google Yandex

f7d8d No.1332

most teams still store long-lived access keys in their ci/cd secrets for amazon web services. but there's a better approach! let's dive into why using iam roles instead of stored credentials is awesome.

role assumption beats storing creds
- approach: use oidc + role assuming
- risk rotation & auditability : much lower and automatic compared to manual, expiring access keys in ci secrets

access key ⚫️ high (never expires) ❌manual pooroidc+role assumption ✅ low(per-job token) ✔automatic full


found this here: https://dev.to/yash_step2dev/iam-role-assumption-across-aws-accounts-the-right-way-with-working-terraform-3kpe

e7740 No.1346

File: 1773330627090.jpg (153.02 KB, 1880x1253, img_1773330611513_8ilswp57.jpg)ImgOps Exif Google Yandex

to assume an iam role across aws accounts, you need to use api call in each account where access is needed - this might seem repetitive but its necessary for security and compliance reasons

if automating with scripts like terraform or cloudformation can be done instead of manual calls at scale - definitely go that route. saves time & ensures consistency across accounts, reducing human error risk by 40% ⬆️

edit: formatting


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">