[
https://issues.apache.org/jira/browse/CASSANDRA-16555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
miklosovic updated CASSANDRA-16555:
-----------------------------------
Attachment: signature.asc
No, it will not fallback to v1.
Exception will be thrown if the response is not 200 and it will retry once.
Why do you think that fallbacking to v1 will suddenly work? I think v/v2 is
same service, v2 is just secured with a token and it is session-oriented
because of it. The IP address of the service is same as well as all endpoints.
\
> Add support for AWS Ec2 IMDSv2
> -------------------------------
>
> Key: CASSANDRA-16555
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16555
> Project: Cassandra
> Issue Type: New Feature
> Components: Consistency/Coordination
> Reporter: Paul Rütter (BlueConic)
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 3.0.30, 3.11.16, 4.0.11, 4.1.3, 5.0
>
> Attachments: signature.asc
>
> Time Spent: 5h 40m
> Remaining Estimate: 0h
>
> In order to patch a vulnerability, Amazon came up with a new version of their
> metadata service.
> It's no longer unrestricted but now requires a token (in a header), in order
> to access the metadata service.
> See
> [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html]
> for more information.
> Cassandra currently doesn't offer an out-of-the-box snitch class to support
> this.
> See
> [https://cassandra.apache.org/doc/latest/operating/snitch.html#snitch-classes]
> This issue asks to add support for this as a separate snitch class.
> We'll probably do a PR for this, as we are in the process of developing one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
