Requirements for the AWS S3 recording bulk action integration
AI-generated summary
Genesys Cloud offers integration capabilities with AWS S3 for recording bulk actions, enabling organizations to export call recordings to AWS S3 buckets for external storage and analysis. The integration requires an AWS account with a general-purpose S3 bucket (not directory buckets) positioned in a Genesys Cloud-supported region, along with an IAM role configured with appropriate access permissions to AWS S3 functions. Organizations should be aware that cross-region bucket placement may incur Amazon S3 data transfer costs.
On the Genesys Cloud side, administrators must possess minimum permissions including Integrations > Integration > Edit and View, and Integrations > Action > All, which grants access to current and future action permissions. The integration must be installed and configured within the Genesys Cloud organization, with IAM role credentials added to the integration settings.
This setup provides a scalable method for leveraging AWS services to process and analyze call recordings outside the Genesys Cloud environment, supporting organizations that require advanced recording management and compliance workflows. Related functionality includes quality management features, IAM resource creation for AWS S3 buckets, exported recording management within S3 environments, optional Customer Master Key (CMK) encryption for exports, and general recording management capabilities. The documentation includes a feedback mechanism allowing users to report issues such as inaccurate or incomplete information, outdated content, or clarity concerns, with role-based categorization for agents, administrators, developers/engineers, partners, supervisors, and support personnel. Additional resources are available through community support channels and linked articles covering AWS S3 bucket configuration, recording export workflows, and encryption options.
The following sections list the requirements for AWS S3 recording bulk action integration.
- An AWS S3 bucket. Note: If the S3 bucket is not in the same region as your Genesys Cloud organization, an Amazon S3 data transfer cost may be incurred. For more information, see AWS regions for Genesys Cloud and Amazon S3 pricing.
- An IAM role that has access to one or more AWS policies or AWS S3 functions. For more information, see Create IAM resources for AWS S3 bucket.
- A Genesys Cloud organization.
- The following permissions (at a minimum) selected for the administrator of the integration and actions: Notes:
- Depending on where you access the permissions in Genesys Cloud, the permission names appear in different formats.
- Instead of selecting individual integrations > action permissions, select All permissions under Integrations > Action. This permission grants administrators access to all permissions—current and future—involving actions.
- Integrations > Integration – Edit and View
- The following permissions allow administrators to edit and view integrations.
- Integrations > Action – Add, Delete, Edit, Execute, and View
- The following permissions allow administrators to add, delete, edit, test, and view custom actions.
- An installed AWS S3 recording bulk actions integration. For more information, see Add the AWS S3 recording bulk actions integration.
- An IAM role added to the integration credentials in Genesys Cloud.
Note: Genesys S3 integration does not support Amazon S3 directory buckets. Use general-purpose Amazon S3 buckets for all export configurations.
For more information about the integration, see About the AWS S3 recording bulk actions integration.[NEXT] Was this article helpful?
Get user feedback about articles.