Accenture MDR Quick Start Guide for Amazon Web Service Relational Database Service (AWS RDS)

This quick start guide will help Accenture MDR customers configure AWS RDS to collect logs to the Log collection Platform (LCP).

This document includes the following topics: 

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal.

Port Requirements

Table 1-1: Port requirements for LCP communication.

Source

     Destination

      Port

    Description

LCP

Cloudwatch

443 (TCP)

Default Port

Configuring AWS RDS

Pre-requisites:

An AWS account that you can sign in to.

A user who's a Global Administrator or RDS Administrator.


Device Configuration Steps:

  1. If you have an existing database in AWS, select the database and click on Modify and then go to Log Export.

Note: Above screenshot is applicable for MariaDB, MySQL Community, AWS Aurora MySQL database. In the case of AWS Aurora PostgreSQL and PostgreSQL, log type will as follows.

In the case of AWS Microsoft SQL Server, log type will be as follows,

2. Once you save the configuration, Navigate to CloudWatch > Logs to see the logs getting collected. The newly created Log Groups will automatically be created once the logs are getting shipped through the instance.

3. Incase of a new database, while creating a database go to Additional Configuration.

4. Select all types to publish logs to Amazon Cloudwatch.

Note: Above screenshot is applicable for MariaDB, MySQL Community, AWS Aurora MySQL database. In the case of AWS Aurora PostgreSQL and PostgreSQL, log type will as follows

In the case of AWS Microsoft SQL Server, log type will be as follows,

5. Once you save the configuration, Navigate to CloudWatch > Logs to see the logs getting collected. The newly created Log Groups will automatically be created once the logs are getting shipped through the instance

6. Please refer below page to check required IAM user policies.

7. Below are the URL details which we need to allow for connectivity (Please identify URLs by referring AWS document according to your services and regions):

IAM: For any logging source IAM URL should be allowed

https://docs.aws.amazon.com/general/latest/gr/iam-service.html

Cloudwatch: For cloudwatch logging source, cloudwatch URL should be allowed.

https://docs.aws.amazon.com/general/latest/gr/cwl_region.html


For additional reference

For engine-specific information, see the following:


LCP Configuration Parameters

MxDR supports log collection using role based access control (RBAC) or access key ID and secret method.

  • To create access key ID and secret please refer

  • To support log collection using RBAC please refer

Table 1-2: AWS RDS generic event collector (API - 3908) properties to be configured by MDR are given in the table.

Property

Access Key and Secret

RBAC

Property

Access Key and Secret

RBAC

Region

Enter region (Eg: us-west-2)

Enter region (Eg: us-west-2)

AWS Access Key ID Or Role ARN

Enter Access Key

Provide Role ARN

AWS Secret Access Key Or External ID

Enter Secret

Enter external ID

Logging Source

Cloudwatch

Cloudwatch

S3 Bucket/Log Group(s)/SQS Queue URL

Provide cloudwatch log group

Provide cloudwatch log group

Bucket Prefix Path(s)

Leave Empty

Leave Empty

 

Legal Notice

Copyright © 2021 Accenture. All rights reserved.

Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.