Squid
Please feel free to contact us
Go
Please feel free to contact us
Go
Squid is a multipurpose caching and forwarding proxy server built mainly to serve HTTP and FTP requests. It extends its capability to support other protocols like SSL, TLS, HTTPS, and Internet Gopher, though with limitations. It was designed to exploit the internet connection for speedy content delivery. Squid also supports building cache server hierarchies with its ability to route requests in various ways. It has the ability to act as a reverse proxy cum webserver accelerator.
You can subscribe to Mediawiki, an AWS Marketplace product and launch an instance from the Mediawiki product’s AMI using the Amazon EC2 launch wizard.
Step 1: Open port 3128 in security group while launching a instance.
Step2: Open putty and connect with your machine. Add IP address of the running EC2 instance.
Step 3: Login with user name “ubuntu”
Step 4: Configuring Squid as an HTTP Proxy on Ubuntu
If you wish to allow only one IP address to access the internet through your new proxy server, you will need to define new acl (access control list) in the configuration file.
sudo vim /etc/squid/squid.conf
The acl rule you should add is:
acl localnet src your_server_IP
Where 192.168.0.102 is the IP address you should change it according to your IP address. This acl should be added in the beginning of the ACL’s section as shown in the following screenshot.
You will need to restart Squid service to take the new changes into effect.
sudo systemctl restart squid
Open Ports in Squid Proxy
By default, only certain ports are allowed in the squid configuration, if you wish to add more just define them in the configuration file as shown.
acl Safe_ports port XX
Where XX is the port number that you wish to allow.
sudo systemctl restart squid
Step 5: Squid Proxy Client Authentication
To allow users to authenticate before using the proxy, you need to enable basic http authentication in the configuration file.
Now we will create a new user and setup its password.
sudo htpasswd /etc/squid/passwords username
Provide a username and password of your choice
sudo systemctl restart squid
Step 6: Block Websites on Squid Proxy
To block access to unwanted websites, first create a file called “blacklisted_sites.acl” that will store the blacklisted sites in it.
sudo touch /etc/squid/blacklisted_sites.acl
Now add the websites that you wish to block access, for example.
.badsite1.com
.badsite2.com
The proceeding dot informs squid to block all references to that sites including www.badsite1, subsite.badsite1.com etc.
Now open Squid’s configuration file.
sudo vim /etc/squid/squid.conf
Just after the above ACLs add the following two lines:
acl bad_urls dstdomain “/etc/squid/blacklisted_sites.acl”
http_access deny bad_urls
Now save the file and restart squid:
sudo systemctl restart squid
Step 7: Connecting through Squid
curl -v -x http://your_squid_username:your_squid_password@your_server_ip:3128 http://www.google.com/
It is also possible to access https:// websites with your Squid proxy
curl -v -x http://your_squid_username:your_squid_password@your_server_ip:3128 https://www.google.com/
Enjoy your Appliation.
All your queries are important to us. Please feel free to connect.
24X7 support provided for all the customers.
We are happy to help you.
Submit your Query: https://miritech.com/contact-us/
Contact Numbers:
Contact E-mail:
Amazon EC2 enables “compute” in the cloud. Amazon EC2’s simple web service interface allows you to obtain and configure capacity with minimal friction. It provides you with complete control of your computing resources and lets you run on Amazon’s proven computing environment. Amazon EC2 reduces the time required to obtain and boot new server instances to minutes, allowing you to quickly scale capacity, both up and down, as your computing requirements change. Amazon EC2 changes the economics of computing by allowing you to pay only for capacity that you actually use.
Until now, small developers did not have the capital to acquire massive compute resources and ensure they had the capacity they needed to handle unexpected spikes in load. Amazon EC2 enables any developer to leverage Amazon’s own benefits of massive scale with no up-front investment or performance compromises. Developers are now free to innovate knowing that no matter how successful their businesses become, it will be inexpensive and simple to ensure they have the compute capacity they need to meet their business requirements.
The “Elastic” nature of the service allows developers to instantly scale to meet spikes in traffic or demand. When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.
Amazon EC2 allows you to set up and configure everything about your instances from your operating system up to your applications. An Amazon Machine Image (AMI) is simply a packaged-up environment that includes all the necessary bits to set up and boot your instance. Your AMIs are your unit of deployment. You might have just one AMI or you might compose your system out of several building block AMIs (e.g., webservers, appservers, and databases). Amazon EC2 provides a number of tools to make creating an AMI easy. Once you create a custom AMI, you will need to bundle it. If you are bundling an image with a root device backed by Amazon EBS, you can simply use the bundle command in the AWS Management Console. If you are bundling an image with a boot partition on the instance store, then you will need to use the AMI Tools to upload it to Amazon S3. Amazon EC2 uses Amazon EBS and Amazon S3 to provide reliable, scalable storage of your AMIs so that we can boot them when you ask us to do so.
Or, if you want, you don’t have to set up your own AMI from scratch. You can choose from a number of globally available AMIs that provide useful instances. For example, if you just want a simple Linux server, you can choose one of the standard Linux distribution AMIs.
Traditional hosting services generally provide a pre-configured resource for a fixed amount of time and at a predetermined cost. Amazon EC2 differs fundamentally in the flexibility, control and significant cost savings it offers developers, allowing them to treat Amazon EC2 as their own personal data center with the benefit of Amazon.com’s robust infrastructure.
When computing requirements unexpectedly change (up or down), Amazon EC2 can instantly respond, meaning that developers have the ability to control how many resources are in use at any given point in time. In contrast, traditional hosting services generally provide a fixed number of resources for a fixed amount of time, meaning that users have a limited ability to easily respond when their usage is rapidly changing, unpredictable, or is known to experience large peaks at various intervals.
Secondly, many hosting services don’t provide full control over the compute resources being provided. Using Amazon EC2, developers can choose not only to initiate or shut down instances at any time, they can completely customize the configuration of their instances to suit their needs – and change it at any time. Most hosting services cater more towards groups of users with similar system requirements, and so offer limited ability to change these.
Finally, with Amazon EC2 developers enjoy the benefit of paying only for their actual resource consumption – and at very low rates. Most hosting services require users to pay a fixed, up-front fee irrespective of their actual computing power used, and so users risk overbuying resources to compensate for the inability to quickly scale up resources within a short time frame.
No. You do not need an Elastic IP address for all your instances. By default, every instance comes with a private IP address and an internet routable public IP address. The private address is associated exclusively with the instance and is only returned to Amazon EC2 when the instance is stopped or terminated. The public address is associated exclusively with the instance until it is stopped, terminated or replaced with an Elastic IP address. These IP addresses should be adequate for many applications where you do not need a long lived internet routable end point. Compute clusters, web crawling, and backend services are all examples of applications that typically do not require Elastic IP addresses.
You have complete control over the visibility of your systems. The Amazon EC2 security systems allow you to place your running instances into arbitrary groups of your choice. Using the web services interface, you can then specify which groups may communicate with which other groups, and also which IP subnets on the Internet may talk to which groups. This allows you to control access to your instances in our highly dynamic environment. Of course, you should also secure your instance as you would any other server.
Load Distribution between interacting hierarchies of servers
Advanced Content Routing Configuration
Advanced Client Access Control Options
Key Performance Parameters Tracking
Data flow Optimization
Squid 
linux