If you created a presigned URL by using a temporary token, then the URL expires when the token expires, even if you created the URL with a later expiration time. For more information about how the credentials you use affect the expiration time, see Who can create a presigned URL.
So you have to use regular IAM user instead of IAM role for service generating presigned urls..? :-/
-
https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html#who-presigned-urlThis feature also eliminates the need for third-party solutions such as kiam or kube2iam.
great
-
https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.htmlUne alternative à kube2iam qui est apparemment plus secure
-
https://github.com/uswitch/kiam/blob/master/README.mdfor user in $(aws iam list-users|jq '.Users|.[]|.UserName' -r); do echo $user;aws iam list-user-policies --user-name $user; done
-
https://links.infomee.fr/?xhJZ2g
-
http://docs.aws.amazon.com/AmazonS3/latest/dev/example-walkthroughs-managing-access-example2.html
-
https://links.infomee.fr/?Vp7r6QEasy one?
Not even close
-
https://aws.amazon.com/blogs/security/iam-policies-and-bucket-policies-and-acls-oh-my-controlling-access-to-s3-resources/
-
https://links.infomee.fr/?bERNcgUne policy IAM est constituée de statement, ce sont des règles (des blocs de codes)
{
"Statement":[{
"Effect":"effect",
"Action":"action",
"Resource":"arn",
"Condition":{
"condition":{
"key":"value"
}
}
}
]
}
Chaque règle dans sa forme la plus simple est composée de 3 choses :
Effect : allow ou deny
Action : quelle action concerne la règle
Resource : la resource concernée
Chaque service Amazon (EC2, ECR, etc...) expose une liste d'action, on peut trouver cette liste dans la doc (http://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#Action)
Et chaque resource peut être identifiée par un arn (une manière simple de retrouver un ARN est d'afficher la resources dans l'interface web AWS, il y a souvent l'arn)
-
https://links.infomee.fr/?3KOHAQ