Questions tagged with Amazon EC2
Content language: English
Sort by most recent
when I scan my ec2 machine using aws patch manager, I am getting this error [ERROR]:**Error loading entrance module.** Traceback (most recent call last): File "/var/log/amazon/ssm/patch-baseline-operations/common_os_selector_methods.py", line 125, in _get_snapshot_info ssm_client = client_selector.get_default_client(instance_id, region, "ssm") File "/var/log/amazon/ssm/patch-baseline-operations/patch_common/client_selector.py", line 61, in get_default_client
My understanding is that all lightsail instances are [burstable CPU instance types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances.html). Normal EC2 burstable instances can be launched in [unlimited mode](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-unlimited-mode.html) for workloads that require high CPU at times and would prefer to pay for overages rather than get slowed down. Is this possible in Lightsail or would one have to move the instances into normal EC2/EBS deployments? It's unclear if account-level [default credit specifications](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-how-to.html#burstable-performance-instance-set-default-credit-specification-for-account) apply to Lightsail instances, although I'd assume not.
![Enter image description here](/media/postImages/original/IM__8iOu_3R-CdbhGNHatH4g) At the moment I can't change the instance type even when the instance is stopped. Can you enable this option? Thank you in advance.
hi, Does anyone know why the private IP address of the MWAA web server keeps changing time to time? Example: i have an AWS MWAA environment and i created a DNS record in route53 against the IP address i get after running the dig command against the web server hostname, but the url stops working after few days and when i check the dig command again, i get a new IP. Any help would be great. Thanks.
Hi I recently created a new EC2 Linux t2.micro instance and have downloaded the necessary resources to run a Minecraft server on it. However, while running the server, it starts loading, and within a minute the instance becomes unresponsive. I am then unable to perform any commands or SSH into it until I restart it. Does anyone have an idea as to what might be going on? Is it that the server doesn't have enough resources to run the server? I have run a Minecraft server on a t2.micro Windows instance before, and that worked fine, so I assumed Linux would be okay too. Any help would be much appreciated.
I want to import an ami, I have followed all everything right on https://docs.aws.amazon.com/vm-import/latest/userguide/vmie_prereqs.html#vmimport-operating-systems and even watched a youtube tutorial yet everytime I try to import the ami it is stuck on progress 39 and doesn't do anything even if I wait for hours. Can I have some help?
Hi all! We have a t3.2xlarge EC2 instance running Windows Server 2019 in the Europe (Frankfurt) region. We want to downsize it to a t3.xlarge, but this is refused with the following error message: "Failed to modify instance type for instance xxxx. The instance configuration for the AWS Marketplace product is not supported. Please see the AWS Marketplace site for more information about supported instance types, regions, and operating systems." I can succesfully change it to a m5.xlarge, so I don't understand why not to a t3.xlarge. I'm doing this from the web interface. I've looked into different documentation pages about this type of instances but cannot find this limitation. Any advice would be welcome. I thank you in advance.
Hello, I have a g4dn.4xlarge running Ubuntu and DCV: - Ubuntu 22.04.2 LTS - DCV Viewer: 2022.2 (r5125) - DCV server version 2022.2 (r14126) - 850b597893b7e9e1fa41688e06be0e9561708670 I'm trying to use multiple displays on my DCV client running on Mac OS Monterey. When I do View -> Fullscreen all Monitors, the DCV window seems to try to go to fullscreen on the monitor it's active on, then automatically exits fullscreen, but nothing happens on the other monitor. DCV gives me this error: > Exiting fullscreen mode: Server and client monitor layout do not match. Server: [0,0 1776x984] Client: [0,0 1440x900], [1440, 106 1920x1080] I saw this page: https://www.ni-sp.com/support/nice-dcv-tips-and-tricks/#h-how-to-enable-multi-monitor-on-nvidia-gpus And the section: How to enable multi-monitor on nVidia GPUs. I followed the instructions there but still can't get multiple displays working. I'd be grateful for any guidance. Thanks Ean
I've deployed two containers, one for my frontend which is react, and another for my flask backend. I run them with docker-compose file which specifies the necessary instruction for the communication. The workflow is working well on my local host, but on ec2, the front is not connecting or sending any requests to the backend. ![Here are my inbound rules for ec2 instance](/media/postImages/original/IMdf_5e4PLSpu_Vs_diI3Bbw)
Hi :) I am currently trying to resolve an issue with our ECS EC2-based cluster. Our Task definitions utilize the container-level soft CPU limit (set to 50 CPU units), but dont utilize the hard CPU limit from task-definition level. In our case we have more than 2000 services running, each one with a single task. These tasks have new revisions being re-deployed at a very high rate and at the same time, and upon startup they often reach levels of CPU usage above 1000%. This causes the whole EC2 instances to become unresponsive, resulting in a need to restart the whole machine. This we have solved with an alarm and a lambda for quickly rebooting failing, unresponsive instances. But this is not a solution, only a temporary fix. What we would like to achieve is to somehow limit the CPU usage of each task to not exceed the soft limit by factors of 10 or more. I have found a way to do it using the hard CPU limit, but this solution is also not great, mainly for the following reasons:* 1. Our tasks even with the soft limit use at most 50% of this reservation, but the hard limit's minimum value for ECS with EC2 is 128 units (compared to current 50) 2. The hard limit automatically increases the reservation value for the chosen task, meaning that setting the limit to 128 for all 2000+ servcies/tasks would require us to host more than double the amount of EC2 machines, without an actual gain, as our cluster's usage right now hangs around 5-10%. So my question is, is there a way to somehow limit the maximum cpu usage of each task/container without using the task-level hard limit? Our EC2 machines are running on Ubuntu
Is there a way to pre-configure an instance type change for an EC2 instance so it happens automatically after the next reboot? Kind of like changes to RDS can set to be executed at the next maintenance interval. The instances are not in an Autoscaler group and they're all one-of-a-kind, various types / AMIs / OSs and whatnot... a CLI option would be amazing, but if I have to click through all of them, so be it. Thanks, Marc