<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Iam on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/iam/</link><description>Recent content in Iam on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 01 Sep 2026 15:20:27 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/iam/index.xml" rel="self" type="application/rss+xml"/><item><title>Amazon Redshift adds IAM Identity Center auth with enhanced VPC routing</title><link>https://curadevops.metacog.co.kr/insights/2026-09-01-amazon-redshift-now-supports-aws-iam-identity-center-authent/</link><pubDate>Tue, 01 Sep 2026 15:20:27 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-01-amazon-redshift-now-supports-aws-iam-identity-center-authent/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If Redshift is in your stack and you have data residency or network-isolation requirements, this is worth adopting: SSO via IAM Identity Center with all auth traffic staying inside your VPC via PrivateLink. Evaluate enabling EVR and wiring up Identity Center for your provisioned clusters or serverless workgroups this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Redshift now supports SSO via IAM Identity Center with network traffic fully contained in your VPC — relevant context if your org has regulatory or data-residency mandates for analytics infrastructure, but no decision is forced by this launch.&lt;/li>
&lt;/ul></description></item><item><title>IAM Roles Anywhere adds native Java SDK v2 plugin for credential resolution</title><link>https://curadevops.metacog.co.kr/insights/2026-08-26-iam-roles-anywhere-now-provides-a-java-plugin-for-the-aws-sd/</link><pubDate>Wed, 26 Aug 2026 11:21:00 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-26-iam-roles-anywhere-now-provides-a-java-plugin-for-the-aws-sd/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Simplifies how Java workloads outside AWS obtain temporary credentials via Roles Anywhere without a sidecar process, worth knowing when evaluating hybrid or on-prem workload auth patterns.&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> Relevant if build pipelines run Java workloads outside AWS that need AWS credentials; the plugin could replace credential_process workarounds, but no deadline or deprecation drives urgency.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>AWS Lambda gains full IAM resource-based policy support</title><link>https://curadevops.metacog.co.kr/insights/2026-08-25-aws-lambda-functions-now-support-full-iam-resource-based-pol/</link><pubDate>Tue, 25 Aug 2026 11:19:32 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-25-aws-lambda-functions-now-support-full-iam-resource-based-pol/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Platform teams managing Lambda in multi-account architectures can now consolidate per-principal permission statements into single policy documents with full IAM condition key support (source IP, principal tags, etc.). Plan a policy consolidation pass for existing Lambda functions to reduce policy sprawl and simplify ongoing management.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> This GA capability reduces IAM policy complexity for Lambda-heavy multi-account orgs, but it&amp;rsquo;s an incremental improvement rather than a strategic or cost-model shift — no leadership decision required.&lt;/li>
&lt;/ul></description></item><item><title>Amazon DynamoDB Streams adds attribute-based access control (ABAC)</title><link>https://curadevops.metacog.co.kr/insights/2026-08-21-amazon-dynamodb-streams-now-supports-attribute-based-access/</link><pubDate>Fri, 21 Aug 2026 11:18:28 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-21-amazon-dynamodb-streams-now-supports-attribute-based-access/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> GA capability that simplifies multi-team DynamoDB Streams IAM policy management via tag-based conditions; worth adopting this quarter if you manage access across multiple environments or teams on DynamoDB Streams.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Amazon Bedrock Web Search gains external public web access option</title><link>https://curadevops.metacog.co.kr/insights/2026-08-20-launching-external-web-access-for-web-search-on-amazon-bedro/</link><pubDate>Thu, 20 Aug 2026 11:19:17 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-20-launching-external-web-access-for-web-search-on-amazon-bedro/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> If the org uses Bedrock for AI-grounded applications, this new IAM-gated capability lets models fetch live public web content, which may affect data-boundary and cost assumptions worth noting during the next AI tooling review.&lt;/li>
&lt;/ul></description></item><item><title>SageMaker Notebooks gain per-user identity propagation via IAM Identity Center</title><link>https://curadevops.metacog.co.kr/insights/2026-08-20-amazon-sagemaker-notebooks-now-support-trusted-identity-prop/</link><pubDate>Thu, 20 Aug 2026 11:19:17 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-20-amazon-sagemaker-notebooks-now-support-trusted-identity-prop/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Relevant if your org runs SageMaker and Lake Formation with fine-grained data access; this GA feature removes the need for shared execution roles and adds per-user CloudTrail audit trails. No immediate action required unless you&amp;rsquo;re actively designing a multi-user analytics platform.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Per-user data boundaries enforced at the Lake Formation layer with automatic identity propagation reduces compliance friction for orgs with strict data governance requirements; worth noting when evaluating SageMaker Unified Studio for enterprise analytics use cases.&lt;/li>
&lt;/ul></description></item><item><title>IAM Policy Autopilot adds Terraform plan file support for policy gen</title><link>https://curadevops.metacog.co.kr/insights/2026-08-19-iam-policy-autopilot-now-supports-terraform-plan-files/</link><pubDate>Wed, 19 Aug 2026 11:17:39 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-19-iam-policy-autopilot-now-supports-terraform-plan-files/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Platform engineers managing Terraform-deployed AWS infra can now generate least-privilege IAM policies directly from plan files rather than hand-crafting them; worth integrating into the IaC workflow this quarter to reduce wildcard usage and policy drift.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Amazon S3 now includes policy ARN in 403 access denied errors</title><link>https://curadevops.metacog.co.kr/insights/2026-08-14-amazon-s3-adds-additional-policy-details-to-access-denied-er/</link><pubDate>Fri, 14 Aug 2026 11:38:17 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-14-amazon-s3-adds-additional-policy-details-to-access-denied-er/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Useful S3 IAM debuggability improvement — policy ARNs now appear directly in 403 error messages, reducing time spent hunting down which SCP or identity-based policy caused a denial. No configuration required; available automatically across all regions.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>AWS IAM Role Manager GA: auto-creates service roles in console</title><link>https://curadevops.metacog.co.kr/insights/2026-08-13-aws-iam-now-provides-role-manager-to-set-up-iam-roles-automa/</link><pubDate>Thu, 13 Aug 2026 11:41:08 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-13-aws-iam-now-provides-role-manager-to-set-up-iam-roles-automa/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Role manager can simplify onboarding new AWS services by auto-generating least-privilege starter roles, but teams with strict IaC discipline should evaluate whether console-created roles conflict with Terraform/CDK-managed IAM. Schedule a review of how role manager interacts with existing role governance before enabling org-wide.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Role manager lowers the barrier to correct IAM role setup for console-driven workflows, which may reduce misconfiguration risk across teams; worth noting as a governance tool but no immediate strategic decision required.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement&lt;/li>
&lt;/ul></description></item><item><title>AWS IAM Identity Center makes account management optional for new instances</title><link>https://curadevops.metacog.co.kr/insights/2026-08-07-aws-iam-identity-center-makes-management-of-aws-account-acce/</link><pubDate>Fri, 07 Aug 2026 00:23:45 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-07-aws-iam-identity-center-makes-management-of-aws-account-acce/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> New configuration option for net-new IAM Identity Center instances reduces the service-linked role footprint when only AWS application SSO is needed. Worth noting for future greenfield deployments; no action required on existing instances.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Reduces the access surface when standardizing on IAM Identity Center for application SSO without requiring full AWS account management delegation — useful context when evaluating identity architecture for new AWS org setups.&lt;/li>
&lt;/ul></description></item><item><title>Amazon Neptune adds tag-based IAM access control (TBAC)</title><link>https://curadevops.metacog.co.kr/insights/2026-07-28-amazon-neptune-now-supports-tag-based-access-control-for-iam/</link><pubDate>Tue, 28 Jul 2026 12:49:37 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-28-amazon-neptune-now-supports-tag-based-access-control-for-iam/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> New GA Neptune capability that replaces static ARN enumeration in IAM policies with attribute-based cluster access using resource and principal tags; plan to adopt TBAC if you operate multiple Neptune clusters in shared VPC environments to enforce team and environment isolation.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Neptune now supports attribute-based access governance across clusters via IAM tags, useful context for organizations running Neptune at scale, but no strategic, licensing, or cost decision is triggered.&lt;/li>
&lt;/ul></description></item></channel></rss>