Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« AWS OpsWorks Now Supports Chef 11.10 | Main | AWS Week in Review - March 24, 2014 »


Feed You can follow this conversation by subscribing to the comment feed for this post.


"Java 6 (java-1.7.0-openjdk)" should be "Java 6 (java-1.6.0-openjdk) " (typo)

Bruno Belotti

Hi Jeff, here's a question for you: after the OpenSSL HeartBleed bug, I had to update my Elastic Beanstalk container (I created a new environment and I performed a "swap url"), choosing PHP as my platform (the more recent EC2 instance was AMI 2014.02).

My problem is: when I connect trough SSL to the server I still get:


I even tried to execute a "sudo yum update", but the server responded with "No packages marked for update".

Why is that? Am I doing something wrong?

BTW, I checked the openssl version... which is the "1.0.1e-fips 11 Feb 2013" but "built on: Mon Apr 7 23:39:44 UTC 2014".... Now I have no idea if my environment is secure and "bug free" or not.

As you can imagine, It's pretty frustrating...
Some tips?


The comments to this entry are closed.

Featured Events

The AWS Report

Brought to You By

Jeff Barr (@jeffbarr):

Jinesh Varia (@jinman):

Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30