We are setting up temporal in a FIPS compliant environment. Archival is anabled in this setup and we are using S3 bucket to store archival data. We would like to ensure that the S3 endpoint used by the application is a FIPS enabled endpoint. But in helm chart or CLI commands we are able to set the endpoint in the format s3://<bucket_name>. Is there any way that we can specify the S3 bucket as a FIPS enabled endpoint or are there any configurations that we can specify to ensure that communication from temporal to S3 bucket and vice versa is FIPS compliant
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Archival to s3 in helm charts | 8 | 2140 | June 10, 2022 | |
| Issue with Archival with AWS S3 provider | 6 | 510 | November 7, 2024 | |
| Configuring a private S3 endpoint for archival | 0 | 279 | December 19, 2023 | |
| How to config temporal S3 authentication in temporal helm chart? | 5 | 941 | February 20, 2023 | |
| Provide s3 credential to archival with helm | 4 | 615 | April 6, 2023 |