By using AWS re:Post, you agree to the Terms of Use

Questions tagged with AWS Marketplace

Sort by most recent

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

Issues with ec2 describe-images when using filters with marketplace AMIs

I seem to be unable to search for marketplace AMIs when using a filter; this is frustrating because we use the product code to find the most up to date AMI. Searching for a standard AMI that you'd find if trying to launch an instance from the console: ``` ➜ aws ec2 describe-images --filters Name="image-id",Values="ami-09e2d756e7d78558d" --debug | cat 2022-09-21 14:38:36,360 - MainThread - awscli.formatter - DEBUG - RequestId: f3bf3f72-eabe-46a2-bdad-151712069a87 { "Images": [ { "Architecture": "x86_64", "CreationDate": "2022-08-17T23:46:17.000Z", "ImageId": "ami-09e2d756e7d78558d", "ImageLocation": "amazon/amzn2-ami-kernel-5.10-hvm-2.0.20220805.0-x86_64-gp2", "ImageType": "machine", "Public": true, "OwnerId": "137112412989", "PlatformDetails": "Linux/UNIX", "UsageOperation": "RunInstances", "State": "available", "BlockDeviceMappings": [ { "DeviceName": "/dev/xvda", "Ebs": { "DeleteOnTermination": true, "SnapshotId": "snap-0b1e0b58f54fc89ef", "VolumeSize": 8, "VolumeType": "gp2", "Encrypted": false } } ], "Description": "Amazon Linux 2 Kernel 5.10 AMI 2.0.20220805.0 x86_64 HVM gp2", "EnaSupport": true, "Hypervisor": "xen", "ImageOwnerAlias": "amazon", "Name": "amzn2-ami-kernel-5.10-hvm-2.0.20220805.0-x86_64-gp2", "RootDeviceName": "/dev/xvda", "RootDeviceType": "ebs", "SriovNetSupport": "simple", "VirtualizationType": "hvm", "DeprecationTime": "2024-08-17T23:46:17.000Z" } ] } ``` Searching for a marketplace AMI using the `--image-id` param: ``` ➜ aws ec2 describe-images --image-ids ami-0e1415fedc1664f51 --debug| cat 2022-09-21 14:39:14,069 - MainThread - awscli.formatter - DEBUG - RequestId: 3d52e935-1d74-48aa-b205-6dad06d23eb6 { "Images": [ { "Architecture": "x86_64", "CreationDate": "2020-07-31T17:51:20.000Z", "ImageId": "ami-0e1415fedc1664f51", "ImageLocation": "aws-marketplace/OpenVPN Access Server Community Image-fe8020db-5343-4c43-9e65-5ed4a825c931-ami-06585f7cf2fb8855c.4", "ImageType": "machine", "Public": true, "OwnerId": "679593333241", "PlatformDetails": "Linux/UNIX", "UsageOperation": "RunInstances", "ProductCodes": [ { "ProductCodeId": "f2ew2wrz425a1jagnifd02u5t", "ProductCodeType": "marketplace" } ], "State": "available", "BlockDeviceMappings": [ { "DeviceName": "/dev/sda1", "Ebs": { "DeleteOnTermination": true, "SnapshotId": "snap-0bb5570e9d1eb75ea", "VolumeSize": 8, "VolumeType": "gp2", "Encrypted": false } }, { "DeviceName": "/dev/sdb", "VirtualName": "ephemeral0" }, { "DeviceName": "/dev/sdc", "VirtualName": "ephemeral1" } ], "Description": "OpenVPN Access Server 2.8.3 publisher image from https://www.openvpn.net/.", "EnaSupport": true, "Hypervisor": "xen", "ImageOwnerAlias": "aws-marketplace", "Name": "OpenVPN Access Server Community Image-fe8020db-5343-4c43-9e65-5ed4a825c931-ami-06585f7cf2fb8855c.4", "RootDeviceName": "/dev/sda1", "RootDeviceType": "ebs", "SriovNetSupport": "simple", "VirtualizationType": "hvm", "DeprecationTime": "2022-07-31T17:51:20.000Z" } ] } ``` Searching for the same AMI; using the `image-id` filter (that worked for the first request): ``` ➜ aws ec2 describe-images --filters Name="image-id",Values="ami-0e1415fedc1664f51" --debug | cat 2022-09-21 14:39:41,422 - MainThread - awscli.formatter - DEBUG - RequestId: 1de1f1a6-76cf-4664-bde5-1f8a3f061815 { "Images": [] } ``` This was working the other day; or so I believe... am I doing something daft or has this behavior changed?
1
answers
0
votes
25
views
asked 13 days ago

EC2 instance stuck at boot with not enough space. Can't log it via SSH (not responsive enough to connect). What can I do?

The instance is running cloudron from marketplace. I had not enough space left to back up apps in cloudron neither update. So here's what I did : Changed the attached volume to 40 gb instead of 20, in Amazon AWS Came back to cloudron. Was still showing 20gb. 127 mb left. Rebooted the machine using cloudron admin Nothing.. Rebooted in AWS.. nothing. Not responding but booting. I managed to get logs after a successfull boot in a really unstable Cloudron admin. AWS says instance is online. But I can't log it via SSH (not responsive enough to connect). What can I do? ` 2022-06-14T15:27:45.621Z box:server ========================================== 2022-06-14T15:27:45.622Z box:server Cloudron 7.1.4 2022-06-14T15:27:45.622Z box:server ========================================== 2022-06-14T15:27:45.840Z box:settings initCache: pre-load settings 2022-06-14T15:27:45.884Z box:tasks stopAllTasks: stopping all tasks 2022-06-14T15:27:45.885Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all 2022-06-14T15:27:45.970Z box:shell stopTask (stdout): sudo: unable to resolve host ip-1xx-xx-30-1xx: Name or service not known Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log 2022-06-14T15:27:46.058Z box:reverseproxy writeDashboardConfig: writing admin config for levis.app 2022-06-14T15:27:46.098Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx 2022-06-14T15:27:46.131Z box:shell reload (stdout): sudo: unable to resolve host ip-1xx-xx-30-1xx: Name or service not known 2022-06-14T15:27:46.312Z box:cloudron onActivated: running post activation tasks 2022-06-14T15:27:46.312Z box:platform initializing addon infrastructure 2022-06-14T15:27:46.314Z box:platform platform is uptodate at version 49.0.0 2022-06-14T15:27:46.314Z box:platform onPlatformReady: platform is ready. infra changed: false 2022-06-14T15:27:46.314Z box:apps schedulePendingTasks: scheduling app tasks 2022-06-14T15:27:46.352Z box:cron startJobs: starting cron jobs 2022-06-14T15:27:46.383Z box:cron backupConfigChanged: schedule 00 00 23 * * * (America/Toronto) 2022-06-14T15:27:46.390Z box:cron autoupdatePatternChanged: pattern - 00 00 1,3,5,23 * * * (America/Toronto) 2022-06-14T15:27:46.392Z box:cron Dynamic DNS setting changed to false 2022-06-14T15:27:46.393Z box:dockerproxy startDockerProxy: started proxy on port 3003`
1
answers
0
votes
51
views
asked 4 months ago