Bug 800439

Summary: Add capability to run user scripts from userdata in RHEL AMIs
Product: Red Hat Enterprise Linux 5 Reporter: Chris Morgan <cmorgan>
Component: relengAssignee: Jay Greguske <jgreguske>
Status: CLOSED CANTFIX QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9CC: atodorov, jgreguske, tkopecek
Target Milestone: rcKeywords: EC2
Target Release: 5.9   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-31 09:12:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Chris Morgan 2012-03-06 13:47:22 UTC 
Request from Amazon:

We have a request from a customer to have RHEL AMI output the ssh fingerprints to the console on boot.  This allows our customers to verify that the host they are ssh'ing to is the same host that is in their account in the console.  We also recommend this to customers in the EC2 User Guide:
http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html

The customer would have setup a script to output these himself but the RHEL amis don't currently have a mechanism to run user scripts from the userdata.

---------------------

Would like to target this for any future regions (add it to all AMIs) and for existing regions, only add it to new versions of RHEL.
Comment 1 RHEL Program Management 2012-04-02 11:21:04 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 2 Jay Greguske 2012-05-21 17:06:34 UTC 
Note that this bug is solved with use of the cloud-init package.
Comment 4 Tomas Kopecek 2012-10-31 09:12:49 UTC 
According to e-mail communication cloud-init will not be available for RHEL5 at all. Supported will be only RHEL6+ distros.