Bug 1962217

User Story: As an object storage administrator, I want to integrate RHCS into the public cloud space so that I can leverage a secure (encrypted) lifecycle solution.

Strategic Value: Ceph Object Gateway remains an impact focus area for standalone object storage, targeting emerging workloads (including data analytics and AI/ML) that require scalable object storage. While RHCS 4 focused on supporting large-scale enterprise private clouds and doubled the object store performance delivered from earlier releases, RHCS 5.1 continues the public cloud effort (of RHCS 5.0) by completing the lifecycle transition story and storage class model to AWS, Microsoft Azure, and Google Cloud Endpoints.

Foremost in the transition effort is the continued adoption of policy-based cloud archiving and cloud tiering:

cloud archiving:
Customers move (archive) older data from a local cluster to an AWS bucket to reduce cost and improve manageability. Archiving is policy-based and automatic based on policy threshold.
cloud tiering
Customers move data (tier) to the public cloud from a local cluster via a time-based or performance-based policy. Tiering is automatic based on policy thresholds.

In addition, RHCS 5.1 builds on the security efforts of RHCS 4 (object expiration, KMS) and RHCS 5.0 (object lock) by increasing encryption and identity management capabilities as well as providing user experience improvements.

This user story will focus on the following use cases:

* Expand lifecycle transition by associating cloud endpoints to storage classes
* Deliver AssumeRoleWithWebIdentity support
* Provide managed bucket encryption
* Provide materialized bucket listings in Parquet format
* Provide S3 bucket notifications via a Simple Notification Service (SNS)
* Simplified RGW HA proxy installation
* Simplified installation of multiple RGW instances on the same host
* Provide a read-only RGW admin role with OpenStack Keystone