4259 links
  • Arnaud's links
  • Home
  • RSS Feed
  • Tag cloud
  • Login
search: tag:aws — newest first
  • wordpress - Degrading Performance of AWS EFS - Stack Overflow

    why EFS sucks

    June 8, 2017 - permalink - 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 - permalink - https://links.infomee.fr/shaare/Vp7r6Q
    aws iam nomarkdown 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 - permalink - https://links.infomee.fr/shaare/1wF2Kg
    aws enpoint s3
  • Configuring the AWS Command Line Interface - AWS Command Line Interface

    Pratique quand on doit jongler entre différents comptes AWS

    et l'équivalent pour s3cmd : http://mikesisk.tumblr.com/post/8703449578/s3cmd-and-multiple-accounts

    April 21, 2017 - permalink - http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-multiple-profiles
    aws profile
  • wallix/awless: A Mighty CLI for AWS
    April 10, 2017 - permalink - https://github.com/wallix/awless
    aws cmd
  • s3fs-fuse/s3fs-fuse: FUSE-based file system backed by Amazon S3

    I may have to use this one, but issue number is freaking me out

    March 30, 2017 - permalink - https://github.com/s3fs-fuse/s3fs-fuse
    aws fs s3 s3fs
  • localstack/README.md at master · atlassian/localstack · GitHub

    Good boy atlassian!

    March 27, 2017 - permalink - https://github.com/atlassian/localstack/blob/master/README.md
    atlassian aws
  • Note: boto3 subnet sorted by name

    subnets = ec2.subnets.all()
    subnets_sorted = sorted(subnets, key=lambda k: k.tags[next(index for (index, d) in enumerate(k.tags) if d["Key"] == "Name")]['Value'])

    Well, my python level is not good enough to clearly understand this but my Google level was largely enough to build this

    March 24, 2017 - permalink - https://links.infomee.fr/shaare/Fn--jw
    aws boto boto3 python
  • mozart-analytics/sqsd: A simple alternative to the Amazon SQS Daemon ("sqsd") used on AWS Beanstalk worker tier instances.

    As the included diagram portrays, in a common workflow, the worker instance will consume messages sent to a specified Amazon SQS from another service (e.g.: a web server or another worker). These messages will be received by the worker via POST requests. This eliminates the necessity of configuring a worker as an always-on service, as well as having to add code for reading and consuming messages from an AWS SQS queue. In other words, the worker is implemented as a standard RESTful API/Service that will react to a message sent to it at an specific endpoint via a POST request. This is an awesome approach by Amazon to microservices and reactive design.

    The conversion of the SQS message to a POST request is executed by what AWS calls the "SQS Daemon" or "Sqsd". This is a simple daemon they pre-install in the worker tier instances that is constantly monitoring an specific AWS SQS queue (provided by configuration) for new messages. When new messages arrive, it constructs a POST request and sends it to a specific endpoint (also provided via configuration). If the endpoint consumes it without errors and returns a 2** HTTP Code in its response, the "Sqsd" deletes the message from the queue to signal that its consumption was successful.

    However, even though this approach is extremely powerful, Amazon does not provide the code of this daemon as open source. Therefore, we have reproduced its behavior by creating our own version of the "Sqsd" free for everyone to use. Moreover, we have provided lots of customization and configuration properties so that it can be molded to your specific use cases.

    March 16, 2017 - permalink - https://github.com/mozart-analytics/sqsd
    aws beanstalk sqs
  • Writing IAM Policies: How to Grant Access to an Amazon S3 Bucket | AWS Security Blog

    Don't give s3 full access policy to your app user
    Prefer to allow access only for specific bucket

    I wonder what's the best choice : create managed policy or simply use inline policy. I got a 1 to 1 relationship between my app-users and bucket so... inline policy looks good here

    March 15, 2017 - permalink - https://aws.amazon.com/blogs/security/writing-iam-policies-how-to-grant-access-to-an-amazon-s3-bucket/
    aws policy s3
  • Note: aws auto scaling

    spoiler alert: auto scaling is far to be magical

    as usual with aws, everything is an object and for autoscaling u got several objects and several links between them
    First you define a launch configuration : what type of machine you want to laucnh
    Then an autoscaling group : it will use the launch configuration to create new EC2
    In this autoscaling group, you have to define auto scaling policies ie what to do (remove or add x instances) and link them to a cloudwatch alert (cpu is high or network or whatever cloudwatch monitors)
    the autoscaling group can also be linked to an ELB so when EC2 are added/removed, they also are registred/deregistered from ELB

    March 13, 2017 - permalink - https://links.infomee.fr/shaare/JIGagw
    auto aws scale scaling
  • Stop and Start Your Instance - Amazon Elastic Compute Cloud

    Each time you start a stopped instance we charge a full instance hour, even if you make this transition multiple times within a single hour.

    March 9, 2017 - permalink - http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html
    aws pricing
  • GitHub - capitalone/cloud-custodian: Rules engine for AWS management, DSL in yaml for query, filter, and actions on resources
    March 7, 2017 - permalink - https://github.com/capitalone/cloud-custodian
    aws policy
  • Worker Environments - AWS Elastic Beanstalk

    Elastic Beanstalk simplifies this process by managing the Amazon SQS queue and running a daemon process on each instance that reads from the queue for you. When the daemon pulls an item from the queue, it sends an HTTP POST request locally to http://localhost/ with the contents of the queue message in the body. All that your application needs to do is perform the long-running task in response to the POST. You can configure the daemon to post to a different path, use a MIME type other than application/JSON, connect to an existing queue, or customize connections, timeouts, and retries.

    March 2, 2017 - permalink - http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features-managing-env-tiers.html
    aws beanstalk sqs worker
  • Description détaillée d'Amazon Simple Queue Service (SQS) – Amazon Web Services (AWS)

    Cycle de vie des messages Amazon SQS

    Les messages stockés dans Amazon SQS ont un cycle de vie facile à gérer, mais qui garantit le traitement de tous les messages.

    Un système qui doit envoyer un message sélectionne une file d'attente Amazon SQS et utilise SendMessage pour lui envoyer un nouveau message.
    Un autre système traitant des messages doit traiter plus de messages : il appelle donc ReceiveMessage, et ce message est renvoyé.
    Dès lors qu'un message est renvoyé par ReceiveMessage, il ne sera pas renvoyé par une autre demande ReceiveMessage avant que le délai de visibilité ne soit expiré. Ainsi, plusieurs destinataires peuvent traiter le même message simultanément.
    Si le système de traitement des messages termine avec succès le traitement de ce message, il appelle DeleteMessage, ce qui supprime le message de la file d'attente pour que personne d'autre ne le traite. Si ce système ne réussit pas à traiter le message, il sera alors lu par un autre appel ReceiveMessage dès que le délai de visibilité sera expiré.
    Si vous avez associé une file d'attente de lettre morte à une file d'attente source, les messages seront déplacés vers la file d'attente de lettre morte lorsque le nombre de tentatives d'envoi que vous avez défini aura été atteint.
    
    March 2, 2017 - permalink - https://aws.amazon.com/fr/sqs/details/
    amazon aws sqs
  • Scaling Based on Amazon SQS - Auto Scaling

    Beanstalk ne permet pas de définir un trigger basé sur le nombre d'éléments dans la queue SQS pour l'auto scaling des environements de type worker

    Pourtant c'est possible mais il y a un peu de boulot :
    - créer des scaling policies qui vont ajouter ou enlever des instances
    - créer des alarmes cloudwatch qui vont se déclencher par rapport au nb d'éléments dans la queue et appeler les scaling policies..

    http://docs.aws.amazon.com/autoscaling/latest/userguide/as-using-sqs-queue.html
    https://forums.aws.amazon.com/thread.jspa?messageID=722589

    On peut surement intégrer ça à beanstalk avec les .ebextensions (http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/ebextensions.html)

    En plus d'être un peu complexe et pas vraiment intégrer à beanstalk, ça n'a pas l'air très réactif, cet article en parle et donne une solution :
    Rapid Auto Scaling with Amazon SQS : https://aws.amazon.com/blogs/aws/auto-scaling-with-sqs/

    February 28, 2017 - permalink - http://docs.aws.amazon.com/autoscaling/latest/userguide/as-using-sqs-queue.html
    auto aws beanstalk scaling sqs
  • Configure Connection Draining for Your Classic Load Balancer - Elastic Load Balancing
    February 24, 2017 - permalink - https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-conn-drain.html
    aws elb
  • Configure the Idle Connection Timeout for Your Classic Load Balancer - Elastic Load Balancing
    February 24, 2017 - permalink - https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/config-idle-timeout.html
    aws elb
  • Custom Platforms - AWS Elastic Beanstalk

    Depuis hier le 22 Février 2017

    seems cool and powerful

    February 23, 2017 - permalink - http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/custom-platforms.html
    aws beanstalk
  • Note: How to know which policy contains a specific action?

    Warning : this loop does a lot of call to aws api, use it with caution

    To know that I needed to list all policies and associated statements (for the default policy version)

    #!/bin/bash
    IFS=$'\n'
    for line in $(aws iam list-policies|jq '.Policies|.[]|[ .PolicyName, .Arn, .DefaultVersionId ]| @csv' -r|sed 's/","/ /g'|sed 's/"//g'); do
        name=$(echo $line|cut -d' ' -f1);
        arn=$(echo $line|cut -d' ' -f2);
        version=$(echo $line|cut -d' ' -f3);
        echo "$name"
        aws iam get-policy-version --policy-arn $arn --version-id $version
    done
    

    Put this in a script, redirect output to a file and go get grep!

    February 22, 2017 - permalink - https://links.infomee.fr/shaare/bERNcg
    aws bash for foreach iam nomarkdown policy separator
  • Configuring Application Version Lifecycle Settings - AWS Elastic Beanstalk

    Since December 22th 2016 you are able to configure application version lifecycle in Beanstalk.

    Very convenient, we can trash our custom api cleaning scripts :-)

    February 22, 2017 - permalink - http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-lifecycle.html
    aws beanstalk
  • General Options for All Environments - AWS Elastic Beanstalk

    Default listener (80) is enabled by default, to disable it :
    aws:elb:listener:
    ListenerEnabled: false

    February 20, 2017 - permalink - http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-elblistener
    aws beanstalk
  • Amazon EBS Update – New Elastic Volumes Change Everything | AWS Blog

    aws <3

    February 14, 2017 - permalink - https://aws.amazon.com/blogs/aws/amazon-ebs-update-new-elastic-volumes-change-everything/
    aws ebs
  • Note: EC2 metadata

    Several ways to get metadata (like ip address) when you're connected to an EC2:

    /opt/aws/bin/ec2-metadata

    curl http://169.254.169.254/latest/meta-data/

    February 10, 2017 - permalink - https://links.infomee.fr/shaare/-mOoAQ
    aws ec2 metadata
  • Multicontainer Docker Configuration - AWS Elastic Beanstalk

    TIL

    Beanstalk is a little bit... magic. Dunno yet if its good or not :

    Elastic Beanstalk creates log volumes on the container instance, one for each container, at /var/log/containers/containername. These volumes are named awseb-logs-containername and should be mounted to the location within the container file structure where logs are written.

    For example, the following mount point maps the nginx log location in the container to the Elastic Beanstalk–generated volume for the nginx-proxy container.

    {
    "sourceVolume": "awseb-logs-nginx-proxy",
    "containerPath": "/var/log/nginx"
    }

    And all this logs can be copied into s3 automagically: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-elasticbeanstalkhostmanager

    February 2, 2017 - permalink - http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_v2config.html#create_deploy_docker_v2config_dockerrun_format
    aws beanstalk log logs
  • How to Setup AWS S3 Access from Specific IPs - Pete Cheslock

    {
    "Id": "S3PolicyId1",
    "Statement": [
    {
    "Sid": "IPDeny",
    "Effect": "Deny",
    "Principal": {
    "AWS": ""
    },
    "Action": "s3:
    ",
    "Resource": "arn:aws:s3:::my-wicked-awesome-bucket/*",
    "Condition": {
    "NotIpAddress": {
    "aws:SourceIp": "72.309.38.2/32"
    }
    }
    }
    ]
    }

    December 19, 2016 - permalink - https://pete.wtf/2012/05/01/how-to-setup-aws-s3-access-from-specific-ips/
    aws ip s3
  • Note sur les Policy IAM

    Une 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)

    December 12, 2016 - permalink - https://links.infomee.fr/shaare/3KOHAQ
    aws iam policy
  • Note: AWS Beanstalk et cron

    On peut avoir besoin de faire tourner un ou plusieurs cron dans un environnement Beanstalk composé de X instances
    Etant donné que toute les instances sont configurées de la meme manière, si on rajoute le cron dans la config, il sera éxecuté sur toutes les instances

    Une solution serait de determiner si on est le "runnner" ou non avant de lancer le cron

    Pour que toutes les instances sachent qui est le runner, on peut imaginer un système comme celui ci :
    - on interroge l'ELB avec les API pour avoir ses backends
    - on trie cette liste de backend
    - le runner est le premier de cette liste
    - si notre ip est égale à celle du runner, on lance le cron

    ça a l'avantage de fonctionner quel que soit le nombre d'instances et ne pas stocker un état (on utilise les infos de l'ELB)

    Et si on ne veut pas faire tourner tous les crons sur le runner, on pourrait déterminer runnner1 runnner2 runner3 etc suivant l'ordre et faire tourner certains crons si on est runner1 ou bien runner2

    December 9, 2016 - permalink - https://links.infomee.fr/shaare/fmh_YQ
    aws beanstalk cron elb
  • Multipart Upload Overview - Amazon Simple Storage Service
    December 8, 2016 - permalink - http://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html
    aws multipart s3
  • aws.png

    Bientôt 3 mois que j'ai commencé avec AWS

    En vert ce avec quoi j'ai pu bien jouer
    En orange survolé
    Et tout le reste

    Ce qui me plait le plus : tout est automatisable soit avec des appels à l'api (SDK dans beaucoup de langage) donc en mode séquentiel, soit avec CloudFormation, une sorte de Configuration Management donc en mode declaratif

    rdv dans 3 mois ;)

    December 7, 2016 - permalink - https://infomee.fr/vrac/aws.png
    aws
  • Solutions Architect—Associate Certification for AWS

    online resources to prepare aws certifications

    December 7, 2016 - permalink - https://cloudacademy.com/learning-paths/solutions-architect-associate-aws-14/
    aws certification courses
  • Amazon EC2 Instance Comparison

    Une vue pratique pour comparer les instances ec2

    November 11, 2016 - permalink - http://www.ec2instances.info/
    aws compare ec2
  • open-guides/og-aws: 📙 Amazon Web Services — a practical guide

    aws community guide

    November 8, 2016 - permalink - https://github.com/open-guides/og-aws
    aws doc guide price traffic
  • General Options for All Environments - AWS Elastic Beanstalk

    THE page you have to bookmark when you work with beanstalk and saved config

    November 8, 2016 - permalink - http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html
    aws beanstalk conf
  • Configuring Websockets behind an AWS ELB | jverkamp.com | John-Paul Verkamp
    November 7, 2016 - permalink - https://blog.jverkamp.com/2015/07/20/configuring-websockets-behind-an-aws-elb/
    aws elb ws
  • Leveraging Multiple IP Addresses for Virtual IP Address Fail-over in 6 Simple Steps : Articles & Tutorials : Amazon Web Services

    un peu homemade, mais why not

    November 3, 2016 - permalink - https://aws.amazon.com/articles/2127188135977316
    aws heatbeat
  • CloudWatch Logs Agent Reference - Amazon CloudWatch Logs

    Donc AWS propose un service équivalent à elastic beats

    L'agent est paramétrable pour collecter tel ou tel fichier de logs et les envoyer dans cloudwatch

    October 20, 2016 - permalink - http://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AgentReference.html
    aws
  • Note: Create an EBS and add a name Tag oneliner

    aws ec2 create-volume --size 40 --availability-zone eu-west-1a --volume-type gp2|grep -Eo 'vol-[^"]+'|xargs -I % aws ec2 create-tags --resources % --tags Key=Name,Value=my_name

    October 19, 2016 - permalink - https://links.infomee.fr/shaare/76LRBQ
    aws ebs
  • Note: aws

    EB

    IAM

    EC2
    ELB
    ECS

    ELB
    ECS
    S3
    RDS(Aurora)

    VPC
    Subnets
    Routing
    NAT
    ACLs
    Security groups
    Group policy

    Cloudwatch
    Flowlogs

    October 13, 2016 - permalink - https://links.infomee.fr/shaare/ldAx8Q
    aws
  • Note: get aws flow logs

    aws logs get-log-events --log-group-name XX --log-stream-name YY --start-time 1476350746000

    Je commence à bien aimer aws.

    October 13, 2016 - permalink - https://links.infomee.fr/shaare/ZHDmkA
    aws flow log logs
  • Amazon RDS FAQs – Amazon Web Services (AWS)

    Q: What is a DB Subnet Group and why do I need one?

    A DB Subnet Group is a collection of subnets that you may want to designate for your RDS DB Instances in a VPC. Each DB Subnet Group should have at least one subnet for every Availability Zone in a given Region. When creating a DB Instance in VPC, you will need to select a DB Subnet Group. Amazon RDS then uses that DB Subnet Group and your preferred Availability Zone to select a subnet and an IP address within that subnet. Amazon RDS creates and associates an Elastic Network Interface to your DB Instance with that IP address.

    Please note that, we strongly recommend you use the DNS Name to connect to your DB Instance as the underlying IP address can change (e.g., during a failover).

    For Multi-AZ deployments, defining a subnet for all Availability Zones in a Region will allow Amazon RDS to create a new standby in another Availability Zone should the need arise. You need to do this even for Single-AZ deployments, just in case you want to convert them to Multi-AZ deployments at some point.

    October 12, 2016 - permalink - https://aws.amazon.com/rds/faqs/
    aws rds
  • AWS - VPC Networking for Beginners - DZone Cloud

    So, an elastic ip and an igw in the routing table are two criterion for an instance to be available directly from the internet. Subnets with such routing tables attached to them are also known as public subnets (non-local traffic routed to internet gateway), as any instance with an elastic ip can be publicly available from this subnet.

    October 11, 2016 - permalink - https://dzone.com/articles/aws-vpc-networking-beginners
    aws networking subnet
  • How to Automatically Tag Amazon EC2 Resources in Response to API Events - AWS Security Blog

    Intéressant comme workflow, l'objectif est de laisser les users/soft créer des EC2 comme ils veulent et avoir les droits seulement sur les EC2 qu'ils ont créé.

    Comment ça marche ? auto tagging des EC2 avec l'userid à la création couplé avec une policy qui autorise les action seulement si le tag avec l'userid est présent.

    pacon

    Dans le meme genre sans l'auto tagging :
    http://blogs.aws.amazon.com/security/post/Tx29HCT3ABL7LP3/Resource-level-Permissions-for-EC2-Controlling-Management-Access-on-Specific-Ins

    October 10, 2016 - permalink - https://blogs.aws.amazon.com/security/post/Tx150Z810KS4ZEC/How-to-Automatically-Tag-Amazon-EC2-Resources-in-Response-to-API-Events
    aws security
  • EC2 — Boto 3 Docs 1.4.0 documentation

    These are the resource's available collections:

    classic_addresses
    dhcp_options_sets
    images
    instances
    internet_gateways
    key_pairs
    network_acls
    network_interfaces
    placement_groups
    route_tables
    security_groups
    snapshots
    subnets
    volumes
    vpc_addresses
    vpc_peering_connections
    vpcs
    
    October 5, 2016 - permalink - http://boto3.readthedocs.io/en/latest/reference/services/ec2.html#service-resource
    aws boto
  • Aurora on Amazon RDS - Amazon Relational Database Service

    Pour un cluster Aurora donné, 3 endpoints :
    - cluster endpoint : pointe toujours sur le master
    - reader endpoint : pointe toujours sur un slave
    - instance endpoint : permet de pointer spécifiquement une instance donnée. Ne garantit pas que cette instance restera un slave ou un master.

    You can determine which DB instance in an Aurora DB cluster that a connection is connected to by checking the innodb_read_only global variable, as shown in the following example.
    SHOW GLOBAL VARIABLES LIKE 'innodb_read_only';
    The innodb_read_only variable will be set to ON if you are connected to an Aurora Replica and OFF if you are connected to the primary instance.

    October 3, 2016 - permalink - http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Aurora.html
    aurora aws mysql
  • minio/mc: Minio Client is a replacement for ls, cp, mkdir, diff and rsync commands for filesystems and object storage.

    via Doo

    September 30, 2016 - permalink - https://github.com/minio/mc
    aws s3
  • Quickstart — Boto 3 Docs 1.4.0 documentation
    September 29, 2016 - permalink - http://boto3.readthedocs.io/en/latest/guide/quickstart.html
    aws boto python
  • Note: Some useful AWS CLI oneliner

    Because terminal > web interface

    To briefly list all env (one env by line):
    aws elasticbeanstalk describe-environments|jq -r '.Environments|.[]| [.ApplicationName, .EnvironmentName, .VersionLabel, .Status, .CNAME] | @csv'|sort

    To get all info about one env (pass EnvironmentName):
    aws elasticbeanstalk describe-environments --environment-names toto-prod

    List all subnets:
    aws ec2 describe-subnets|jq -r '.Subnets|.[]|.SubnetId'

    List all ec2 instanceId:
    aws ec2 describe-instances|jq -r '.Reservations|.[]|.Instances|.[]|.InstanceId'

    List all ec2 instanceId with its associated subnetId:
    aws ec2 describe-instances|jq -r '.Reservations|.[]|.Instances|.[]|[.InstanceId, .SubnetId] | @csv'

    September 28, 2016 - permalink - https://links.infomee.fr/shaare/uMBmyg
    aws cli
  • Security in Your VPC - Amazon Virtual Private Cloud

    AWS, c'est un métier.

    September 27, 2016 - permalink - http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Security.html
    aws
  • Identities (Users, Groups, and Roles) - AWS Identity and Access Management

    Diff between user and role

    September 21, 2016 - permalink - http://docs.aws.amazon.com/IAM/latest/UserGuide/id.html
    aws iam
▼ Load 50 more