**This page is only for existing customers of the Amazon Glacier service using Vaults and the original REST API from 2012.**
If you're looking for archival storage solutions, we recommend using the Amazon Glacier storage classes in Amazon S3, S3 Glacier Instant Retrieval, S3 Glacier Flexible Retrieval, and S3 Glacier Deep Archive. To learn more about these storage options, see [Amazon Glacier storage classes](https://aws.amazon.com/s3/storage-classes/glacier/).
Amazon Glacier (original standalone vault-based service) is no longer accepting new customers. Amazon Glacier is a standalone service with its own APIs that stores data in vaults and is distinct from Amazon S3 and the Amazon S3 Glacier storage classes. Your existing data will remain secure and accessible in Amazon Glacier indefinitely. No migration is required. For low-cost, long-term archival storage, AWS recommends the [Amazon S3 Glacier storage classes](https://aws.amazon.com/s3/storage-classes/glacier/), which deliver a superior customer experience with S3 bucket-based APIs, full AWS Region availability, lower costs, and AWS service integration. If you want enhanced capabilities, consider migrating to Amazon S3 Glacier storage classes by using our [AWS Solutions Guidance for transferring data from Amazon Glacier vaults to Amazon S3 Glacier storage classes](https://aws.amazon.com/solutions/guidance/data-transfer-from-amazon-s3-glacier-vaults-to-amazon-s3/).
# Identity and Access Management for Amazon Glacier
AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use Amazon Glacier resources. IAM is an AWS service that you can use with no additional charge.
**Topics**
+ [
## Audience
](#security_iam_audience)
+ [
## Authenticating with identities
](#security_iam_authentication)
+ [
## Managing access using policies
](#security_iam_access-manage)
+ [
# How Amazon Glacier works with IAM
](security_iam_service-with-iam.md)
+ [
# Identity-based policy examples for Amazon Glacier
](security_iam_id-based-policy-examples.md)
+ [
# Resource-based policy examples for Amazon Glacier
](security_iam_resource-based-policy-examples.md)
+ [
# Troubleshooting Amazon Glacier identity and access
](security_iam_troubleshoot.md)
+ [
# API Permissions Reference
](glacier-api-permissions-ref.md)
## Audience
How you use AWS Identity and Access Management (IAM) differs based on your role:
+ **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting Amazon Glacier identity and access](security_iam_troubleshoot.md))
+ **Service administrator** - determine user access and submit permission requests (see [How Amazon Glacier works with IAM](security_iam_service-with-iam.md))
+ **IAM administrator** - write policies to manage access (see [Identity-based policy examples for Amazon Glacier](security_iam_id-based-policy-examples.md))
## Authenticating with identities
Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role.
You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*.
For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*.
### AWS account root user
When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*.
### Federated identity
As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials.
A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials.
For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*.
### IAM users and groups
An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*.
An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*.
### IAM roles
An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*.
IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
## Managing access using policies
You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*.
Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**.
By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation.
### Identity-based policies
Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.
Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*.
### Resource-based policies
Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy.
Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy.
### Other policy types
AWS supports additional policy types that can set the maximum permissions granted by more common policy types:
+ **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*.
+ **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*.
+ **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*.
+ **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*.
### Multiple policy types
When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*.
# How Amazon Glacier works with IAM
Before you use IAM to manage access to Amazon Glacier, learn what IAM features are available to use with Amazon Glacier.
**IAM features you can use with Amazon Glacier**
| IAM feature | Amazon Glacier support |
| --- | --- |
| [Identity-based policies](#security_iam_service-with-iam-id-based-policies) | Yes |
| [Resource-based policies](#security_iam_service-with-iam-resource-based-policies) | Yes |
| [Policy actions](#security_iam_service-with-iam-id-based-policies-actions) | Yes |
| [Policy resources](#security_iam_service-with-iam-id-based-policies-resources) | Yes |
| [Policy condition keys (service-specific)](#security_iam_service-with-iam-id-based-policies-conditionkeys) | Yes |
| [ACLs](#security_iam_service-with-iam-acls) | No |
| [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | No |
| [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | Yes |
| [Principal permissions](#security_iam_service-with-iam-principal-permissions) | No |
| [Service roles](#security_iam_service-with-iam-roles-service) | No |
| [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | No |
To get a high-level view of how Amazon Glacier and other AWS services work with most IAM features, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
## Identity-based policies for Amazon Glacier
**Supports identity-based policies:** Yes
Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.
With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. To learn about all of the elements that you can use in a JSON policy, see [IAM JSON policy elements reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*.
### Identity-based policy examples for Amazon Glacier
To view examples of Amazon Glacier identity-based policies, see [Identity-based policy examples for Amazon Glacier](security_iam_id-based-policy-examples.md).
## Resource-based policies within Amazon Glacier
**Supports resource-based policies:** Yes
Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services.
To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
The Amazon Glacier service supports only one type of resource-based policy called a *vault policy*, which is attached to a vault. This policy defines which principals can perform actions on the vault.
Amazon Glacier vault policies manage permissions in the following ways:
+ Manage user permissions in an account using a single vault policy, instead of more than one individual user policies.
+ Manage cross-account permissions as an alternative to using IAM roles.
### Resource-based policy examples within Amazon Glacier
To view examples of Amazon Glacier resource-based policies, see [Resource-based policy examples for Amazon Glacier](security_iam_resource-based-policy-examples.md).
## Policy actions for Amazon Glacier
**Supports policy actions:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation.
To see a list of Amazon Glacier actions, see [Actions defined by Amazon Glacier](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazons3glacier.html#amazons3glacier-actions-as-permissions) in the *Service Authorization Reference*.
Policy actions in Amazon Glacier use the following prefix before the action:
```
glacier
```
To specify multiple actions in a single statement, separate them with commas.
```
"Action": [
"glacier:CreateVault",
"glacier:DescribeVault",
"glacier:ListVaults"
]
```
You can specify multiple actions using wildcards (\$1). For example, to specify all actions that begin with the word `Describe`, include the following action:
```
"Action": "glacier:GetVault*"
```
To view examples of Amazon Glacier identity-based policies, see [Identity-based policy examples for Amazon Glacier](security_iam_id-based-policy-examples.md).
## Policy resources for Amazon Glacier
**Supports policy resources:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources.
```
"Resource": "*"
```
To see a list of Amazon Glacier resource types and their ARNs, see [Resources defined by Amazon Glacier](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazons3glacier.html#amazons3glacier-resources-for-iam-policies) in the *Service Authorization Reference*. To learn which actions you can specify the ARN of each resource, see [Actions defined by Amazon Glacier](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazons3glacier.html#amazons3glacier-actions-as-permissions).
In Amazon Glacier, the primary resource is a *vault*. Amazon Glacier supports policies only at the vault level. That is, in an IAM policy, the `Resource` value that you specify can be a specific vault or a set of vaults in a specific AWS Region. Amazon Glacier doesn't support archive-level permissions.
For all Amazon Glacier actions, `Resource` specifies the vault on which you want to grant the permissions. These resources have unique Amazon Resource Names (ARNs) associated with them as shown in the following table, and you can use a wildcard character (\$1) in the ARN to match vault names that start with the same prefix.
****
| Resource Type | ARN Format |
| --- | --- |
| Vaults | arn:aws:glacier:region:account-id:vaults/vault-name |
| Vaults with names starting with "example" | arn:aws:glacier:region:account-id:vaults/example\$1 |
Amazon Glacier provides a set of operations to work with the Amazon Glacier resources. For information on the available operations, see [API Reference for Amazon Glacier](amazon-glacier-api.md).
Some Amazon Glacier API actions support multiple resources. For example, `glacier:AddTagsToVault` accesses examplevault1 and examplevault2, so a principal must have permissions to access both resources. To specify multiple resources in a single statement, separate the ARNs with commas.
```
"Resource": [
""arn:aws:glacier:us-west-2:123456789012:vaults/examplevault1",",
""arn:aws:glacier:us-west-2:123456789012:vaults/examplevault2","
]
```
## Policy condition keys for Amazon Glacier
**Supports service-specific policy condition keys:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*.
To see a list of Amazon Glacier condition keys, see [Condition keys for Amazon Glacier](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazons3glacier.html#amazons3glacier-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [Actions defined by Amazon Glacier](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazons3glacier.html#amazons3glacier-actions-as-permissions).
For examples of using the glacier–specific condition keys, see [Vault Lock Policies](vault-lock-policy.md).
## ACLs in Amazon Glacier
**Supports ACLs:** No
Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format.
## ABAC with Amazon Glacier
**Supports ABAC (tags in policies):** No
Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource.
To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `aws:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys.
If a service supports all three condition keys for every resource type, then the value is **Yes** for the service. If a service supports all three condition keys for only some resource types, then the value is **Partial**.
For more information about ABAC, see [Define permissions with ABAC authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*.
## Using temporary credentials with Amazon Glacier
**Supports temporary credentials:** Yes
Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
## Cross-service principal permissions for Amazon Glacier
**Supports forward access sessions (FAS):** No
Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html).
## Service roles for Amazon Glacier
**Supports service roles:** No
A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see [Create a role to delegate permissions to an AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*.
**Warning**
Changing the permissions for a service role might break Amazon Glacier functionality. Edit service roles only when Amazon Glacier provides guidance to do so.
## Service-linked roles for Amazon Glacier
**Supports service-linked roles:** No
A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles.
For details about creating or managing service-linked roles, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html). Find a service in the table that includes a `Yes` in the **Service-linked role** column. Choose the **Yes** link to view the service-linked role documentation for that service.
# Identity-based policy examples for Amazon Glacier
By default, users and roles don't have permission to create or modify Amazon Glacier resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.
To learn how to create an IAM identity-based policy by using these example JSON policy documents, see [Create IAM policies (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) in the *IAM User Guide*.
For details about actions and resource types defined by Amazon Glacier, including the format of the ARNs for each of the resource types, see [Actions, resources, and condition keys for Amazon Glacier](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazons3glacier.html) in the *Service Authorization Reference*.
The following is an example policy that grants permissions for three Amazon Glacier vault-related actions (`glacier:CreateVault`, `glacier:DescribeVault` and `glacier:ListVaults`) on a resource, using the Amazon Resource Name (ARN) that identifies all of the vaults in the `us-west-2` AWS Region. ARNs uniquely identify AWS resources. For more information about ARNs used with Amazon Glacier, see [Policy resources for Amazon Glacier](security_iam_service-with-iam.md#security_iam_service-with-iam-id-based-policies-resources).
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"glacier:CreateVault",
"glacier:DescribeVault",
"glacier:ListVaults"
],
"Resource": "arn:aws:glacier:us-west-2:123456789012:vaults/*"
}
]
}
```
------
The policy grants permissions to create, list, and obtain descriptions of vaults in the `us-west-2` Region. The wildcard character (\$1) at the end of the ARN means that this statement can match any vault name.
**Important**
When you grant permissions to create a vault using the `glacier:CreateVault` operation, you must specify a wildcard character (\$1) because you don't know the vault name until after you create the vault.
**Topics**
+ [
## Policy best practices
](#security_iam_service-with-iam-policy-best-practices)
+ [
## Using the Amazon Glacier console
](#security_iam_id-based-policy-examples-console)
+ [
## Allow users to view their own permissions
](#id-based-policy-view-own-permissions)
+ [
## Customer Managed Policy Examples
](#id-based-policy-customer-managed)
## Policy best practices
Identity-based policies determine whether someone can create, access, or delete Amazon Glacier resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations:
+ **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*.
+ **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*.
+ **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*.
+ **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*.
+ **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*.
For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*.
## Using the Amazon Glacier console
To access the Amazon Glacier console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the Amazon Glacier resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy.
You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform.
The Amazon Glacier console provides an integrated environment for you to create and manage Amazon Glacier vaults. At a minimum IAM identities that you create must be granted permissions for the `glacier:ListVaults` action to view the Amazon Glacier console as shown in the following example.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Action": [
"glacier:ListVaults"
],
"Effect": "Allow",
"Resource": "*"
}
]
}
```
------
AWS addresses many common use cases by providing standalone IAM policies that are created and administered by AWS. Managed policies grant necessary permissions for common use cases so you can avoid having to investigate what permissions are needed. For more information, see [AWS Managed Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*.
The following AWS managed policies, which you can attach to users in your account, are specific to Amazon Glacier:
+ **AmazonGlacierReadOnlyAccess** – Grants read only access to Amazon Glacier through the AWS Management Console.
+ **AmazonGlacierFullAccess** – Grants full access to Amazon Glacier through the AWS Management Console.
You can also create your own custom IAM policies to allow permissions for Amazon Glacier API actions and resources. You can attach these custom policies to the custom IAM roles that you create for your Amazon Glacier vaults.
Both of the Amazon Glacier AWS Managed policies discussed in the next section grant permissions for `glacier:ListVaults`.
For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the *IAM User Guide*.
## Allow users to view their own permissions
This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ViewOwnUserInfo",
"Effect": "Allow",
"Action": [
"iam:GetUserPolicy",
"iam:ListGroupsForUser",
"iam:ListAttachedUserPolicies",
"iam:ListUserPolicies",
"iam:GetUser"
],
"Resource": ["arn:aws:iam::*:user/${aws:username}"]
},
{
"Sid": "NavigateInConsole",
"Effect": "Allow",
"Action": [
"iam:GetGroupPolicy",
"iam:GetPolicyVersion",
"iam:GetPolicy",
"iam:ListAttachedGroupPolicies",
"iam:ListGroupPolicies",
"iam:ListPolicyVersions",
"iam:ListPolicies",
"iam:ListUsers"
],
"Resource": "*"
}
]
}
```
## Customer Managed Policy Examples
In this section, you can find example user policies that grant permissions for various Amazon Glacier actions. These policies work when you are using Amazon Glacier REST API, the Amazon SDKs, the AWS CLI, or, if applicable, the Amazon Glacier management console.
**Note**
All examples use the US West (Oregon) Region (`us-west-2`) and contain fictitious account IDs.
**Topics**
+ [
### Example 1: Allow a User to Download Archives from a Vault
](#vault-access-policy-example-init-jobs)
+ [
### Example 2: Allow a User to Create a Vault and Configure Notifications
](#vault-access-policy-example-create-vault)
+ [
### Example 3: Allow a User to Upload Archives to a Specific Vault
](#vault-access-policy-example-upload-archives)
+ [
### Example 4: Allow a User Full Permissions on a Specific Vault
](#vault-access-policy-example-full-permission)
### Example 1: Allow a User to Download Archives from a Vault
To download an archive, you first initiate a job to retrieve the archive. After the retrieval job is complete, you can download the data. The following example policy grants permissions for the `glacier:InitiateJob` action to initiate a job (which allows the user to retrieve an archive or a vault inventory from the vault), and permissions for the `glacier:GetJobOutput` action to download the retrieved data. The policy also grants permissions to perform the `glacier:DescribeJob` action so that the user can get the job status. For more information, see [Initiate Job (POST jobs)](api-initiate-job-post.md).
The policy grants these permissions on a vault named `examplevault`. You can get the vault ARN from the [Amazon Glacier console](https://console.aws.amazon.com/glacier/home), or programmatically by calling either the [Describe Vault (GET vault)](api-vault-get.md) or the [List Vaults (GET vaults)](api-vaults-get.md) API actions.
### Example 2: Allow a User to Create a Vault and Configure Notifications
The following example policy grants permissions to create a vault in the us-west-2 Region as specified in the `Resource` element and configure notifications. For more information about working with notifications, see [Configuring Vault Notifications in Amazon Glacier](configuring-notifications.md). The policy also grants permissions to list vaults in the AWS Region and get a specific vault description.
**Important**
When you grant permissions to create a vault using the `glacier:CreateVault` operation, you must specify a wildcard character (\$1) in the `Resource` value because you don't know the vault name until after you create the vault.
### Example 3: Allow a User to Upload Archives to a Specific Vault
The following example policy grants permissions to upload archives to a specific vault in the us-west-2 Region. These permissions allow a user to upload an archive all at once using the [Upload Archive (POST archive)](api-archive-post.md) API operation or in parts using the [Initiate Multipart Upload (POST multipart-uploads)](api-multipart-initiate-upload.md) API operation.
### Example 4: Allow a User Full Permissions on a Specific Vault
The following example policy grants permissions for all Amazon Glacier actions on a vault named `examplevault`.
# Resource-based policy examples for Amazon Glacier
A Amazon Glacier vault can have one vault access policy and one Vault Lock policy associated with it. A Amazon Glacier *vault access policy* is a resource-based policy that you can use to manage permissions to your vault. A *Vault Lock policy* is vault access policy that can be locked. After you lock a Vault Lock policy, the policy can't be changed. You can use a Vault Lock Policy to enforce compliance controls.
**Topics**
+ [
# Vault Access Policies
](vault-access-policy.md)
+ [
# Vault Lock Policies
](vault-lock-policy.md)
# Vault Access Policies
An Amazon Glacier vault access policy is a resource-based policy that you can use to manage permissions to your vault.
You can create one vault access policy for each vault to manage *permissions*. You can modify permissions in a vault access policy at any time. Amazon Glacier also supports a Vault Lock policy on each vault that, after you lock it, cannot be altered. For more information about working with Vault Lock policies, see [Vault Lock Policies](vault-lock-policy.md).
**Topics**
+ [
## Example 1: Grant Cross-Account Permissions for Specific Amazon Glacier Actions
](#vault-access-multiple-accounts)
+ [
## Example 2: Grant Cross-Account Permissions for MFA Delete Operations
](#vault-access-mfa-authentication)
## Example 1: Grant Cross-Account Permissions for Specific Amazon Glacier Actions
The following example policy grants cross-account permissions to two AWS accounts for a set of Amazon Glacier operations on a vault named `examplevault`.
**Note**
The account that owns the vault is billed for all costs associated with the vault. All requests, data transfer, and retrieval costs made by allowed external accounts are billed to the account that owns the vault.
## Example 2: Grant Cross-Account Permissions for MFA Delete Operations
You can use multi-factor authentication (MFA) to protect your Amazon Glacier resources. To provide an extra level of security, MFA requires users to prove physical possession of an MFA device by providing a valid MFA code. For more information about configuring MFA access, see [Configuring MFA-Protected API Access](https://docs.aws.amazon.com/IAM/latest/UserGuide/MFAProtectedAPI.html) in the *IAM User Guide*.
The example policy grants an AWS account with temporary credentials permission to delete archives from a vault named examplevault, provided the request is authenticated with an MFA device. The policy uses the `aws:MultiFactorAuthPresent` condition key to specify this additional requirement. For more information, see [Available Keys for Conditions](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#AvailableKeys) in the *IAM User Guide*.
# Vault Lock Policies
An Amazon Glacier (Amazon Glacier) vault can have one resource-based vault access policy and one Vault Lock policy attached to it. A *Vault Lock policy* is a vault access policy that you can lock. Using a Vault Lock policy can help you enforce regulatory and compliance requirements. Amazon Glacier provides a set of API operations for you to manage the Vault Lock policies, see [Locking a Vault by Using the Amazon Glacier API](vault-lock-how-to-api.md).
As an example of a Vault Lock policy, suppose that you are required to retain archives for one year before you can delete them. To implement this requirement, you can create a Vault Lock policy that denies users permissions to delete an archive until the archive has existed for one year. You can test this policy before locking it down. After you lock the policy, the policy becomes immutable. For more information about the locking process, see [Vault Lock Policies](#vault-lock-policy). If you want to manage other user permissions that can be changed, you can use the vault access policy (see [Vault Access Policies](vault-access-policy.md)).
You can use the Amazon Glacier API, Amazon SDKs, AWS CLI, or the Amazon Glacier console to create and manage Vault Lock policies. For a list of Amazon Glacier actions allowed for vault resource-based policies, see [API Permissions Reference](glacier-api-permissions-ref.md).
**Topics**
+ [
## Example 1: Deny Deletion Permissions for Archives Less Than 365 Days Old
](#vault-lock-archive-age)
+ [
## Example 2: Deny Deletion Permissions Based on a Tag
](#vault-lock-legal-hold-tag)
## Example 1: Deny Deletion Permissions for Archives Less Than 365 Days Old
Suppose that you have a regulatory requirement to retain archives for up to one year before you can delete them. You can enforce that requirement by implementing the following Vault Lock policy. The policy denies the `glacier:DeleteArchive` action on the examplevault vault if the archive being deleted is less than one year old. The policy uses the Amazon Glacier-specific condition key `ArchiveAgeInDays` to enforce the one-year retention requirement.
## Example 2: Deny Deletion Permissions Based on a Tag
Suppose that you have a time-based retention rule that an archive can be deleted if it is less than a year old. At the same time, suppose that you need to place a legal hold on your archives to prevent deletion or modification for an indefinite duration during a legal investigation. In this case, the legal hold takes precedence over the time-based retention rule specified in the Vault Lock policy.
To put these two rules in place, the following example policy has two statements:
+ The first statement denies deletion permissions for everyone, locking the vault. This lock is performed by using the `LegalHold` tag.
+ The second statement grants deletion permissions when the archive is less than 365 days old. But even when archives are less than 365 days old, no one can delete them when the condition in the first statement is met.
# Troubleshooting Amazon Glacier identity and access
Use the following information to help you diagnose and fix common issues that you might encounter when working with Amazon Glacier and IAM.
**Topics**
+ [
## I am not authorized to perform an action in Amazon Glacier
](#security_iam_troubleshoot-no-permissions)
+ [
## I am not authorized to perform iam:PassRole
](#security_iam_troubleshoot-passrole)
+ [
## I want to allow people outside of my AWS account to access my Amazon Glacier resources
](#security_iam_troubleshoot-cross-account-access)
## I am not authorized to perform an action in Amazon Glacier
If you receive an error that you're not authorized to perform an action, your policies must be updated to allow you to perform the action.
The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a fictional `my-example-widget` resource but doesn't have the fictional `glacier:GetWidget` permissions.
```
User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: glacier:GetWidget on resource: my-example-widget
```
In this case, the policy for the `mateojackson` user must be updated to allow access to the `my-example-widget` resource by using the `glacier:GetWidget` action.
If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials.
## I am not authorized to perform iam:PassRole
If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to Amazon Glacier.
Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service.
The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in Amazon Glacier. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service.
```
User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole
```
In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action.
If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials.
## I want to allow people outside of my AWS account to access my Amazon Glacier resources
You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources.
To learn more, consult the following:
+ To learn whether Amazon Glacier supports these features, see [How Amazon Glacier works with IAM](security_iam_service-with-iam.md).
+ To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*.
+ To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*.
+ To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*.
+ To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
# API Permissions Reference
When you are setting up [How Amazon Glacier works with IAM](security_iam_service-with-iam.md) and writing a permissions policy that you can attach to an IAM identity (identity-based policies) or a resource (resource-based policies), you can use the following table as a reference. The table lists each Amazon Glacier API operation, the corresponding actions for which you can grant permissions to perform the action, and the AWS resource for which you can grant the permissions.
You specify the actions in the policy's `Action` element, and you specify the resource value in the policy's `Resource` element. Also, you can use the IAM policy language `Condition` element to specify when a policy should take effect.
To specify an action, use the `glacier:` prefix followed by the API operation name (for example, `glacier:CreateVault`). For most Amazon Glacier actions, `Resource` is the vault on which you want to grant the permissions. You specify a vault as the `Resource` value by using the vault ARN. To express conditions, you use predefined condition keys. For more information, see [Resource-based policies within Amazon Glacier](security_iam_service-with-iam.md#security_iam_service-with-iam-resource-based-policies).
The following table lists actions that can be used with identity-based policies and resource-based policies.
**Note**
Some actions can only be used with identity-based policies. These actions are marked by an asterisk (\$1) after the name of the API operation in the first column.
Use the scroll bars to see the rest of the table.
**Amazon Glacier API and Required Permissions for Actions**
| Amazon Glacier API Operations | Required Permissions (API Actions) | Resources | Condition Keys |
| --- | --- | --- | --- |
| [Abort Multipart Upload (DELETE uploadID)](api-multipart-abort-upload.md) | glacier:AbortMultipartUpload | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [Abort Vault Lock (DELETE lock-policy)](api-AbortVaultLock.md) | glacier:AbortVaultLock | | |
| [Add Tags To Vault (POST tags add)](api-AddTagsToVault.md) | glacier:AddTagsToVault | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Complete Multipart Upload (POST uploadID)](api-multipart-complete-upload.md) | glacier:CompleteMultipartUpload | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Complete Vault Lock (POST lockId)](api-CompleteVaultLock.md) | glacier:CompleteVaultLock | | `glacier:ResourceTag/TagKey` |
| [Create Vault (PUT vault)](api-vault-put.md) \$1 | glacier:CreateVault | | |
| [Delete Archive (DELETE archive)](api-archive-delete.md) | glacier:DeleteArchive | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ArchiveAgeInDays` `glacier:ResourceTag/TagKey` |
| [Delete Vault (DELETE vault)](api-vault-delete.md) | glacier:DeleteVault | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Delete Vault Access Policy (DELETE access-policy)](api-DeleteVaultAccessPolicy.md) | glacier:DeleteVaultAccessPolicy | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Delete Vault Notifications (DELETE notification-configuration)](api-vault-notifications-delete.md) | glacier:DeleteVaultNotifications | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Describe Job (GET JobID)](api-describe-job-get.md) | glacier:DescribeJob | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` |
| [Describe Vault (GET vault)](api-vault-get.md) | glacier:DescribeVault | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [Get Data Retrieval Policy (GET policy)](api-GetDataRetrievalPolicy.md) \$1 | glacier:GetDataRetrievalPolicy | `arn:aws:glacier:region:account-id:policies/retrieval-limit-policy` | |
| [Get Job Output (GET output)](api-job-output-get.md) | glacier:GetJobOutput | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [Get Vault Access Policy (GET access-policy)](api-GetVaultAccessPolicy.md) | glacier:GetVaultAccessPolicy | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [Get Vault Lock (GET lock-policy)](api-GetVaultLock.md) | glacier:GetVaultLock | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [Get Vault Notifications (GET notification-configuration)](api-vault-notifications-get.md) | glacier:GetVaultNotifications | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [Initiate Job (POST jobs)](api-initiate-job-post.md) | glacier:InitiateJob | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ArchiveAgeInDays` `glacier:ResourceTag/TagKey` |
| [Initiate Multipart Upload (POST multipart-uploads)](api-multipart-initiate-upload.md) | glacier:InitiateMultipartUpload | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Initiate Vault Lock (POST lock-policy)](api-InitiateVaultLock.md) | glacier:InitiateVaultLock | | `glacier:ResourceTag/TagKey` |
| [List Jobs (GET jobs)](api-jobs-get.md) | glacier:ListJobs | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [List Multipart Uploads (GET multipart-uploads)](api-multipart-list-uploads.md) | glacier:ListMultipartUploads | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [List Parts (GET uploadID)](api-multipart-list-parts.md) | glacier:ListParts | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [List Tags For Vault (GET tags)](api-ListTagsForVault.md) | glacier:ListTagsForVault | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | |
| [List Vaults (GET vaults)](api-vaults-get.md) | glacier:ListVaults | | |
| [Remove Tags From Vault (POST tags remove)](api-RemoveTagsFromVault.md) | glacier:RemoveTagsFromVault | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Set Data Retrieval Policy (PUT policy)](api-SetDataRetrievalPolicy.md) \$1 | glacier:SetDataRetrievalPolicy | `arn:aws:glacier:region:account-id:policies/retrieval-limit-policy` | |
| [Set Vault Access Policy (PUT access-policy)](api-SetVaultAccessPolicy.md) | glacier:SetVaultAccessPolicy | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Set Vault Notification Configuration (PUT notification-configuration)](api-vault-notifications-put.md) | glacier:SetVaultNotifications | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Upload Archive (POST archive)](api-archive-post.md) | glacier:UploadArchive | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |
| [Upload Part (PUT uploadID)](api-upload-part.md) | glacier:UploadMultipartPart | `arn:aws:glacier:region:account-id:vaults/vault-name` `arn:aws:glacier:region:account-id:vaults/example*` `arn:aws:glacier:region:account-id:vaults/*` | `glacier:ResourceTag/TagKey` |