Questions tagged with Amazon EC2

Hello, for production on an EC2 machine, I usually associate an Elastic IP address with it. There are a lot of clients connecting to that address. If I lose this Elastic IP address (wrong manipulation, errors, etc...), I will never be able to find the same address and I will have to update all the clients to give them the new Elastic IP address? What are my options to avoid this? Thanks for your helplg...

I believe I'm correct when I identify the following services as compute services: - EC2 - Elastic Compute Cloud - ECS - Elastic Container Service - ECR - Elastic Container Registry - EKS - Elastic Container Service for Kubernetes - AWS Elastic Beanstalk - AWS Lambda - AWS Batch - Amazon Lightsail My question is, are there other AWS services that are considered to be compute services?lg...

I have a EC2 instance running on RHEL 7.9 with one volume /dev/xvda. I am not a linux admin. I just know some basic stuff. How do I move /var & /home directory into separate partition? I have to do this due to some requirement. What would be the impacts by doing so?lg...

Team, Please suggest if we can install the Office 365 premium license on EC2 Windows 2022 datacenter edition. We already have office 365 business premium license in place.lg...

Can a container be considered a compute service?lg...

I'm trying start instance remotely in code, because all I need are two apis StartInstances and StopInstances so don't really want to install the sdk. So I followed the example here: https://docs.aws.amazon.com/general/latest/gr/sigv4-signed-request-examples.html#sig-v4-examples-post replaced with my own credentials and the parameters listed here: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_StartInstances.html but i'm still getting this error: Could not find operation StartInstances for version 2016-11-15 Any idea why it's throwing this error?lg...

What am I running? * EC2 instance Ubuntu 22.04 with a static elastic ip address * The instance has only one network interface, whose details say it is an Elastic network interface. (I believed every instance has a primary network interface, but I do not see any PNI). What I want to do? My company has an on-prem virtual machine running MSSQL server at 192.168.181.75:1433, but that is behind the globalprotect VPN from Palo Alto Networks. Even when I make a call to that database, I have to connect to global protect manually from my laptop. So my question is, is there any special step I need to take to make the EC2 part of the globalprotect network? I talked to my company network administrator, who want the public IP address of the EC2 instance (which I use for SSH) and the mac address. I got the mac address by entering ``` $ ip addr ``` in the terminal, under the *ens3* interface. But can I assume these two will remain fixed across stopping and restarting the instance? Also, the inbound/outbound rules have to be altered? Some readings led me to believe I have to create an ENI, as the primary network interfaces do not support it. But when I checked the instance details, it seems the only interface present is an ENI.lg...

My api service was up and running on the ec2 instance but suddenly started throwing error message: {"status":false,"message":"failure","result":{"code":0,"message":"Request failed with status code 451","data":{}},"responseCode":500} while any user trying to re-login. The API is allowing new users to register but not allowing to login back. I fear is it something https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/451. If yes how can I verify?lg...

Hello everyone, I have a webapp on production and here are my configs: * OS is Amazon Linux 2 * Backend hosted in my EC2 with a CodeDeploy pipeline between AWS and Github * I have an elastic IP Address * Webapp has a website and a mobile app * Frontend is hosted in another EC2 instance * I have a script in my backend that does the automation of the build and deployment each time I push to GitHub I wanted to do some minor changes to my backend but I could not due to glibc as shown in the image bellow https://preview.redd.it/3wmkhably83a1.png?width=1537&format=png&auto=webp&s=7c1a34ef09598482dd628ed93715a6b5eddf6353 After research I found out that Amazon Linux 2 does not update the libraries that are needed by node as shown in this link: https://repost.aws/questions/QUrXOioL46RcCnFGyELJWKLw/glibc-2-27-on-amazon-linux-2 Now I am thinking of installing a new OS in my EC2 and I do not quite see all risks that might affect my clients. Any suggestions ?lg...

I am doing a lift and shift with software from an on-premises architecture. There are two servers (main and auxiliary) that have to talk to one another over the network. I currently have tested and confirmed that I can manually add their hostnames and private IP address to the hosts file (`"C:\Windows\System32\drivers\etc\hosts"`) and the software works fine. For those that don't know, this file is used by Windows to map a network hostname like `EC2AM-1A2B3C` to a IP address. So if I added the hostname and IP address of the main server into the hosts file of the auxiliary server, then the auxiliary server could route to the main server. (i.e. `PS> ping EC2AM-1A2B3C` would then work). How could I pass the required information to both servers? They both have to know the other server's private IP address and hostname. If this is not possible at server spin-up time, how might the servers connect and pass this information? I would really like to automate this if possible.lg...

My website was down from the last night and when we checked in the morning we could not login to the EC2 server with our SSH. Our website is built on Elementor and we checked our health status and it seems to work fine.lg...

I have a scary situation that is currently unfolding. Our production server, which has been running for nearly three years, suddenly terminated itself. We have no idea why or more importantly how since the instance had termination protection enabled. As soon as I learned the server was down I checked the details in AWS and saw that somehow termination protection had been changed to disabled. How is any of this possible? Why would an instance terminate itself? Isn't the point of termination protection to make sure this doesn't happen? I've now got a production environment completely offline and I have no idea why. I'm fortunate that my senior developers were able to jump right in, but they are not AWS experts. So who knows how long it will take to get everything back online. I'd just really like to know how this could happen. Especially with the amount of money I pay each month. I'm just dumbfounded.lg...