# AWS Organizations

AWS Organizations is an Amazon Web Services service for centrally governing and managing AWS resources across multiple accounts and services.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## This Month in AWS DevOps Agent: November 2026

DevFeed: [This Month in AWS DevOps Agent: November 2026](<https://devfeed.tech/articles/this-month-in-aws-devops-agent-november-2026-146990.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/this-month-in-aws-devops-agent-november-2026/>)

Author: Nereida Woo

Published: 2026-11-21T01:47:57Z

Content type: release

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [DevAIOps](<https://devfeed.tech/topics/devaiops.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>)

Tags: [agent-sandbox](<https://devfeed.tech/tags/agent-sandbox.md>), [amazon-bedrock-guardrails](<https://devfeed.tech/tags/amazon-bedrock-guardrails.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-govcloud-us](<https://devfeed.tech/tags/aws-govcloud-us.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [faster](<https://devfeed.tech/tags/faster.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [post-types](<https://devfeed.tech/tags/post-types.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [reviews](<https://devfeed.tech/tags/reviews.md>)

### AI overview

November updates extend AWS DevOps Agent to AWS GovCloud (US-West) and let teams associate an Agent Space with an organizational unit or organization root; organization mode is unavailable in GovCloud, and GovCloud omits some features, including Sandbox and private connections. Investigations now finish faster and stream summaries, while Sandbox (preview) runs code in an isolated environment scoped to one investigation or conversation, with read-only AWS calls and restricted network access. Teams can replay investigations to compare configuration changes, receive sampled automatic quality Reviews, and track nine CloudWatch metrics. Memory additions include importing custom knowledge, semantic search, linked memories, and weekly reviews that can remove stale claims, merge duplicates, or resolve contradictions with recorded evidence and version history. The agent also adds partner-hosted MCP connectors, a skills catalog, chat in Slack, Teams, and MCP clients, and code change risk analysis in preview. Availability and capabilities vary by Region; partner connector requests may leave the Agent Space's AWS Region.

### Source excerpt

Introduction November brought AWS DevOps Agent to AWS GovCloud (US-West) and added AWS Organizations support, so teams can connect an entire organizational unit to an Agent Space instead of one account at a time. Investigations now complete faster and show a real-time summary as they run. Replay and automatic Reviews give teams a way to [...]

## Announcing custom execution roles for AWS CloudFormation StackSets

DevFeed: [Announcing custom execution roles for AWS CloudFormation StackSets](<https://devfeed.tech/articles/announcing-custom-execution-roles-for-aws-cloudformation-stacksets-145204.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/announcing-custom-execution-roles-for-aws-cloudformation-stacksets/>)

Author: Tanvi Ravindra Malali

Published: 2026-11-20T00:46:23Z

Content type: release

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [amazon](<https://devfeed.tech/topics/amazon.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [custom](<https://devfeed.tech/tags/custom.md>), [define](<https://devfeed.tech/tags/define.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [iam](<https://devfeed.tech/tags/iam.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [least-privilege](<https://devfeed.tech/tags/least-privilege.md>), [macros](<https://devfeed.tech/tags/macros.md>), [managed](<https://devfeed.tech/tags/managed.md>), [nested](<https://devfeed.tech/tags/nested.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [roles](<https://devfeed.tech/tags/roles.md>)

### AI overview

Custom execution role templates let service-managed CloudFormation StackSets use a workload-scoped IAM role in each member account instead of the default AdministratorAccess role. StackSets validates and stores a template that must create exactly one IAM role, use the `stacksets-exec-custom-` name prefix, trust the management account's StackSets service-linked role, provide the `StackSetExecutionRoleName` output, and contain no nested stacks or transforms. The role template requires `CAPABILITY_NAMED_IAM`; workload templates using transforms or macros also require `CAPABILITY_AUTO_EXPAND`. This enables service-managed stack sets to deploy workloads with nested stacks, transforms, and macros. Switching roles does not delete the default role; reverting to it likewise leaves the custom role and bootstrap stack behind, so cleanup is manual. Custom role templates require service-managed permissions and Organizations trusted access, and cannot be used with self-managed StackSets.

### Source excerpt

AWS CloudFormation StackSets now supports custom execution role templates, so you can define the IAM role StackSets uses in each member account instead of the default AdministratorAccess role. Scope permissions to least privilege, and deploy service-managed stack sets that use nested stacks, macros, and transforms.

## Track AWS CloudFormation StackSets deployments with progress visibility

DevFeed: [Track AWS CloudFormation StackSets deployments with progress visibility](<https://devfeed.tech/articles/track-aws-cloudformation-stacksets-deployments-with-progress-visibility-145205.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/track-aws-cloudformation-stacksets-deployments-with-progress-visibility/>)

Author: Idriss Laouali Abdou

Published: 2026-11-20T00:40:44Z

Content type: article

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-cloud-development-kit](<https://devfeed.tech/tags/aws-cloud-development-kit.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cdk](<https://devfeed.tech/tags/cdk.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [code](<https://devfeed.tech/tags/code.md>), [console](<https://devfeed.tech/tags/console.md>), [counts](<https://devfeed.tech/tags/counts.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [progress](<https://devfeed.tech/tags/progress.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

AWS CloudFormation StackSets adds stage-by-stage deployment progress for operations started after launch. In the console, the Progress tab shows role provisioning and stack deployment status and counts, with stack deployment progress by Region; results remain available after completion. The DescribeStackSetOperation API includes regional details, while ListStackSetOperations provides stage details without the regional breakdown. This helps explain cases where an overall SUCCEEDED operation deployed nothing: role provisioning may have failed and all stack instances were skipped. Counts and totals may be absent until targets are resolved, and older operations lack the new Stages field. The change is additive; use AWS CLI version 2 or an AWS SDK released on or after November 18, 2026 to access the fields.

### Source excerpt

AWS CloudFormation StackSets now adds deployment progress visibility, a stage-by-stage view of where each stack set operation stands. See how much work is complete and which accounts and stack instances need attention, and follow a deployment while it runs across tens or thousands of accounts.

## Securing multi-team Amazon Neptune with tag-based access control

DevFeed: [Securing multi-team Amazon Neptune with tag-based access control](<https://devfeed.tech/articles/securing-multi-team-amazon-neptune-with-tag-based-access-control-144313.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/securing-multi-team-amazon-neptune-with-tag-based-access-control/>)

Author: Brian M. Slater

Published: 2026-11-19T21:03:50Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Dynamic authorization rules](<https://devfeed.tech/topics/dynamic-authorization-rules.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [amazon-neptune](<https://devfeed.tech/tags/amazon-neptune.md>), [applications](<https://devfeed.tech/tags/applications.md>), [aws](<https://devfeed.tech/tags/aws.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [data](<https://devfeed.tech/tags/data.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [iam](<https://devfeed.tech/tags/iam.md>), [policies](<https://devfeed.tech/tags/policies.md>), [tag](<https://devfeed.tech/tags/tag.md>), [tags](<https://devfeed.tech/tags/tags.md>), [team](<https://devfeed.tech/tags/team.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Amazon Neptune's tag-based access control (TBAC) can isolate teams on shared clusters by requiring both caller and cluster tags--such as LineOfBusiness and ApplicationID--to match. Separate deny-on-mismatch statements in an organization-level Service Control Policy (SCP) enforce both checks; a central security team can own the guardrail while a provisioning pipeline controls resource tags and federated identity supplies principal tags. The source requires Neptune engine 1.3.x or later and IAM authentication. TBAC gates access at cluster level, not individual graph elements, and connections without IAM authentication bypass these policies. Because a deny-based SCP cannot require IAM authentication at cluster creation, the source recommends provisioning controls, AWS Config detection, and SSM remediation; enabling IAM authentication on an existing cluster restarts its engine and ends open connections. It also notes tag changes take about five minutes to affect evaluation, IAM policy changes up to ten minutes, and suggests validating matched and mismatched access and checking CloudTrail denials. The same tag taxonomy may extend to other data services, subject to each service's condition

### Source excerpt

Amazon Neptune now supports tag-based access control (TBAC) for data-plane operations. This post walks through three scenarios for isolating multiple teams on a shared fleet of Neptune clusters using AWS resource tags and IAM principal tags as conditions in IAM policies and service control policies.

## Control your AWS Lambda runtimes with customer-managed runtimes

DevFeed: [Control your AWS Lambda runtimes with customer-managed runtimes](<https://devfeed.tech/articles/control-your-aws-lambda-runtimes-with-customer-managed-runtimes-141947.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/control-your-aws-lambda-runtimes-with-customer-managed-runtimes/>)

Author: Jonathan Tuliani

Published: 2026-11-18T18:53:02Z

Content type: article

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [container-security](<https://devfeed.tech/topics/container-security.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [enterprise deployment](<https://devfeed.tech/topics/enterprise-deployment.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [change](<https://devfeed.tech/tags/change.md>), [contents](<https://devfeed.tech/tags/contents.md>), [control](<https://devfeed.tech/tags/control.md>), [customer](<https://devfeed.tech/tags/customer.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [event](<https://devfeed.tech/tags/event.md>), [functions](<https://devfeed.tech/tags/functions.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [managed](<https://devfeed.tech/tags/managed.md>), [organization](<https://devfeed.tech/tags/organization.md>), [package](<https://devfeed.tech/tags/package.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [runtimes](<https://devfeed.tech/tags/runtimes.md>), [share](<https://devfeed.tech/tags/share.md>), [updates](<https://devfeed.tech/tags/updates.md>), [zip](<https://devfeed.tech/tags/zip.md>)

### AI overview

AWS Lambda customer-managed runtimes let publishers package runtime contents in immutable ECR-backed versions, share them with function developers, and manage updates through aliases. Developers reference an alias and keep deploying .zip files; functions pick up alias changes at cold starts without per-function redeployment. Publishers can stage rollouts across environments or Regions, monitor invocation and error metrics, and roll back by repointing an alias. Publishers must rebuild and patch runtimes themselves; Lambda does not patch them. Cross-account use requires both a runtime resource policy and consumer identity permissions, and publishers are trusted to change code used by consuming functions. Deletion is delayed 7-30 days, with restoration possible during the wait; removing an alias or version can make dependent functions inactive and cold-start invocations fail. There is no additional Lambda charge, though ECR image storage fees apply.

### Source excerpt

AWS Lambda customer-managed runtimes give you full control over the contents, updates, access, and lifecycle of the runtime your Lambda Event Functions use. Package a runtime once, share it across your organization, and roll out updates centrally. Functions pick up the change automatically, keeping the same .zip deployment experience.

## Governing your AI workloads on AWS at scale: visibility, controls, and monitoring

DevFeed: [Governing your AI workloads on AWS at scale: visibility, controls, and monitoring](<https://devfeed.tech/articles/governing-your-ai-workloads-on-aws-at-scale-visibility-controls-and-monitoring-141047.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/governing-your-ai-workloads-on-aws-at-scale-visibility-controls-and-monitoring/>)

Author: Matej Macek

Published: 2026-11-18T18:33:55Z

Content type: tutorial

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [AWS Security Hub](<https://devfeed.tech/topics/aws-security-hub.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>), [aws inspector](<https://devfeed.tech/topics/aws-inspector.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-inventory](<https://devfeed.tech/tags/ai-inventory.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-config](<https://devfeed.tech/tags/aws-config.md>), [aws-security-hub](<https://devfeed.tech/tags/aws-security-hub.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloud-governance](<https://devfeed.tech/tags/cloud-governance.md>), [cloud-operations](<https://devfeed.tech/tags/cloud-operations.md>), [configuration-compliance-and-auditing](<https://devfeed.tech/tags/configuration-compliance-and-auditing.md>), [conformance-pack](<https://devfeed.tech/tags/conformance-pack.md>), [controls](<https://devfeed.tech/tags/controls.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [enterprise-governance-and-control](<https://devfeed.tech/tags/enterprise-governance-and-control.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [learn-how-to](<https://devfeed.tech/tags/learn-how-to.md>), [management-governance](<https://devfeed.tech/tags/management-governance.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [organization](<https://devfeed.tech/tags/organization.md>), [route](<https://devfeed.tech/tags/route.md>), [scale](<https://devfeed.tech/tags/scale.md>), [security](<https://devfeed.tech/tags/security.md>), [teams](<https://devfeed.tech/tags/teams.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [type](<https://devfeed.tech/tags/type.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

The article presents a four-step approach to governing AI workloads across AWS accounts: build an inventory, select controls by workload type and autonomy, deploy AWS Config conformance packs organization-wide, and route findings to owners. Visibility combines Security Hub AI inventory, Config, CloudTrail and optional model invocation logs, Network Firewall category alerts, and CloudWatch telemetry; each source has limits, and Config's AI resource coverage is still growing. The article recommends preventive, detective, and proactive controls, including Bedrock policies and SCPs, plus four packs for supporting infrastructure, Bedrock, SageMaker AI, and self-hosted AI/ML. Managed rules leave gaps, so custom Guard or Lambda rules may be needed. Config results can feed Security Hub and EventBridge workflows; newly deployed packs may initially show incomplete results, and Config has no exception mechanism, so accepted risks should be tracked through existing security processes.

### Source excerpt

Learn how to govern AI workloads across your organization with native AWS services: build visibility with the AWS Security Hub AI inventory and AWS Config, choose controls by workload type, deploy the AWS Config AI conformance packs to every account, and route findings to the teams that fix them.

## Introducing AWS Backup logically air-gapped vault support for Amazon RDS

DevFeed: [Introducing AWS Backup logically air-gapped vault support for Amazon RDS](<https://devfeed.tech/articles/introducing-aws-backup-logically-air-gapped-vault-support-for-amazon-rds-137222.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/introducing-aws-backup-logically-air-gapped-vault-support-for-amazon-rds/>)

Author: Mounika Buragapu

Published: 2026-11-16T19:19:22Z

Content type: release

Language: en

Sources: [AWS Storage Blog](<https://devfeed.tech/sources/aws-storage-blog.md>)

Topics: [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [AWS IAM Identity Center](<https://devfeed.tech/topics/aws-iam-identity-center.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [air-gapped](<https://devfeed.tech/tags/air-gapped.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws-backup](<https://devfeed.tech/tags/aws-backup.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backups](<https://devfeed.tech/tags/backups.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cyber-recovery](<https://devfeed.tech/tags/cyber-recovery.md>), [database](<https://devfeed.tech/tags/database.md>), [design](<https://devfeed.tech/tags/design.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [vault](<https://devfeed.tech/tags/vault.md>)

### AI overview

AWS Backup can store Amazon RDS snapshots in logically air-gapped vaults held in a service-owned account and automatically locked in compliance mode. In this excerpt, copying is limited to the same account and Region; continuous backups with point-in-time recovery stay in a standard vault, so snapshot frequency determines the air-gapped copy's recovery point objective. AWS RAM enables direct restores and scheduled restore testing from a separate account, while Multi-party approval provides controlled access if the owning account or Organization is compromised. RDS instances encrypted with the AWS managed aws/rds key cannot be copied to these vaults; they need a customer managed key or no encryption. Air-gapped storage costs more: primary-target workflows also incur temporary standard-vault storage, while copy actions retain and charge for recovery points in both vaults. The excerpt also describes a separate standard-vault copy in another Region for regional recovery.

### Source excerpt

AWS Backup now extends logically air-gapped vault support to Amazon RDS. Learn how to protect, validate, and recover your RDS database backups with isolated, immutable vaults, along with the design, encryption, and cost considerations for a cyber recovery strategy that keeps backups recoverable even when your production account can't be trusted.

## Best practices for deploying Amazon CloudWatch Omni at enterprise scale

DevFeed: [Best practices for deploying Amazon CloudWatch Omni at enterprise scale](<https://devfeed.tech/articles/best-practices-for-deploying-amazon-cloudwatch-omni-at-enterprise-scale-137733.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/best-practices-for-deploying-amazon-cloudwatch-omni-at-enterprise-scale/>)

Author: Raviteja Sunkavalli

Published: 2026-11-16T17:00:50Z

Content type: tutorial

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [AWS IAM Identity Center](<https://devfeed.tech/topics/aws-iam-identity-center.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [api](<https://devfeed.tech/tags/api.md>), [applications](<https://devfeed.tech/tags/applications.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cloudwatch-omni](<https://devfeed.tech/tags/cloudwatch-omni.md>), [data](<https://devfeed.tech/tags/data.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-scale](<https://devfeed.tech/tags/enterprise-scale.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [latency](<https://devfeed.tech/tags/latency.md>), [management-tools](<https://devfeed.tech/tags/management-tools.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring-and-observability](<https://devfeed.tech/tags/monitoring-and-observability.md>), [monitoring-observability](<https://devfeed.tech/tags/monitoring-observability.md>)

### AI overview

Amazon CloudWatch Omni provides organization-wide observability through one IAM Identity Center sign-in domain, but telemetry must be centralized into monitoring accounts before spaces can query it. The article's enterprise pattern creates one space per business unit and Region boundary, routes AWS telemetry with CloudWatch centralization rules, and sends non-AWS telemetry directly to the matching regional OTLP endpoint. Rules process only new telemetry and do not backfill; creating a space backfills up to seven days of logs and traces, except data encrypted with customer-managed KMS keys. Spaces cannot query across one another, so use access grants and row-level data scopes for team boundaries within a space. Scopes filter logs and traces, not metrics, and do not hide fields such as prompts. Sensitive content therefore needs layered controls: redact span attributes before export, mask log patterns at ingestion, and tightly scope access to retained prompts. The article also notes that storage for centralized logs and spans is charged in the destination account, while OpenTelemetry metrics have no additional storage charge.

### Source excerpt

At enterprise scale, organizations run applications and AI agents side by side across hundreds of AWS accounts, several Regions, and often other clouds and on-premises data centers. Site reliability engineering (SRE) teams watch service latency, agent developers observe agent traces and evaluation scores, operation teams monitor alerts, and security reviews AWS API activity. When a [...]

## Tokenomics at scale: Track and cap Amazon Bedrock spend per IAM principal with CUR 2.0 and AWS Budgets

DevFeed: [Tokenomics at scale: Track and cap Amazon Bedrock spend per IAM principal with CUR 2.0 and AWS Budgets](<https://devfeed.tech/articles/tokenomics-at-scale-track-and-cap-amazon-bedrock-spend-per-iam-principal-with-cur-2-0-and-aws-budgets-130883.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/tokenomics-at-scale-track-and-cap-amazon-bedrock-spend-per-iam-principal-with-cur-2-0-and-aws-budgets/>)

Author: Arun Chandapillai

Published: 2026-11-12T19:29:55Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-budgets](<https://devfeed.tech/tags/aws-budgets.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [explorer](<https://devfeed.tech/tags/explorer.md>), [iam](<https://devfeed.tech/tags/iam.md>), [report](<https://devfeed.tech/tags/report.md>), [tags](<https://devfeed.tech/tags/tags.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

Amazon Bedrock spend can be attributed to IAM users or roles automatically, then reported through Cost Explorer or CUR 2.0 and capped with AWS Budgets actions that attach a Deny policy. For shared roles, session tags can distinguish users in aggregated billing data, but the role trust policy must allow sts:TagSession; a budget action targeting that shared role blocks everyone using it. Cost Explorer provides a console view, while CUR 2.0 with Athena supports detailed SQL analysis and requires enabling caller identity data and creating the Glue table. Include input, output, cache-read, and cache-write tokens, and match pricing to usage type because service tier and cross-Region routing affect rates. Budget data refreshes up to three times daily, so enforcement can lag and spend can exceed thresholds. Tags take time to populate and are not retroactive by default; CUR data is aggregated rather than per request. The approach uses AWS-native features without custom code for the common case.

### Source excerpt

Get per-identity Amazon Bedrock cost visibility and enforceable spend limits using only AWS-native features, with no application code for the common case. Attribute spend with IAM principal tags, report with CUR 2.0 or Cost Explorer, and enforce with AWS Budgets actions that apply a Deny policy when a threshold is crossed.

## Ease of use and secure defaults in the new AWS experience

DevFeed: [Ease of use and secure defaults in the new AWS experience](<https://devfeed.tech/articles/ease-of-use-and-secure-defaults-in-the-new-aws-experience-129701.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/ease-of-use-and-secure-defaults-in-the-new-aws-experience/>)

Author: Keshav Narsipur

Published: 2026-11-11T19:57:21Z

Content type: article

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [AWS Management Console](<https://devfeed.tech/topics/aws-management-console.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [budget](<https://devfeed.tech/tags/budget.md>), [building](<https://devfeed.tech/tags/building.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [cost](<https://devfeed.tech/tags/cost.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [data](<https://devfeed.tech/tags/data.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [ease](<https://devfeed.tech/tags/ease.md>), [experience](<https://devfeed.tech/tags/experience.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [iam](<https://devfeed.tech/tags/iam.md>), [mfa](<https://devfeed.tech/tags/mfa.md>), [secure-by-default](<https://devfeed.tech/tags/secure-by-default.md>), [secure-defaults](<https://devfeed.tech/tags/secure-defaults.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>)

### AI overview

The new AWS experience aims to let developers start building quickly while keeping secure defaults in place. Sign-in uses an individual AWS Builder ID with optional MFA; AWS creates a managed organization and project account with scoped collaborators and guardrails, which users can take over through advanced features without migration or downtime. Projects start with a foundational data perimeter and a single home Region. A project spend limit starts at $20 per month, sends alerts as the limit approaches, and pauses the project at the ceiling until the user raises it. IAM Role Manager creates app roles with typical service permissions; developers can later take over and tighten them. These defaults provide a starting foundation, not a complete enterprise data perimeter or permanent least-privilege roles. The article says account-level S3 Block Public Access protections are being worked on, with no timeline given.

### Source excerpt

Starting on Amazon Web Services (AWS) is now more straightforward and more secure by default than it's ever been. Over the past several months, we rolled out a new AWS experience that changes how you start building. It brings together a set of sensible, secure defaults, and taken one at a time, it's easy to [...]

## Where to run AWS workloads and how to limit their access

DevFeed: [Where to run AWS workloads and how to limit their access](<https://devfeed.tech/articles/where-to-run-aws-workloads-and-how-to-limit-their-access-129355.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/aws-account-management/>)

Author: Mallory Mooney

Published: 2026-11-11T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [actions](<https://devfeed.tech/tags/actions.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-elastic-kubernetes-service-amazon-eks](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service-amazon-eks.md>), [amazon-guardduty](<https://devfeed.tech/tags/amazon-guardduty.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-waf](<https://devfeed.tech/tags/aws-waf.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [deployment-tools](<https://devfeed.tech/tags/deployment-tools.md>), [development](<https://devfeed.tech/tags/development.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

AWS recommends running workloads in member accounts and reserving the management account for organization-wide tasks such as billing, because SCPs and RCPs add restrictions in member accounts but do not apply in the management account. A compromised management-account workload may also reach member accounts through trusted roles such as `OrganizationAccountAccessRole` or, where enabled, privileged `sts:AssumeRoot` sessions. Organize workload accounts by ownership, purpose, and isolation needs, and use delegated administration for shared services. For deployment pipelines, narrowly scope IAM `sts:AssumeRole` permissions and destination-role trust policies; an SCP can further deny assumption of roles outside an ARN allowlist. Restrict which GitHub Actions workflows can assume the pipeline's initial role. Test SCPs in a small test OU before broad rollout, verifying both required work and denied access, then review account placement, roles, and policies as workloads change.

### Source excerpt

Learn how to organize AWS workloads and shared services, how that affects security, and which permissions to review as you set up or reorganize your accounts.

## Amazon Bedrock tokenomics data lake

DevFeed: [Amazon Bedrock tokenomics data lake](<https://devfeed.tech/articles/amazon-bedrock-tokenomics-data-lake-127426.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/amazon-bedrock-tokenomics-data-lake/>)

Author: Steph Gooch

Published: 2026-11-10T16:56:36Z

Content type: article

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [streaming data to S3 with Parquet](<https://devfeed.tech/topics/streaming-data-to-s3-with-parquet.md>), [Parquet files in Amazon S3](<https://devfeed.tech/topics/parquet-files-in-amazon-s3.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Data serialization](<https://devfeed.tech/topics/data-serialization.md>), [elt](<https://devfeed.tech/topics/elt.md>), [pii](<https://devfeed.tech/topics/pii.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-data-firehose](<https://devfeed.tech/tags/amazon-data-firehose.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [api](<https://devfeed.tech/tags/api.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-cost-and-usage-report](<https://devfeed.tech/tags/aws-cost-and-usage-report.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-key-management-service-aws-kms](<https://devfeed.tech/tags/aws-key-management-service-aws-kms.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-quick-sight](<https://devfeed.tech/tags/aws-quick-sight.md>), [cost](<https://devfeed.tech/tags/cost.md>), [data-lake](<https://devfeed.tech/tags/data-lake.md>), [logs](<https://devfeed.tech/tags/logs.md>), [model](<https://devfeed.tech/tags/model.md>), [observability](<https://devfeed.tech/tags/observability.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [tokenomics](<https://devfeed.tech/tags/tokenomics.md>)

### AI overview

The data lake centralizes Amazon Bedrock invocation logs from linked accounts into an Athena-queryable table, exposing prompts and responses, token counts, model, stop reason, account, timestamp, and IAM identity. CloudWatch subscription filters forward logs to a central account, where Lambda unwraps batches, removes non-invocation messages, and flattens identity data; Data Firehose converts records to Parquet in S3, and Glue defines the Athena table. Deployment uses two CloudFormation stacks: create the central stack first, then source-account stacks, enable Bedrock logging separately in each account, verify data arrival, and run the saved Athena query to create the flattened view. Joining the table to CUR 2.0 by IAM ARN can attribute spend. The S3 bucket uses KMS encryption and IAM policies control access; because prompts may contain PII, permissions need review. The article notes that S3 buckets must be emptied and the Athena workgroup deleted manually during cleanup.

### Source excerpt

Running Amazon Bedrock across many accounts shows you the bill but not what happened inside each call. This post builds a centralized observability data lake that aggregates Bedrock invocation logs from every linked account into one queryable table, so you can see prompts, token counts, model choice, and per-invocation cost across your organization.

## Build an organization-wide Amazon RDS posture dashboard with Kiro

DevFeed: [Build an organization-wide Amazon RDS posture dashboard with Kiro](<https://devfeed.tech/articles/build-an-organization-wide-amazon-rds-posture-dashboard-with-kiro-115549.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-an-organization-wide-amazon-rds-posture-dashboard-with-kiro/>)

Author: Sam Mukherjee

Published: 2026-11-03T16:38:19Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [organization](<https://devfeed.tech/tags/organization.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The solution collects existing AWS posture events from five services into one organization-wide Amazon CloudWatch dashboard for RDS and Aurora. It shows the latest status per resource for deletion protection, Multi-AZ, and backups, plus engine/version details where available, protection changes with principal and source IP, and engines nearing end of standard support. Member accounts forward events directly to a central EventBridge bus; CloudWatch Logs, metric filters, alarms, and dashboard widgets provide the view without a maintained Lambda or separate database. A baseline seed fills the pre-deployment gap. The transition alarm is suited to paging when protection is disabled; the recurring Security Hub state alarm serves as a reminder. The dashboard is read-only, near real-time, and relies on events within its time range; Security Hub CSPM and AWS Config remain authoritative inventory sources. Deployment requires several configured AWS services, and the Trusted Advisor feed requires an eligible support plan. In the tested account, estimated custom-metric costs were $15-$45 monthly, with a stated worst case around $90.

### Source excerpt

Deletion protection on an Amazon RDS database is a single setting that anyone can switch off, and across hundreds of accounts there is no single place to see which databases still run without it. This post shows how to track Amazon RDS posture organization-wide with one Amazon CloudWatch dashboard, built and verified with Kiro.

## Using Claude on Amazon Bedrock with Claude Code and Cowork

DevFeed: [Using Claude on Amazon Bedrock with Claude Code and Cowork](<https://devfeed.tech/articles/using-claude-on-amazon-bedrock-with-claude-code-and-cowork-119458.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/10/31/using-claude-on-amazon-bedrock-with-claude-code-and-cowork/>)

Author: Ritesh Patel

Published: 2026-10-31T23:00:00Z

Content type: tutorial

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-marketplace](<https://devfeed.tech/tags/aws-marketplace.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-sdk](<https://devfeed.tech/tags/aws-sdk.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [browser](<https://devfeed.tech/tags/browser.md>), [budget](<https://devfeed.tech/tags/budget.md>), [cache](<https://devfeed.tech/tags/cache.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-cowork](<https://devfeed.tech/tags/claude-cowork.md>), [iam](<https://devfeed.tech/tags/iam.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Claude Code and Cowork can send model requests to Amazon Bedrock and bill them through AWS, but they use different setup and identity flows. Claude Code uses the AWS credential chain: enable Bedrock access, grant inference permissions, choose a region, and pin model IDs before rollout. Managed settings can restrict startup model checks with an allowlist on v2.1.287 or later; an allowlist alone does not enforce that restriction. Cowork is configured in Claude Desktop and deployed through MDM, with IAM Identity Center sign-in and a permission set; AWS setup runs once per organization. Cowork's in-app sign-in and named profiles provide per-user CloudTrail identity, while a shared bearer token does not. The excerpt also notes limits: Claude Code lacks WebSearch and /logout on Bedrock, uses the Invoke API rather than Converse, and gateways must preserve the eventstream response type.

### Source excerpt

Set up Claude Code and Claude Cowork on Amazon Bedrock with AWS sign-in, pinned model IDs, a managed model allowlist and the IAM policy that each one needs.

## Enable cross-Region fine-grained data access with AWS Lake Formation and Trusted Identity Propagation

DevFeed: [Enable cross-Region fine-grained data access with AWS Lake Formation and Trusted Identity Propagation](<https://devfeed.tech/articles/enable-cross-region-fine-grained-data-access-with-aws-lake-formation-and-trusted-identity-propagation-98494.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/enable-cross-region-fine-grained-data-access-with-aws-lake-formation-and-trusted-identity-propagation/>)

Author: Maneesh Sharma

Published: 2026-10-23T19:50:12Z

Content type: article

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [AWS IAM Identity Center](<https://devfeed.tech/topics/aws-iam-identity-center.md>), [AWS Lake Formation](<https://devfeed.tech/topics/aws-lake-formation.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-redshift](<https://devfeed.tech/tags/amazon-redshift.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [auditability](<https://devfeed.tech/tags/auditability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [aws-iam-identity-center](<https://devfeed.tech/tags/aws-iam-identity-center.md>), [aws-lake-formation](<https://devfeed.tech/tags/aws-lake-formation.md>), [cloudtrail](<https://devfeed.tech/tags/cloudtrail.md>), [control](<https://devfeed.tech/tags/control.md>), [corporate](<https://devfeed.tech/tags/corporate.md>), [cross](<https://devfeed.tech/tags/cross.md>), [data](<https://devfeed.tech/tags/data.md>), [fine](<https://devfeed.tech/tags/fine.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity](<https://devfeed.tech/tags/identity.md>), [region](<https://devfeed.tech/tags/region.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

AWS IAM Identity Center Trusted Identity Propagation (TIP) lets users query Lake Formation governed data across Regions as their own identities, with Lake Formation authorization and per-user AWS CloudTrail auditability. The producer and consumer accounts must share an organization instance of IAM Identity Center, replicated to the Regions in use. For S3 data queried with Athena, share the Lake Formation catalog and table, accept the AWS RAM share, create a resource link in the consumer's query Region, and grant users Describe access to it; the data stays in the producer Region while the query runs elsewhere. For Redshift data, register a Redshift Serverless namespace in the producer's AWS Glue Data Catalog, share it through Lake Formation, and configure a consumer external schema that references that catalog; no resource link is needed. The engines differ in cross-Region constraints: Athena works across Regions without additional constraints, while a Redshift datashare requires the Redshift query engine to be in the namespace's Region.

### Source excerpt

Trusted Identity Propagation with AWS IAM Identity Center now works across Regions. Learn how to share AWS Lake Formation-governed Amazon S3 and Amazon Redshift data in one Region and query it from another as the actual corporate user, with fine-grained access control and per-user auditability in AWS CloudTrail.

## Centralized multi-account server migration to AWS with AWS Transform

DevFeed: [Centralized multi-account server migration to AWS with AWS Transform](<https://devfeed.tech/articles/centralized-multi-account-server-migration-to-aws-with-aws-transform-95806.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/centralized-multi-account-server-migration-to-aws-with-aws-transform/>)

Author: Suhail Fouzan

Published: 2026-10-22T14:42:40Z

Content type: article

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [AWS Transform](<https://devfeed.tech/topics/aws-transform.md>), [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-transform](<https://devfeed.tech/tags/aws-transform.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [migration](<https://devfeed.tech/tags/migration.md>), [multi-account](<https://devfeed.tech/tags/multi-account.md>), [network](<https://devfeed.tech/tags/network.md>), [planning](<https://devfeed.tech/tags/planning.md>), [server](<https://devfeed.tech/tags/server.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS Transform can coordinate a server migration across multiple AWS accounts from one central workspace. The central account acts as a delegated administrator and hosts a staging VPC subnet shared with target accounts through AWS RAM; AWS Transform assigns migration waves to those accounts and deploys required IAM roles. Prerequisites include accounts in the same AWS Organization, target VPCs and subnets, enabled AWS Transform access, and required network connectivity. For each wave, teams tag target resources, select the shared replication subnet, validate inventory and network mappings, then replicate, test, and cut over workloads into the target account's VPC. The shared staging area avoids duplicating MGN replication infrastructure in every account. The subnet can be shared in advance or only while a specific account is migrating. Agent installation can use the recommended MGN connector across waves and accounts, or existing tools/manual installation; the latter requires credentials from each workload's target account.

### Source excerpt

Introduction AWS Transform for migrations lets you orchestrate a centralized, multi-account migration of your workloads to Amazon EC2 from a single location. It coordinates the migration across all your target accounts and applies AI-powered automation to dependency mapping, wave planning, and network configuration, so dependent workloads move together while landing in their intended destination accounts. [...]

## Scope workloads and share resilience policies with AWS Resilience Hub

DevFeed: [Scope workloads and share resilience policies with AWS Resilience Hub](<https://devfeed.tech/articles/scope-workloads-and-share-resilience-policies-with-aws-resilience-hub-86344.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/scope-workloads-and-share-resilience-policies-with-aws-resilience-hub/>)

Author: Sinisa Mikasinovic

Published: 2026-10-13T21:30:10Z

Content type: tutorial

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [Resilience](<https://devfeed.tech/topics/resilience.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-resilience-hub-arh](<https://devfeed.tech/tags/aws-resilience-hub-arh.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [resilience](<https://devfeed.tech/tags/resilience.md>)

### AI overview

AWS Resilience Hub adds EKS label selectors for scoping service resources, generative AI Dependency Insights to prioritize discovered dependencies for resilience review, and policy sharing through AWS Organizations. The walkthrough explains setup, how to interpret findings, and limitations such as DNS discovery gaps and the need to validate recovery targets with resilience testing.

### Source excerpt

The next generation of AWS Resilience Hub adds three capabilities to keep workload scope and resilience requirements aligned with your running environment: Amazon EKS label support for service input sources, generative AI-powered Dependency Insights, and resilience policy sharing through AWS Organizations.

## Adopt AWS Backup policies at enterprise scale using AWS Organizations

DevFeed: [Adopt AWS Backup policies at enterprise scale using AWS Organizations](<https://devfeed.tech/articles/adopt-aws-backup-policies-at-enterprise-scale-using-aws-organizations-66402.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/adopt-aws-backup-policies-at-enterprise-scale-using-aws-organizations/>)

Author: Stuart Lupton

Published: 2026-10-06T18:01:36Z

Content type: tutorial

Language: en

Sources: [AWS Storage Blog](<https://devfeed.tech/sources/aws-storage-blog.md>)

Topics: [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [air-gapped-backup](<https://devfeed.tech/tags/air-gapped-backup.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [and-best-practices](<https://devfeed.tech/tags/and-best-practices.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-backup](<https://devfeed.tech/tags/aws-backup.md>), [aws-cloud-storage](<https://devfeed.tech/tags/aws-cloud-storage.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [backup](<https://devfeed.tech/tags/backup.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [data-protection](<https://devfeed.tech/tags/data-protection.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [learning-levels](<https://devfeed.tech/tags/learning-levels.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [scale](<https://devfeed.tech/tags/scale.md>), [storage](<https://devfeed.tech/tags/storage.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

The article explains how to apply AWS Backup policies across an AWS Organizations hierarchy to govern backups for many accounts. It covers policy inheritance operators, multiple protection plans, account and Region variables, OU-level segmentation, and rollout practices intended to maintain coverage during migration.

### Source excerpt

Consider a platform team responsible for data protection across a large, regulated enterprise. Over years of growth, the organization now runs hundreds of Amazon Web Services (AWS) accounts across many teams and AWS Regions, and each team has configured its own backup approach. The platform team now faces a familiar challenge: how to enforce consistent, [...]

## Share Systems Manager documents across your AWS Organization with AWS RAM

DevFeed: [Share Systems Manager documents across your AWS Organization with AWS RAM](<https://devfeed.tech/articles/share-systems-manager-documents-across-your-aws-organization-with-aws-ram-63623.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/share-systems-manager-documents-across-your-aws-organization-with-aws-ram/>)

Author: Erik Weber

Published: 2026-10-01T19:37:35Z

Content type: tutorial

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [Resource Access Manager (RAM)](<https://devfeed.tech/topics/resource-access-manager-ram.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [enterprise deployment](<https://devfeed.tech/topics/enterprise-deployment.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>)

Tags: [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-systems-manager](<https://devfeed.tech/tags/aws-systems-manager.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloud-operations](<https://devfeed.tech/tags/cloud-operations.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [management-tools](<https://devfeed.tech/tags/management-tools.md>), [resource-access-manager-ram](<https://devfeed.tech/tags/resource-access-manager-ram.md>), [systems-manager-automation](<https://devfeed.tech/tags/systems-manager-automation.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS Systems Manager now supports sharing documents, including Automation runbooks and Run Command documents, with an AWS Organization or specific organizational units through AWS Resource Access Manager. The article walks through creating a resource share, granting member accounts access, and running a shared Active Directory domain-join runbook. It also covers CloudFormation, AWS CLI, migration from account ID lists, and cleanup.

### Source excerpt

Introduction If you operate AWS Systems Manager (SSM) documents, such as Automation runbooks and Run Command documents, across an AWS Organization, you must decide which accounts can run them. Until now, that meant sharing each document with a list of individual account IDs through the ModifyDocumentPermission API, which accepts up to 1,000 account IDs per [...]

## Maintaining HIPAA compliance when migrating with AWS Transform MGN

DevFeed: [Maintaining HIPAA compliance when migrating with AWS Transform MGN](<https://devfeed.tech/articles/maintaining-hipaa-compliance-when-migrating-with-aws-transform-mgn-50010.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/maintaining-hipaa-compliance-when-migrating-with-aws-transform-mgn/>)

Author: Diya

Published: 2026-09-07T07:11:02Z

Content type: tutorial

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [AWS Transform](<https://devfeed.tech/topics/aws-transform.md>), [migration](<https://devfeed.tech/topics/migration.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [Logging](<https://devfeed.tech/topics/logging.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-application-migration-service](<https://devfeed.tech/tags/aws-application-migration-service.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-transform](<https://devfeed.tech/tags/aws-transform.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [healthcare](<https://devfeed.tech/tags/healthcare.md>), [hipaa](<https://devfeed.tech/tags/hipaa.md>), [least-privilege](<https://devfeed.tech/tags/least-privilege.md>), [logging](<https://devfeed.tech/tags/logging.md>), [migration](<https://devfeed.tech/tags/migration.md>), [security](<https://devfeed.tech/tags/security.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This post explains how healthcare organizations can maintain HIPAA security and privacy controls while migrating regulated workloads to AWS with AWS Transform MGN. It covers encrypted private replication, multi-account architecture, audit continuity, access controls, and evidence collection across replication, testing, and cutover.

### Source excerpt

Healthcare organizations migrating regulated workloads to AWS must maintain security and privacy controls at every phase, including replication, testing, and cutover, not just after workloads reach production. This post shows how to layer HIPAA controls onto the proven multi-account AWS Transform MGN (formerly AWS Application Migration Service) migration architecture using AWS Resource Access Manager, covering encrypted private replication, audit continuity, and evidence collection. [...]

## How Moeve scales AWS governance with automated AWS Organization Service Control Policies

DevFeed: [How Moeve scales AWS governance with automated AWS Organization Service Control Policies](<https://devfeed.tech/articles/how-moeve-scales-aws-governance-with-automated-aws-organization-service-control-policies-49996.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/mt/how-moeve-scales-aws-governance-with-automated-aws-organization-service-control-policies/>)

Author: Gonzalo Guerrero

Published: 2026-08-26T15:20:58Z

Content type: tutorial

Language: en

Sources: [AWS Cloud Operations Blog](<https://devfeed.tech/sources/aws-cloud-operations-blog.md>)

Topics: [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Infrastructure as code](<https://devfeed.tech/topics/infrastructure-as-code.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [automated](<https://devfeed.tech/tags/automated.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-control-tower](<https://devfeed.tech/tags/aws-control-tower.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-partner-network](<https://devfeed.tech/tags/aws-partner-network.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [governance](<https://devfeed.tech/tags/governance.md>), [has](<https://devfeed.tech/tags/has.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [organization](<https://devfeed.tech/tags/organization.md>), [policies](<https://devfeed.tech/tags/policies.md>)

### AI overview

Moeve automated the lifecycle of AWS Organizations Service Control Policies by managing them as code in a central Git repository. Pull requests and GitHub Actions deploy reviewed changes, while EventBridge and Lambda monitor organizational and policy-attachment changes.

### Source excerpt

Moeve, formerly known as Cepsa, is a global integrated energy company with over 90 years of experience and more than 11,000 employees. Moeve is committed to driving Europe's energy transition and accelerating decarbonization efforts. The company has embraced digital transformation to enhance energy efficiency, safety, and sustainability, focusing on investments in green hydrogen, second-generation biofuels, [...]

## Protect Amazon Route 53 domains during account lifecycle events: Best practices for domain governance in multi-account organizations

DevFeed: [Protect Amazon Route 53 domains during account lifecycle events: Best practices for domain governance in multi-account organizations](<https://devfeed.tech/articles/protect-amazon-route-53-domains-during-account-lifecycle-events-best-practices-for-domain-governance-in-multi-account-organizations-49879.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/protect-amazon-route-53-domains-during-account-lifecycle-events-best-practices-for-domain-governance-in-multi-account-organizations/>)

Author: Yagya Vir Singh

Published: 2026-07-22T18:49:03Z

Content type: article

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-support](<https://devfeed.tech/tags/aws-support.md>), [aws-well-architected-framework](<https://devfeed.tech/tags/aws-well-architected-framework.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [centralized-operations-management](<https://devfeed.tech/tags/centralized-operations-management.md>), [configuration-compliance-and-auditing](<https://devfeed.tech/tags/configuration-compliance-and-auditing.md>), [dns](<https://devfeed.tech/tags/dns.md>), [enterprise-governance-and-control](<https://devfeed.tech/tags/enterprise-governance-and-control.md>), [governance](<https://devfeed.tech/tags/governance.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [outage](<https://devfeed.tech/tags/outage.md>), [security-governance](<https://devfeed.tech/tags/security-governance.md>), [ssl](<https://devfeed.tech/tags/ssl.md>)

### AI overview

This article explains how to govern Amazon Route 53 domain registrations during AWS account lifecycle events in multi-account organizations. It describes the risks of account closure, including service outages, failed email delivery, and SSL/TLS validation, and advocates preventive governance, architectural patterns, and operational controls.

### Source excerpt

Domain governance in Amazon Route 53 can mean the difference between a routine account decommissioning and an unplanned outage. Picture this situation: your organization closes an Amazon Web Services (AWS) account, and five days later a customer-facing website becomes unreachable, email stops flowing, and SSL certificate validation fails. A domain that this account had registered [...]

## Introducing self-managed Amazon S3 buckets for AWS Lambda function code

DevFeed: [Introducing self-managed Amazon S3 buckets for AWS Lambda function code](<https://devfeed.tech/articles/introducing-self-managed-amazon-s3-buckets-for-aws-lambda-function-code-4667.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/introducing-self-managed-amazon-s3-buckets-for-aws-lambda-function-code/>)

Author: Doug Perkes

Published: 2026-07-17T10:49:14Z

Content type: release

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Security](<https://devfeed.tech/topics/security.md>), [Replication](<https://devfeed.tech/topics/replication.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [replication](<https://devfeed.tech/tags/replication.md>), [security](<https://devfeed.tech/tags/security.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

AWS Lambda now supports self-managed Amazon S3 buckets for function deployment packages. Lambda reads code directly from the customer-controlled bucket, removing deployment-package copies from the Lambda code storage quota and giving teams control over encryption, access policies, compliance, lifecycle management, audit trails, and cross-Region replication.

### Source excerpt

If you manage Lambda functions at scale, you've likely hit the 75 GB code storage limit or explained to your security team why deployment artifacts live in an S3 bucket you don't control. Today, we're announcing self-managed Amazon S3 buckets for AWS Lambda deployment packages. Lambda reads your code directly from your bucket, eliminating quota [...]

## A Story of Delayed AWS Pipelines

DevFeed: [A Story of Delayed AWS Pipelines](<https://devfeed.tech/articles/a-story-of-delayed-aws-pipelines-23718.md>)

Original publisher: [Read original article](<https://medium.com/booking-com-development/a-story-of-delayed-aws-pipelines-382e4a1fede6?source=rss----1c36c35f9c76---4>)

Author: Vladimir Romashov

Published: 2026-05-08T14:23:22Z

Content type: article

Language: en

Sources: [Booking.com Development](<https://devfeed.tech/sources/booking-com-development-medium.md>)

Topics: [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [booking](<https://devfeed.tech/tags/booking.md>), [cdk](<https://devfeed.tech/tags/cdk.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [ci-cd-pipeline](<https://devfeed.tech/tags/ci-cd-pipeline.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [data](<https://devfeed.tech/tags/data.md>), [iac](<https://devfeed.tech/tags/iac.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [s3](<https://devfeed.tech/tags/s3.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

Terraform's `aws_organizations_organization` data source can create organization-wide API delays because it calls `DescribeOrganization`, `ListAccounts`, and `ListRoots`, even when a caller only needs the organization ID. The excerpt reports that denied `ListAccounts` calls still triggered retries and exponential backoff, while Terraform plans and applies repeatedly read the data source. Since Organizations API quotas are shared across an AWS organization, concurrent pipelines can exhaust burst capacity and queue behind the documented base rate of one request per second. In the reported testing, about 1 in 10 Terraform pipelines encountered delays of 1-15 minutes; CDK pipelines in the same accounts did not. The provider change to make `ListAccounts` and `ListRoots` optional was merged for AWS provider v6.29.0. As a temporary workaround, the team cached the data source output centrally, trading reduced API calls for the need to maintain a central update mechanism. The excerpt says AWS automatic quota management did not yet cover the Organizations API.

### Source excerpt

How a seemingly simple AWS API call can silently slow down your CI/CD pipelines Review/co-researcher: Gonzalo Ulla The Mystery It started with a line in one of our team's CI/CD logs that nobody expected: module.project.module.user_buckets.module.s3_bucket.data.aws_organizations_organization.current: Still reading... [15m10s elapsed] 15 minutes and 10 seconds -- just to read organization data. A value that should return in milliseconds was holding up entire pipelines. After digging deeper, we discovered this wasn't a one-off issue. During testing, roughly 1 in 10 pipelines containing Terraform were affected, with delays ranging from 1 to 15 minutes each. At Booking.com, we deploy and manage our AWS infrastructure using two primary Infrastructure as Code (IaC) technologies: Terraform and AWS Cloud Development Kit (CDK). To standardize and enforce our compliance and security controls, we maintain a set of internal Terraform and CDK modules to provision resources that handle personally identifiable information (PII). Interestingly, only Terraform pipelines were affected by this issue -- CDK ones running in the same accounts and against the same AWS Organization were completed without any delays. [spoiler alert/] CDK uses CloudFormation under the hood, which doesn't make additional Organizations API calls directly. [/spoiler alert]. This ruled out a general AWS-side outage or account-level throttling and pointed us toward something specific to how Terraform interacts with the Organizations API. This is the story of how we tracked down the root cause -- and why the fix isn't as simple as you'd think. What is aws_organizations_organization? Terraform's aws_organizations_organization data source retrieves information about, guess what, your AWS Organization. On the surface, it maps to the AWS DescribeOrganization API call -- a flat request. No iteration. No pagination. Simple... Or so we thought. The First Clue: Reproducing the Issue The references to the Organizations API mostly c

[Next page](<https://devfeed.tech/topics/aws-organizations.md?cursor=WyIyMDI2LTA1LTA4VDE0OjIzOjIyKzAwOjAwIiwgImFjY2MwNWQxLWExZWMtNGE3Mi05YjE1LWQ4MGFkZGQ4YTFmOSJd>)