Amazon WorkMail

(1)

Amazon WorkMail

Administrator Guide

Version 1.0

(2)

Amazon WorkMail: Administrator Guide

Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be aﬃliated with, connected to, or sponsored by Amazon.

(3)

What is Amazon WorkMail?

Amazon WorkMail is a secure, managed business email and calendaring service with support for existing desktop and mobile email clients. Amazon WorkMail users can access their email, contacts, and calendars using Microsoft Outlook, their browser, or their native iOS and Android email applications. You can integrate Amazon WorkMail with your existing corporate directory and control both the keys that encrypt your data and the location in which your data is stored.

For a list of supported AWS Regions and endpoints, see AWS Regions and Endpoints.

Topics

• Amazon WorkMail system requirements (p. 1)

• Amazon WorkMail concepts (p. 1)

• Related AWS services (p. 2)

• Amazon WorkMail pricing (p. 3)

• Amazon WorkMail resources (p. 3)

Amazon WorkMail system requirements

Amazon WorkMail works with all major mobile devices and operating systems that support the Exchange ActiveSync protocol. These devices include the iPad, iPhone, Android, and Windows Phone. Users of macOS can add their Amazon WorkMail account to their Mail, Calendar, and Contacts apps.

If you have a valid Microsoft Outlook license, you can access Amazon WorkMail using the following versions of Microsoft Outlook:

• Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019

• Outlook 2010 and Outlook 2013 Click-to-Run

• Outlook for Mac 2011, Outlook 2016 for Mac, and Outlook 2019 for Mac

The Amazon WorkMail web application is accessed at https://alias.awsapps.com/mail. Amazon WorkMail can also be used with IMAP clients. For more information, see Setting up email clients for Amazon WorkMail in the Amazon WorkMail User Guide.

Amazon WorkMail concepts

The terminology and concepts that are central to your understanding and use of Amazon WorkMail are described below.

Organization

A tenant setup for Amazon WorkMail.

Alias

