s3 backup credentials for cloud deployments (AWS)

Description

  There are different ways of getting AWS credentials from inside AWS. The most preferable and secure is using instance_profile for ec2 or  IAM Roles for Service Accounts (kube2iam or kiam) for k8s. The idea is as simple as getting temporary credentials form aws sts service and renew the keys as the time goes. The only business for a user is to create a proper policy with resource permissions and attach it to a role that is attached to instance_profile or k8s service account. So the idea is: no hardcoded or predefined key!

Percona mongo operator now have this:

If no Credentials set - return an error.

 

it would be nice to have the option not to set the credentials if the mongo cluster is run on AWS (operator checks or an extra field in CRD). In case there is no credentials set and the environment is AWS - ask STS for credentials with further updates.

Environment

operator version 1.3.0 deployed on AWS EKS. 5 mongo clusters in the same namespace.

Smart Checklist

Activity

Show:

Sergey Pronin November 5, 2021 at 12:09 PM

AWS has the capability to authenticate applications running on EC2 instances without using IAM keys, but relying on IAM roles assigned to the instance.

 

Starting from version 1.6.1 Percona Backup for MongoDB supports EC2 profiles. It would be great to add this support into the Operator as well.

 

PBM doc about it: https://www.percona.com/doc/percona-backup-mongodb/automate-s3-access.html

Mykola Marzhan June 3, 2020 at 12:33 PM


it is in our long term roadmap, please escalate via regular channels if you have a contract with Percona.

Lalit Choudhary May 27, 2020 at 10:31 AM

Engineering will review this request if this can be done.

Thank you for the report. 

 

Lalit Choudhary May 27, 2020 at 10:17 AM
Edited

Hi

Thank you for the report.

Done

Details

Assignee

Reporter

Labels

Needs Doc

Yes

Fix versions

Affects versions

Priority

Smart Checklist

Created March 5, 2020 at 1:56 PM
Updated March 5, 2024 at 5:09 PM
Resolved May 5, 2022 at 3:51 PM