Building Scalable Web Applications with AWS Elastic Beanstalk Reviews

Building Scalable Web Applications with AWS Elastic Beanstalk Reviews

2324 reviews

Camil S. · Reviewed about 8 years ago

Ricardo T. · Reviewed about 8 years ago

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].

Ian T. · Reviewed about 8 years ago

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

Paul R. · Reviewed about 8 years ago

Alan J. · Reviewed about 8 years ago

Peter L. · Reviewed about 8 years ago

This lab lacks details and the correct command.

Rayette T. · Reviewed about 8 years ago

Julien S. · Reviewed about 8 years ago

攀 舒. · Reviewed about 8 years ago

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.

Robert S. · Reviewed about 8 years ago

shunli z. · Reviewed about 8 years ago

Chris J. · Reviewed about 8 years ago

Alan P. · Reviewed about 8 years ago

jinlong l. · Reviewed about 8 years ago

Chris B. · Reviewed about 8 years ago

Mike S. · Reviewed about 8 years ago

Jesus B. · Reviewed about 8 years ago

Bob H. · Reviewed about 8 years ago

Steve H. · Reviewed about 8 years ago

Matt P. · Reviewed about 8 years ago

Roger G. · Reviewed about 8 years ago

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.

Dawn N. · Reviewed about 8 years ago

Stuart C. · Reviewed about 8 years ago

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

Homer D. · Reviewed about 8 years ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.