[
https://issues.apache.org/jira/browse/CASSANALYTICS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai reassigned CASSANALYTICS-155:
---------------------------------------
Assignee: Jon Haddad
> support IAM when bulk writing to S3
> -----------------------------------
>
> Key: CASSANALYTICS-155
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-155
> Project: Apache Cassandra Analytics
> Issue Type: Improvement
> Reporter: Jon Haddad
> Assignee: Jon Haddad
> Priority: Normal
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When triggering a restore job via Apache Cassandra Sidecar, the analytics
> library currently requires explicit static S3 credentials to be passed in the
> job request. This prevents deployments where the Sidecar node authenticates
> to S3 via IAM instance profiles or other non-static credential providers.
> CASSSIDECAR-415 adds support on the Sidecar side for a credentialType field
> in the restore job request, allowing the Sidecar to use its own IAM role when
> credentials are not provided.
> This ticket tracks the corresponding changes in Cassandra Analytics to allow
> users to configure a CredentialType on StorageCredentialPair, selecting how
> the Sidecar should authenticate to S3. The initial supported types are STATIC
> (existing behavior, no change) and IAM. The design leaves room for additional
> credential types in the future without structural changes.
> All existing restore job functionality (coordinated writes, consistency
> levels, cross-region support, lease management) is unaffected — only the
> authentication method passed to the Sidecar changes.
> The same authentication method passed to sidecar will also need to be used to
> push the files to S3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
