Page MenuHomePhabricator

Make PhutilAWSEC2Future signs requests correctly
ClosedPublic

Authored by epriestley on Nov 29 2016, 10:39 PM.
Tags
None
Referenced Files
F19704926: D16963.id.diff
Wed, Feb 11, 5:51 AM
F19704924: D16963.id.diff
Wed, Feb 11, 5:51 AM
F19561765: D16963.id40822.diff
Sat, Jan 31, 11:43 AM
F19550189: D16963.id40822.diff
Jan 27 2026, 7:36 PM
F19544004: D16963.id40823.diff
Jan 23 2026, 1:52 AM
F19524079: D16963.diff
Jan 17 2026, 10:03 PM
F19516356: D16963.diff
Jan 14 2026, 11:16 PM
F19152915: D16963.id40822.diff
Dec 11 2025, 6:07 AM
Subscribers
None

Details

Summary

I partially automated a bit of provisioning stuff; the signature algorithm for EC2 is slightly different from the algorithm for S3.

Test Plan

Used bin/provision ... in rCORE to create and attach device volumes in the Phacility cluster.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make PhutilAWSEC2Future signs requests correctly.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Nov 29 2016, 10:57 PM
This revision was automatically updated to reflect the committed changes.