Questions tagged with Linux Provisioning
Content language: English
Sort by most recent
Cannot SSH into Resized EC2 Instance
Hi all, I have been working on deploying an application on an EC2 instance (ubuntu 22.04) and have ran into some issues with ssh'ing back into the server after a restart. I take it that the associated volume is fine, as I'm able to migrate and mount it to other EC2 instances with my .pem file and get in via ssh without issue. I have verified that this pem file is valid, as well as that it is the relevant one for this specific instance. I've included a picture of the verbose errors I've received when trying to ssh, and am happy to provide more granular details if needed.![Enter image description here](/media/postImages/original/IMMvT3wf5fRqyQ6pLE0wwjAA).
container selinux policy support in ECS task definition
HI, We are using Amazon Linux 2 AMI for ECS machine. seLinux enabled at host level. But not clear on how to implement the selinux policies at container level in task definition. Steps followed to install container linux: $ sudo yum update -y $ sudo amazon-linux-extras enable selinux-ng $ sudo amazon-linux-extras install selinux-ng $ yum install container-selinux Can you confirm if it is supported or not? If supported please guide on the steps to create selinux policy and apply the same at the container level using ECS task definition. Thanks in advance.
Error while exporting an instance
Hello I'm trying to export an instance but i got this error : An error occurred (NotExportable) when calling the CreateInstanceExportTask operation: This instance has multiple volumes attached. Please remove additional volumes. i've checked and there is 3 storages attached to the VM. i don't know what are the use of the 2 others. Someone can help me please.
Failed to identify volume with AWS Replication Agent
![Enter image description here](/media/postImages/original/IMH-zXnQe-RWC2LzlkIF6V4g) I want to rehost DB to EC2 using MGN. After running the installer command for Replication Agent, i got this error "Failed to identify volume with AWS Replication Agent". This server is 1 of 2 nodes of Oracle DB clustering. Oracle Linux 6.2, Oracle DB 11.2 Standard kernel 2.6.32-300.3.1.el66uek.x86_64 Has anyone encountered this error yet? Thank you advance for your helping
Instance reachability check failed
Hi In the Instance status checks show "Instance reachability check failed" and I am unable to SSH to the Instance. The AWS Compute Optimizer was throwing an error in EBS for reading and write bandwidth, so I decided to upgrade the instance from t2.medium to t3.large, also the hard drive from 8GB to 16GB to gp3. Now It shows Running. But in Status checks, Instance status check shows "Instance reachability check failed". The instance was working fine a few days back. I tried rebooting instance. It doesn't reboot. I start stop and start, that works and shows Running, but same instance status check issue. I tried rescue option mentioned in https://aws.amazon.com/premiumsupport/knowledge-center/ec2-instance-boot-issues/, but still the same issue. Here is the system log ` [ 12.483121] </TASK> [ 12.485967] Kernel Offset: 0x10600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 12.497046] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]--- `
EC2 instance can't connect to AWS SecretManager via private IP
When debugging a startup issue in our ElasticBeanstalk container, my startup was hanging on `aws secretsmanager get-secret-value --secret-id=[redacted] --region='us-east-1'`. It would hang indefinitely and not give me any "denied" message or any other indication that I had a permission issue in SecretsManager. I narrowed the issue down to reachability to SecretsManager when I discovered that I couldn't even telnet to SecretsManager via `telnet secretsmanager.us-east-1.amazonaws.com 443`. It wouldn't even connect. I then noticed that it was resolving SecretsManager's IP to an IP that is internal to our VPC. Updating `/etc/resolv.conf` to use another DNS provider switched the IP address and we were able to connect no problem. I am moving forward with a fix that will add a static IP to `/etc/hosts`. Interestingly, AWS's Reachability Analyzer reports that my instances should be able to reach secretsmanager.us-east-1.amazonaws.com. I am able to reach other AWS services like s3, etc. I don't have any outbound Security Group settings that should prevent this. Everything in this instance is AWS managed. It's an AWS image with no special configuration on our side. It's a AWS Linux Corretto Java 17 image. Any thoughts on what may have caused this seemingly out of the blue? Any thoughts on what to probe at to determine where the issue is coming from?
AMI scan for Marketplace
I am scanning an AMI for AWS Marketplace and need to follow these guidelines:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/building-shared-amis.html. I am supposed to remove all keys (~/.ssh/authorized_keys) for security reasons and use cloud-init to inject public keys but during scanning I get the error that AWS cannot ssh into the AMI because there is no key. so the dilemma is if (~/.ssh/authorized_keys) are removed scanning cannot happen because AWS cannot ssh into the server, but if (~/.ssh/authorized_keys) is present then its a security issue and throws an error. I need solutions please!
Errors when installing Aws Replication Agent
![Enter image description here](/media/postImages/original/IMpyToxN0-R_OpJ1hOX9MMlQ) I have checked connection to S3 endpoint with telnet and sucessfully. But got this error when run this .py file? Anyone ever face this error. Help me Oracle Linux 6.2 Python 3.5