Building Scalable Web Applications with AWS Elastic Beanstalk (日本語版) のレビュー

Samaha Camil · 約8年前にレビュー済み

Triana Ricardo · 約8年前にレビュー済み

Broken again! 2016-02-12 18:07:21 UTC+1100 ERROR Failed to deploy application. 2016-02-12 18:07:20 UTC+1100 ERROR Service:AmazonCloudFormation, Message:Stack named 'awseb-e-mw8rcekq9q-stack' aborted operation. Current state: 'UPDATE_ROLLBACK_IN_PROGRESS' Reason: The following resource(s) failed to create: [MyElastiCache].

Timms Ian · 約8年前にレビュー済み

needed to log in a second time to the dev ec2 instance for it to run under the (py27) virtual environment - also v2 of the eb didn't deploy and was rolled back

Romanus Paul · 約8年前にレビュー済み

Jex Alan · 約8年前にレビュー済み

Landy Peter · 約8年前にレビュー済み

This lab lacks details and the correct command.

Toles-Abdullah Rayette · 約8年前にレビュー済み

Simon Julien · 約8年前にレビュー済み

舒 攀 · 約8年前にレビュー済み

Does not work as described. - The documentation is outdated. - Image is not configured properly, eb command missing due to missing awsebcli. - Python script could not be deployed successfully. Error Message. -.... Waste of time and credits.

Soellner Robert · 約8年前にレビュー済み

zhou shunli · 約8年前にレビュー済み

Jones Chris · 約8年前にレビュー済み

Philpott Alan · 約8年前にレビュー済み

liu jinlong · 約8年前にレビュー済み

Brunning Chris · 8年以上前にレビュー済み

Smialek Mike · 8年以上前にレビュー済み

Bonequi Jesus · 8年以上前にレビュー済み

Henkel Bob · 8年以上前にレビュー済み

Hummel Steve · 8年以上前にレビュー済み

Ploeger Matt · 8年以上前にレビュー済み

Grantham Roger · 8年以上前にレビュー済み

Time allotted made it difficult to complete. eb start took 19 minutes to complete. Then even though I answered y to deploy latest Git commit to the env, it deployed a 'Sample Application' instead. Finally got the correct application deployed using the UI, but then found that each config change took about 4 mins to deploy and the final update took another 9 mins to deploy. I also found that during step 32 the instance profile setup did not match instructions, as it stated I did not have sufficient permission. Also Step 41 was incorrect.

Nerud Dawn · 8年以上前にレビュー済み

Cracraft Stuart · 8年以上前にレビュー済み

There's an IAM permission issue that led to the super slow creation of resources.

Dong Homer · 8年以上前にレビュー済み