IAM actions and service prefixes appearing for the first time anywhere in the AWS managed policy archive. AWS usually ships the IAM component of a service before the SDK and the docs, so a brand-new prefix is often the earliest public sign of something unannounced.
283 service prefixes and 7,120 actions have appeared since tracking began on 2019-02-10. A further 146 prefixes were already present at that point, so they have no discoverable first sighting and are excluded here.
These land in real time on the read-only Telegram channel , by email via the discoveries topic, and in the discoveries RSS feed.
New service prefixes
30 of 30agent-registry
9 actions to date, first seen in AgentRegistryReadOnlyAccess
bedrock-websearch
3 actions to date, first seen in AmazonBedrockExternalWebSearchFullAccess
builderid
4 actions to date, first seen in AWSManagedSettingsAdminAccess
account-access
4 actions to date, first seen in AWSManagedAccountUserEntitlementAccess
aco-automation
5 actions to date, first seen in WellArchitectedAgentResourceScanning
cases
10 actions to date, first seen in WellArchitectedAgentResourceScanning
nova-act
2 actions to date, first seen in WellArchitectedAgentResourceScanning
simspaceweaver
2 actions to date, first seen in WellArchitectedAgentResourceScanning
evs
6 actions to date, first seen in AWSSupportServiceRolePolicy
eventsbilltoaws
2 actions to date, first seen in ReInventTicketApprovalAccess
bcm-pricing-calculator
7 actions to date, first seen in FinOpsAgentAgentPolicy
finops-agent
31 actions to date, first seen in FinOpsAgentOperatorPolicy
interconnect
13 actions to date, first seen in ReadOnlyAccess
transform
8 actions to date, first seen in ReadOnlyAccess
bcm-dashboards
3 actions to date, first seen in AWSConfigServiceRolePolicy
gameliftstreams
7 actions to date, first seen in AWSConfigServiceRolePolicy
rtbfabric
9 actions to date, first seen in AWSConfigServiceRolePolicy
s3files
15 actions to date, first seen in AmazonS3FilesClientFullAccess
aws-external-anthropic
45 actions to date, first seen in AnthropicInferenceAccess
elemental-inference
5 actions to date, first seen in ReadOnlyAccess
aidevops
82 actions to date, first seen in AIDevOpsAgentAccessPolicy
route53globalresolver
48 actions to date, first seen in AmazonRoute53GlobalResolverFullAccess
inspector2-telemetry
4 actions to date, first seen in AmazonInspector2ManagedTelemetryPolicy
kendra-ranking
3 actions to date, first seen in AWSConfigServiceRolePolicy
license-manager-linux-subscriptions
5 actions to date, first seen in AWSSupportServiceRolePolicy
license-manager-user-subscriptions
5 actions to date, first seen in AWSSupportServiceRolePolicy
bcm-recommended-actions
1 action to date, first seen in AccountManagementFromVercel
rds-db
1 action to date, first seen in ConsoleFullAccessFromVercel
geo-maps
2 actions to date, first seen in AWSSupportServiceRolePolicy
geo-places
7 actions to date, first seen in AWSSupportServiceRolePolicy
New actions on existing services
30 of 30first seen in AWSTransformServerMigrationAgentPolicy
first seen in AWSTransformServerMigrationAgentPolicy
first seen in AWSTransformServerMigrationAgentPolicy
Dates are the earliest appearance in an AWS managed policy tracked here, not official AWS launch dates. Actions are matched case-insensitively, as IAM does, and wildcards such as s3:* are excluded because they name no concrete action. For a year-by-year view of the same namespace growth, see the service growth timeline.