AmazonKinesisFullAccess
Summary
Provides full access to all streams via the AWS Management Console.
Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.
Identity
- ARN
arn:aws:iam::aws:policy/AmazonKinesisFullAccess- Default version
- v1
- Created
- Last edited
- Services
- kinesis
Control-plane actions (42)
By access level: 4 List, 9 Read, 5 Tagging, 24 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Kinesis | All 42 actions (see the Kinesis page) | 4 List, 9 Read, 5 Tagging, 24 Write; 0 restricted, 0 conditional | kinesis:* |
Data-plane actions (5)
By access level: 3 Read, 2 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Kinesis | All 5 actions (see the Kinesis page) | 3 Read, 2 Write; 0 restricted, 0 conditional | kinesis:* |
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: all-resources.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants at least 80% of the write and permissions-management actions of: kinesis (26 of 26).
Guidance
Practical scope
One statement allows kinesis:* on Resource "*". The wildcard covers every kinesis action, including stream create and delete actions and the data-plane actions that put and get records.
Use cases
- Give users or roles full control of Amazon Kinesis streams, including reading and writing records.
Best practices
- AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.
Security considerations
- kinesis:* on all resources lets a principal create and delete any stream and read and write its records, not just view it.
- The policy has no resource or condition restriction, so it is not limited to particular streams.
- You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.
Assignment guidance
You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. It fits where full access to Amazon Kinesis streams is intended.
Related policies
Same service
- AmazonChimeSDKMessagingServiceRolePolicy
- AmazonKinesisAnalyticsFullAccess
- AmazonKinesisAnalyticsReadOnly
- AmazonKinesisReadOnlyAccess
- AmazonRDSServiceRolePolicy
- AmazonRekognitionServiceRole
- AmazonWorkSpacesWebServiceRolePolicy
- AWSIoTRuleActions
Same domain
Frequently asked questions
- When should I attach AmazonKinesisFullAccess?
- The reference page says you can attach AmazonKinesisFullAccess to your users, groups and roles, and describes it as full access to all streams via the console. Attach it where full control of streams is intended.
- What does AmazonKinesisFullAccess grant?
- It allows kinesis:* on all resources. That covers every kinesis action, including creating and deleting streams and putting and getting records.
- What are the security risks of AmazonKinesisFullAccess?
- kinesis:* lets a principal delete any stream and read and write its records, with no resource or condition restriction. AWS managed policies don't grant least privilege permissions, and you must consider the security risk of granting principals more permissions than they need. AWS updates to the policy affect every identity it is attached to.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "kinesis:*",
"Resource": "*"
}
]
}
Version history
Current version v1, edited by AWS on 2015-02-06. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.
Attach snippets
AWS CLI
aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AmazonKinesisFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonKinesisFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonKinesisFullAccessCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AmazonKinesisFullAccessTerraform
resource "aws_iam_role_policy_attachment" "amazonkinesisfullaccess" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AmazonKinesisFullAccess"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonKinesisFullAccess"),
);Sources
- AmazonKinesisFullAccess (AWS Managed Policy Reference Guide) (retrieved ; supports summary, practicalScope, useCases, securityConsiderations, assignmentGuidance, faqs)
- Managed policies and inline policies (IAM User Guide) (retrieved ; supports securityConsiderations, faqs)
- AWS managed policies for job functions (IAM User Guide) (retrieved ; supports bestPractices, faqs)