Difference between revisions of "AWS S3 VPC Flow Log Access"

From Observer GigaFlow Support | VIAVI Solutions Inc.
Jump to: navigation, search
Line 1: Line 1:
  
 
Observer Gigaflow uses the Amazon Web Services (AWS) Command Line Interface (CLI) tools to access AWS services. You can install the latest version of the CLI tools for AWS system from https://aws.amazon.com/cli/.
 
Observer Gigaflow uses the Amazon Web Services (AWS) Command Line Interface (CLI) tools to access AWS services. You can install the latest version of the CLI tools for AWS system from https://aws.amazon.com/cli/.
 +
{| class="wikitable"
 +
|-
 +
| '''Note:''' The CLI tools must be configured with the same user used to run Gigaflow for it to be able to access the configuration profile.<br />
 +
For Linux, you can use the "su" command to choose the correct user and then run the AWS CLI commands.<br />
 +
For Windows, you need to change the Gigaflow service (using the services manager) to run as a local user. Then log in as that user, install the CLI tools and configure your AWS access.
 +
|}
 +
 +
Once installed, you must add a role to your AWS instance with the following permissions:
 +
 +
* S3 List/Read/Download
 +
{
 +
"Version": "2012-10-17",
 +
"Statement": [
 +
{
 +
"Effect": "Allow",
 +
"Action": [
 +
"s3:Get*",
 +
"s3:List*",
 +
"s3-object-lambda:Get*",
 +
"s3-object-lambda:List*"
 +
],
 +
"Resource": "*"
 +
}
 +
]
 +
}

Revision as of 16:43, 25 August 2022

Observer Gigaflow uses the Amazon Web Services (AWS) Command Line Interface (CLI) tools to access AWS services. You can install the latest version of the CLI tools for AWS system from https://aws.amazon.com/cli/.

Note: The CLI tools must be configured with the same user used to run Gigaflow for it to be able to access the configuration profile.

For Linux, you can use the "su" command to choose the correct user and then run the AWS CLI commands.
For Windows, you need to change the Gigaflow service (using the services manager) to run as a local user. Then log in as that user, install the CLI tools and configure your AWS access.

Once installed, you must add a role to your AWS instance with the following permissions:

  • S3 List/Read/Download
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:Get*",
"s3:List*",
"s3-object-lambda:Get*",
"s3-object-lambda:List*"
],
"Resource": "*"
}
]
}