4337 links
  • Arnaud's links
  • Home
  • Login
  • RSS Feed
  • ATOM Feed
  • Tag cloud
  • Picture wall
  • Daily
Links per page: 20 50 100
◄Older
page 5 / 8
Newer►
156 results tagged aws x
  • GitHub - abutaha/aws-es-proxy: aws-es-proxy is a small web server application sitting between your HTTP client (browser, curl, etc...) and Amazon Elasticsearch service.

    Amazon 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

    September 5, 2017 at 5:35:53 PM GMT+2 * - permalink - archive.org - https://github.com/abutaha/aws-es-proxy
    aws elasticsearch es
  • Note: List item in dynamo db table

    aws dynamodb scan --table-name foo

    August 18, 2017 at 11:10:05 AM GMT+2 - permalink - archive.org - https://links.infomee.fr/?AqSZDA
    aws dynamodb
  • Note: Delete dynamo db item in cmdline

    aws dynamodb delete-item --table-name foo --key "{\"id\":{\"S\":\"$id\"}}"

    August 18, 2017 at 11:08:55 AM GMT+2 - permalink - archive.org - https://links.infomee.fr/?bx3KXg
    aws dynamodb
  • upload-server-certificate — AWS CLI 1.11.124 Command Reference

    --path

    July 25, 2017 at 11:07:06 AM GMT+2 - permalink - archive.org - http://docs.aws.amazon.com/cli/latest/reference/iam/upload-server-certificate.html
    aws iam ssl
  • SQS — Boto 3 Docs 1.4.4 documentation

    On peut "remettre" ou plutot rendre disponible de nouveau un message SQS en changeant sa visibility timeout à 0

    July 12, 2017 at 11:37:59 AM GMT+2 - permalink - archive.org - http://boto3.readthedocs.io/en/latest/reference/services/sqs.html#SQS.Client.change_message_visibility
    aws sqs
  • Note: Count object in bucket/folder

    aws s3 ls s3://bucket/path/ --recursive --summarize | grep "Total Objects:"

    July 12, 2017 at 10:12:14 AM GMT+2 - permalink - archive.org - https://links.infomee.fr/?rcG0hg
    aws count s3
  • set-repository-policy — AWS CLI 1.11.117 Command Reference

    Truc 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

    July 11, 2017 at 5:19:45 PM GMT+2 * - permalink - archive.org - http://docs.aws.amazon.com/cli/latest/reference/ecr/set-repository-policy.html
    aws ecs
  • Amazon Glacier Direct Upload vs Glacier Upload via Amazon S3

    So 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

    June 27, 2017 at 11:01:12 AM GMT+2 - permalink - archive.org - https://www.cloudberrylab.com/blog/compare-amazon-glacier-direct-upload-and-glacier-upload-through-amazon-s3/
    aws glacier s3
  • Creating a Redis (cluster mode enabled) Cluster with Replicas from Scratch - Amazon ElastiCache
    June 20, 2017 at 11:31:28 AM GMT+2 - permalink - archive.org - http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/Replication.CreatingReplGroup.NoExistingCluster.Cluster.html
    aws redis
  • Creating a Redis (cluster mode disabled) Cluster with Replicas from Scratch - Amazon ElastiCache
    June 20, 2017 at 11:31:18 AM GMT+2 - permalink - archive.org - http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/Replication.CreatingReplGroup.NoExistingCluster.Classic.html
    aws redis
  • Replication: Redis (cluster mode disabled) vs. Redis (cluster mode enabled) - Amazon ElastiCache
    June 20, 2017 at 9:59:57 AM GMT+2 - permalink - archive.org - http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/Replication.Redis-RedisCluster.html
    aws redis
  • Replication: Multi-AZ with Automatic Failover (Redis) - Amazon ElastiCache
    June 19, 2017 at 5:05:58 PM GMT+2 - permalink - archive.org - http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/AutoFailover.html
    aws redis
  • Note: some draft about monitoring beanstalk applications health with boto3 python script
    import pprint
    p = pprint.PrettyPrinter(indent=4)
    p.pprint(x)

    or

    import pprint
    pprint.pformat(x)


    import logging
    import pprint
    logging.info(pprint.pformat(dict))



     $ cat monitor_beanstalk.py
    #!/bin/python

    import boto3
    import pprint
    pp = pprint.PrettyPrinter(indent=4)


    #List all env and status and instances health

    client = boto3.client('elasticbeanstalk')


    envs = client.describe_environments()['Environments']

    #pp.pprint(envs)


    for env in envs:
        print 'ApplicationName: {} EnvironmentName: {} Health: {} HealthStatus: {} Status: {}'.format(env['ApplicationName'].ljust(30),env['EnvironmentName'].ljust(30),env['Health'].ljust(10),env.get('HealthStatus', 'N/A').ljust(10),env['Status'].ljust(10))
        if (env['Health'] != 'Green') or (env.get('HealthStatus', 'N/A') != 'Ok' and env.get('HealthStatus', 'N/A') != 'N/A'):
            print '\nProblem'
            details = client.describe_environment_health(EnvironmentName=env['EnvironmentName'],AttributeNames=['All'])
            #pp.pprint(details)
            print details['Causes']
            print details['InstancesHealth']
            print '\n'
    June 15, 2017 at 11:12:05 AM GMT+2 * - permalink - archive.org - https://links.infomee.fr/?eFFzMg
    aws beanstalk boto pprint python
  • Note: EFS size by api

    aws 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

    June 13, 2017 at 11:56:27 AM GMT+2 * - permalink - archive.org - https://links.infomee.fr/?MzuW2A
    aws efs size
  • Example 2: Bucket Owner Granting Cross-Account Bucket Permissions - Amazon Simple Storage Service
    Donc pour autoriser un compte externe, on va créer une bucket policy sur notre bucket pour autoriser "arn:aws:iam::account_id:root" ou plus précis sur l'user arn:aws:iam::account_id:user/foobar ou le role

    C'est le compte en face qui va décider qui a le droit de venir sur notre bucket avec des user policy standard (quand on est dans le contexte du compte en face, c'est comme si le bucket nous appartenait)

    Exemple bucket policy à mettre sur le BUCKET de l'account A pour autoriser l'account xxx en RW


    {
        "Version": "2012-10-17",
        "Statement": [





            {
                "Sid": "Allow account_xx on aws account xxx RW",
                "Effect": "Allow",
                "Principal": {
                    "AWS": "arn:aws:iam::OTHER_ACCOUNT_ID:root"
                },
                "Action": ["s3:GetBucketLocation", "s3:ListBucket"],
                "Resource": "arn:aws:s3:::BUCKET"
            },
            {
                "Sid": "Allow account_xx on aws account xxx RW",
                "Effect": "Allow",
                "Principal": {
                    "AWS": "arn:aws:iam::OTHER_ACCOUNT_ID:root"
                },
                "Action": [
                    "s3:*"
                ],
                "Resource": "arn:aws:s3:::BUCKET/*"
            }




        ]
    }

    Pour Read only, remplacer action du deuxieme bloc par "Action": ["s3:Get*","s3:List*"],
    June 12, 2017 at 8:48:42 AM GMT+2 * - permalink - archive.org - http://docs.aws.amazon.com/AmazonS3/latest/dev/example-walkthroughs-managing-access-example2.html
    aws cross iam policy s3
  • thumbnail
    Copy between S3 buckets w/ different accounts · GitHub
    June 8, 2017 at 5:29:42 PM GMT+2 - permalink - archive.org - https://gist.github.com/ushu/7217693
    aws s3
  • The Challenges of EFS

    one more

    June 8, 2017 at 4:54:01 PM GMT+2 - permalink - archive.org - https://convox.com/blog/challenges-of-efs/
    aws efs
  • wordpress - Degrading Performance of AWS EFS - Stack Overflow

    why EFS sucks

    June 8, 2017 at 4:44:50 PM GMT+2 - permalink - archive.org - https://stackoverflow.com/questions/41673284/degrading-performance-of-aws-efs
    aws efs
  • Note: s3 policy one bucket
    ReadWrite :

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                 "Action": ["s3:GetBucketLocation", "s3:ListBucket"],
                "Resource": [
                    "arn:aws:s3:::LeBucket"
                ]
            },
            {
                "Effect": "Allow",
                "Action": [
                    "s3:*"
                ],
                "Resource": [
                    "arn:aws:s3:::LeBucket/*"
                ]
            }
        ]
    }

    Pour Read only, remplacer action du deuxieme bloc par "Action": ["s3:Get*","s3:List*"],
    May 17, 2017 at 5:02:27 PM GMT+2 * - permalink - archive.org - https://links.infomee.fr/?Vp7r6Q
    aws iam s3
  • Note: s3 enpoint

    If you enable s3 enpoint in your route table, it's kind of tricky to know if the endpoint is really working. Two things to validate:
    1) traceroute tcp before and after (traceroute -T s3-us-west-1.amazonaws.com 443)
    You will see more hope when endpoint not activated
    2) try an s3 sync cross region with enpoint activated : it should failed since it's not supported (yet @ 2017-05-02)

    May 2, 2017 at 9:51:18 AM GMT+2 - permalink - archive.org - https://links.infomee.fr/?1wF2Kg
    aws enpoint s3
Links per page: 20 50 100
◄Older
page 5 / 8
Newer►
Shaarli - The personal, minimalist, super-fast, database free, bookmarking service by the Shaarli community - Help/documentation