3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Hey there,
This isn't an AWS solution, but one that you may find interesting.
As for more 'native' solutions to the AWS CLI, you can go down the route of Environment Variables, as previously mentioned by another user. On the matter of your idea of passing the Access Key and Secret Key along with each command, I only know that you can do this in AWS Tools for PowerShell. I cannot see anything in the AWS CLI which would indicate that you can do the same in it.
con risposta 2 anni fa
0
Have you considered the AWS Secrets Manager? Would that be a good fit for your particular situation?
con risposta 2 anni fa
Thank you for your answer @sharpedgewv , i need to read more about the AWS Secrets Manager, but if it is using "IAM static access keys" at any point, then it is not solution for us.
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 2 anni fa
Thank you for you answer @Ciaran Carragher, we probably will go with setuping shell variables, but the AWS VAULT does look as interesting solution.