The Public Cloud Connector brings visibility and business alignment to the company’s cloud investments. The ServiceNow Certified scoped application is the most robust integration between ServiceNow and Amazon Web Services (AWS), Azure, and Google Cloud. Having full, up-to-date knowledge of the infrastructure and providing the tools to take action on that information, brings the tools to manage the business and leverage the investment.
Documentation available on-line: https://icgautomation.atlassian.net/wiki/spaces/PD/pages/1990524937/Public+Cloud+Connector
PLEASE CONTACT US PRIOR TO INSTALLING.
Data Synchronization
- Integrated with the ServiceNow credential store.
Cloud Integration.
CMDB
- Populates CMDB with relevant CIs and relationships from AWS, Azure and Google Cloud.
Budgets
- Set custom budgets inside of ServiceNow for AWS Accounts.
- See Linked Account costing data.
- Track money spent and projected cost inside tables and a custom Budget Portal
- Control access to resources based on amount budget used on a per-AWS Account basis.
- Set leases and sleep schedules for EC2 Servers to reduce resources used.
- Track and Monitor EC2 resource costs.
- Display EC2 Instance costs prior to provisioning.
Service Catalog and Data Integration for AWS
- Access catalog items and provisioned CI’s in a custom Service Portal.
- Provision AWS Service Catalog items from a single ServiceNow form.
- Provision Cloud Formation Templates from a single ServiceNow form.
- Full EC2 Provisioning and Day 2 action support.
- Create and Modify IAM Users, Groups and Policies.
- Create and Modify Security Groups firewall rules and see their association with EC2 Instances.
- Automatically updates the CMDB when requests in AWS finish.
- Control user and group access to specific catalog items.
- Assign approval policies. Supports multiple stages of user and group approval.
- Trigger incidents when AWS catalog requests fail.
- Discover:
- IAM Groups, IAM Users, IAM Roles, IAM Policies, S3 Buckets, Instance Profiles, Hosted Zones, Route53 Traffic Policy and Policy Instances
- VPC, Availability Zone, Subnets, Security Groups (firewall rules), Key Pairs, Network Adapters, EC2 Instances, Volumes, RDS Instances, Autoscaling groups, CF Stacks, Kubernetes Clusters, Portfolios, Products, Alarms, Load Balancers, Tags, Snapshots and more.
Service Catalog and Data Integration for Azure
- Request new Azure Virtual Machines and Resource Groups
- Create and use new SSH keys to access your Virtual Machines
- Perform Lifecycle Operations on deployed and discovered Virtual Machine resources
- Terminate Resource Groups and Virtual Machines
- Automatically updates the CMDB when requests in Azure finish.
- Discover:
- Resource Groups, Networks, Images, Virtual Machines, Vault, Security Group, Snapshots, App Gateways and Storage Accounts
Service Catalog and Data Integration for Google
- Request new Google Virtual machines
- Perform Lifecycle Operations on deployed and discovered Virtual Machine resources
- Terminate Virtual Machines
- Automatically updates the CMDB when requests in Google finish.
- Discover:
- Regions, Zones, Networks, Subnets, Sizes, Virtual Machines, Instance Templates and Images
Change Management
Create and assign approval policies to catalog items.
- Supports OOTB ServiceNOW approval processes.
- Enables the easy creation of custom approval policies in ServiceNow.
- Supports multiple stages of group and user approval.
- Supports change windows, meaning that automated requests will execute in a user specified change window.
Incident Management
Trigger Incidents and assign incidents to support groups automatically when problems in the environment are detected such as:
- Connectivity issues between ServiceNOW, MID Server, and external systems.
- Authorization issues between ServiceNOW and external systems.
- Catalog request failures for provisioning and day 2 operations.
- CMDB operation failures.
Robust Error Handling
Automatically detects and analyzes errors encountered during automated processes.
- Analyzed errors are automatically presented in a dashboard that described their root cause.
- High impact errors trigger the automatic creation of incidents.
Support Levels
Assign support groups to various criteria so that the proper groups are automatically notified when issues are encountered.
- Assign support groups and level of impact for specific classes of errors.
- Assign support groups for specific external system endpoints.
This release enhances the Data Synchronization process, optimizing database queries meant to improve performance in large environments and provides increased options for processing data. Minor bug issues also addressed.
Documentation available on-line: https://icgautomation.atlassian.net/wiki/spaces/PD/pages/1990524937/Public+Cloud+Connector
ServiceNow Configuration
Version
ServiceNow Vancouver, Washington DC, Xanadu
Windows or Linux MID Server for compatible ServiceNow version (See below for more details)
Cloud Configuration
An active AWS Account
An Active Azure Subscription
An Active Google Cloud Projecct
MID Server Configuration
Operating System
Windows or Linux operating system.
Version
The MID server must be running the 64-bit version. If the MID server installation files are downloaded according to the instructions listed on the ServiceNow documentation, then this requirement will be met.
https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/mid-server/reference/r_MIDServerSystemRequirements.html
Installation
Please see the following ServiceNow documentation for information on how to install a MID Server:
https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/mid-server/concept/mid-server-installation.html
Hardware
Follow ServiceNow guidelines, in general, each MID server should have at least:
- 2 CPUs
- 8192 MB (8 GB) of Memory
- 40 GB Linux, 100 GB Windows total on the primary Hard Disk
- Java Virtual Environment RAM should be set to a minimum of 2048 mb in the MID Server wrapper.override.conf file (3072 - 4096 for Large environments)
Load Balancing
If multiple MID servers are used for failover, then the MID server cluster must adhere to the guidelines as described below:
https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/mid-server/task/t_ConfigureAMIDServerCluster.html