Requirements:
Immuta permission AUDIT
If you will use the Immuta CLI instead of GraphQL API, . Must be CLI v1.4.0 or newer.
Use the following how-to to configure a periodical export of your Immuta audit logs to an S3 bucket. This export configuration requires access to your S3 bucket to add objects using one of the following authentication methods:
Configure your Immuta audit logs to export to your S3 bucket and allow Immuta to authenticate using your AWS access key ID and secret access key.
Before Immuta can export audit events to your S3 bucket, you need to create a bucket policy that allows the Immuta audit service to add objects to your specified S3 bucket. The following Amazon S3 action will be granted to the audit service in the bucket policy:
: Adds an object to a bucket.
To create the policy for the bucket, you must be the bucket owner.
Follow for adding a bucket policy in the Amazon S3 console. To create the policy for the bucket, you must be the bucket owner.
Edit the JSON in the Policy section to include a bucket policy like the example below. In this example, the policy allows immuta-audit-service (the ) to add objects to your-bucket-name (and the contents within that bucket).
Note: If you use this example, replace the content in angle brackets with your and bucket name.
Save your changes.
Configure the audit export to S3 using the Immuta CLI or GraphQL API with the following fields:
interval: The interval at which audit logs will be exported to your S3 bucket. They can be sent at 2-, 4-, 6-, 12-, or 24-hour intervals.
bucket name: Name of the bucket your audit logs will be sent to that you added the policy to above.
bucket path: The name of the folder within the bucket to put the audit logs in. This field is optional.
region: AWS region (such as "us-east-1").
Run the following command with the above fields in a JSON file:
Example ./exportConfig.json file
For additional CLI commands, see the .
Run the following mutation to this URL, https://your-immuta.com/api/audit/graphql, with the above fields passed directly:
Example response
For additional GraphQL API commands, see the.
Configure your Immuta audit logs to export to your S3 bucket and allow Immuta to authenticate using an .
Immuta requires a role with the following allowed action to the S3 bucket you want the audit logs exported to:
which allows the role to add an object to a bucket.
Follow to create a new role for Immuta to assume and add objects to your S3 bucket.
Follow for creating IAM policies in the Amazon S3 console for the new role. Use the example JSON below to allow the provided role to add objects to the specified buckets. Ensure the buckets provided here are the ones used when configuring the export.
Note: If you use this example, replace the content in angle brackets with your bucket name.
Response error
When creating the export configuration, this step will return an error. Take the returned export configuration ID and continue with step 3 and 4 to create a trust relationship and verify the connection between Immuta and S3.
Configure the audit export to S3 using the Immuta CLI or GraphQL API with the following fields:
interval: The interval at which audit logs will be exported to your S3 bucket. They can be sent at 2-, 4-, 6-, 12-, or 24-hour intervals.
bucket name: Name of the bucket your audit logs will be sent to.
bucket path: The name of the folder within the bucket to put the audit logs in. This field is optional.
region: AWS region (such as "us-east-1").
Run the following command with the above fields in a JSON file:
Example ./exportConfig.json file
Example response:
For additional CLI commands, see the
Run the following mutation to this URL, https://your-immuta.com/api/audit/graphql, with the above fields passed directly:
Example response
For additional GraphQL API commands, see the .
Follow for creating IAM policies in the Amazon S3 console. Use the example JSON below to create a trust policy that sets the export configuration external ID as the requirement for assuming the role.
Fill in the content in angle brackets with the following:
AWS Account ID: Your AWS account ID.
Export Configuration ID: Insert the ID from step 2's response.
Now that the configuration and the trust relationship have been created, test the connection from Immuta to S3 to ensure your audit logs are exported to your S3 bucket.
If connectionStatus returns SUCCESS, your export configuration has been successfully set up.
Run the following command
Run the following mutation to this URL, https://your-immuta.com/api/audit/graphql:
accessKeyId: AWS access key ID for authentication. See the AWS documentation for information about using an access key ID and secret access key.
secretAccessKey: AWS secret access key for authentication.
roleArn: AWS role ARN for authentication that you added the policies to above. Immuta will assume this role when exporting audit logs to S3.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::<Your AWS account ID>:user/<Your IAM User>"
},
"Action": [
"s3:PutObject"
],
"Resource": [
"arn:aws:s3:::<your-s3-bucket>",
"arn:aws:s3:::<your-s3-bucket>/*"
]
}
]
}immuta audit exportConfig create:s3:accessKey ./exportConfig.json{
"interval": "EVERY_12_HOURS",
"bucket": "your-s3-bucket",
"path": "your-optional-s3-bucket-path",
"region": "your-aws-region",
"accessKeyId": "YOURACCESSKEYID",
"secretAccessKey": "YOUR/SECRET/ACCESSKEY"
}mutation {
createS3AccessKeyExportConfiguration(
data: {
interval: EVERY_12_HOURS
bucket: "your-s3-bucket"
path: "your-optional-s3-bucket-path"
region: "your-aws-region"
accessKeyId: "YOURACCESSKEYID"
secretAccessKey: "YOUR/SECRET/ACCESSKEY"
}
)
{
id
interval
enabled
connectionStatus
endpointConfiguration {
... on S3AccessKeyEndpointConfiguration {
bucket
path
region
}
}
}
}{
"data": {
"createS3AccessKeyExportConfiguration": {
"id": "259fc41c-b502-418a-a8ff-d875335dbe9b",
"interval": "EVERY_12_HOURS",
"enabled": true,
"connectionStatus": "SUCCESS",
"endpointConfiguration": {
"bucket": "your-s3-bucket",
"path": "your-optional-s3-bucket-path",
"region": "your-region",
}
}
}
}{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:PutObject"
],
"Resource": [
"arn:aws:s3:::<your-s3-bucket>",
"arn:aws:s3:::<your-s3-bucket>/*"
]
}
]
}immuta audit exportConfig create:s3:assumedRole ./exportConfig.json{
"interval": "EVERY_12_HOURS",
"bucket": "your-s3-bucket",
"path": "your-optional-s3-bucket-path",
"region": "your-region",
"roleArn": "arn:aws:iam::<Your AWS Account ID>:role/<the prepared role>"
}{
"data": {
"createS3AssumedRoleExportConfiguration": {
"id": "259fc41c-b502-418a-a8ff-d875335dbe9b",
"interval": "EVERY_12_HOURS",
"enabled": true,
"connectionStatus": "Error testing access to S3 using AssumedRole <Your Role> - User: <Immuta Account> is not authorized to perform: sts:AssumeRole on resource: <Your Role>",
"endpointConfiguration": {
"__typename": "S3AssumedRoleEndpointConfiguration",
"bucket": "your-s3-bucket",
"path": "your-optional-s3-bucket-path",
"region": "your-region",
}
}
}
}mutation {
createS3AssumedRoleExportConfiguration(
data: {
interval: EVERY_12_HOURS
bucket: "your-s3-bucket"
path: "your-optional-s3-bucket-path"
region: "your-region"
roleArn: "arn:aws:iam::<Your AWS Account ID>:role/<the prepared role>"
}
)
{
id
interval
enabled
connectionStatus
endpointConfiguration {
... on S3AssumedRoleEndpointConfiguration {
bucket
path
region
}
}
}
}{
"data": {
"createS3AssumedRoleExportConfiguration": {
"id": "259fc41c-b502-418a-a8ff-d875335dbe9b",
"interval": "EVERY_12_HOURS",
"enabled": true,
"connectionStatus": "Error testing access to S3 using AssumedRole <Your Role> - User: <Immuta Account> is not authorized to perform: sts:AssumeRole on resource: <Your Role>",
"endpointConfiguration": {
"bucket": "your-s3-bucket",
"path": "your-optional-s3-bucket-path",
"region": "your-region",
}
}
}
}{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::<AWS Account ID>:root"
},
"Action": "sts:AssumeRole",
"Condition": {"StringEquals": {"sts:ExternalId": "<Export Configuration ID>"}}
}
]
}immuta audit exportConfig listquery {
getAllExportConfigurations{
id
connectionStatus
}
}