I'm running a CLI on an EC2 server (Amazon Linux image), which I let run indefinitely with the screen terminal multiplexer. My program queries an API continuously and logs the current state to stdout:
The CLI logs encounters error occasionally, and it logs them, but when I SSH back into the EC2 server and recover the screen session, I see the latest logs only.
How can I keep track of everything printed to stdout, so I can inspect them later? CloudWatch?
Here's what happened:
However, if I open any page on my blog now, it takes more than 10 seconds to load. In my admin dashboard, I can't make any edit - it returns server errors every time I hit save.
I know that there can be many reasons for the cause of this lag, but I thought to ask this question in case this is a common problem? Is the AWS System Manager known to cause this lag to EC2 instances after an automation flow is executed?
I'm running a t2.micro Ubuntu 18.04 machine in the "eu-west-2" region.
The question is about Amazon CloudFront.
The names in the title refer to two types of settings. The former can be edited via the "Origins and Origin Groups" tab, while the latter via the "Behaviors" tab.
What is the difference between the two? Do they influence one another in any way?
I created an EC2 instance on AWS, and I was assigned a default "security group". I understand that this acts as a virtual firewall for my server.
I had trouble connecting into this EC2 instance using SSH, and it turned out that the issue was not setting the "Source" to 0.0.0.0/0 in the security group's "Inbound Rules", as shown in the image below.
Is it safe to keep it like this or should I restrict the source to the IP of my home network?
Nobody can ssh into my EC2 instance without the *.pem file, right?
