Questions tagged with Amazon EC2

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

HI, I am following the tutorial here: https://docs.aws.amazon.com/codepipeline/latest/userguide/tutorials-simple-s3.html But the deployment fails. Where I run status on the CodeDeployAgent Service using: **sudo service codedeploy-agent status ** I get this error: <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:151:in `require': cannot load such file -- net/smtp (LoadError) from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:151:in `require' from /opt/codedeploy-agent/vendor/gems/logging-1.8.2/lib/logging/appenders/email.rb:2:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:151:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:151:in `require' from /opt/codedeploy-agent/vendor/gems/logging-1.8.2/lib/logging/appenders.rb:57:in `<module:Logging>' from /opt/codedeploy-agent/vendor/gems/logging-1.8.2/lib/logging/appenders.rb:2:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:151:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:151:in `require' from /opt/codedeploy-agent/vendor/gems/logging-1.8.2/lib/logging.rb:537:in `<module:Logging>' from /opt/codedeploy-agent/vendor/gems/logging-1.8.2/lib/logging.rb:18:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:162:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:162:in `rescue in require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:152:in `require' from /opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/log.rb:2:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:99:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:99:in `require' from /opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager.rb:9:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:162:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:162:in `rescue in require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:152:in `require' from /opt/codedeploy-agent/lib/instance_agent.rb:10:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:88:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:88:in `require' from /opt/codedeploy-agent/bin/../lib/codedeploy-agent.rb:22:in `<main>' <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:151:in `require': cannot load such file -- logging (LoadError) Did you mean? logger from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:151:in `require' from /opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager/log.rb:2:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:99:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:99:in `require' from /opt/codedeploy-agent/vendor/gems/process_manager-0.0.13/lib/process_manager.rb:9:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:162:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:162:in `rescue in require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:152:in `require' from /opt/codedeploy-agent/lib/instance_agent.rb:10:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:88:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:88:in `require' from /opt/codedeploy-agent/bin/../lib/codedeploy-agent.rb:22:in `<main>' <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:88:in `require': cannot load such file -- process_manager (LoadError) from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:88:in `require' from /opt/codedeploy-agent/lib/instance_agent.rb:10:in `<top (required)>' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:88:in `require' from <internal:/usr/share/ruby3.2-rubygems/rubygems/core_ext/kernel_require.rb>:88:in `require' from /opt/codedeploy-agent/bin/../lib/codedeploy-agent.rb:22:in `<main>' Has anyone experienced this before.
0
answers
0
votes
5
views
asked 4 hours ago
My ec2 instance is of type g4dn.xlarge. I tried nvidia-smi but it seems the drivers are not pre-installed so I want to install them. I couldn't find much documentation for Amazon Linux online. On the nvidia instructions it isn't specifically mentioned. When running `sudo cat /etc/os-release` I get this output: ``` NAME="Amazon Linux" VERSION="2023" ID="amzn" ID_LIKE="fedora" VERSION_ID="2023" ... ``` So i tried to follow the instructions for fedora (randomly fedora34) but I got errors during the installation (I guess because of incompatibility). Any help highly appreciated.
1
answers
0
votes
9
views
Nina
asked 7 hours ago
Hello, I'm running a computation in Python using `pool.map()` of the `multiprocessing` library. On the EC2 parent instance, when I run the process first using only one thread and then 2 threads using `pool.map` the processing time is approximately divided by two as I would expect. However, in the Nitro Enclave (with 2 cpus) the computation time is the same. Any idea what could be wrong? Thanks
0
answers
0
votes
2
views
asked 9 hours ago
I am trying to get SSL certificate with let's encrypt nginx. First, I added epel using the commands ```$ wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm``` and ```$ sudo rpm -ihv --nodeps ./epel-release-latest-8.noarch.rpm``` and it was added with no problem then I used ``` sudo yum install python3-certbot-nginx``` and got the error message: ``` Problem: package certbot-1.22.0-1.el8.noarch requires python3-certbot = 1.22.0-1.el8, but none of the providers can be installed - conflicting requests - nothing provides python3.6dist(setuptools) >= 39.0.1 needed by python3-certbot-1.22.0-1.el8.noarch - nothing provides python3.6dist(cryptography) >= 2.5.0 needed by python3-certbot-1.22.0-1.el8.noarch - nothing provides python3.6dist(configobj) >= 5.0.6 needed by python3-certbot-1.22.0-1.el8.noarch - nothing provides python3.6dist(distro) >= 1.0.1 needed by python3-certbot-1.22.0-1.el8.noarch - nothing provides /usr/bin/python3.6 needed by python3-certbot-1.22.0-1.el8.noarch - nothing provides python3.6dist(pytz) needed by python3-certbot-1.22.0-1.el8.noarch - nothing provides python(abi) = 3.6 needed by python3-certbot-1.22.0-1.el8.noarch (try to add '--skip-broken' to skip uninstallable packages) ``` I also tried ``` sudo dnf install python3-certbot-nginx ``` I learned i may need a Code ready builder but haven't been able to install it. Please how can I get it. If that is not the issue, please what I'm I doing wrong and how can I resolve it?
0
answers
0
votes
12
views
Sanmi
asked 13 hours ago
I have to launch an EC2 instance, running RHEL 8, with some storage requirements. And I was wondering how to set it up. 1. \>= 60 GB free storage for requirements: - \>= 50 GB of free storage on the partition that contains /var/lib/<name>. The partition mountpoint should not have the noexec option. - \>= 5 GB of additional space in /var/log - \>= 5 GB of additional space in /var/lib/<othername> 2. \>= 500 GB of dedicated storage
0
answers
0
votes
8
views
asked 14 hours ago
My client is not able to access ALB URL, but I am able to access the same. ALB URL's security group has "All Traffic" rule in both inbound and outbound rules. Also my EC2 instance is windows and I have deactivated its firewall to not block any incoming IP addresses. How to solve this issue.
0
answers
0
votes
11
views
asked 16 hours ago
How to connect my EC2 instance(Microscoft window server 2022 with SQL base standard), with physical gateway IP address. When i try to ping form command line of EC2, ping (my gateway ip) ... it show the request time out. Anyway to connect with my Physical Gateway IP address with EC2? When I try to ping the ip address of gateway in my laptop, it is working.. But when i try to ping in the EC2 remote desktop, it returns request time out. And when i try to ping google.com, its working. EC2 is successfully connected VPC . Any solution ??
0
answers
0
votes
17
views
asked 16 hours ago
After completion of Reverse replication in case of Cross Region failback, launching of recovery instance failed with below mentioned error: ``` Error: An error occurred (VPCIdNotSpecified) when calling the RunInstances operation: No default VPC for this user. GroupName is only supported for EC2-Classic and default VPC. ``` How should I fix it? You help is appreciated. Thank you.
0
answers
0
votes
8
views
asked 18 hours ago
Hi, I have a instance EC2 associate with a EBS volumen, this instance was stopped but the used disk size keeps increasing. I don't understand why the used volume size keeps increasing if the instance was stopped. Thanks.
0
answers
0
votes
16
views
asked a day ago
Is this compulsory that we have to use linux for EC2 connection, because in window its showing connection error.. can anybody help to do this task? I am new on AWS so i didn't understand.
0
answers
0
votes
5
views
Dhrupal
asked a day ago
Why this question? If `eb deploy` does change the IP address of ec2 instance then it is okay to use `eb ssh` and then select the instance number or id, depending upon how many instances are there in a single environment. If not, why not just directly `ssh -i <key.pem> ec2-user@<instance-ip>` Am I missing something here?
0
answers
0
votes
3
views
asked a day ago
Is there an API call you can make that gives you the state capacity (used/available) of the bucket (capacity and refill rate). CloudWatch monitors failures (RequestLimitExceeded) but only once you exceeded the limit, so you can be at the 99% mark and see zero failures and then pass it without noticing.
1
answers
0
votes
4
views
Kobster
asked a day ago