tag: Access-Control · 5 items
- Platform/SRE — Learn: Interesting pattern for zero-trust mainframe access using Boundary workers, but no deadline or GA capability change — worth evaluating if mainframes are in scope for the platform.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: New GA controls for AI agent traffic (stateful authz and rate limiting) are worth evaluating if your platform exposes Bedrock-based agents, but there is no operational urgency or EOL signal.
- CI/CD — Skip
- Leader — Learn: Temporal policies and rate limiting in AgentCore address governance and fairness concerns for AI agent deployments — relevant context for teams standardizing on AWS AI infrastructure, but no strategic decision required now.
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Learn: If your org has standardized on GitHub Copilot, this new dedicated policy gives enterprise and org admins finer-grained control over who can access the Copilot app — worth knowing when setting AI tooling governance standards.
- Platform/SRE — Plan: New GA Neptune capability that replaces static ARN enumeration in IAM policies with attribute-based cluster access using resource and principal tags; plan to adopt TBAC if you operate multiple Neptune clusters in shared VPC environments to enforce team and environment isolation.
- CI/CD — Skip
- Leader — Learn: Neptune now supports attribute-based access governance across clusters via IAM tags, useful context for organizations running Neptune at scale, but no strategic, licensing, or cost decision is triggered.
- Platform/SRE — Learn: Useful reference for SREs managing Grafana Cloud RBAC as observability centralizes across teams, but no operational change required — no EOL, deprecation, or security anchor present.
- CI/CD — Skip
- Leader — Learn: Outlines a scalable access governance model for centralized observability platforms, relevant when evaluating Grafana Cloud as a standard or managing sprawl across cloud/on-prem data sources.