group.of.nepali.translators team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

** Changed in: ec2-instance-connect (Ubuntu Cosmic)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1834525

Title:
  [SRU] Instance Connect release

Status in ec2-instance-connect package in Ubuntu:
  Fix Released
Status in ec2-instance-connect source package in Xenial:
  Fix Released
Status in ec2-instance-connect source package in Bionic:
  Fix Released
Status in ec2-instance-connect source package in Cosmic:
  Won't Fix
Status in ec2-instance-connect source package in Disco:
  Fix Released

Bug description:
  [Impact]
  New service on Amazon AWS cloud, providing SSH access to instances; available to any AWS users.

  [Test Cases]
  This is manually tested by Amazon:

  0) Deploy an Amazon AWS instance with Instance Connect feature enabled
  1) Install the ec2-instance-connect package
  2) Verify that the sshd process has been restarted with the changed command-line, now including "AuthorizedKeysCommand*" options.
  3) Attempt to connect to the instance using a SSH key that is known by the Instance Connect service.

  [Regression Potential]
  Limited to SSH access on instances where the package gets installed. This is a brand new package for a new service provided to AWS customers. In the case of an issue, things to watch out for would be for some keys to not be usable to connect to the instance when they are expected to be, as the list of authorized keys is collated by the service to include both the usual authorized_keys contents, as well as keys provided by the Instance Connect service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1834525/+subscriptions