A globally unique name to identify your organization. The alias is used to access the Amazon WorkMail web application (https://alias.awsapps.com/mail).

(7)

Domain

The web address that comes after the @ symbol in an email address. You can add a domain that receives mail and delivers it to mailboxes in your organization.

Test mail domain

A domain is automatically conﬁgured during setup that can be used for testing Amazon WorkMail.

The test mail domain is alias.awsapps.com and is used as the default domain if you do not conﬁgure your own domain. The test mail domain is subject to diﬀerent limits. For more information, see Amazon WorkMail quotas (p. 49).

Directory

An AWS Simple AD, AWS Managed AD, or AD Connector created in AWS Directory Service. If you create an organization using the Amazon WorkMail Quick setup, we create a WorkMail directory for you. You cannot view a WorkMail directory in AWS Directory Service.

User

A user created in the AWS Directory Service. When a user is enabled for Amazon WorkMail, they receive their own mailbox to access. When a user is disabled, they cannot access Amazon WorkMail.

Group

A group used in AWS Directory Service. A group can be used as a distribution list or a security group in Amazon WorkMail. Groups do not have their own mailboxes.

Resource

A resource represents a meeting room or equipment resource that can be booked by Amazon WorkMail users.

Mobile device policy

Various IT policy rules that control the security features and behavior of a mobile device.

Related AWS services

The following services are used along with Amazon WorkMail:

• AWS Directory Service—You can integrate Amazon WorkMail with an existing AWS Simple AD, AWS Managed AD, or AD Connector. Create a directory in the AWS Directory Service and then enable Amazon WorkMail for this directory. After you've conﬁgured this integration, you can choose which users you would like to enable for Amazon WorkMail from a list of users in your existing directory, and users can log in using their existing Active Directory credentials. For more information, see AWS Directory Service Administration Guide.

• Amazon Simple Email Service—Amazon WorkMail uses Amazon SES to send all outgoing email. The test mail domain and your domains are available for management in the Amazon SES console. There is no cost for outgoing email sent from Amazon WorkMail. For more information, see Amazon Simple Email Service Developer Guide.

• AWS Identity and Access Management—The AWS Management Console requires your user name and password so that any service you use can determine whether you have permission to access its resources. We recommend that you avoid using AWS account credentials to access AWS because AWS account credentials cannot be revoked or limited in any way. Instead, we recommend that you create an IAM user and add the user to an IAM group with administrative permissions. You can then access the console using the IAM user credentials.

If you signed up for AWS but have not created an IAM user for yourself, you can create one using the IAM console. For more information, see Create individual IAM users in the IAM User Guide.

(8)

• AWS Key Management Service—Amazon WorkMail is integrated with AWS KMS for encryption of customer data. Key management can be performed from the AWS KMS console. For more information, see What is the AWS Key Management Service in the AWS Key Management Service Developer Guide.

Amazon WorkMail pricing

With Amazon WorkMail, there are no upfront fees or commitments. You pay only for active user accounts. For more speciﬁc information about pricing, see Pricing.

Amazon WorkMail resources

The following related resources can help you as you work with this service.

• Classes & Workshops – Links to role-based and specialty courses, in addition to self-paced labs to help sharpen your AWS skills and gain practical experience.

• AWS Developer Tools – Links to developer tools, SDKs, IDE toolkits, and command line tools for developing and managing AWS applications.

• AWS Whitepapers – Links to a comprehensive list of technical AWS whitepapers, covering topics such as architecture, security, and economics and authored by AWS Solutions Architects or other technical experts.

• AWS Support Center – The hub for creating and managing your AWS Support cases. Also includes links to other helpful resources, such as forums, technical FAQs, service health status, and AWS Trusted Advisor.

• AWS Support – The primary webpage for information about AWS Support, a one-on-one, fast- response support channel to help you build and run applications in the cloud.

• Contact Us – A central contact point for inquiries concerning AWS billing, account, events, abuse, and other issues.

• AWS Site Terms – Detailed information about our copyright and trademark; your account, license, and site access; and other topics.

(9)

Prerequisites

To use Amazon WorkMail you'll need an AWS account. If you haven't signed up for AWS yet, complete the following tasks to get set up.

Topics

• Get an AWS account and your root user credentials (p. 4)

• Create AWS Identity and Access Management users and groups (p. 4)

Get an AWS account and your root user credentials

To access AWS, you must sign up for an AWS account.

To sign up for an AWS account

1. Open https://portal.aws.amazon.com/billing/signup.

2. Follow the online instructions.

Part of the sign-up procedure involves receiving a phone call and entering a veriﬁcation code on the phone keypad.

AWS sends you a conﬁrmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to https://aws.amazon.com/ and choosing My Account.

Create AWS Identity and Access Management users and groups

The AWS Management Console requires your username and password so that the service can determine whether you have permission to access its resources. We recommend that you avoid using root account credentials to access AWS because root account credentials cannot be revoked or limited in any way.

Instead, use AWS Identity and Access Management (IAM) to create an IAM user and add the user to an IAM group with administrative permissions. You can then access the console using the credentials for the IAM user.

If you signed up for AWS but have not created an IAM user for yourself, you can create one using the IAM console. For more information, see Create Individual IAM Users in IAM User Guide.

Grant IAM users permissions for Amazon WorkMail

By default, IAM users don't have permissions to manage Amazon WorkMail resources; you must attach an AWS managed policy (AmazonWorkMailFullAccess or AmazonWorkMailReadOnlyAccess) or create a customer managed policy that explicitly grants IAM users those permissions, and attach the policy to the speciﬁc IAM users or groups that require those permissions. For more information, see Identity and access management for Amazon WorkMail (p. 12).

(10)

Security in Amazon WorkMail

Cloud security at AWS is the highest priority. As an AWS customer, you beneﬁt from a data center and network architecture that is built to meet the requirements of the most security-sensitive organizations.

Security is a shared responsibility between AWS and you. The shared responsibility model describes this as security of the cloud and security in the cloud:

• Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. Third-party auditors regularly test and verify the eﬀectiveness of our security as part of the AWS compliance programs. To learn about the compliance programs that apply to Amazon WorkMail, see AWS Services in Scope by Compliance Program.

• Security in the cloud – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your company’s requirements, and applicable laws and regulations.

This documentation helps you understand how to apply the shared responsibility model when using Amazon WorkMail. The following topics show you how to conﬁgure Amazon WorkMail to meet your security and compliance objectives. You also learn how to use other AWS services that help you to monitor and secure your Amazon WorkMail resources.

Topics

• Data protection in Amazon WorkMail (p. 5)

• Identity and access management for Amazon WorkMail (p. 12)

• Using service-linked roles for Amazon WorkMail (p. 25)

• Logging and monitoring in Amazon WorkMail (p. 27)

• Compliance validation for Amazon WorkMail (p. 38)

• Resilience in Amazon WorkMail (p. 38)

• Infrastructure security in Amazon WorkMail (p. 38)

Data protection in Amazon WorkMail

The AWS shared responsibility model applies to data protection in Amazon WorkMail. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud.

You are responsible for maintaining control over your content that is hosted on this infrastructure. This content includes the security conﬁguration and management tasks for the AWS services that you use. For more information about data privacy, see the Data Privacy FAQ. For information about data protection in Europe, see the AWS Shared Responsibility Model and GDPR blog post on the AWS Security Blog.

For data protection purposes, we recommend that you protect AWS account credentials and set up individual user accounts with AWS Identity and Access Management (IAM). That way each user is given only the permissions necessary to fulﬁll their job duties. We also recommend that you secure your data in the following ways:

• Use multi-factor authentication (MFA) with each account.

(11)

• Use SSL/TLS to communicate with AWS resources. We recommend TLS 1.2 or later.

• Set up API and user activity logging with AWS CloudTrail.

• Use AWS encryption solutions, along with all default security controls within AWS services.

• Use advanced managed security services such as Amazon Macie, which assists in discovering and securing personal data that is stored in Amazon S3.

• If you require FIPS 140-2 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see Federal Information Processing Standard (FIPS) 140-2.

We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form fields such as a Name field. This includes when you work with Amazon WorkMail or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server.

How Amazon WorkMail uses AWS KMS

Amazon WorkMail transparently encrypts all messages in the mailboxes of all Amazon WorkMail organizations before the messages are written to disk and transparently decrypts the messages when users access them. There is no option to disable encryption. To protect the encryption keys that protect the messages, Amazon WorkMail is integrated with AWS Key Management Service (AWS KMS).

Amazon WorkMail also provides an option for enabling users to send signed or encrypted email. This encryption feature does not use AWS KMS. For more information, see Enabling signed or encrypted email (p. 99).

Topics

• Amazon WorkMail encryption (p. 6)

• Authorizing use of the CMK (p. 9)

• Amazon WorkMail encryption context (p. 10)

• Monitoring Amazon WorkMail interaction with AWS KMS (p. 11)

Amazon WorkMail encryption

In Amazon WorkMail, each organization can contain multiple mailboxes, one for each user in the organization. All messages, including email and calendar items, are stored in the user's mailbox.

To protect the contents of the mailboxes in your Amazon WorkMail organizations, Amazon WorkMail encrypts all mailbox messages before they are written to disk. No customer-provided information is stored in plaintext.

Each message is encrypted under a unique data encryption key. The message key is protected by a mailbox key, which is a unique encryption key that is used only for that mailbox. The mailbox key is encrypted under an AWS KMS customer master key (CMK) for the organization that never leaves AWS KMS unencrypted. The following diagram shows the relationship of the encrypted messages, encrypted message keys, encrypted mailbox key, and the CMK for the organization in AWS KMS.

(12)

A CMK for the organization

When you create an Amazon WorkMail organization, you have the option to select an AWS KMS

customer master key (CMK) for the organization. This CMK protects all mailbox keys in that organization.

You can either select the default AWS managed CMK for Amazon WorkMail, or select an existing customer managed CMK that you own and manage. For more information, see customer master keys (CMKs) in the AWS Key Management Service Developer Guide. You can select the same CMK or a diﬀerent CMK for each of your organizations, but you cannot change the CMK once you have selected it.

Important

Amazon WorkMail supports only symmetric CMKs. You cannot use an asymmetric CMK to encrypt data in Amazon WorkMail. For help determining whether a CMK is symmetric or asymmetric, see Identifying symmetric and asymmetric CMKs in the AWS Key Management Service Developer Guide.

To ﬁnd the CMK for your organization, use the AWS CloudTrail log entry that records calls to AWS KMS.

A unique encryption key for each mailbox

When you create a new mailbox, Amazon WorkMail generates a unique 256-bit Advanced Encryption Standard (AES) symmetric encryption key for the mailbox, known as its mailbox key, outside of AWS KMS.

Amazon WorkMail uses the mailbox key to protect the encryption keys for each message in the mailbox.

(13)

To protect the mailbox key, Amazon WorkMail calls AWS KMS to encrypt the mailbox key under the CMK for the organization. Then it stores the encrypted mailbox key in the mailbox metadata.

Note

Amazon WorkMail uses a symmetric mailbox encryption key to protect message keys. Previously, Amazon WorkMail protected each mailbox with an asymmetric key pair. It used the public key to encrypt each message key and the private key to decrypt it. The private mailbox key was protected by the CMK for the organization. Existing mailboxes might still use an asymmetric mailbox key pair. This change does not aﬀect the security of the mailbox or its messages.

A unique encryption key for each message

When a message is added to the mailbox, Amazon WorkMail generates a unique 256-bit AES symmetric encryption key for the message outside of AWS KMS. It uses this message key to encrypt the message.

Amazon WorkMail encrypts the message key under the mailbox key and stores the encrypted message key with the message. Then, it encrypts the mailbox key under the CMK for the organization.

Creating a new mailbox

When Amazon WorkMail creates a new mailbox, it uses the following process to prepare the mailbox to hold encrypted messages.

• Amazon WorkMail generates a unique 256-bit AES symmetric encryption key for the mailbox outside of AWS KMS.

• Amazon WorkMail calls the AWS KMS Encrypt operation. It passes in the mailbox key and the identiﬁer of the customer master key (CMK) for the organization. AWS KMS returns a ciphertext of the mailbox key encrypted under the CMK.

• Amazon WorkMail stores the encrypted mailbox key with the mailbox metadata.

Encrypting a mailbox message

To encrypt a message, Amazon WorkMail uses the following process.

1. Amazon WorkMail generates a unique 256-bit AES symmetric key for the message. It uses the

plaintext message key and the Advanced Encryption Standard (AES) algorithm to encrypt the message outside of AWS KMS.

2. To protect the message key under the mailbox key, Amazon WorkMail needs to decrypt the mailbox key, which is always stored in its encrypted form.

Amazon WorkMail calls the AWS KMS Decrypt operation and passes in the encrypted mailbox key.

AWS KMS uses the CMK for the organization to decrypt the mailbox key and it returns the plaintext mailbox key to Amazon WorkMail.

3. Amazon WorkMail uses the plaintext mailbox key and the Advanced Encryption Standard (AES) algorithm to encrypt the message key outside of AWS KMS.

4. Amazon WorkMail stores the encrypted message key in the metadata of the encrypted message so it is available to decrypt it.

Decrypting a mailbox message

To decrypt a message, Amazon WorkMail uses the following process.

1. Amazon WorkMail calls the AWS KMS Decrypt operation and passes in the encrypted mailbox key.

AWS KMS uses the CMK for the organization to decrypt the mailbox key and it returns the plaintext mailbox key to Amazon WorkMail.

2. Amazon WorkMail uses the plaintext mailbox key and the Advanced Encryption Standard (AES) algorithm to decrypt the encrypted message key outside of AWS KMS.

(14)

3. Amazon WorkMail uses the plaintext message key to decrypt the encrypted message.

Caching mailbox keys

To improve performance and minimize calls to AWS KMS, Amazon WorkMail caches each plaintext mailbox key for each client locally for up to one minute. At the end of the caching period, the mailbox key is removed. If the mailbox key for that client is required during the caching period, Amazon WorkMail can get it from the cache instead of calling AWS KMS. The mailbox key is protected in the cache and is never written to disk in plaintext.

Authorizing use of the CMK

When Amazon WorkMail uses a customer master key (CMK) in cryptographic operations, it acts on behalf of the mailbox administrator.

To use the AWS KMS customer master key (CMK) for a secret on your behalf, the administrator must have the following permissions. You can specify these required permissions in an IAM policy or key policy.

• kms:Encrypt

• kms:Decrypt

• kms:CreateGrant

To allow the CMK to be used only for requests that originate in Amazon WorkMail, you can use the kms:ViaService condition key with the workmail.<region>.amazonaws.com value.

You can also use the keys or values in the encryption context (p. 10) as a condition for using the CMK for cryptographic operations. For example, you can use a string condition operator in an IAM or key policy document or use a grant constraint in a grant.

Key policy for the AWS managed CMK

The key policy for the AWS managed CMK for Amazon WorkMail gives users permission to use the CMK for speciﬁed operations only when Amazon WorkMail makes the request on the user's behalf. The key policy does not allow any user to use the CMK directly.

This key policy, like the policies of all AWS managed keys, is established by the service. You cannot change the key policy, but you can view it at any time. For details, see Viewing a key policy in the AWS Key Management Service Developer Guide.

The policy statements in the key policy have the following eﬀect:

• Allow users in the account and Region to use the CMK for cryptographic operations and to create grants, but only when the request comes from Amazon WorkMail on their behalf. The kms:ViaService condition key enforces this restriction.

• Allows the AWS account to create IAM policies that allow users to view CMK properties and revoke grants.

The following is a key policy for an example AWS managed CMK for Amazon WorkMail.

{

"Version" : "2012-10-17", "Id" : "auto-workmail-1", "Statement" : [ {

"Sid" : "Allow access through WorkMail for all principals in the account that are authorized to use WorkMail",

(15)

"Effect" : "Allow", "Principal" : { "AWS" : "*"

},

"Action" : [ "kms:Decrypt", "kms:CreateGrant", "kms:ReEncrypt*", "kms:DescribeKey", "kms:Encrypt" ],

"Resource" : "*", "Condition" : { "StringEquals" : {

"kms:ViaService" : "workmail.us-east-1.amazonaws.com", "kms:CallerAccount" : "111122223333"

} } }, {

"Sid" : "Allow direct access to key metadata to the account", "Effect" : "Allow",

"Principal" : {

"AWS" : "arn:aws:iam::111122223333:root"

},

"Action" : [ "kms:Describe*", "kms:List*", "kms:Get*", "kms:RevokeGrant" ], "Resource" : "*"

} ] }

Using grants to authorize Amazon WorkMail

In addition to key policies, Amazon WorkMail uses grants to add permissions to the CMK for each organization. To view the grants on the CMK in your account, use the ListGrants operation.

Amazon WorkMail uses grants to add the following permissions to the CMK for the organization.

• Add the kms:Encrypt permission to allow Amazon WorkMail to encrypt the mailbox key.

• Add the kms:Decrypt permission to allow Amazon WorkMail to use the CMK to decrypt the mailbox key. Amazon WorkMail requires this permission in a grant because the request to read mailbox messages uses the security context of the user who is reading the message. The request does not use the credentials of the AWS account. Amazon WorkMail creates this grant when you select a CMK for the organization.

To create the grants, Amazon WorkMail calls CreateGrant on behalf of the user who created the

organization. Permission to create the grant comes from the key policy. This policy allows account users to call CreateGrant on the CMK for the organization when Amazon WorkMail makes the request on an authorized user's behalf.

The key policy also allows the account root to revoke the grant on the AWS managed key. However, if you revoke the grant, Amazon WorkMail cannot decrypt the encrypted data in your mailboxes.

Amazon WorkMail encryption context

An encryption context is a set of key-value pairs that contain arbitrary nonsecret data. When you include an encryption context in a request to encrypt data, AWS KMS cryptographically binds the encryption context to the encrypted data. To decrypt the data, you must pass in the same encryption context. For more information, see Encryption context in the AWS Key Management Service Developer Guide.

Amazon WorkMail uses the same encryption context format in all AWS KMS cryptographic operations.

You can use the encryption context to identify a cryptographic operation in audit records and logs, such as AWS CloudTrail, and as a condition for authorization in policies and grants.

In its Encrypt and Decrypt requests to AWS KMS, Amazon WorkMail uses an encryption context where the key is aws:workmail:arn and the value is the Amazon Resource Name (ARN) of the organization.

(16)

"aws:workmail:arn":"arn:aws:workmail:region:account ID:organization/organization-ID"

For example, the following encryption context includes an example organization ARN in the Europe (Ireland) (eu-west-1) Region.

"aws:workmail:arn":"arn:aws:workmail:eu-west-1:111122223333:organization/m- a123b4c5de678fg9h0ij1k2lm234no56"

Monitoring Amazon WorkMail interaction with AWS KMS

You can use AWS CloudTrail and Amazon CloudWatch Logs to track the requests that Amazon WorkMail sends to AWS KMS on your behalf.

Encrypt

When you create a new mailbox, Amazon WorkMail generates a mailbox key and calls AWS KMS to encrypt the mailbox key. Amazon WorkMail sends an Encrypt request to AWS KMS with the plaintext mailbox key and an identiﬁer for the CMK of the Amazon WorkMail organization.

The event that records the Encrypt operation is similar to the following example event. The user is the Amazon WorkMail service. The parameters include the CMK ID (keyId) and the encryption context for the Amazon WorkMail organization. Amazon WorkMail also passes in the mailbox key, but that is not recorded in the CloudTrail log.

{

"eventVersion": "1.05", "userIdentity": {

"type": "AWSService",

"invokedBy": "workmail.eu-west-1.amazonaws.com"

},

"eventTime": "2019-02-19T10:01:09Z", "eventSource": "kms.amazonaws.com", "eventName": "Encrypt",

"awsRegion": "eu-west-1",

"sourceIPAddress": "workmail.eu-west-1.amazonaws.com", "userAgent": "workmail.eu-west-1.amazonaws.com", "requestParameters": {

"encryptionContext": {

"aws:workmail:arn": "arn:aws:workmail:eu-west-1:111122223333:organization/m- a123b4c5de678fg9h0ij1k2lm234no56"

},

"keyId": "arn:aws:kms:eu-

west-1:111122223333:key/1a2b3c4d-5e6f-1a2b-3c4d-5e6f1a2b3c4d"

},

"responseElements": null,

"requestID": "76e96b96-7e24-4faf-a2d6-08ded2eaf63c", "eventID": "d5a59c18-128a-4082-aa5b-729f7734626a", "readOnly": true,

"resources": [ {

"ARN": "arn:aws:kms:eu-

west-1:111122223333:key/1a2b3c4d-5e6f-1a2b-3c4d-5e6f1a2b3c4d", "accountId": "111122223333",

"type": "AWS::KMS::Key"

} ],

"eventType": "AwsApiCall",

"recipientAccountId": "111122223333",

"sharedEventID": "d08e60f1-097e-4a00-b7e9-10bc3872d50c"

}

(17)

Decrypt

When you add, view, or delete a mailbox message, Amazon WorkMail asks AWS KMS to decrypt the mailbox key. Amazon WorkMail sends a Decrypt request to AWS KMS with the encrypted mailbox key and an identiﬁer for the CMK of the Amazon WorkMail organization.

The event that records the Decrypt operation is similar to the following example event. The user is the Amazon WorkMail service. The parameters include the encrypted mailbox key (as a ciphertext blob), which is not recorded in the log, and the encryption context for the Amazon WorkMail organization. AWS KMS derives the ID of the CMK from the ciphertext.

{ "eventVersion": "1.05", "userIdentity": {

"type": "AWSService",

"invokedBy": "workmail.eu-west-1.amazonaws.com"

},

"eventTime": "2019-02-20T11:51:10Z", "eventSource": "kms.amazonaws.com", "eventName": "Decrypt",

"awsRegion": "eu-west-1",

"sourceIPAddress": "workmail.eu-west-1.amazonaws.com", "userAgent": "workmail.eu-west-1.amazonaws.com", "requestParameters": {

"encryptionContext": {

"aws:workmail:arn": "arn:aws:workmail:eu-west-1:111122223333:organization/m- a123b4c5de678fg9h0ij1k2lm234no56"

} },

"responseElements": null,

"requestID": "4a32dda1-34d9-4100-9718-674b8e0782c9", "eventID": "ea9fd966-98e9-4b7b-b377-6e5a397a71de", "readOnly": true,

"resources": [ {

"ARN": "arn:aws:kms:eu-

west-1:111122223333:key/1a2b3c4d-5e6f-1a2b-3c4d-5e6f1a2b3c4d", "accountId": "111122223333",

"type": "AWS::KMS::Key"

} ],

"eventType": "AwsApiCall",

"recipientAccountId": "111122223333",

"sharedEventID": "241e1e5b-ff64-427a-a5b3-7949164d0214"

}

Identity and access management for Amazon WorkMail

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 WorkMail resources. IAM is an AWS service that you can use with no additional charge.

Topics

• Audience (p. 13)

• Authenticating With identities (p. 13)

(18)

• Managing access using policies (p. 15)

• How Amazon WorkMail works with IAM (p. 16)

• Amazon WorkMail identity-based policy examples (p. 20)

• Troubleshooting Amazon WorkMail identity and access (p. 23)

Audience

How you use AWS Identity and Access Management (IAM) diﬀers, depending on the work that you do in Amazon WorkMail.

Service user – If you use the Amazon WorkMail service to do your job, then your administrator provides you with the credentials and permissions that you need. As you use more Amazon WorkMail features to do your work, you might need additional permissions. Understanding how access is managed can help you request the right permissions from your administrator. If you cannot access a feature in Amazon WorkMail, see Troubleshooting Amazon WorkMail identity and access (p. 23).

Service administrator – If you're in charge of Amazon WorkMail resources at your company, you probably have full access to Amazon WorkMail. It's your job to determine which Amazon WorkMail features and resources your employees should access. You must then submit requests to your IAM administrator to change the permissions of your service users. Review the information on this page to understand the basic concepts of IAM. To learn more about how your company can use IAM with Amazon WorkMail, see How Amazon WorkMail works with IAM (p. 16).

IAM administrator – If you're an IAM administrator, you might want to learn details about how you can write policies to manage access to Amazon WorkMail. To view example Amazon WorkMail identity-based policies that you can use in IAM, see Amazon WorkMail identity-based policy examples (p. 20).

Authenticating With identities

Authentication is how you sign in to AWS using your identity credentials. For more information about signing in using the AWS Management Console, see Signing in to the AWS Management Console as an IAM user or root user in the IAM User Guide.

You must be authenticated (signed in to AWS) as the AWS account root user, an IAM user, or by assuming an IAM role. You can also use your company's single sign-on authentication or even sign in using Google or Facebook. In these cases, your administrator previously set up identity federation using IAM roles.

When you access AWS using credentials from another company, you are assuming a role indirectly.

To sign in directly to the AWS Management Console, use your password with your root user email address or your IAM user name. You can access AWS programmatically using your root user or IAM users access keys. AWS provides SDK and command line tools to cryptographically sign your request using your credentials. If you don't use AWS tools, you must sign the request yourself. Do this using Signature Version 4, a protocol for authenticating inbound API requests. For more information about authenticating requests, see Signature Version 4 signing process in the AWS General Reference.

Regardless of the authentication method that you use, you might also be required to provide additional security information. For example, AWS recommends that you use multi-factor authentication (MFA) to increase the security of your account. To learn more, see Using multi-factor authentication (MFA) in AWS in the IAM User Guide.

AWS account root user

When you ﬁrst create an AWS account, you begin with a single sign-in identity that has complete access to all AWS services and resources in the account. This identity is called the AWS account root user and is accessed by signing in with the email address and password that you used to create the account. We strongly recommend that you do not use the root user for your everyday tasks, even the administrative

(19)

ones. Instead, adhere to the best practice of using the root user only to create your ﬁrst IAM user. Then securely lock away the root user credentials and use them to perform only a few account and service management tasks.

IAM users and groups

An IAM user is an identity within your AWS account that has speciﬁc permissions for a single person or application. An IAM user can have long-term credentials such as a user name and password or a set of access keys. To learn how to generate access keys, see Managing access keys for IAM users in the IAM User Guide. When you generate access keys for an IAM user, make sure you view and securely save the key pair. You cannot recover the secret access key in the future. Instead, you must generate a new access key pair.

An IAM group is an identity that speciﬁes a collection of IAM users. You can't sign in as a group. You can use groups to specify permissions for multiple users at a time. Groups make permissions easier to manage for large sets of users. For example, you could have a group named IAMAdmins and give that group permissions to administer IAM resources.

Users are diﬀerent from roles. A user is uniquely associated with one person or application, but a role is intended to be assumable by anyone who needs it. Users have permanent long-term credentials, but roles provide temporary credentials. To learn more, see When to create an IAM user (instead of a role) in the IAM User Guide.

IAM roles

An IAM role is an identity within your AWS account that has speciﬁc permissions. It is similar to an IAM user, but is not associated with a speciﬁc person. You can temporarily assume an IAM role in the AWS Management Console by switching roles. You can assume a role by calling an AWS CLI or AWS API operation or by using a custom URL. For more information about methods for using roles, see Using IAM roles in the IAM User Guide.

IAM roles with temporary credentials are useful in the following situations:

• Temporary IAM user permissions – An IAM user can assume an IAM role to temporarily take on diﬀerent permissions for a speciﬁc task.

• Federated user access – Instead of creating an IAM user, you can use existing identities from AWS Directory Service, your enterprise user directory, or a web identity provider. These are known as federated users. AWS assigns a role to a federated user when access is requested through an identity provider. For more information about federated users, see Federated users and roles in the IAM User Guide.

• Cross-account access – You can use an IAM role to allow someone (a trusted principal) in a diﬀerent account to access resources in your account. Roles are the primary way to grant cross-account access.

However, with some AWS services, you can attach a policy directly to a resource (instead of using a role as a proxy). To learn the diﬀerence between roles and resource-based policies for cross-account access, see How IAM roles diﬀer from resource-based policies in the IAM User Guide.

• Cross-service access – Some AWS services use features in other AWS services. For example, when you make a call in a service, it's common for that service to run applications in Amazon EC2 or store objects in Amazon S3. A service might do this using the calling principal's permissions, using a service role, or using a service-linked role.

• Principal permissions – When you use an IAM user or role to perform actions in AWS, you are considered a principal. Policies grant permissions to a principal. When you use some services, you might perform an action that then triggers another action in a diﬀerent service. In this case, you must have permissions to perform both actions. To see whether an action requires additional dependent actions in a policy, see in the Service Authorization Reference.

• Service role – A service role is an IAM role 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 Creating a role to delegate permissions to an AWS service in the IAM User Guide.

(20)

• Service-linked role – 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 IAM account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles.

• Applications running on Amazon EC2 – You can use an IAM role to manage temporary credentials for applications that are running on an EC2 instance and making AWS CLI or AWS API requests.

This is preferable to storing access keys within the EC2 instance. To assign an AWS role to an EC2 instance and make it available to all of its applications, you create an instance proﬁle that is attached to the instance. An instance proﬁle contains the role and enables programs that are running on the EC2 instance to get temporary credentials. For more information, see Using an IAM role to grant permissions to applications running on Amazon EC2 instances in the IAM User Guide.

To learn whether to use IAM roles or IAM users, see When to create an IAM role (instead of a user) in the IAM User Guide.

Managing access using policies

You control access in AWS by creating policies and attaching them to IAM identities or AWS resources. A policy is an object in AWS that, when associated with an identity or resource, deﬁnes their permissions.

You can sign in as the root user or an IAM user, or you can assume an IAM role. When you then make a request, AWS evaluates the related identity-based or resource-based policies. Permissions in the policies determine whether the request is allowed or denied. Most policies are stored in AWS as JSON documents. For more information about the structure and contents of JSON policy documents, see Overview of JSON policies in the IAM User Guide.

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.

Every IAM entity (user or role) starts with no permissions. In other words, by default, users can do nothing, not even change their own password. To give a user permission to do something, an administrator must attach a permissions policy to a user. Or the administrator can add the user to a group that has the intended permissions. When an administrator gives permissions to a group, all users in that group are granted those permissions.

IAM policies deﬁne permissions for an action regardless of the method that you use to perform the operation. For example, suppose that you have a policy that allows the iam:GetRole action. A user with that policy can get role information from the AWS Management Console, the AWS CLI, or the AWS API.

Identity-based policies

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 Creating IAM policies in the IAM User Guide.

Identity-based policies can be further categorized as inline policies or managed policies. Inline policies are embedded directly into a single user, group, or role. Managed policies are standalone policies that you can attach to multiple users, groups, and roles in your AWS account. Managed policies include AWS managed policies and customer managed policies. To learn how to choose between a managed policy or an inline policy, see Choosing between managed policies and inline policies in the IAM User Guide.

Resource-based policies

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

(21)

on that resource and under what conditions. You must specify a principal in a resource-based policy.

Principals can include accounts, users, roles, federated users, or AWS services.

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.

Access Control Lists (ACLs)

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.

Amazon S3, AWS WAF, and Amazon VPC are examples of services that support ACLs. To learn more about ACLs, see Access control list (ACL) overview in the Amazon Simple Storage Service Developer Guide.

Other policy types

AWS supports additional, less-common policy types. These policy types can set the maximum permissions granted to you by the more common policy types.

• Permissions boundaries – A permissions boundary is an advanced feature in which you set the maximum permissions that an identity-based policy can grant to an IAM entity (IAM user or role).

You can set a permissions boundary for an entity. The resulting permissions are the intersection of entity's identity-based policies and its permissions boundaries. Resource-based policies that specify the user or role in the Principal ﬁeld are not limited by the permissions boundary. An explicit deny in any of these policies overrides the allow. For more information about permissions boundaries, see Permissions boundaries for IAM entities in the IAM User Guide.

• Service control policies (SCPs) – SCPs are JSON policies that specify the maximum permissions for an organization or organizational unit (OU) in AWS Organizations. AWS Organizations is a service for grouping and centrally managing multiple AWS accounts that your business owns. If you enable all features in an organization, then you can apply service control policies (SCPs) to any or all of your accounts. The SCP limits permissions for entities in member accounts, including each AWS account root user. For more information about Organizations and SCPs, see How SCPs work in the AWS Organizations User Guide.

• Session policies – Session policies are advanced policies that you pass as a parameter when you programmatically create a temporary session for a role or federated user. The resulting session's permissions are the intersection of the user or role's identity-based policies and the session policies.

Permissions can also come from a resource-based policy. An explicit deny in any of these policies overrides the allow. For more information, see Session policies 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 in the IAM User Guide.

How Amazon WorkMail works with IAM

Before you use IAM to manage access to Amazon WorkMail, you should understand what IAM features are available to use with Amazon WorkMail. To get a high-level view of how Amazon WorkMail and other AWS services work with IAM, see AWS services that work with IAM in the IAM User Guide.

Topics

• Amazon WorkMail identity-based policies (p. 17)

• Amazon WorkMail resource-based policies (p. 19)

(22)

• Authorization based on Amazon WorkMail tags (p. 19)

• Amazon WorkMail IAM roles (p. 19)

Amazon WorkMail identity-based policies

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. Amazon WorkMail supports speciﬁc actions, resources, and condition keys. To learn about all of the elements that you use in a JSON policy, see IAM JSON Policy Elements Reference in the IAM User Guide.

Actions

The Action element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Policy actions usually have the same name as the associated AWS API operation. There are some exceptions, such as permission-only actions that don't have a matching API operation. There are also some operations that require multiple actions in a policy. These additional actions are called dependent actions.

Include actions in a policy to grant permissions to perform the associated operation.

Policy actions in Amazon WorkMail use the following preﬁx before the action: workmail:. For example, to grant someone permission to retrieve a list of users with the Amazon WorkMail ListUsers API operation, you include the workmail:ListUsers action in their policy. Policy statements must include either an Action or NotAction element. Amazon WorkMail deﬁnes its own set of actions that describe tasks that you can perform with this service.

To specify multiple actions in a single statement, separate them with commas as follows:

"Action": [

"workmail:ListUsers", "workmail:DeleteUser"

You can specify multiple actions using wildcards (*). For example, to specify all actions that begin with the word List, include the following action:

"Action": "workmail:List*"

To see a list of Amazon WorkMail actions, see Actions deﬁned by Amazon WorkMail in the IAM User Guide.

Resources

The Resource JSON policy element speciﬁes the object or objects to which the action applies.

Statements must include either a Resource or a NotResource element. As a best practice, specify a resource using its Amazon Resource Name (ARN). You can do this for actions that support a speciﬁc resource type, known as resource-level permissions.

For actions that don't support resource-level permissions, such as listing operations, use a wildcard (*) to indicate that the statement applies to all resources.

"Resource": "*"

(23)

Amazon WorkMail supports resource-level permissions for Amazon WorkMail organizations.

The Amazon WorkMail organization resource has the following ARN:

arn:aws:workmail:${Region}:${Account}:organization/${OrganizationId}

For more information about the format of ARNs, see Amazon Resource Names (ARNs) and AWS service namespaces.

For example, to specify the m-n1pq2345678r901st2u3vx45x6789yza organization in your statement, use the following ARN.

"Resource": "arn:aws:workmail:us-east-1:111122223333:organization/m- n1pq2345678r901st2u3vx45x6789yza"

To specify all organizations that belong to a speciﬁc account, use the wildcard (*):

"Resource": "arn:aws:workmail:us-east-1:111122223333:organization/*"

Some Amazon WorkMail actions, such as those for creating resources, cannot be performed on a speciﬁc resource. In those cases, you must use the wildcard (*).

"Resource": "*"

To see a list of Amazon WorkMail resource types and their ARNs, see Resources deﬁned by Amazon WorkMail in the IAM User Guide. To learn with which actions you can specify for the ARN of each resource, see Actions, resources, and condition keys for Amazon WorkMail.

Condition keys

Amazon WorkMail does not provide any service-speciﬁc condition keys, but it does support using the following global condition keys.

• aws:CurrentTime

• aws:EpochTime

• aws:MultiFactorAuthAge

• aws:MultiFactorAuthPresent

• aws:PrincipalOrgID

• aws:PrincipalArn

• aws:RequestedRegion

• aws:SecureTransport

• aws:UserAgent

The following example policy grants access to the Amazon WorkMail console only from MFA authenticated IAM principals in the eu-west-1 AWS Region.

{ "Version": "2012-10-17", "Statement": [

{

"Effect": "Allow", "Action": [

"ses:Describe*", "ses:Get*",

"workmail:Describe*",

(24)

"workmail:Get*", "workmail:List*", "workmail:Search*", "lambda:ListFunctions", "iam:ListRoles",

"logs:DescribeLogGroups", "cloudwatch:GetMetricData"

],

"Resource": "*", "Condition": { "StringEquals": {

"aws:RequestedRegion": [ "eu-west-1"

] },

"Bool": {

"aws:MultiFactorAuthPresent": true }

} } ] }

To see all AWS global condition keys, see AWS global condition context keys in the IAM User Guide.

Examples

To view examples of Amazon WorkMail identity-based policies, see Amazon WorkMail identity-based policy examples (p. 20).

Amazon WorkMail resource-based policies

Amazon WorkMail does not support resource-based policies.

Authorization based on Amazon WorkMail tags

You can attach tags to Amazon WorkMail resources or pass tags in a request to Amazon WorkMail. To control access based on tags, you provide tag information in the condition element of a policy using the workmail:ResourceTag/key-name, aws:RequestTag/key-name, or aws:TagKeys condition keys.

For more information about tagging Amazon WorkMail resources, see Tagging an organization (p. 56).

Amazon WorkMail IAM roles

An IAM role is an entity within your AWS account that has speciﬁc permissions.

Using temporary credentials with Amazon WorkMail

You can use temporary credentials to sign in with federation, assume an IAM role, or to assume a cross- account role. You obtain temporary security credentials by calling AWS STS API operations such as AssumeRole or GetFederationToken.

Amazon WorkMail supports using temporary credentials.

Service-linked roles

Service-linked roles allow AWS services to access resources in other services to complete an action on your behalf. Service-linked roles appear in your IAM account and are owned by the service. An IAM administrator can view but not edit the permissions for service-linked roles.

Amazon WorkMail supports service-linked roles. For details about creating or managing Amazon WorkMail service-linked roles, see Using service-linked roles for Amazon WorkMail (p. 25).

(25)

Service roles

This feature allows a service to assume a service role on your behalf. This role allows the service to access resources in other services to complete an action on your behalf. Service roles appear in your IAM account and are owned by the account. This means that an IAM administrator can change the permissions for this role. However, doing so might break the functionality of the service.

Amazon WorkMail supports service roles.

Amazon WorkMail identity-based policy examples

By default, IAM users and roles don't have permission to create or modify Amazon WorkMail resources.

They also can't perform tasks using the AWS Management Console, AWS CLI, or AWS API. An IAM administrator must create IAM policies that grant users and roles permission to perform speciﬁc API operations on the speciﬁed resources they need. The administrator must then attach those policies to the IAM users or groups that require those permissions.

To learn how to create an IAM identity-based policy using these example JSON policy documents, see Creating policies on the JSON tab in the IAM User Guide.

Topics

• Policy best practices (p. 20)

• Using the Amazon WorkMail console (p. 20)

• Allow users to view their own permissions (p. 22)

• Allow users read-only access to Amazon WorkMail resources (p. 23)

Policy best practices

Identity-based policies are very powerful. They determine whether someone can create, access, or delete Amazon WorkMail 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 using AWS managed policies – To start using Amazon WorkMail quickly, use AWS managed policies to give your employees the permissions they need. These policies are already available in your account and are maintained and updated by AWS. For more information, see Get started using permissions with AWS managed policies in the IAM User Guide.

• Grant least privilege – When you create custom policies, grant only the permissions required to perform a task. Start with a minimum set of permissions and grant additional permissions as necessary. Doing so is more secure than starting with permissions that are too lenient and then trying to tighten them later. For more information, see Grant least privilege in the IAM User Guide.

• Enable MFA for sensitive operations – For extra security, require IAM users to use multi-factor authentication (MFA) to access sensitive resources or API operations. For more information, see Using multi-factor authentication (MFA) in AWS in the IAM User Guide.

• Use policy conditions for extra security – To the extent that it's practical, deﬁne the conditions under which your identity-based policies allow access to a resource. For example, you can write conditions to specify a range of allowable IP addresses that a request must come from. You can also write conditions to allow requests only within a speciﬁed date or time range, or to require the use of SSL or MFA. For more information, see IAM JSON policy elements: Condition in the IAM User Guide.

Using the Amazon WorkMail console

To access the Amazon WorkMail console, you must have a minimum set of permissions. These

permissions must allow you to list and view details about the Amazon WorkMail resources in your AWS

(26)

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 (IAM users or roles) with that policy.

To ensure that those entities can still use the Amazon WorkMail console, also attach the following AWS managed policy, AmazonWorkMailFullAccess, to the entities. For more information, see Adding permissions to a user in the IAM User Guide.

The AmazonWorkMailFullAccess policy grants an IAM user full access to Amazon WorkMail resources.

This policy gives the user access to all Amazon WorkMail, AWS Key Management Service, Amazon Simple Email Service, and AWS Directory Service operations. This also includes several Amazon EC2 operations that Amazon WorkMail needs to perform on your behalf. The logs and cloudwatch permissions are required for email event logging and viewing metrics in the Amazon WorkMail console. For more information, see Logging and monitoring in Amazon WorkMail (p. 27).

{

"ds:AuthorizeApplication", "ds:CheckAlias",

"ds:CreateAlias", "ds:CreateDirectory",

"ds:CreateIdentityPoolDirectory", "ds:DeleteAlias",

"ds:DeleteDirectory", "ds:DescribeDirectories", "ds:GetDirectoryLimits",

"ds:ListAuthorizedApplications", "ds:UnauthorizeApplication",

"ec2:AuthorizeSecurityGroupEgress", "ec2:AuthorizeSecurityGroupIngress", "ec2:CreateNetworkInterface",

"ec2:CreateSecurityGroup", "ec2:CreateSubnet", "ec2:CreateTags", "ec2:CreateVpc",

"ec2:DeleteSecurityGroup", "ec2:DeleteSubnet", "ec2:DeleteVpc",

"ec2:DescribeAvailabilityZones", "ec2:DescribeRouteTables", "ec2:DescribeSubnets", "ec2:DescribeVpcs",

"ec2:RevokeSecurityGroupEgress", "ec2:RevokeSecurityGroupIngress", "kms:DescribeKey",

"kms:ListAliases"

"lambda:ListFunctions",

"route53:ChangeResourceRecordSets", "route53:ListHostedZones",

"route53:ListResourceRecordSets",

"route53domains:CheckDomainAvailability", "route53domains:ListDomains",

"ses:*", "workmail:*", "iam:ListRoles",

"logs:DescribeLogGroups", "logs:CreateLogGroup", "logs:PutRetentionPolicy", "cloudwatch:GetMetricData"

], "Resource": "*"

(27)

}, {

"Effect": "Allow",

"Action": "iam:CreateServiceLinkedRole", "Resource": "*",

"Condition": {

"StringEquals": {

"iam:AWSServiceName": "events.workmail.amazonaws.com"

} } }, {

"iam:DeleteServiceLinkedRole",

"iam:GetServiceLinkedRoleDeletionStatus"

],

"Resource": "arn:aws:iam::*:role/aws-service-role/

events.workmail.amazonaws.com/AWSServiceRoleForAmazonWorkMailEvents*"

}, {

"Effect": "Allow", "Action": "iam:PassRole",

"Resource": "arn:aws:iam::*:role/*workmail*", "Condition": {

"StringLike": {

"iam:PassedToService": "events.workmail.amazonaws.com"

} } } ]

}

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 you're trying to perform.

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.

