Unsure if this is deliberate. I might fork this and add it as an option. As things stand you end up with a non-functioning CLI, e.g.
done pausing..
Successfully used new key. Inactivating old key and retesting...
download: s3://bucket/test-object-do-not-delete.txt to ./KeyRotationTest.txt
Successfully used new key after inactivating the old key. Deleting the old key...
Outputing JSON to log.json...
Outputing .csv to credentials.csv...
$ aws s3 ls
A client error (InvalidAccessKeyId) occurred when calling the ListBuckets operation: The AWS Access Key Id you provided does not exist in our records.
Unsure if this is deliberate. I might fork this and add it as an option. As things stand you end up with a non-functioning CLI, e.g.
done pausing..
Successfully used new key. Inactivating old key and retesting...
download: s3://bucket/test-object-do-not-delete.txt to ./KeyRotationTest.txt
Successfully used new key after inactivating the old key. Deleting the old key...
Outputing JSON to log.json...
Outputing .csv to credentials.csv...
$ aws s3 ls
A client error (InvalidAccessKeyId) occurred when calling the ListBuckets operation: The AWS Access Key Id you provided does not exist in our records.