SYNOPSIS
get-login
[--registry-ids <value> [<value>...]]
[--include-email | --no-include-email]
OPTIONS
--registry-ids (string) A list of AWS account IDs that correspond to
the Amazon ECR registries that you want to log in to.
--include-email | --no-include-email (boolean) Specify if the '-e' flag
should be included in the 'docker login' command. The '-e' option has
been deprecated and is removed in docker version 17.06 and later. You
must specify --no-include-email if you're using docker version 17.06 or
later. The default behavior is to include the '-e' flag in the 'docker
login' output.
-
https://links.infomee.fr/shaare/ECje8gfor 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/shaare/xhJZ2gTo apply this lifecycle rule to all objects in the bucket, choose Next.
That's why wildcard was not working :D
-
http://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-lifecycle.htmlAmazon Elasticsearch access control may be based on IAM account with signed request mechanism
One way not to rewrite all applications is using such a proxy
-
https://github.com/abutaha/aws-es-proxyaws dynamodb scan --table-name foo
-
https://links.infomee.fr/shaare/AqSZDAaws dynamodb delete-item --table-name foo --key "{\"id\":{\"S\":\"$id\"}}"
-
https://links.infomee.fr/shaare/bx3KXgOn peut "remettre" ou plutot rendre disponible de nouveau un message SQS en changeant sa visibility timeout à 0
-
http://boto3.readthedocs.io/en/latest/reference/services/sqs.html#SQS.Client.change_message_visibilityaws s3 ls s3://bucket/path/ --recursive --summarize | grep "Total Objects:"
-
https://links.infomee.fr/shaare/rcG0hgTruc con : on ne peut pas utiliser le résultat du get-repository-policy dans le set-repository-policy pour cloner.
Il faut au passage enlever les \n qui trainent dans la réponse
-
http://docs.aws.amazon.com/cli/latest/reference/ecr/set-repository-policy.htmlSo you can put your data into glacier with 2 differents ways:
1) directly to glacier via API
2) Store them to s3 then with a management policy, it'll go to Glacier
Warning : Huge cost when you download from glacier and when you delete before 3 months
-
https://www.cloudberrylab.com/blog/compare-amazon-glacier-direct-upload-and-glacier-upload-through-amazon-s3/
-
https://links.infomee.fr/shaare/eFFzMgaws efs describe-file-systems| jq '.FileSystems|.[]|[.Name, .SizeInBytes.Timestamp, .SizeInBytes.Value]' -c
Retourne une ligne par EFS
Sur chaque ligne, un array avec :
[0] = nom de l'efs
[1] = timestamp du moment où la taille a été calculée
[2] = la taille en bytes
Pour avoir la taille en GB :
aws efs describe-file-systems| jq '.FileSystems|.[]|[.Name, .SizeInBytes.Timestamp, .SizeInBytes.Value / 1024 /1024 / 1024]' -c
aws efs describe-file-systems| jq '.FileSystems|.[]|[.Name, .SizeInBytes.Value / 1024 /1024 / 1024]' -c
-
https://links.infomee.fr/shaare/MzuW2A
-
http://docs.aws.amazon.com/AmazonS3/latest/dev/example-walkthroughs-managing-access-example2.html