- Subject: Re: F16 AMI start-up configuration
- From: Max Spevack <mspevack@xxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Feb 2012 20:57:38 -0800 (PST)
- Delivered-to: cloud@xxxxxxxxxxxxxxxxxxxxxxx
- In-reply-to: <CAHhDTV=7Gnk_bTca9La=4ciBh+hP1aaMgO1Fx1hvOLYsaY6YMw@mail.gmail.com>
- References: <CAHhDTV=7Gnk_bTca9La=4ciBh+hP1aaMgO1Fx1hvOLYsaY6YMw@mail.gmail.com>
- Reply-to: Fedora Cloud SIG <cloud@xxxxxxxxxxxxxxxxxxxxxxx>
- User-agent: Alpine 2.02 (LRH 1266 2009-07-14)
On Wed, 15 Feb 2012, Franck wrote:
I'm trying to figure out where the start-up configuration on this AMI
is. I'm used to look at the rc.local file, where all the ec2
initialization used to be, but here there is no such file anymore. I
know, I could create the file and do whatever I was doing before, but
I would prefer to do it the new way. For example, the hostname is set
to the internal hostname. Where is it done now?
On a high level, the answer is that systemd calls cloud-init, which is
used in Fedora 16 AMIs to handle (among other things) taking the
instance metadata (like the ssh public key) and putting it in the right
place (~ec2-user/.ssh/authorized_keys).
You can see the results in /var/log/cloud-init.log
I'm poking around to find the exact place in the code where it handles
the ssh public key, but I haven't found it yet. I'm sure someone else
will chime in with that piece of info.
--Max
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
[Older Fedora Users Mail]
[Fedora Advisory Board]
[Fedora Security]
[Fedora Maintainers]
[Fedora Devel Java]
[Fedora Legacy]
[Fedora Desktop]
[ATA RAID]
[Fedora Marketing]
[Fedora Mentors]
[Fedora Package Announce]
[Fedora Package Review]
[Fedora Music]
[Fedora Packaging]
[Centos]
[Fedora SELinux]
[Fedora Triage]
[Deep Creek Hot Springs]
[Coolkey]
[Yum Users]
[Tux]
[Big List of Linux Books]
[Yosemite News]
[Yosemite Photos]
[Linux Apps]
[KDE Users]
[Fedora Tools]
[Fedora Art]
[Fedora Docs]
[Asterisk PBX]