New answers tagged

2

On-premises hardware or software is installed and runs on the premises of the person or organization using the service Colocation is software or hardware is installed and runs outside the premises of the person or organization using the service.


3

From my personal experience, On-premises and Colocation are similar in that the customer owns the equipment that is in question. The difference is where the equipment is located at. On-premises implies that the equipment is at a location that the company in question owns/rents/leases. It is physical equipment in one of their physical locations. ...


0

After much research, I realized that .pyd files (which is the file type of the file that was being ignored) are basically (very roughly) .lld files with some imbedded python, so that they can be used by python programs. So, I replaced the .pyd file with a supposedly equivalent .pyx file, which I'm fairly certain is the same file, precompilation. But, that ...


2

If you have an EC2 instance, you could schedule it using cron. If you want to use AWS in general, I suggest that you use Lambda with scheduled events. The first method needs you to have running infrastructure (an EC2 instance), but is easier. The second method has a bit of a learning curve.


0

You could setup a VNC server perhaps by following these instructions.


1

Spamd is not something which is scheduled. Its run whenever a process calls it. There is no simple bullet, and a lot of the answer is "it depends on your setup", but (assuming you have a normallish email server/user profile) you can greatly drop the amount of email your server needs to process by introducing grey-listing. (Greylisting is a lightweight way ...


0

My environment is have a homestead to work with Laravel, but I'm using Vagrant Box, so I have this problem, the solution that I found was: Works for me: vagrant reload --provision Inside the folder Homestead.


1

The most easiest way to setup Apache on an EC2 instance is to configure a script that will download and launch during instance start. Here is an example: #!/bin/bash yum update -y yum install httpd -y service httpd start More detailed instruction about how to do it is here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html


0

You haven't launched any instances to be in your cluster, but I think you'd still be able to see the cluster in the ECS manager. I started working from this file: https://github.com/Capgemini/terraform-amazon-ecs/blob/master/ecs.tf Where there is an Autoscaling group that launches instances for the cluster, and uses user_data to mark the machine as part of ...


0

Log-in to Amazon Web Services and check the followings: Security Group for your instance is allowing Inbound SSH access (check: view rules). For VPC instance, check its attached Route table which should have 0.0.0.0/0 as Destination and your Internet Gateway as Target. Double check your route info in System Log in Networking of the instance. For more ...


0

Just a silly question: Are you using the same IP address to ssh to this instance ? Because when you stop an instance and start it again, it gets a completely new IP address.


1

Are you trying to telnet one of your company's web server on the public subnet or on the Internet/corporate network ? If you are trying to telnet an instance (your web server) within the same VPC and the same subnet. And if the security group of your VPC is not the default, you need to add the rule to allow that security group. (the default security group ...


1

The error message suggests you in the incorrect region. According to the AWS documentation you need to specify a zone. You do this with the option flag -z zonename. In your instance I think it would be -z eu-west-1, I am not familiar enough with the Amazon platform to confirm the zone. According to further research in addition to specifying the zone you ...


0

Assuming you can reach the site over the internet using www.tempurl.com and that emails are currently working, then you should be able to just update the DNS A record for the production host to point to the new IP address and DON'T change the existing MX records. You also want to keep in mind the fact that if you do not use elastic IP on AWS, then your ...



Top 50 recent answers are included