How AWS Wickr works with IAM

Before you use IAM to manage access to Wickr, learn what IAM features are available to use with Wickr.

IAM features you can use with AWS Wickr
IAM feature	Wickr support
Identity-based policies	Yes
Resource-based policies	No
Policy actions	Yes
Policy resources	No
Policy condition keys	No
ACLs	No
ABAC (tags in policies)	No
Temporary credentials	No
Principal permissions	No
Service roles	No
Service-linked roles	No

To get a high-level view of how Wickr and other AWS services work with most IAM features, see AWS services that work with IAM in the IAM User Guide.

Using temporary credentials with Wickr

Supports temporary credentials: No

Some AWS services don't work when you sign in using temporary credentials. For additional information, including which AWS services work with temporary credentials, see AWS services that work with IAM in the IAM User Guide.

You are using temporary credentials if you sign in to the AWS Management Console using any method except a user name and password. For example, when you access AWS using your company's single sign-on (SSO) link, that process automatically creates temporary credentials. You also automatically create temporary credentials when you sign in to the console as a user and then switch roles. For more information about switching roles, see Switching to a role (console) in the IAM User Guide.

You can manually create temporary credentials using the AWS CLI or AWS API. You can then use those temporary credentials to access AWS. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see Temporary security credentials in IAM.