{

"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",

(28)

"iam:GetPolicyVersion", "iam:GetPolicy",

"iam:ListAttachedGroupPolicies", "iam:ListGroupPolicies",

"iam:ListPolicyVersions", "iam:ListPolicies", "iam:ListUsers"

],

"Resource": "*"

} ] }

Allow users read-only access to Amazon WorkMail resources

The following policy statement grants an IAM user read-only access to Amazon WorkMail resources. This policy gives the same level of access as the AWS managed policy AmazonWorkMailReadOnlyAccess.

Either policy gives the user access to all of the Amazon WorkMail Describe operations. Access to the AWS Directory Service DescribeDirectories operation is needed to obtain information about your AWS Directory Service directories. Access to the Amazon SES service is needed to obtain information about the conﬁgured domains. Access to AWS Key Management Service is needed to obtain information about the used encryption keys. The logs and cloudwatch permissions are required for email event logging and viewing metrics in the Amazon WorkMail console. For more information, see Logging and monitoring in Amazon WorkMail (p. 27).

{

"ses:Describe*", "ses:Get*",

"workmail:Describe*", "workmail:Get*", "workmail:List*", "workmail:Search*", "lambda:ListFunctions", "iam:ListRoles",

"logs:DescribeLogGroups", "cloudwatch:GetMetricData"

], "Resource": "*"

} ] }}

