Welcome to ECM!

Great job on completing the ECM onboarding process. By now, you should have received a confirmation from the ECM team that you the resources in your ECM AWS Cloud Account have been provisioned with details on login and billing access.  This welcome packet contains additional resources that may be of assistance to you as an ECM Tenant as well as who to reach out for help.

Register your ECM Environment w/ CIS Vulnerability Management & SPLUNK:

Visit the ECM Environment SPLUNK/Vulnerability Management page for instructions on how to register your newly provisioned ECM environment w/ both CIS Vulnerability Managment and SPLUNK. 

Firewall Rule Management:

Information on how to submit a Firewall Rule Management Request can be found here.

Logging In: 

AWS

Azure

  Due to the fact that Leidos regular credentials are in use for consuming M365 offerings, in order to login to the GCC-H environment with the AAD_credentials, administrators and engineers must use a Incognito window in Google Chrome or a Private Window in Firefox to complete the login.

AWS Navigating KION and Resources:

For more information on navigating KION, here is a informational recording on how to access KION and more.

KION Cost Saving Opportunities:

https://ecm.leidos.com/portal/project/132/savings-opportunity

Viewing Cost Utilization & Inventory Information in KION   

*Please note: your regular account needs to be part of the billing AD group below* 

               CorporateITS_CIVCMIG_BillingAccess

Once you have successfully logged in, please reply and let us know so we can close your ticket with ECM.  

AWS Customer DNS and Certificate Options:

Customer certificates are handled through Identrust, so you would request the certificate through this process: https://prism.leidos.com/technology/corporate_information_security/security_for_system_administrators/security_for_system_administrators_wiki_articles/order_a_secure_socket_layer_ssl_certificate_identrust

It can be imported into AWS Certificate Manager or installed directly on EC2 instances, but if you use ACM you're limited to a 2048-bit private key when generating the CSR.

As for DNS, you have two options: on-premises DNS, or Route 53. Here is more information on Customer DNS and options.

https://confluence.sdo.leidos.com/x/tgP2Dw

ECM Liability Policy and Responsibility Matrix

ECM Memorandum of Understanding (MOU)

The MOU contains the ECM liability and responsibility matrix for the ECM service offering. In the MOU you will find the following:


For Further Assistance:

Please refer to our ECM Customer Post Deployment Support page.

Also, see the rest of our resources available at the ECM Knowledge Base for additional documents and information.