Working with AWS OpsWorks recensioni

Sam L. · Recensione inserita circa 8 anni fa

度 下. · Recensione inserita circa 8 anni fa

Nikunj R. · Recensione inserita circa 8 anni fa

John G. · Recensione inserita circa 8 anni fa

J L. · Recensione inserita circa 8 anni fa

Rolando C. · Recensione inserita circa 8 anni fa

Saurabh S. · Recensione inserita circa 8 anni fa

Rexwell M. · Recensione inserita circa 8 anni fa

Ian Y. · Recensione inserita circa 8 anni fa

Muhammad A. · Recensione inserita circa 8 anni fa

Fabio M. · Recensione inserita circa 8 anni fa

Jayakumar K. · Recensione inserita circa 8 anni fa

Pierre-Alain M. · Recensione inserita circa 8 anni fa

Nathaniel S. · Recensione inserita circa 8 anni fa

Santosh Kumar K. · Recensione inserita circa 8 anni fa

Srinivas M. · Recensione inserita circa 8 anni fa

Excellent

Luis D. · Recensione inserita circa 8 anni fa

I don't mind a few typos and these lab guide labs are really good. This one, however, seems woefully out of synch with AWS: Under "Add your first stack," there is no step “1.” or “2.” before step 3, in the lab guide. Is it misnumbered or is something missing? The lab guide references Chef 11 and OpsWorks is at Chef 12. The lab guide references choosing the same region as the lab uses, but OpsWorks, in actual lab, indicates that OpsWorks in Global and does not require region selection. Step 9, Add a Layer, says "The Rails App Server layer type is already selected," but it's not. The lab guide says "leave all Rails-specfics settings as they are and click Add layer. There is no Rails-specific anything indicated. But "Name" and "Short name" are required fields. There is no mention of or reference to Rails in the actual lab on AWS. When I deployed and started the first layer, I got this: This site can’t be reached ec2-52-37-40-224.us-west-2.compute.amazonaws.com took too long to respond. ERR_CONNECTION_TIMED_OUT ---------- details from OpsWorks: Details page: Hostnamebrucerails1 Statusonline Layers Rails App Server layer for Bruce EC2 instance IDi-6682a2a1 OpsWorks ID02734a9e-0844-4e52-9312-0e7e48c10c46 Instance type24/7 Sizec3.large Subnetsubnet-2a4f0d4f 172.31.16.0/20 - us-west-2a Operating systemAmazon Linux 2015.09 Reported OSAmazon Linux 2015.09 OW Agent versionInherited from stack Reported OW Agent4008 (Mar 16th 2016) Changelog Tenancydefault Architecture64bit Virtualization typeparavirtual EBS Optimizedno Root device typeEBS backed Root device IDvol-cfb39978 Network and Security Public DNSec2-52-37-40-224.us-west-2.compute.amazonaws.com Public IP52.37.40.224 Private DNSip-172-31-30-159.us-west-2.compute.internal Private IP172.31.30.159 SSH key– Step 30 says change the laeyer type from HAProxy to MySql. There is no obvious apparent way to change Layer type and no mention of type on the Layers page of the layer detail page for my second layer. And... when I click "Add layer," it, again, wants me to add a Name and Short name. Step 37 says "Change the Data source type value from None to OpsWorks. It is none, but the other choice is "RDS." I changed it RDS and there is no database instance. At that point I gave up. I will retry the lab from scratch.

Bruce L. · Recensione inserita circa 8 anni fa

Sudo R. · Recensione inserita circa 8 anni fa

Dixon Jose P. · Recensione inserita circa 8 anni fa

Nikolai L. · Recensione inserita circa 8 anni fa

instances start and deployment are really slow

Igor F. · Recensione inserita circa 8 anni fa

David P. · Recensione inserita circa 8 anni fa

Wasawatt C. · Recensione inserita circa 8 anni fa

Bjoern S. · Recensione inserita circa 8 anni fa