Debian GNU/Linux 8 (Jessie)
Debian | 8.7Linux/Unix, Debian 8.6+1 - 64-bit Amazon Machine Image (AMI)
Сant upgrade to 2018 instance series(m5, m5n)
Using this debain from 2017, cant upgrade too from m4.2xlarge to m5.2xlarge :(
Please fix it. Thanks.
It works., good product.
- Leave a Comment |
- Mark review as helpful
It just works!
Keeps on working :) never had a problem and I for sure recommend this OS as the foundation fo any project.
Ultime Power !!!, but cant upgrade to 2018 instance series(m5,t3,etc)
using this debain from 2017, im using t2.2xlarge, but cant upgrade to t3.2xlarge,
and cant upgrade too from m4.2xlarge to m5.2xlarge :(
not up-to-date for latest instance types
been using this for years, and upgraded it to stretch without an issue. now i want to upgrade from t2 to t3 and it says it isn't compatible. :(
Lacks c4.8xlarge support. Why?
Lacks c4.8xlarge support. Why? Big m4 instances are there, but not c4? Is there any reason for that? Very strange.
Great, it's Debian after all
The only thing I wish is that an ami with /var separated out would be nice to have. It's a significant hassle to do this.
AMI Instance Authentication Issues
If this AMI is used to create an instance, that would change something and use it to create a new AMI, then the authentication on the latest instance created will be possible only using the initial SSH authentication keys that has been used initially, even if you add a different key when creating the final instance. Anyone has an idea why?
Could not use snapshot to launch new instance
I use Debian everywhere but am not sure if I will use it again on aws. Today, I created a new image from a snapshot but could not launch a new instance from the image. Here is the error message:
Launch Failed
The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=3f8t6t8fp5m9xx18yzwriozxi for more information about supported instance types, regions, and operating systems.
Creating security groups Successful
Authorizing inbound rules Successful
Initiating launches Failure
This means if you terminate your instance intentionally or by accident, you won't be able to create it from your snapshots.
Nothing wrong with this image (Check your routing table)
Like others I experienced some issues connecting to instances spun up from this image. The reason people are having trouble is this image runs on a VPC which is a little bit trickier to configure than EC2. In addition to the Elastic IP and Security Group you need a VPC, Subnet, Routing Table, Gateway. None of the configuration is terribly complex if you're familiar with the concepts but there's just a lot of ways it can be done incorrectly. In my case I forgot to add my gateway to the routing table so none of the instance's traffic was making it back to me. Once I added the gateway to the routing table everything worked great. :)
Only 8GB
Totally sucks. Every Debian Jessie AMI in marketplace and community will ONLY partition itself with 8GB despite setting the EBS size.