Thanks for the tip! I'll look into it also. On Thu, Feb 28, 2019, 01:42 Igor Cicimov <[email protected]> wrote:
> Hi Eric, > > Great answers :-) ! However, if caching is not a requirement I would > recommend Haproxy for this task though, I'm sure you will find it much > easier to setup and use and more appropriate for the task in hand. > > On Thu, Feb 21, 2019 at 1:59 AM Eric Chaves <[email protected]> wrote: > >> Hi Igor, >> >> Great questions! The short answer: it allows me to handle integration at >> the edge of my networks. >> >> The long answer: >> >> The majority of our application runs in cloud-based solutions, some of >> them in serverless environments and even those who do require (virtual) >> servers (ie ec2 based) are dynamically allocated across a multiple >> regions/locations. On top of that some communications must follow a given >> route but other should be able to work in the actual IP network where they >> are. In this scenario the network design (ie network ranges, nat, routing >> tables, ip tables, vpn, etc) have too many moving parts. >> >> Since the majority of my integrations falls into two categories: >> Webservices (HTTP/REST/SOAP etc) and File Transfers (FTP, SFTP, FTPS). >> Those are all very well handled by proxies battled tested over years in >> high demanding scenarios and it's easier to setup in accordance with my >> integrations endpoint network requirements without actually incurring in a >> complex network design on my side. >> >> Caching is not a requirement, in fact it will hardly be used. But I need >> to have good management support, ability to growth in cluster modes and >> some other facilities where ATS (at a first glance) seems better than >> squid, which is why I'm giving ATS a shot. The Proxy does need to know nor >> handle anything specific to support my applications, it just need to do >> it's job. Everything else is on my application side =) >> >> Regards, >> >> Em qua, 20 de fev de 2019 às 00:28, Igor Cicimov < >> [email protected]> escreveu: >> >>> Eric, >>> >>> On Wed, 20 Feb 2019 6:56 am Eric Chaves <[email protected] wrote: >>> >>>> Nice! Thank you for answering! >>>> >>>> Em ter, 19 de fev de 2019 às 17:57, Jeremy Payne <[email protected]> >>>> escreveu: >>>> >>>>> i've configured putty to send traffic through ATS, same should work >>>>> for FTP. >>>>> your FTP client will just have to support using a HTTP proxy. >>>>> >>>>> On Tue, Feb 19, 2019 at 2:47 PM Eric Chaves <[email protected]> wrote: >>>>> > >>>>> > Hi Jeremy, thanks replying. I'm still working to have a basic >>>>> version working on my AWS infrastructure (I'm having a hard time to work >>>>> my >>>>> way around the logs, I confess) so I wasn't able to test much yet. =) >>>>> > >>>>> > Your point on manually setting the proxy on the my application's is >>>>> correct and are expected. >>>>> > >>>>> > Would you be able to confirm if the ATS knows how to handle the FTP >>>>> protocol, or is it HTTP "aware" only? >>>>> > >>>>> > Cheers, >>>>> > >>>>> > Em ter, 19 de fev de 2019 às 17:32, Jeremy Payne <[email protected]> >>>>> escreveu: >>>>> >> >>>>> >> CONNECT method should work here.. Have you tried that ? >>>>> >> Of course you'll have to explicitly set a proxy at the client end. >>>>> >> >>>>> >> >>>>> >> On Tue, Feb 19, 2019 at 12:46 PM Eric Chaves <[email protected]> >>>>> wrote: >>>>> >> > >>>>> >> > Hi Folks, >>>>> >> > >>>>> >> > I'm new to traffic-server and I'd like to evaluate it to be used >>>>> as a non-cache forward proxy between my application servers and some 3rd >>>>> partners servers. My applications server are dynamically allocated (AWS >>>>> EC2 >>>>> auto-scaled) but my partners services require us to reach them with a >>>>> single IP addres, hence the idea of using ATS. >>>>> >> > >>>>> >> > In my scenario one important feature is the ability to handle >>>>> other protcolos other than HTTP/S like FTP/S (and not required but desired >>>>> SFTP). >>>>> >> > >>>>> >> > I've scouted the ATS docs but didn't found any specific reference >>>>> for those other protocols. >>>>> >> > >>>>> >> > If possible I would like to hear from more experienced users if >>>>> ATS is a good choice for this use case and if can handle other protocols >>>>> than HTTP. >>>>> >> > >>>>> >> > Thanks in advance for any help, >>>>> >> > >>>>> >> > Eric >>>>> >>>> >>> Just out of curiosity, why ats? Why not something simpler, squid or >>> socat or even iptables on an ec2 instance will do the job as tcp proxy? Is >>> it caching the requirement? Also how good is ats in supporting dynamic >>> backends like constantly changing ec2 instances? Is it something custom >>> made taking care of it? >>> >>>> > > -- > > Igor Cicimov | Senior DevOps Engineer > > t +61 (1) 300-362-667 > > e [email protected] > > w www.encompasscorporation.com > > a Level 4, 65 York Street, Sydney, NSW, Australia 2000 > > > > follow encompass > > Blogs <http://bit.ly/2BgrjjJ> | LinkedIn <http://bit.ly/2sgXnkI> | > Twitter <http://bit.ly/2E8VtV1> >