Troubleshooting Amazon WorkMail identity and access

Use the following information to help you diagnose and ﬁx common issues that you might encounter when working with Amazon WorkMail and IAM.

Topics

• I am not authorized to perform an action in Amazon WorkMail (p. 24)

• I am not authorized to perform iam:PassRole (p. 24)

• I want to view my access keys (p. 24)

Amazon WorkMail

Amazon WorkMail

Administrator Guide

Version 1.0

Amazon WorkMail: Administrator Guide

Table of Contents

What is Amazon WorkMail?

Amazon WorkMail system requirements

Amazon WorkMail concepts

Related AWS services

Amazon WorkMail pricing

Amazon WorkMail resources

Prerequisites

Get an AWS account and your root user credentials

To sign up for an AWS account

Create AWS Identity and Access Management users and groups

Grant IAM users permissions for Amazon WorkMail

Security in Amazon WorkMail

Data protection in Amazon WorkMail

How Amazon WorkMail uses AWS KMS

Amazon WorkMail encryption

A CMK for the organization

Important

A unique encryption key for each mailbox

Note

A unique encryption key for each message

Creating a new mailbox

Encrypting a mailbox message

Decrypting a mailbox message

Caching mailbox keys

Authorizing use of the CMK

Amazon WorkMail encryption context

Monitoring Amazon WorkMail interaction with AWS KMS

Encrypt

Decrypt

Identity and access management for Amazon WorkMail

Audience

Authenticating With identities

AWS account root user

IAM users and groups

IAM roles

Managing access using policies

Identity-based policies

Resource-based policies

Access Control Lists (ACLs)

Other policy types

Multiple policy types

How Amazon WorkMail works with IAM

Amazon WorkMail identity-based policies

Actions

Resources

Condition keys

Examples

Amazon WorkMail resource-based policies

Authorization based on Amazon WorkMail tags

Amazon WorkMail IAM roles

Using temporary credentials with Amazon WorkMail

Service-linked roles

Service roles

Amazon WorkMail identity-based policy examples

Policy best practices

Using the Amazon WorkMail console

Allow users to view their own permissions

Allow users read-only access to Amazon WorkMail resources

Troubleshooting Amazon WorkMail identity and access