-
EC2 — Boto 3 Docs 1.4.0 documentation
5 octobre 2016 à 10:05:58 UTC+2 - permalink -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
-
http://boto3.readthedocs.io/en/latest/reference/services/ec2.html#service-resource
-
Aurora on Amazon RDS - Amazon Relational Database Service
3 octobre 2016 à 16:01:46 UTC+2 - permalink -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.
-
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Aurora.html
-
Note: Some useful AWS CLI oneliner
28 septembre 2016 à 10:56:53 UTC+2 - permalink -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'|sortTo get all info about one env (pass EnvironmentName):
aws elasticbeanstalk describe-environments --environment-names toto-prodList 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'
-
https://links.infomee.fr/?uMBmyg
-
Getting Credential Reports for Your AWS Account - AWS Identity and Access Management
21 septembre 2016 à 11:16:54 UTC+2 - permalink -To generate a report
- :
In addition to using credential reports, you can also determine when a password or access key was last used by using these IAM APIs:
ListUsers (AWS CLI command: aws iam list-users)
GetUser (AWS CLI command: aws iam get-user)
GetAccessKeyLastUsed (AWS CLI command: aws iam get-access-key-last-used)
-
http://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_getting-report.html
-
![thumbnail]()
Release Notes : Amazon Web Services
31 août 2016 à 14:03:39 UTC+2 - permalink -les releases notes de l'ecosysteme aws
(rss ok)
-
https://aws.amazon.com/releasenotes
-
IAM Best Practices - AWS Identity and Access Management
31 août 2016 à 11:32:26 UTC+2 - permalink -Premières choses à faire, best practice concernant iam. En résumé : ne pas générer d'access key pour l'utilisateur "root", créer des users avec des droits bien determinés.
-
http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html
