89. How we chose AWS We were using another cloud hosting service provider.
90. How we chose AWS We were using another cloud hosting service provider. We were having availability problems due to the cloud service’s instability.
91. How we chose AWS We were using another cloud hosting service provider. We were having availability problems due to the cloud service’s instability. Our quick fixwas to do a 1:1 migration.
92. How we chose AWS We were using another cloud hosting service provider. We were having availability problems due to the cloud service’s instability. Our quick fixwas to do a 1:1 migration. We migrated our first region to AWS January 16, 2011, and finished moving the last region at the beginning of April 2011.
93. How we chose AWS We were using another cloud hosting service provider. We were having availability problems due to the cloud service’s instability. Our quick fixwas to do a 1:1 migration. We migrated our first region to AWS January 16, 2011, and finished moving the last region at the beginning of April 2011. We went from a classical stack in the cloud, to a classical stack in AWS.
94. How we chose AWS We went from a classical stack in the cloud, to a classical stack in AWS.
123. Not able to use only Simple Email Service, attachments via Postfix
124. Multiregion connecting to an RDS instance from one AWS region (US West to EU West) is not possible, so it’s not possible to backup databases: administration of AWS is per AWS region
125. Loadbalancing: No backend loadbalancing (e.g. db), setting up ssl certs on loadbalancers is not straightforward, configuration of loadbalancers is very simplistic
126.
Editor's Notes
----- Meeting Notes (5/13/11 13:28) ------ each region is separate aws account because we aren't using iam ("eye-m")- four regions in EU, 1 in South America-
EBL ReadLatency: Time taken between a request and the corresponding response as seen by the LoadBalancer.RDS ReadLatency: The average amount of time taken per disk I/O operation.