Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.The `nm-cloud-setup` utility now supports IMDSv2 configuration
Users can configure an AWS Red Hat Enterprise Linux EC2 instance with Instance Metadata Service Version 2 (IMDSv2) with the `nm-cloud-setup` utility. To comply with improved security that restricts unauthorized access to EC2 metadata and new features, integration between AWS and Red Hat services is necessary to provide advanced features. This enhancement enables the `nm-cloud-setup` utility to fetch and save the IMDSv2 tokens, verify an EC2 environment, and retrieve information about available interfaces and IP configuration by using the secured IMDSv2 tokens.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:7118
VERIFIED in NetworkManager-1.40.16-4.el8: Token is requested: Hypertext Transfer Protocol PUT /latest/api/token HTTP/1.1\r\n [Expert Info (Chat/Sequence): PUT /latest/api/token HTTP/1.1\r\n] [PUT /latest/api/token HTTP/1.1\r\n] [Severity level: Chat] [Group: Sequence] Request Method: PUT Request URI: /latest/api/token Request Version: HTTP/1.1 Host: 169.254.169.254\r\n Accept: */*\r\n X-aws-ec2-metadata-token-ttl-seconds: 180\r\n \r\n [Full request URI: http://169.254.169.254/latest/api/token] [HTTP request 1/1] [Response in frame: 2] And then used: Hypertext Transfer Protocol GET /2018-09-24/meta-data/network/interfaces/macs/ HTTP/1.1\r\n [Expert Info (Chat/Sequence): GET /2018-09-24/meta-data/network/interfaces/macs/ HTTP/1.1\r\n] [GET /2018-09-24/meta-data/network/interfaces/macs/ HTTP/1.1\r\n] [Severity level: Chat] [Group: Sequence] Request Method: GET Request URI: /2018-09-24/meta-data/network/interfaces/macs/ Request Version: HTTP/1.1 Host: 169.254.169.254\r\n Accept: */*\r\n X-aws-ec2-metadata-token: AQAAALH-k7i18JMkK-ORLZQfAa7nkNjQbKwpQPExNHqzk1oL_7eh-A==\r\n \r\n [Full request URI: http://169.254.169.254/2018-09-24/meta-data/network/interfaces/macs/] [HTTP request 1/1] [Response in frame: 4]