Accenture MDR Quick Start Guide for Amazon Web Service (AWS) Elastic Load Balancer
This quick start guide will help Accenture MDR customers configure Amazon Web Service (AWS) Elastic Load balancer to allow log collection from the Log Collection Platform (LCP).Â
The 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 | SQS | 443 (TCP) | Default port |
Configuring AWS Elastic Load Balancer
MxDR supports log collection using S3 via SQS.
Prerequisite:
S3 bucket is created. Please refer the following page to create a S3 bucket. https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-bucket.html
To create Elastic Load Balancer please refer https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/load-balancer-getting-started.html
Â
Device Configuration Steps:
To enable access logging to send Access Logs to S3
Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
In the navigation pane, choose Load Balancers.
Select your load balancer.
On the Description tab, choose Edit attributes.
On the Edit load balancer attributes page, do the following:
Choose Enable access logs.
For S3 location, type the name of your S3 bucket, including any prefix (for example,Â
my-loadbalancer-logs/my-app
). Please be sure that you own this bucket and that you configured the required bucket policy.Choose Save.
Â
Creating Amazon Simple Queue Service (SQS) and attaching it to S3:
To create SQS and attach it with S3 please refer https://mdrkb.atlassian.net/wiki/x/AQCeEQ
Â
For more information please refer : https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-access-logs.html#enable-access-logging
Note: Please refer below page to check required IAM user and KMS Key policies for S3, SQS and KMS
https://mdrkb.atlassian.net/wiki/x/hoCdEQ
Â
Note: 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
S3: For S3 or SQS logging source, S3 URL should be allowed.
SQS: For SQS logging source, SQS URL should be allowed.
Â
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: The AWS Elastic Load balancer event collector (3965 -API) properties to be configured by MDR in table.
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 | SQS | SQS |
S3 Bucket/Log Group(s)/SQS Queue URL | Provide SQS URL | Provide SQS URL |
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.