Skip to main content
IAM Policy Map

AmazonKinesisAnalyticsFullAccess

AdminAWS managedActiveReviewedShow on mapCompare

Summary

Provides full access to Amazon Kinesis Analytics 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/AmazonKinesisAnalyticsFullAccess
Default version
v1
Created
Last edited
Services
cloudwatch, firehose, iam, kinesis, kinesisanalytics, logs

Control-plane actions (44)

By access level: 5 List, 14 Read, 2 Tagging, 23 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
Firehose2 of 101 List, 1 Read; 0 restricted, 0 conditionalfirehose:DescribeDeliveryStream, firehose:ListDeliveryStreams
IAM3 of 1902 List, 1 Write; 1 restricted, 0 conditionaliam:ListPolicyVersions, iam:ListRoles, iam:PassRole
Kinesis4 of 421 List, 1 Read, 2 Write; 0 restricted, 0 conditionalkinesis:CreateStream, kinesis:DeleteStream, kinesis:DescribeStream, kinesis:ListStreams
Kinesis AnalyticsAll 34 actions (see the Kinesis Analytics page)1 List, 11 Read, 2 Tagging, 20 Write; 0 restricted, 0 conditionalkinesisanalytics:*
CloudWatch Logs1 of 1331 Read; 0 restricted, 0 conditionallogs:GetLogEvents
Firehose: 2 actions
  • firehose:DescribeDeliveryStream (Read)
  • firehose:ListDeliveryStreams (List)
IAM: 3 actions
  • iam:ListPolicyVersions (List)
  • iam:ListRoles (List)
  • iam:PassRole (Write)
Kinesis: 4 actions
  • kinesis:CreateStream (Write)
  • kinesis:DeleteStream (Write)
  • kinesis:DescribeStream (Read)
  • kinesis:ListStreams (List)
CloudWatch Logs: 1 actions
  • logs:GetLogEvents (Read)

Data-plane actions (4)

By access level: 1 List, 1 Read, 2 Write.

Data-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
CloudWatch2 of 51 List, 1 Read; 0 restricted, 0 conditionalcloudwatch:GetMetricStatistics, cloudwatch:ListMetrics
Kinesis2 of 52 Write; 0 restricted, 0 conditionalkinesis:PutRecord, kinesis:PutRecords
CloudWatch: 2 actions
  • cloudwatch:GetMetricStatistics (Read)
  • cloudwatch:ListMetrics (List)
Kinesis: 2 actions
  • kinesis:PutRecord (Write)
  • kinesis:PutRecords (Write)

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: mixed.

Can be attached: Yes, to users, groups and roles.

Why this tier

  • Grants at least 80% of the write and permissions-management actions of: kinesisanalytics (20 of 20).
  • Grants iam:PassRole, but only for scoped roles or under conditions (for example iam:PassedToService).

Guidance

Practical scope

Seven statements. The first allows kinesisanalytics:* on Resource "*". Others allow kinesis:CreateStream, kinesis:DeleteStream, kinesis:DescribeStream, kinesis:ListStreams, kinesis:PutRecord and kinesis:PutRecords; firehose:DescribeDeliveryStream and firehose:ListDeliveryStreams; cloudwatch:GetMetricStatistics and cloudwatch:ListMetrics; logs:GetLogEvents; and iam:ListPolicyVersions and iam:ListRoles. The last allows iam:PassRole on roles under service-role/ whose names start with kinesis-analytics, with no iam:PassedToService condition.

Use cases

  • Let users build and manage Amazon Kinesis Analytics applications in the AWS Management Console, including creating the Kinesis streams they read from and write to.

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

  • kinesisanalytics:* and kinesis:CreateStream, kinesis:DeleteStream, kinesis:PutRecord and kinesis:PutRecords apply to all resources, so a principal can create and delete any stream and put records into it.
  • iam:PassRole on service-role/kinesis-analytics* roles has no iam:PassedToService condition. Passing a role to a service needs iam:PassRole. The IAM User Guide says that to pass a role to an AWS service, a user must have permission to pass the role to the service, which helps administrators ensure that only approved users can configure a service with a role that grants permissions.
  • 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 use of Amazon Kinesis Analytics in the console is intended.

Same service

Same domain

Frequently asked questions

When should I attach AmazonKinesisAnalyticsFullAccess?
The reference page says you can attach AmazonKinesisAnalyticsFullAccess to your users, groups and roles, and describes it as full access to Amazon Kinesis Analytics via the console. Attach it for people who build Kinesis Analytics applications there.
What does AmazonKinesisAnalyticsFullAccess grant?
It allows kinesisanalytics:* on all resources, six kinesis stream actions, Firehose describe and list actions, CloudWatch metric reads, logs:GetLogEvents, IAM role listing and iam:PassRole on service-role/kinesis-analytics* roles.
What are the security risks of AmazonKinesisAnalyticsFullAccess?
kinesisanalytics:* and the kinesis create, delete and put actions apply to all resources, and iam:PassRole has no service condition. 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

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "kinesisanalytics:*",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "kinesis:CreateStream",
        "kinesis:DeleteStream",
        "kinesis:DescribeStream",
        "kinesis:ListStreams",
        "kinesis:PutRecord",
        "kinesis:PutRecords"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "firehose:DescribeDeliveryStream",
        "firehose:ListDeliveryStreams"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "cloudwatch:GetMetricStatistics",
        "cloudwatch:ListMetrics"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "logs:GetLogEvents",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "iam:ListPolicyVersions",
        "iam:ListRoles"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "iam:PassRole",
      "Resource": "arn:aws:iam::*:role/service-role/kinesis-analytics*"
    }
  ]
}

Version history

Current version v1, edited by AWS on 2016-09-21. 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/AmazonKinesisAnalyticsFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonKinesisAnalyticsFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonKinesisAnalyticsFullAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AmazonKinesisAnalyticsFullAccess

Terraform

resource "aws_iam_role_policy_attachment" "amazonkinesisanalyticsfullaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AmazonKinesisAnalyticsFullAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonKinesisAnalyticsFullAccess"),
);

Sources