Re: AWS has surrendered!
Re: AWS has surrendered!
- Subject: Re: AWS has surrendered!
- From: Theodore Petrosky <email@hidden>
- Date: Mon, 24 Oct 2016 14:09:50 -0400
It looks like I stumbled on the same method as you. I took that script and started editing. I wanted apache 2.4 and an updated JavaMonitor and wotaskd.
what was nice actually is that I learned a lot about the system and where WO wants things.
I have to think about editing the wiki page a little as some of the information is outdated. the script is referenced on Simon’s AWS S3 instance. If they turn that off, it all goes away so we should think about a home for the script and the information needed to edit it.
On Oct 24, 2016, at 5:37 AM, Paul Hoadley < email@hidden> wrote:
Hi Ted, On 24 Oct 2016, at 1:00 AM, Theodore Petrosky < email@hidden> wrote: I feel I have a grip on what is going on!! I followed the wiki mostly, but there were problems.
Congratulations.
Can you list the wiki page(s) you were following, and the problems you encountered? Maybe we could update them.
If I recall correctly, that’s some rather old work from Simon McLean—but that’s where I started as well. To this day, we still deploy our apps with a (now heavily modified) version of that script.
security seems good. your instance runs on an internal IP and you attach an Elastic IP (static). you can set security to only allow traffic on port 80 and 443 and in my case I added port 56789 from my IP only.
That’s a good idea, though if your IP address isn’t static, you can avoid constantly changing the security group by tunnelling over SSH:
That will tunnel local 56789 over SSH to the remote’s 56789, security group doesn’t need to know anything about it. JavaMonitor is then at:
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden