Skip to main content
IAM Policy Map

AmazonTimestreamFullAccess

High privilegeAdminAWS managedActiveReviewedShow on mapCompare

Summary

Provides full access to Amazon Timestream. The policy also grants certain KMS operation access. The Amazon Timestream guide covers Timestream Live Analytics.

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

Identity

ARN
arn:aws:iam::aws:policy/AmazonTimestreamFullAccess
Default version
v2
Created
Last edited
Services
kms, s3, timestream

Control-plane actions (35)

By access level: 5 List, 1 Permissions management, 10 Read, 2 Tagging, 17 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
KMS2 of 581 Permissions management, 1 Read; 1 restricted, 1 conditionalkms:CreateGrant, kms:DescribeKey
S31 of 1551 List; 0 restricted, 0 conditionals3:ListAllMyBuckets
TimestreamAll 32 actions (see the Timestream page)4 List, 9 Read, 2 Tagging, 17 Write; 0 restricted, 0 conditionaltimestream:*
KMS: 2 actions
  • kms:CreateGrant (Permissions management)
  • kms:DescribeKey (Read)
S3: 1 actions
  • s3:ListAllMyBuckets (List)

Data-plane actions (5)

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

Data-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
TimestreamAll 5 actions (see the Timestream page)2 List, 2 Read, 1 Write; 0 restricted, 0 conditionaltimestream:*

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: timestream (18 of 18).
  • Grants data-plane write actions on a data store on all resources without conditions.
  • 3 granted write or permissions-management actions have no data-plane classification from AWS, so the data-plane rule cannot assess them.

Guidance

Practical scope

4 statements, all Allow, all on Resource "*". They allow timestream:*, kms:DescribeKey, s3:ListAllMyBuckets, and kms:CreateGrant with conditions: ForAnyValue:StringEquals on kms:EncryptionContextKeys (aws:timestream:database-name), Bool on kms:GrantIsForAWSResource (true) and StringLike on kms:ViaService (timestream.*.amazonaws.com). The reference page says that if you use a customer managed CMK you should refer to the documentation for additional permissions needed.

Use cases

  • Give users or roles full access to Amazon Timestream, including the KMS access Timestream needs.

Best practices

  • The Amazon Timestream guide says AWS managed policies might not grant least-privilege permissions for your specific use cases and recommends reducing permissions further with customer managed policies specific to your use cases.

Security considerations

  • timestream:* on Resource "*" allows every Timestream action, not only reads.
  • kms:CreateGrant is allowed on Resource "*", with conditions on the encryption context key, kms:GrantIsForAWSResource and kms:ViaService.
  • 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. The Amazon Timestream guide says you can attach it to your users, groups and roles. It fits where full access to Amazon Timestream is intended.

Related policies

Same service

Same domain

Frequently asked questions

When should I attach AmazonTimestreamFullAccess?
The reference page says you can attach AmazonTimestreamFullAccess to your users, groups and roles, and describes it as: provides full access to Amazon Timestream. Attach it where full access to Amazon Timestream is the intended scope.
What does AmazonTimestreamFullAccess grant?
It allows timestream:*, kms:DescribeKey and s3:ListAllMyBuckets on all resources, and kms:CreateGrant on all resources under conditions on kms:EncryptionContextKeys, kms:GrantIsForAWSResource and kms:ViaService.
What are the security risks of AmazonTimestreamFullAccess?
timestream:* allows every Timestream action, and kms:CreateGrant applies to all resources under the stated conditions. 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": [
        "timestream:*"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "kms:DescribeKey"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "kms:CreateGrant"
      ],
      "Resource": "*",
      "Condition": {
        "ForAnyValue:StringEquals": {
          "kms:EncryptionContextKeys": "aws:timestream:database-name"
        },
        "Bool": {
          "kms:GrantIsForAWSResource": true
        },
        "StringLike": {
          "kms:ViaService": "timestream.*.amazonaws.com"
        }
      }
    },
    {
      "Effect": "Allow",
      "Action": [
        "s3:ListAllMyBuckets"
      ],
      "Resource": "*"
    }
  ]
}

Version history

Current version v2, edited by AWS on 2021-11-26. 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/AmazonTimestreamFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonTimestreamFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonTimestreamFullAccess

CloudFormation

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

Terraform

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

CDK (TypeScript)

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

Sources