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.

C-A
:swap-window -t 0

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.

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

ça a l'air un peu plus compliqué qu'avec irc à première vue

living in the windows side is a pain

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

via Doo

via Doo

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'