Skip to main content
IAM Policy Map

AmazonKinesisFirehoseFullAccess

AdminAWS managedActiveReviewedShow on mapCompare

Summary

Provides full access to all Amazon Kinesis Firehose Delivery Streams.

Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.

Identity

ARN
arn:aws:iam::aws:policy/AmazonKinesisFirehoseFullAccess
Default version
v1
Created
Last edited
Services
firehose

Control-plane actions (10)

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

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
FirehoseAll 10 actions (see the Firehose page)2 List, 1 Read, 2 Tagging, 5 Write; 0 restricted, 0 conditionalfirehose:*

Data-plane actions (2)

By access level: 2 Write.

Data-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
FirehoseAll 2 actions (see the Firehose page)2 Write; 0 restricted, 0 conditionalfirehose:*

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: firehose (7 of 7).

Guidance

Practical scope

One statement allows firehose:* on Resource "*". The wildcard covers every firehose action, including the create, delete and update actions and the actions that put records into a delivery stream.

Use cases

  • Give users or roles full control of Amazon Kinesis Firehose delivery streams, for example to create, change and delete them.

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

  • firehose:* on all resources lets a principal create, change and delete any delivery stream and put records into it, not just view it.
  • The policy has no resource or condition restriction, so it is not limited to particular delivery 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 Firehose delivery streams is intended.

Related policies

Same service

Same domain

Frequently asked questions

When should I attach AmazonKinesisFirehoseFullAccess?
The reference page says you can attach AmazonKinesisFirehoseFullAccess to your users, groups and roles, and describes it as full access to all Amazon Kinesis Firehose delivery streams. Attach it where full control of delivery streams is intended.
What does AmazonKinesisFirehoseFullAccess grant?
It allows firehose:* on all resources. That covers every firehose action, including creating, updating and deleting delivery streams and putting records.
What are the security risks of AmazonKinesisFirehoseFullAccess?
Full access to every delivery stream means a principal can change or delete them and put records into them. The statement has 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

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Action": [
        "firehose:*"
      ],
      "Effect": "Allow",
      "Resource": "*"
    }
  ]
}

Version history

Current version v1, edited by AWS on 2015-10-07. 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/AmazonKinesisFirehoseFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonKinesisFirehoseFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonKinesisFirehoseFullAccess

CloudFormation

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

Terraform

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

CDK (TypeScript)

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

Sources