# AWS IAM

AWS service for securely controlling access to AWS resources through identities, authentication, authorization, and permissions.

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

## 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.

## 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.

## Use Amazon ECR global authentication token across AWS Regions

DevFeed: [Use Amazon ECR global authentication token across AWS Regions](<https://devfeed.tech/articles/use-amazon-ecr-global-authentication-token-across-aws-regions-146422.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/containers/use-amazon-ecr-global-authentication-token-across-aws-regions/>)

Author: Sourav Kundu

Published: 2026-11-19T20:09:23Z

Content type: article

Language: en

Sources: [Containers](<https://devfeed.tech/sources/containers.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-elastic-container-registry](<https://devfeed.tech/tags/amazon-elastic-container-registry.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-tokens](<https://devfeed.tech/tags/authentication-tokens.md>), [aws](<https://devfeed.tech/tags/aws.md>), [docker](<https://devfeed.tech/tags/docker.md>), [global](<https://devfeed.tech/tags/global.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [images](<https://devfeed.tech/tags/images.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [lifetime](<https://devfeed.tech/tags/lifetime.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [one](<https://devfeed.tech/tags/one.md>), [partition](<https://devfeed.tech/tags/partition.md>), [post](<https://devfeed.tech/tags/post.md>), [regions](<https://devfeed.tech/tags/regions.md>), [request](<https://devfeed.tech/tags/request.md>), [sign](<https://devfeed.tech/tags/sign.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [token](<https://devfeed.tech/tags/token.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Amazon ECR global authentication tokens let one bearer token authenticate to ECR registry endpoints across AWS Regions within the same partition, simplifying multi-Region pushes and pulls. Request it through AWS Sign-In with `CreateBearerToken` for `ecr.amazonaws.com`; the caller needs `signin:CreateBearerToken`, and the token carries the caller's existing IAM permissions, which ECR checks for every operation. Its lifetime defaults to 12 hours and can be shortened to 5 minutes. AWS CLI 2.39.7 or later supports the command, and the ECR credential helper, Kubernetes credential provider, and GitHub Actions login action can opt in. CloudTrail records a shared sign-in session ARN on token issuance and authorized ECR events, supporting cross-Region tracing and session-specific denial. Registries and images remain Regional, existing regional tokens continue to work, and opt-in Regions require account enrollment. The walkthrough also cautions that credential tooling must accept variable-length tokens.

### Source excerpt

Amazon ECR now supports global authentication tokens: request one token from AWS Sign-In and use it to push and pull images across AWS Regions in the same partition, with a lifetime from 5 minutes to 12 hours. This post shows how to request a global token and use it with Docker in two Regions.

## Introducing resource context for firewall policies with AWS Transit Gateway

DevFeed: [Introducing resource context for firewall policies with AWS Transit Gateway](<https://devfeed.tech/articles/introducing-resource-context-for-firewall-policies-with-aws-transit-gateway-144604.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-resource-context-for-firewall-policies-with-aws-transit-gateway/>)

Author: Rajat Tyagi

Published: 2026-11-19T18:41:56Z

Content type: article

Language: en

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

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-transit-gateway](<https://devfeed.tech/tags/aws-transit-gateway.md>), [context](<https://devfeed.tech/tags/context.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gateway-load-balancer](<https://devfeed.tech/tags/gateway-load-balancer.md>)

### AI overview

AWS Transit Gateway can attach source resource context to traffic sent to third-party firewalls through Gateway Load Balancer network function attachments. A separate AWS Network Manager context store maps the compact packet context IDs to VPCs, subnets, security groups, and attachments, letting firewalls apply resource-based policies alongside existing IP rules without waiting for IP synchronization. The walkthrough requires a transit gateway, healthy Gateway Load Balancer firewall targets, an endpoint service, static routes to the attachment, and a context store association; the firewall assumes an IAM role to read the store. The documented limits include source context only, no inspection of traffic within the same VPC, no context sharing across inter-Region peering, and omission of security groups when a resource has more than five. Routing changes during migration may interrupt active connections.

### Source excerpt

AWS Transit Gateway now shares AWS resource context (VPCs, subnets, security groups, and attachments) with third-party firewalls, so you can write firewall policies based on how resources are organized instead of IP addresses. This post shows how to create a Gateway Load Balancer network function attachment and turn on context sharing.

## Fivetran Enhances AWS Support | Blog | Fivetran

DevFeed: [Fivetran Enhances AWS Support | Blog | Fivetran](<https://devfeed.tech/articles/fivetran-enhances-aws-support-blog-fivetran-140223.md>)

Original publisher: [Read original article](<https://wf.fivetran.com/blog/fivetran-enhances-aws-support>)

Author: Fivetran

Published: 2026-11-18T02:45:59Z

Content type: article

Language: en

Sources: [Fivetran Blog](<https://devfeed.tech/sources/fivetran-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.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>), [fivetran](<https://devfeed.tech/tags/fivetran.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [permissions](<https://devfeed.tech/tags/permissions.md>)

### AI overview

Fivetran adds integrations for AWS CloudTrail and Service Manager Inventory to centralize their data in a data warehouse. CloudTrail data can help identify common user actions that may be destructive and add historical anomaly data to operational dashboards. Inventory data can provide a consolidated view of services to examine team permissions through AWS IAM and infrastructure efficiency gaps. The source recommends testing integrations and describes 14 days of free usage for each new connector for current customers, and 14 days of unlimited usage for prospective users.

### Source excerpt

With key new integrations, Fivetran continues to help companies gain visibility into their AWS environment.

## Govern and discover records with common metadata in AWS Agent Registry

DevFeed: [Govern and discover records with common metadata in AWS Agent Registry](<https://devfeed.tech/articles/govern-and-discover-records-with-common-metadata-in-aws-agent-registry-138534.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/govern-and-discover-records-with-common-metadata-in-aws-agent-registry/>)

Author: Sana Iqbal

Published: 2026-11-17T20:31:04Z

Content type: article

Language: en

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

Topics: [schema design](<https://devfeed.tech/topics/schema-design.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>)

Tags: [administrator](<https://devfeed.tech/tags/administrator.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [aws](<https://devfeed.tech/tags/aws.md>), [custom](<https://devfeed.tech/tags/custom.md>), [define](<https://devfeed.tech/tags/define.md>), [definition](<https://devfeed.tech/tags/definition.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [enrichment](<https://devfeed.tech/tags/enrichment.md>), [fields](<https://devfeed.tech/tags/fields.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [one](<https://devfeed.tech/tags/one.md>), [post](<https://devfeed.tech/tags/post.md>), [records](<https://devfeed.tech/tags/records.md>), [registry](<https://devfeed.tech/tags/registry.md>), [resources](<https://devfeed.tech/tags/resources.md>), [schema](<https://devfeed.tech/tags/schema.md>), [schemas](<https://devfeed.tech/tags/schemas.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

AWS Agent Registry custom metadata schemas give records shared, administrator-defined fields and allowed values, with validation on creation and updates. Records created without metadata can be saved as NON_COMPLIANT drafts but cannot be submitted for approval until required values are supplied; invalid or incomplete metadata is rejected. COMPLIANT indicates schema compliance, not approval. In the walkthrough, automation enriches an MCP record with scan and inventory data, then a custom Lambda approval function checks compliance, scan status, CMDB ID, and data classification. Approved records can be found through metadata filters or the registry's MCP endpoint; matching unapproved records stay out of discovery results. Schema changes are additive, and existing records are not rewritten: they may become NON_COMPLIANT while retaining approval until updated. The excerpt recommends choosing shared fields and values carefully and keeping secrets and sensitive findings out of broadly readable metadata.

### Source excerpt

Custom metadata schemas in AWS Agent Registry let an administrator define typed, validated fields that every agent, MCP server, and skill must carry. This post follows an MCP record from schema definition through registration, enrichment, approval, and discovery, so teams govern and find resources with one shared set of facts.

## Agent identity for Amazon WorkSpaces for AI agents

DevFeed: [Agent identity for Amazon WorkSpaces for AI agents](<https://devfeed.tech/articles/agent-identity-for-amazon-workspaces-for-ai-agents-138612.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/desktop-and-application-streaming/agent-identity-for-amazon-workspaces-for-ai-agents/>)

Author: Roberto Moreno

Published: 2026-11-17T20:05:28Z

Content type: article

Language: en

Sources: [Desktop and Application Streaming](<https://devfeed.tech/sources/desktop-and-application-streaming.md>)

Topics: [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Entra ID](<https://devfeed.tech/topics/entra-id.md>), [okta](<https://devfeed.tech/topics/okta.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-workspaces](<https://devfeed.tech/tags/amazon-workspaces.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [aws-end-user-computing](<https://devfeed.tech/tags/aws-end-user-computing.md>), [can](<https://devfeed.tech/tags/can.md>), [end-user-computing](<https://devfeed.tech/tags/end-user-computing.md>), [first](<https://devfeed.tech/tags/first.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [generation](<https://devfeed.tech/tags/generation.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [leave](<https://devfeed.tech/tags/leave.md>), [management](<https://devfeed.tech/tags/management.md>), [model](<https://devfeed.tech/tags/model.md>), [non-human-identities](<https://devfeed.tech/tags/non-human-identities.md>), [people](<https://devfeed.tech/tags/people.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [re-invent](<https://devfeed.tech/tags/re-invent.md>), [workspaces](<https://devfeed.tech/tags/workspaces.md>)

### AI overview

Amazon WorkSpaces for AI agents uses on-behalf-of (OBO) identity so an agent acts with a user's delegated access while remaining separately identifiable. The user signs in through an existing identity provider (such as Microsoft Entra ID or Okta); the agent exchanges that sign-in for a provider-signed token naming both identities. AWS STS issues short-lived credentials for the agent's IAM role, and IAM policies can restrict which agents act for which users and environments. CloudTrail records both identities, with per-action data events available when enabled. Revoking an agent or user prevents new sessions; stopping an active agent requires removing role permissions or revoking active role sessions. Non-domain-joined fleets use the basic flow. Domain-joined fleets additionally require working certificate-based authentication and Active Directory user attributes in the token; users must be synchronized from Active Directory. The model depends on a signed-in user and does not fit agents operating without one. IdP token attribute mapping is security-critical, and long-running work needs token refresh under the IdP's policies.

### Source excerpt

Identity management has always followed whoever, or whatever, does the work. The first generation secured people: authenticate a person, authorize what they can reach, and remove their access when they leave. The second generation extended that model to software through service accounts, which are non-human identities with a fixed set of permissions and, often, long-lived [...]

## Secure MCP integrations for AWS DevOps Agent with Amazon Bedrock AgentCore

DevFeed: [Secure MCP integrations for AWS DevOps Agent with Amazon Bedrock AgentCore](<https://devfeed.tech/articles/secure-mcp-integrations-for-aws-devops-agent-with-amazon-bedrock-agentcore-139361.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/secure-mcp-integrations-for-aws-devops-agent-with-amazon-bedrock-agentcore/>)

Author: Lakshmi Kumkala

Published: 2026-11-17T18:24:37Z

Content type: article

Language: en

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

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [admin](<https://devfeed.tech/tags/admin.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-opensearch-service](<https://devfeed.tech/tags/amazon-opensearch-service.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-vpc-lattice](<https://devfeed.tech/tags/amazon-vpc-lattice.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [mcp-tools](<https://devfeed.tech/tags/mcp-tools.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [observability](<https://devfeed.tech/tags/observability.md>), [private](<https://devfeed.tech/tags/private.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [rotation](<https://devfeed.tech/tags/rotation.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

AWS DevOps Agent can connect to MCP servers directly or through Amazon Bedrock AgentCore Gateway. Direct registration suits one or two servers in a single account and supports private endpoints through VPC Lattice; each tool must use streamable HTTP and a supported authentication method, and admins classify tools as read-only, mutating, or destructive. AgentCore Gateway offers a single registration and SigV4 connection, centralizes backend credentials, and can apply Cedar policies, unified CloudWatch audit logs, and X-Ray tracing across targets. It is useful when servers or accounts multiply or shared policy and observability are needed; private Gateway targets add central controls, while a direct private connection requires less configuration. The article recommends checking native integrations and existing vendor or sample MCP servers before building a custom one, and starting with a read-only tool in a non-production agent space.

### Source excerpt

As you connect more Model Context Protocol (MCP) tools to AWS DevOps Agent, each one adds its own authentication, credential rotation, and audit overhead. This post shows how to extend AWS DevOps Agent with MCP tools securely using Amazon Bedrock AgentCore, so new tools inherit consistent security, access control, private connectivity, and observability.

## Analyze Anthropic usage, spend, and access with AWS Glue, Amazon S3 Tables, and AWS Quick

DevFeed: [Analyze Anthropic usage, spend, and access with AWS Glue, Amazon S3 Tables, and AWS Quick](<https://devfeed.tech/articles/analyze-anthropic-usage-spend-and-access-with-aws-glue-amazon-s3-tables-and-aws-quick-136178.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/analyze-anthropic-usage-spend-and-access-with-aws-glue-amazon-s3-tables-and-aws-quick/>)

Author: Daniyal Alam

Published: 2026-11-16T20:09:24Z

Content type: tutorial

Language: en

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

Topics: [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [Amazon S3 Tables](<https://devfeed.tech/topics/amazon-s3-tables.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [anthropic](<https://devfeed.tech/topics/anthropic.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [JOIN](<https://devfeed.tech/topics/join.md>), [data ownership](<https://devfeed.tech/topics/data-ownership.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-s3-tables](<https://devfeed.tech/tags/amazon-s3-tables.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-iceberg-tables](<https://devfeed.tech/tags/apache-iceberg-tables.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [athena](<https://devfeed.tech/tags/athena.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-quick](<https://devfeed.tech/tags/aws-quick.md>), [s3](<https://devfeed.tech/tags/s3.md>), [s3-tables](<https://devfeed.tech/tags/s3-tables.md>), [tables](<https://devfeed.tech/tags/tables.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

AWS Glue's native Anthropic connector can load usage, cost, users, workspaces, and API key data into an AWS lakehouse without custom integration code. The walkthrough stores API keys in Secrets Manager, uses separate Admin and workspace connections for their different data scopes, and writes raw and curated Apache Iceberg tables to Amazon S3 Tables. AWS Glue materialized views join that data with business unit, outcome, and employee reference data; Athena queries the results, and AWS Quick can build dashboards directly from the views. The example surfaces spending by business unit, cost per outcome, and recently used keys created by former employees for ownership review--not automatic evidence of misuse. The article notes API rate limits, recommends bounded incremental reads, and specifies Glue materialized view requirements including Glue 5.1 or later, iam:PassRole, deterministic definitions, and inline subqueries because WITH-based views failed to refresh in its testing.

### Source excerpt

The new AWS Glue connector for Anthropic reads Claude usage, cost, and API key data into AWS without custom code. This post shows how to land it in Amazon S3 Tables as Apache Iceberg tables, join it with your business data, query it with Amazon Athena, and visualize AI spend and governance in AWS Quick.

## 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.

## Talk to your clinical data: unlocking AWS HealthLake with OpenSharing and Genie One

DevFeed: [Talk to your clinical data: unlocking AWS HealthLake with OpenSharing and Genie One](<https://devfeed.tech/articles/talk-to-your-clinical-data-unlocking-aws-healthlake-with-opensharing-and-genie-one-136420.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/talk-your-clinical-data-unlocking-aws-healthlake-opensharing-and-genie-one>)

Author: Michael McCarthy; Lily Goldstein; Douglas Moore

Published: 2026-11-16T18:30:00Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS Lake Formation](<https://devfeed.tech/topics/aws-lake-formation.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [API](<https://devfeed.tech/topics/api.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [accelerate](<https://devfeed.tech/tags/accelerate.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-use](<https://devfeed.tech/tags/ai-use.md>), [aws](<https://devfeed.tech/tags/aws.md>), [data](<https://devfeed.tech/tags/data.md>), [genie](<https://devfeed.tech/tags/genie.md>), [healthcare](<https://devfeed.tech/tags/healthcare.md>), [healthcare-and-life-sciences](<https://devfeed.tech/tags/healthcare-and-life-sciences.md>), [healthcare-life-sciences](<https://devfeed.tech/tags/healthcare-life-sciences.md>), [industries](<https://devfeed.tech/tags/industries.md>), [life](<https://devfeed.tech/tags/life.md>), [life-sciences](<https://devfeed.tech/tags/life-sciences.md>), [manage](<https://devfeed.tech/tags/manage.md>), [one](<https://devfeed.tech/tags/one.md>), [opensharing](<https://devfeed.tech/tags/opensharing.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [talk](<https://devfeed.tech/tags/talk.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The described OpenSharing integration lets Databricks query AWS HealthLake's FHIR data directly, avoiding export pipelines and duplicate copies. A custom OpenSharing server deployed as a Databricks App obtains temporary Lake Formation credentials, resolves each table's current Iceberg snapshot, and returns pre-signed data files; Databricks compute reads them directly from S3, so data does not pass through the server. OIDC federation lets AWS trust the app's Databricks identity. Unity Catalog governs shared-catalog access with grants and fine-grained, attribute-based, and role-based controls, and supports auditing. Curated Genie Agents can provide natural-language exploration, generating SQL and returning summarized answers, tables, and charts subject to Unity Catalog permissions. The text presents this as an option for Databricks analytics, notebooks, dashboards, and AI, alongside existing Athena or Redshift paths, and points to a reference implementation deployed as a Declarative Automation Bundle.

### Source excerpt

Many healthcare and life sciences organizations have standardized on AWS HealthLake to manage clinical data...

## Automate Bedrock AgentCore Security with Harness

DevFeed: [Automate Bedrock AgentCore Security with Harness](<https://devfeed.tech/articles/automate-bedrock-agentcore-security-with-harness-136342.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/control-access-to-ai-agents-deployed-on-aws-bedrock-agentcore>)

Author: Akshit Madan

Published: 2026-11-16T08:09:00Z

Content type: article

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [canary release](<https://devfeed.tech/topics/canary-release.md>), [Security](<https://devfeed.tech/topics/security.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-behavior](<https://devfeed.tech/tags/agent-behavior.md>), [agent-service](<https://devfeed.tech/tags/agent-service.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [automate](<https://devfeed.tech/tags/automate.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-iam](<https://devfeed.tech/tags/aws-iam.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [canary](<https://devfeed.tech/tags/canary.md>), [custom](<https://devfeed.tech/tags/custom.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [harness](<https://devfeed.tech/tags/harness.md>), [iam](<https://devfeed.tech/tags/iam.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Harness CD treats a Bedrock AgentCore agent as a deployable service and applies its authorizer configuration on each deployment. AWS_IAM accepts callers using AWS SigV4 credentials; CUSTOM_JWT validates OIDC/OAuth tokens against a discovery URL and configured audiences, clients, scopes, or claims. Either can be restricted to calls through the AgentCore Gateway. The authorizer governs inbound callers, while the execution role governs the agent's outbound AWS access. For canary traffic shifting, provision a Gateway and target rule pointing to the initial endpoint; without one, deployments cut over directly and skip traffic shifting. A pipeline can deploy revisions, shift traffic in stages with validations or approvals between shifts, and roll back to the previous revision on failure. Agent deployments require the CDS_AGENT_RUNTIME_DEPLOYMENT feature flag.

### Source excerpt

Set the agent authorizer (AWS_IAM or CUSTOM_JWT) in Harness. Then every Bedrock AgentCore deployment ships with access control, canary rollout, and rollback. | Blog

## 56 AWS API calls in 141 milliseconds: Inside an AI-run intrusion

DevFeed: [56 AWS API calls in 141 milliseconds: Inside an AI-run intrusion](<https://devfeed.tech/articles/56-aws-api-calls-in-141-milliseconds-inside-an-ai-run-intrusion-133228.md>)

Original publisher: [Read original article](<https://www.elastic.co/security-labs/threat-command/cyberstrikeai-aws-cloudtrail-intrusion>)

Author: Samir Bousseaden,Bryan Porras Blanch,Terrance DeJesus

Published: 2026-11-13T15:27:20Z

Content type: news

Language: en

Sources: [Elastic Security Labs](<https://devfeed.tech/sources/elastic-security-labs.md>)

Topics: [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [adversary](<https://devfeed.tech/tags/adversary.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-platform](<https://devfeed.tech/tags/agentic-platform.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-attacks](<https://devfeed.tech/tags/ai-assisted-attacks.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloudtrail](<https://devfeed.tech/tags/cloudtrail.md>), [cyberstrikeai](<https://devfeed.tech/tags/cyberstrikeai.md>), [detection](<https://devfeed.tech/tags/detection.md>), [detection-engineering](<https://devfeed.tech/tags/detection-engineering.md>), [detection-rules](<https://devfeed.tech/tags/detection-rules.md>), [rules](<https://devfeed.tech/tags/rules.md>), [server](<https://devfeed.tech/tags/server.md>), [threat-intelligence](<https://devfeed.tech/tags/threat-intelligence.md>)

### AI overview

The article documents a 16-day intrusion in which one server attributed to CyberStrikeAI used eight AWS identities across four accounts. Activity included validating credentials, harvesting secrets, reading EC2 user data, decrypting an SSM parameter, and issuing an SSM command; the audit log does not reveal the command or whether it succeeded. The authors characterize the activity as AI-assisted based on attribution and machine-speed behavior, but cannot establish that an LLM agent made decisions or how credentials were obtained. Six Elastic rules produced 78 mostly medium- and low-severity alerts; shared source IP and a 14-day gap made correlation essential. The article proposes two high-severity detections for bulk user-data and account enumeration, behavioral CloudTrail hunts, and an Elastic Workflows proof of concept to deactivate keys and restrict IAM access. Its response steps include rotating credentials and sessions, reviewing SSM history, treating user-data secrets as exposed, and limiting access to userData. IPs are offered for retrospective hunting, while behavioral indicators are described as more durable.

### Source excerpt

A CyberStrikeAI server spent 16 days in four AWS accounts using eight identities, and the CloudTrail record shows why six detection rules each caught only part of it.

## 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.

## Using AWS Backup to resynchronize a SQL Server AlwaysOn Availability Group

DevFeed: [Using AWS Backup to resynchronize a SQL Server AlwaysOn Availability Group](<https://devfeed.tech/articles/using-aws-backup-to-resynchronize-a-sql-server-alwayson-availability-group-131175.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/using-aws-backup-to-resynchronize-a-sql-server-alwayson-availability-group/>)

Author: Gabriel Pereira

Published: 2026-11-12T18:37:14Z

Content type: tutorial

Language: en

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

Topics: [sql-server](<https://devfeed.tech/topics/sql-server.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.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>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [alwayson](<https://devfeed.tech/tags/alwayson.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-backup](<https://devfeed.tech/tags/aws-backup.md>), [backup](<https://devfeed.tech/tags/backup.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [rebuild](<https://devfeed.tech/tags/rebuild.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [replica](<https://devfeed.tech/tags/replica.md>), [restore](<https://devfeed.tech/tags/restore.md>), [snapshot](<https://devfeed.tech/tags/snapshot.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS Backup can rebuild a failed SQL Server AlwaysOn secondary by restoring an application-consistent, VSS-enabled EC2 snapshot, then reconfiguring the node and rejoining it to the Availability Group. This EC2-level restore avoids streaming data from the primary as automatic seeding does and avoids the manual full backup, shipping, and restore cycle. The SQL Server VSS restore runbook cannot restore a secondary; it is limited to standalone databases or AG primaries. After restore, secondary IP addresses must be assigned manually. If VSS prerequisites are missing, resolve any cluster split-brain before rejoining. A broken LSN chain--such as when a primary log backup truncates records while the secondary is offline--requires per-database differential and log backups restored on the secondary with NORECOVERY before rejoining. The text reports about 10 minutes for one 100 GB lab restore and 6m13s to copy backup files in its broken-chain scenario; actual timing depends on volume size, file size, network throughput, and storage performance.

### Source excerpt

Learn how to use AWS Backup to rebuild a failed secondary replica in a SQL Server AlwaysOn Availability Group on Amazon EC2. We walk through capturing an application-consistent snapshot, restoring the EC2 instance, rejoining the Availability Group, and handling a broken LSN chain to reduce recovery time compared to a manual backup and restore.

## AI-driven database investigation using MCP, Agent Skills, and AWS DevOps Agent

DevFeed: [AI-driven database investigation using MCP, Agent Skills, and AWS DevOps Agent](<https://devfeed.tech/articles/ai-driven-database-investigation-using-mcp-agent-skills-and-aws-devops-agent-131174.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/integrate-mcp-tools-agent-skills-and-aws-devops-agent-for-ai-driven-database-investigation/>)

Author: Sudhir Amin

Published: 2026-11-12T18:34:07Z

Content type: article

Language: en

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

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>), [RDS for SQL Server](<https://devfeed.tech/topics/rds-for-sql-server.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [connect](<https://devfeed.tech/tags/connect.md>), [database](<https://devfeed.tech/tags/database.md>), [dba](<https://devfeed.tech/tags/dba.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [diagnostic](<https://devfeed.tech/tags/diagnostic.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [rds-for-sql-server](<https://devfeed.tech/tags/rds-for-sql-server.md>), [skills](<https://devfeed.tech/tags/skills.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS DevOps Agent can investigate RDS for SQL Server incidents by combining CloudWatch and Database Insights telemetry with SQL-specific MCP tools hosted in Lambda and exposed through Amazon Bedrock AgentCore Gateway. A Markdown skill defines triage thresholds, diagnostic steps, and report format; built-in telemetry identifies the problem type, while Gateway tools retrieve session, query, plan, and index details. In the example, an alarm led the agent to identify a head blocker holding a lock on dbo.Orders, with about 14 sessions waiting. It linked recurring spikes to a five-minute transaction pattern, noted it could not identify the client process, and recommended removing the delay, bounding client timeouts, and raising the alarm threshold. Access is constrained through SigV4, an allowlist, Secrets Manager credential retrieval by Lambda, and a read-only SQL login. The sample requires Database Insights, suitable database permissions, private VPC access, and supported AWS services and region.

### Source excerpt

Learn how to connect Amazon RDS for SQL Server diagnostic tools to AWS DevOps Agent through Amazon Bedrock AgentCore Gateway. MCP tools run in AWS Lambda behind a governed Gateway endpoint, and an investigation skill encodes your DBA team's method so the agent can triage alarms and run autonomous, auditable database investigations.

## Fine-grained access control for Amazon Bedrock Managed Knowledge Base tools

DevFeed: [Fine-grained access control for Amazon Bedrock Managed Knowledge Base tools](<https://devfeed.tech/articles/fine-grained-access-control-for-amazon-bedrock-managed-knowledge-base-tools-130562.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/fine-grained-access-control-for-amazon-bedrock-managed-knowledge-base-tools/>)

Author: Renya Kujirada

Published: 2026-11-12T15:40:24Z

Content type: article

Language: en

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

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-bedrock-knowledge-bases](<https://devfeed.tech/tags/amazon-bedrock-knowledge-bases.md>), [base](<https://devfeed.tech/tags/base.md>), [based](<https://devfeed.tech/tags/based.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [control](<https://devfeed.tech/tags/control.md>), [fine](<https://devfeed.tech/tags/fine.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [identity](<https://devfeed.tech/tags/identity.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [knowledge-base](<https://devfeed.tech/tags/knowledge-base.md>), [managed](<https://devfeed.tech/tags/managed.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

The design keeps a shared agent from choosing whose documents it searches: a gateway interceptor overwrites the MCP tool's `userContext` with the email from a JWT validated by the gateway, and Managed Knowledge Base ACL awareness filters results to that user's permitted documents. ACL awareness trusts the supplied identity, so it is not authorization by itself. Policy in AgentCore can independently deny calls when the injected user ID does not match the JWT email; a knowledge base resource policy can also restrict `Retrieve` and `GetDocumentContent` to the gateway execution role, blocking direct calls and other principals. These defenses have limits: the resource policy cannot distinguish another gateway using the same role, and explicit denial can affect other consumers. The sample requires a verified email claim; Cognito token customization needs the Essentials or Plus plan. S3 ACL updates apply after sync, and ACL mistakes silently omit documents.

### Source excerpt

Learn how to expose an Amazon Bedrock Managed Knowledge Base to AI agents as MCP tools through Amazon Bedrock AgentCore Gateway while keeping per-user access control. A request interceptor injects verified identity, Policy in AgentCore validates it independently, and a resource-based policy restricts direct access to the knowledge base.

## Resilient IAM database authentication with Amazon Aurora Global Database writer endpoint

DevFeed: [Resilient IAM database authentication with Amazon Aurora Global Database writer endpoint](<https://devfeed.tech/articles/resilient-iam-database-authentication-with-amazon-aurora-global-database-writer-endpoint-129590.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/resilient-iam-database-authentication-with-amazon-aurora-global-database-writer-endpoint/>)

Author: Raunak Gupta

Published: 2026-11-11T22:01:27Z

Content type: tutorial

Language: en

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

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cross](<https://devfeed.tech/tags/cross.md>), [database](<https://devfeed.tech/tags/database.md>), [failover](<https://devfeed.tech/tags/failover.md>), [global](<https://devfeed.tech/tags/global.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [iam](<https://devfeed.tech/tags/iam.md>), [id](<https://devfeed.tech/tags/id.md>), [passwordless](<https://devfeed.tech/tags/passwordless.md>), [policy](<https://devfeed.tech/tags/policy.md>), [primary](<https://devfeed.tech/tags/primary.md>), [region](<https://devfeed.tech/tags/region.md>), [resource](<https://devfeed.tech/tags/resource.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>), [writer](<https://devfeed.tech/tags/writer.md>)

### AI overview

A stable Aurora Global Database writer endpoint handles routing after a cross-Region promotion, while IAM authentication requires the token's SigV4 signing Region and `rds-db:connect` authorization to match the new primary. The walkthrough discovers the current primary Region through `describe-global-clusters`, signs a token for it, and lists each Regional cluster resource ID in the IAM policy; this keeps connections working with the same endpoint and policy after switchover or failover. IAM authentication must be enabled on both clusters, clients need cross-Region network access and TLS, and discovery needs a healthy Region during an impairment. Managed failover may lose writes not yet replicated and requires compatible engine versions. The excerpt also advises caching Region discovery to limit throttling, refreshing tokens per connection because they expire after 15 minutes, and respecting DNS TTL. AWS Advanced Drivers can automate token handling; the JDBC wrapper additionally supports Global Database failover reconnection.

### Source excerpt

Learn how to combine the Amazon Aurora Global Database writer endpoint with IAM database authentication so that passwordless access survives a cross-Region switchover or failover with no configuration changes. This walkthrough signs the token for the dynamically discovered primary Region and scopes the policy to every Regional cluster resource ID.

## Build a data foundation for agentic AI on AWS: From lakehouse to MCP

DevFeed: [Build a data foundation for agentic AI on AWS: From lakehouse to MCP](<https://devfeed.tech/articles/build-a-data-foundation-for-agentic-ai-on-aws-from-lakehouse-to-mcp-129558.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/build-a-data-foundation-for-agentic-ai-on-aws-from-lakehouse-to-mcp/>)

Author: Adrien Lebret

Published: 2026-11-11T21:03:43Z

Content type: article

Language: en

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

Topics: [AI-Ready Data](<https://devfeed.tech/topics/ai-ready-data.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [Amazon OpenSearch Service](<https://devfeed.tech/topics/amazon-opensearch-service.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-data](<https://devfeed.tech/tags/ai-data.md>), [aws](<https://devfeed.tech/tags/aws.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [context](<https://devfeed.tech/tags/context.md>), [context-engineering](<https://devfeed.tech/tags/context-engineering.md>), [data](<https://devfeed.tech/tags/data.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [governance](<https://devfeed.tech/tags/governance.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [like](<https://devfeed.tech/tags/like.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [model](<https://devfeed.tech/tags/model.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

The article presents a four-pillar AWS data foundation for agentic AI: a unified lakehouse, context engineering, interoperability, and governance. Amazon SageMaker Lakehouse and S3 Tables bring operational, analytical, and AI data into a governed foundation with Apache Iceberg, zero-ETL ingestion, and federated queries. Context engineering combines knowledge bases, short- and long-term memory, and tools that fetch selected data, addressing stateless models' limited context windows. For collaboration, A2A supports agent-to-agent communication over HTTP and JSON, while MCP standardizes agent access to resources, tools, and prompts; Amazon Bedrock AgentCore Gateway centralizes connections, authentication, audit logging, and permission-scoped semantic tool discovery. Amazon SageMaker Data Catalog adds dataset discovery, lineage, quality indicators, and publish-and-subscribe access controls. The article recommends establishing the lakehouse and ingestion first, developing context capabilities before scaling orchestration, and treating governance as an ongoing effort from the start.

### Source excerpt

Building a data foundation ready for agentic AI relies on a unified lakehouse and interoperability protocols like Model Context Protocol (MCP). This post walks through four pillars for building an agentic AI data foundation on AWS: a unified lakehouse, context engineering, multi-agent interoperability, and data governance.

## 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.

## Hackers exploit trusted AWS access to breach multiple cloud environments

DevFeed: [Hackers exploit trusted AWS access to breach multiple cloud environments](<https://devfeed.tech/articles/hackers-exploit-trusted-aws-access-to-breach-multiple-cloud-environments-127362.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/hackers-exploit-trusted-aws-access-to-breach-multiple-cloud-environments/>)

Author: Bill Toulas

Published: 2026-11-10T19:31:11Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [breach](<https://devfeed.tech/tags/breach.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-environments](<https://devfeed.tech/tags/cloud-environments.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [customers](<https://devfeed.tech/tags/customers.md>), [data](<https://devfeed.tech/tags/data.md>), [iam](<https://devfeed.tech/tags/iam.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [qubole](<https://devfeed.tech/tags/qubole.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [supply-chain-attack](<https://devfeed.tech/tags/supply-chain-attack.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Between October 14 and 26, an attacker used two compromised Qubole IAM users to assume roles in customer AWS accounts whose trust policies allowed access from Qubole's AWS account. Using the roles' existing permissions, the attacker surveyed resources, retrieved secrets and environment variables, validated discovered credentials, and downloaded accessible S3 data through a repeated sequence of listing buckets and objects, inspecting them, then calling GetObject. The report describes dozens of victims and millions of files stolen from one customer, but does not establish the compromise method or exact victim count. Administrators potentially affected are advised to review CloudTrail from October 1 onward, investigate secret and S3 access, rotate exposed credentials, revoke active role sessions, remove unused integrations, and restrict remaining roles' permissions, trusted identities, and source networks.

### Source excerpt

A threat actor used compromised identity and access management (IAM) credentials for a Qubole big data platform's AWS account to access and exfiltrate data from multiple customers' AWS environments. [...]

## Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub...

DevFeed: [Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub...](<https://devfeed.tech/articles/self-service-namespace-onboarding-on-amazon-eks-automating-access-entries-and-rbac-with-github-127576.md>)

Original publisher: [Read original article](<https://blog.devops.dev/self-service-namespace-onboarding-on-amazon-eks-automating-access-entries-and-rbac-with-github-74f0347e71e2?source=rss----33f8b2d9a328---4>)

Author: Oleh Adam Dubnytskyy

Published: 2026-11-10T09:42:12Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-web-services](<https://devfeed.tech/tags/amazon-web-services.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-eks](<https://devfeed.tech/tags/aws-eks.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [iam](<https://devfeed.tech/tags/iam.md>), [job](<https://devfeed.tech/tags/job.md>), [keys](<https://devfeed.tech/tags/keys.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [self-service](<https://devfeed.tech/tags/self-service.md>)

### AI overview

The excerpt describes namespace onboarding on Amazon EKS as two coordinated permission updates: an EKS access policy scope and Kubernetes RBAC. GitHub Actions authenticates through OIDC and temporary IAM role credentials. The EKS authorizer and RBAC authorizer can each allow a request, so effective permissions are their union; a restrictive custom RBAC role cannot narrow permissions already granted by a broader managed policy. The proposed setup uses separate workflows: one applies ClusterRoles and per-namespace RoleBindings, while another updates the access entry's namespace scope from files in a namespaces directory. The scripts validate namespace names, reject empty desired scopes, skip unchanged access-policy updates, and optionally prune stale managed RoleBindings. The excerpt notes that RBAC synchronization requires cluster-scoped rights and that missing namespaces are skipped with a warning before the workflow reports an error. The supplied text ends after describing this implementation and its pull request workflow.

### Source excerpt

Self-Service Namespace Onboarding on Amazon EKS: Automating Access Entries and RBAC with GitHub ActionsTwo authorization layers on Amazon EKS Every call my pipeline makes to the cluster's Kubernetes API server passes through two authorizers: Kubernetes RBAC and EKS access policies. Authentication: the access entry says who you are The pipeline never holds long-lived AWS keys. A GitHub Actions job gets an OIDC token, exchanges it for temporary credentials of an IAM role, and calls the cluster with them. More details on how it works can be seen here. Layer 1: Kubernetes RBAC RBAC is the standard Kubernetes model: Roles and ClusterRoles define rules, and RoleBindings attach them to a user or group. These objects live inside the cluster. You can write any rule you need, including rules for custom resources such as KEDA ScaledObject. Layer 2: EKS access policies Access policies are permission sets that AWS manages and that you attach to an access entry through the EKS API. They mirror the Kubernetes user-facing roles: AmazonEKSEditPolicy corresponds to edit, AmazonEKSAdminPolicy to admin, and so on. Each association has a scope: the whole cluster (type=cluster) or a list of namespaces (type=namespace). You can't modify an access policy or create your own. When the managed policies don't fit, more control can be configured by leveraging Kubernetes RBAC objects instead. How the two layers combine The API server chains its authorizers. The RBAC authorizer runs first and returns immediately if it allows the request. If RBAC has no opinion, the request goes to the EKS authorizer, which checks the access policies. If neither allows it, the request is denied. The access entry only establishes who the caller is; RBAC and access policies each get one chance to allow the request. Both authorizers can only allow or pass, so the effective permissions of ci-github-actions in a namespace are the union of both layers. That has two consequences for the automation: Onboarding a namespace

## LangSmith BYOC on AWS is generally available

DevFeed: [LangSmith BYOC on AWS is generally available](<https://devfeed.tech/articles/langsmith-byoc-on-aws-is-generally-available-123894.md>)

Original publisher: [Read original article](<https://www.langchain.com/blog/langsmith-byoc-is-now-generally-available-on-aws>)

Author: LangChain Accounts

Published: 2026-11-09T18:30:23Z

Content type: release

Language: en

Sources: [LangChain Blog](<https://devfeed.tech/sources/langchain-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [observability](<https://devfeed.tech/topics/observability.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-in-production](<https://devfeed.tech/tags/agents-in-production.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bring-your-own-cloud](<https://devfeed.tech/tags/bring-your-own-cloud.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [inside](<https://devfeed.tech/tags/inside.md>), [langsmith](<https://devfeed.tech/tags/langsmith.md>), [managed](<https://devfeed.tech/tags/managed.md>), [observability](<https://devfeed.tech/tags/observability.md>), [teams](<https://devfeed.tech/tags/teams.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

LangSmith BYOC is generally available to Enterprise customers on AWS, placing sensitive LangSmith data and agent workloads in the customer's AWS account and VPC while LangChain operates the deployment. Its data plane includes a private EKS cluster, databases, and storage; a control plane in LangChain's cloud handles authentication, organization settings, billing metadata, and provisioning. The planes communicate through AWS PrivateLink. LangChain manages upgrades, scaling, patching, backups, and monitoring. Customers retain ownership of the AWS environment and data, and the provisioning role is scoped to infrastructure management without specified trace or database read permissions. BYOC is offered across 15 AWS regions in the US, EU, and APAC. Most core observability, evaluation, deployment, sandbox, and gateway capabilities are available; it requires the Enterprise plan and contacting LangChain to get started.

### Source excerpt

LangSmith Bring Your Own Cloud is now generally available on AWS, giving Enterprise teams managed observability, evaluation, and deployment inside their own VPC.

## Simplify cross-partition access with AWS IAM outbound identity federation

DevFeed: [Simplify cross-partition access with AWS IAM outbound identity federation](<https://devfeed.tech/articles/simplify-cross-partition-access-with-aws-iam-outbound-identity-federation-126474.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/simplify-cross-partition-access-with-aws-iam-outbound-identity-federation/>)

Author: Bill Wells

Published: 2026-11-09T16:08:30Z

Content type: release

Language: en

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

Topics: [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [AWS Security Token Service](<https://devfeed.tech/topics/aws-security-token-service.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.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-iam](<https://devfeed.tech/tags/aws-iam.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [china](<https://devfeed.tech/tags/china.md>), [cross](<https://devfeed.tech/tags/cross.md>), [govcloud](<https://devfeed.tech/tags/govcloud.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [partition](<https://devfeed.tech/tags/partition.md>), [partitions](<https://devfeed.tech/tags/partitions.md>), [resources](<https://devfeed.tech/tags/resources.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [services](<https://devfeed.tech/tags/services.md>), [sovereign-cloud](<https://devfeed.tech/tags/sovereign-cloud.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

IAM outbound identity federation enables cross-partition AWS access by having a workload request a short-lived, AWS-signed JWT in its source partition and exchange it through `sts:AssumeRoleWithWebIdentity` for temporary credentials in the destination partition. The destination role's trust policy can restrict access using token audience, subject, source Region, account, organization, or principal context. CloudTrail records a shared token ID across issuance and exchange for correlation, and destination policies can revoke sessions. Setup requires enabling federation in the source account, registering its issuer as an OIDC provider in the destination account, and configuring role trust and permissions. The feature is available across Commercial, China, GovCloud (US), and European Sovereign Cloud partitions at no additional cost; it does not support same-partition federation. AWS advises least privilege, short token lifetimes, audit monitoring, and compliance review. Organizations with existing PKI can alternatively use IAM Roles Anywhere.

### Source excerpt

You can now use tokens from AWS Identity and Access Management (IAM) outbound federation to assume roles in other Amazon Web Services (AWS) partitions. When your workloads run across AWS partitions such as Commercial, China, GovCloud (US), and European Sovereign Cloud, a workload in one partition might need to access resources or communicate with AWS [...]

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