Questions tagged with Linux Provisioning
Content language: English
Sort by most recent
Hi Team,
One of my ec2 machine is memory under provisioned. Just wanted to know that what is the threshold value by default where instance say under provision or over provision. How much memory should be free for instance to run normally. Suggest any references to understand the limits where this under/over provisions trigger for instances
Hello,
do you have any Information on when AWS Elastic Disaster Recovery will support Ubuntu 22.04 LTS in the near Future? We got Production Critical On-Premise Linux Machines that need 2b replicated with AWS for Failovers.
A lot of the Servers are Ubuntu 20.04 LTS that work like a charm wit h the Service, but the Main Servers won't.
Would appreciate some update on this. Thanks in advance
I want to install cloudwatch on suse.
Could you help me please?
I am trying to determine if EC2 will let me create a VM with the OS Scientific Linux 6.x. I cannot seem to find an instance with that OS when creating one in the EC2 management console.
I've been sitting here waiting to SSH into my new instance for ten minutes and this thing is STILL installing. Why is it so painfully slow? This is insane.
Created in launch template with script:
```
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
```
How can I export and import EC2 Launch Templates, including version history and launch scripts (advanced)? Exporting to another EC2 account/region is not sufficient, I need a way to get them off AWS and stored locally.
Thanks!
I created several EC2 instances running Amazon Linux 2 a few weeks ago, all with SSH access. A few days ago, one instance stopped allowing SSH access with the message `ec2-user@10.0.145.93: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).` - an error message I'd expect to see if my SSH keys were invalid.
The instance is still running, and the cron jobs I configured on it are still running as normal. I don't have serial console to the instance but I was able to create an AMI and then a VMDK from the instance in its current state and mount the filesystem to attempt to figure out what's wrong. As far as I can tell all the SSH configuration is still as I configured it: all the correct keys are still present in `~/.ssh/authorized_keys` and the contents of `/etc/ssh/` are identical to a clean AL2 install.
The security groups haven't changed (they still allow SSH access) and the SSHD config is the same, so what is going on?
I'm developing a Java web application, based on Spring boot, which stores data in a MySql DB instance (single instance).
It's a "light" application, in terms of use of resources.
What I need is a virtual machine hosting a Linux Ubuntu installation, having the following features:
- Cpu with 4/8 core (no need for high clock rate).
- 8 GB RAM.
- 20 GB HD.
I don't need huge resources, as you see.
Moreover, the virtual machine has to run as ftp server.
Which is the solution that best fits my needs?
Thank you,
Andrea
I was creating a multi-player experience for quest using unreal engine and AWS because I saw https://aws.amazon.com/blogs/spatial/building-an-openxr-enabled-unreal-engine-vr-server-on-aws/ .
I created a aws account just because of this documentation for VR multi-player.
I followed the whole documentation uploaded linux.zip to my ec2 instance created apk for my 2 quest 2 devices and side loaded it with side quest.
But I have a problem when I open the map and press the connect button my position and the whole map just resets for both of my devices (Not at the same time but after few seconds) and they don't see each other and they don't even see the object interaction. In short words I don't think the multiplayer is working. There are no errors while building or launching the apk.
I am using Unreal Engine 5.1.1 and meta quest 2.
Thanks for reading and I would really appreciate everyone's help because I am not familiar with aws much and using it because I found this documentation.
If you need any other info do tell me.
If you are building an instance, and you search for an AMI with 'Ubuntu Mate', you get a collection of results that include 33 Marketplace and 1 Community. The Community AMI seems to come from Ubuntu themselves. It has an Ubuntu logo and a Verified Provider stamp. It is defined as:
Verified provider
Ubuntu Desktop 22.04 LTS - GUI Mate with VNC - v0822-852675f6-b132-4b36-844e-9bd39171a762
ami-0256fae9ba5c5a428
When I Select it, I get taken to an error: Instance launch failed In order to use this AWS Marketplace product you need to accept terms and subscribe. To do so please visit https://aws.amazon.com/marketplace/pp?sku=7vs4oeivly897ootc0hciswv6 Following this link, I am taken to another Ubuntu offering by Arara Solutions, which is an extra cost offering.
Why are these two items being confused? How can I install the version from Ubuntu themselves?
According to the documentation, this resource requires the following. The question I have is it possible add IAM policies to Role so that no AWS CLI configuration is required. I was able to get the fence_aws command to work with embeddeing AWS CLI config info by providing specific IAM policies.
- preconfigured AWS CLI running environment (AccessKey, SecretAccessKey, etc.)
# - a reserved secondary private IP address for EC2 instances high availablity
# - IAM user role with the following permissions:
# * DescribeInstances
# * AssignPrivateIpAddresses
# * UnassignPrivateIpAddresses
Getting below mentioned Warning Messages while trying to upgrade from CEDR to DRS in Linux System installed with AMI 2.0.
```
python3 cloudendure_to_drs_upgrade_tool.py start-upgrade --api-token <API Token> --project-id <ProjectID> —aws-access-key-id <AccessKey> —aws-secret-access-key <SecretKey> --import-blueprint --import-replication-configuration --import-test-snapshot
Running the CloudEndure to DRS Upgrade tool.
Connecting to the CloudEndure Console... Finished.
Warnings:
- Unable to detect if the Machine's operating system is supported by DRS.
Refer to DRS documentation for the list of supported operating systems (UnableToDetermineOperatingSystemSupport)
- Unencrypted volumes are not supported in DRS.
It is recommended to set an explicit encryption key in your Replication settings prior to performing the upgrade.
Machines with no volume encryption configured will be converted to use the default EBS encryption key in DRS. (UnencryptedVolumesUnsupported)
There are warnings for this machine. Would you like to continue? [Y/n]:n
```
As per below mentioned AWS Doc AL 2.0 is supported by DRS:
[https://docs.aws.amazon.com/drs/latest/userguide/Supported-Operating-Systems.html
]()
Moreover I have set Default key for EBS Volume Encryption in both CEDR and DRS Service.
What should I do fix these warning signs besides the steps which I have taken?