AmazonTimestreamConsoleFullAccess

Summary

Provides full access to manage Amazon Timestream using the AWS Management Console. The policy also grants permissions for certain KMS operations and operations to manage your saved queries. 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/AmazonTimestreamConsoleFullAccessCopy ARN

Default version

v13

Created

2020-09-30

Last edited

2026-02-12

Services

aws-marketplace, dbqms, iam, kms, pricing, s3, sns, timestream

Control-plane actions (56)

By access level: 13 List, 1 Permissions management, 14 Read, 2 Tagging, 26 Write.

Data-plane actions (5)

By access level: 2 List, 2 Read, 1 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: 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

Related policies

Same service

• AmazonQLDBConsoleFullAccess
• AmazonRDSDataFullAccess
• AmazonTimestreamFullAccess
• AmazonTimestreamReadOnlyAccess
• AWSDataExchangeFullAccess
• AWSDataExchangeProviderFullAccess
• AWSDataExchangeReadOnly
• AWSDataExchangeSubscriberFullAccess

Same domain

• AdministratorAccess
• AdministratorAccess-Amplify
• AIDevOpsAgentActionsPolicy
• AmazonDataZoneProjectDeploymentPermissionsBoundary
• AmazonDynamoDBFullAccess
• AmazonDynamoDBFullAccess_v2
• AmazonDynamoDBFullAccesswithDataPipeline
• AmazonEC2RoleforDataPipelineRole

Frequently asked questions

When should I attach AmazonTimestreamConsoleFullAccess?

The reference page says you can attach AmazonTimestreamConsoleFullAccess to your users, groups and roles, and describes it as: provides full access to manage Amazon Timestream using the AWS Management Console. Attach it where managing Timestream through the console is the intended scope.

What does AmazonTimestreamConsoleFullAccess grant?

It allows timestream:* on all resources, KMS key listing and describing, kms:CreateGrant under conditions, 9 dbqms saved-query actions, S3 bucket listing, SNS topic listing, IAM role listing, pricing:GetProducts and AWS Marketplace subscription and agreement actions.

What are the security risks of AmazonTimestreamConsoleFullAccess?

timestream:* allows every Timestream action, it can create KMS grants under conditions, and it includes AWS Marketplace subscribe and agreement actions. 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",
        "kms:ListKeys",
        "kms:ListAliases"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "kms:CreateGrant"
      ],
      "Resource": [
        "arn:aws:kms:*:*:key/*"
      ],
      "Condition": {
        "ForAnyValue:StringEquals": {
          "kms:EncryptionContextKeys": "aws:timestream:database-name"
        },
        "Bool": {
          "kms:GrantIsForAWSResource": true
        },
        "StringLike": {
          "kms:ViaService": "timestream.*.amazonaws.com"
        },
        "StringEquals": {
          "aws:ResourceAccount": "${aws:PrincipalAccount}"
        }
      }
    },
    {
      "Effect": "Allow",
      "Action": [
        "dbqms:CreateFavoriteQuery",
        "dbqms:DescribeFavoriteQueries",
        "dbqms:UpdateFavoriteQuery",
        "dbqms:DeleteFavoriteQueries",
        "dbqms:GetQueryString",
        "dbqms:CreateQueryHistory",
        "dbqms:DescribeQueryHistory",
        "dbqms:UpdateQueryHistory",
        "dbqms:DeleteQueryHistory"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "s3:ListAllMyBuckets"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "sns:ListTopics",
        "iam:ListRoles"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "pricing:GetProducts"
      ],
      "Resource": "*"
    },
    {
      "Sid": "AWSMarketplaceViewSubscriptions",
      "Effect": "Allow",
      "Action": [
        "aws-marketplace:ViewSubscriptions"
      ],
      "Resource": [
        "*"
      ]
    },
    {
      "Sid": "AWSMarketplaceAccess",
      "Effect": "Allow",
      "Action": [
        "aws-marketplace:SearchAgreements",
        "aws-marketplace:AcceptAgreementRequest",
        "aws-marketplace:CreateAgreementRequest",
        "aws-marketplace:ListEntitlementDetails",
        "aws-marketplace:DescribeAgreement",
        "aws-marketplace:Subscribe"
      ],
      "Resource": "*",
      "Condition": {
        "ForAnyValue:StringEquals": {
          "aws-marketplace:ProductId": [
            "prod-xcc5llpq4vlbc",
            "prod-5jijo74ujy36m",
            "prod-rjppt7huo35fm"
          ]
        }
      }
    }
  ]
}

Version history

Current version v13, edited by AWS on 2026-02-12. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AmazonTimestreamConsoleFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonTimestreamConsoleFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonTimestreamConsoleFullAccess

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

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

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

Sources

• AmazonTimestreamConsoleFullAccess (AWS Managed Policy Reference Guide) (retrieved 2026-11-13; supports summary, practicalScope, useCases, securityConsiderations, assignmentGuidance, faqs)
• AWS managed policies for Amazon Timestream Live Analytics (retrieved 2026-11-13; supports summary, useCases, bestPractices, securityConsiderations, assignmentGuidance, faqs)
• Managed policies and inline policies (IAM User Guide) (retrieved 2026-11-12; supports securityConsiderations, faqs)
• AWS managed policies for job functions (IAM User Guide) (retrieved 2026-11-12; supports faqs)

• Official AWS reference for AmazonTimestreamConsoleFullAccess
• AWS service guide
• Report a data issue