CLI AWS Commands

[Jicxer]

The user should be able to easily view the logs and log information depending on what was sent to AWS. Since the IAM CLI for the client already requires making use of AWS, it would be possible to simply make use of the AWS commands to view the tables if we don't have any visualization available. This can be done by simply having the user interact with the command line and have those commands enter the arguments through AWS.

Two commands that I could think of would be:

• [ ] List tables
• [ ] Scan tables

[Jicxer]

The AWS CLI commands currently just make use of the installed software for entering the commands. The commands for AWS are: aws dynamodb -list-tables --table-name {table-name} aws dynamodb scan --table-name {table naem}

[Jicxer]

I deleted the iam and util rust files for this client implementation on one of the test branches.

I will finalize all the solutions to the code and push it to jicxer-predev.

IAM file deletion is due to unused functionality of the admin AWS CLI. It requires that AWS be already installed. The util function housed the code for the previous ratatui menu, s3, Kinesis firehose, dynamodb, and IAM implementations. The only things we kept were dynamoDB and IAM permissions. However, the admin or user never needs to access the IAM policies directly through the client. It's much better for them to do so on the AWS site itself.

This issue will still remain open as listing the dynamodb commands, such as scanning a table or listing them, would not be difficult if we are able to access AWS commands.