Skip to content

Instantly share code, notes, and snippets.

AzSKADOContinuousAssurance Scanning Report

Look at the individual control evaluation status in the CSV file.

  1. If the control has passed, no action is necessary.
  2. If the control has failed, look at the control evaluation detail in the LOG file to understand why.
  3. If the control status says Verify, it means that human judgement is required to determine the final control status. Look at the control evaluation output in the LOG file to make a determination.
  4. If the control status says Manual, it means that AzSK.ADO (currently) does not cover the control via automation OR AzSK.ADO is not able to fetch the data. You need to manually implement/verify it.

Prerequisites

  • required aws permission
    • create EC2 instance
    • export image
    • create folder and upload file to a S3 bucket
  • aws-cli/2.0.8 or later

Process

Create VM Image

Create a EC2 instance

What is Apache Nifi?

Apache NiFi is a data flow tool that is focused on moving data between systems.
NiFi's focus is on capabilities like visual command and control, filtering of data, enrichment of data, data provenance, and security, just to name a few. With NiFi, you aren't writing code and deploying it as a job, you are building a living data flow through the UI that is taking effect with each action.
Data flow tool is often complimentary and used to manage the flow of data from the sources to the streaming processing platforms, such as SAS ESP.

What is SAS Event Stream Processing (a.k.a. SAS ESP)?

Event stream processing applications typically perform real-time analytics on streams of events. These streams are continuously published into an event stream processing engine. Typical use cases for event stream processing include but are not limited to the following:

  • sensor data monitoring and management
  • operational systems monitoring and management
This file has been truncated, but you can view the full file.
G2018-05-11 19:38:58,193 WARN (WrapperSimpleAppMain) [com.springsource.tcserver.serviceability.rmi.JmxSocketListener] Detected LDAP configuration 'D:/SAS/Config/Lev1/Web/WebAppServer/SASServer8_1/conf/jaas.config', but there is no ldap configuration entry specified.
2018-05-11 19:38:58,259 INFO (WrapperSimpleAppMain) [org.apache.catalina.startup.Catalina] Initialization processed in 1368 ms
2018-05-11 19:39:03,565 INFO (WrapperSimpleAppMain) [org.apache.catalina.core.StandardService] Starting service Catalina
2018-05-11 19:39:03,565 INFO (WrapperSimpleAppMain) [org.apache.catalina.core.StandardEngine] Starting Servlet Engine: Pivotal tc Runtime 3.0.0.RELEASE/7.0.55.A.RELEASE
2018-05-11 19:39:03,584 INFO (localhost-startStop-1) [org.apache.catalina.startup.HostConfig] Deploying configuration descriptor D:\SAS\Config\Lev1\Web\WebAppServer\SASServer8_1\conf\Catalina\localhost\SASComplianceSolutionsMid.xml
2018-05-11 19:39:09,553 INFO (localhost-startStop-1) [org.apache.tomcat.util.digester.Digester] TLD sk
# Copyright 2016 The TensorFlow Authors. All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
1 OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [OBJECT_E]
Segmentation Violation
Traceback of the Exception:
@neallee2012
neallee2012 / New capacity scheduler
Created May 19, 2016 05:39
New capacity scheduler
<?xml version="1.0"?>
<configuration>
<property>
<name>yarn.scheduler.capacity.root.queues</name>
<value>default,tk,spark</value>
</property>
<property>
<name>yarn.scheduler.capacity.root.capacity</name>
<value>100</value>
</property>