We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.
If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”
Essential cookies are necessary to provide our site and services and cannot be deactivated. They are usually set in response to your actions on the site, such as setting your privacy preferences, signing in, or filling in forms.
Performance cookies provide anonymous statistics about how customers navigate our site so we can improve site experience and performance. Approved third parties may perform analytics on our behalf, but they cannot use the data for their own purposes.
Functional cookies help us provide useful site features, remember your preferences, and display relevant content. Approved third parties may set these cookies to provide certain site features. If you do not allow these cookies, then some or all of these services may not function properly.
Advertising cookies may be set through our site by us or our advertising partners and help us deliver relevant marketing content. If you do not allow these cookies, you will experience less relevant advertising.
Blocking some types of cookies may impact your experience of our sites. You may review and change your choices at any time by selecting Cookie preferences in the footer of this site. We and selected third-parties use cookies or similar technologies as specified in the AWS Cookie Notice.
We display ads relevant to your interests on AWS sites and on other properties, including cross-context behavioral advertising. Cross-context behavioral advertising uses data from one site or app to advertise to you on a different company’s site or app.
To not allow AWS cross-context behavioral advertising based on cookies or similar technologies, select “Don't allow” and “Save privacy choices” below, or visit an AWS site with a legally-recognized decline signal enabled, such as the Global Privacy Control. If you delete your cookies or visit this site from a different browser or device, you will need to make your selection again. For more information about cookies and how we use them, please read our AWS Cookie Notice.
To not allow all other AWS cross-context behavioral advertising, complete this form by email.
For more information about how AWS handles your information, please read the AWS Privacy Notice.
We will only store essential cookies at this time, because we were unable to save your cookie preferences.
If you want to change your cookie preferences, try again later using the link in the AWS console footer, or contact support if the problem persists.
AWS Service Management Connector (SMC or connector) enable customers to provision, manage, and operate native AWS resources and capabilities in familiar ITIL® tooling, such as ServiceNow and Atlassian. These integrations enable Enterprises to accelerate migration and AWS adoption at scale through oversight and governance in their declared operational tooling and system of record.
AWS Service Management Connector currently integrates with ServiceNow and Atlassian’s Jira Service Management (Data Center or Cloud) version.
Available integrations are listed in the public documentation.
The AWS services integrated with AWS Service Management Connector for ServiceNow are AWS Service Catalog, AWS Service Catalog AppRegistry, AWS Health, AWS Config, AWS Security Hub, AWS Support, AWS Systems Manager OpsCenter, AWS Systems Manager Automation, AWS Systems Manager Change Manager, and AWS Systems Manager Incident Manager
Available integrations are listed in the public documentation.
If you use AWS Management & Governance services to enable, secure, provision, and operate cloud resources, you can use the connector to enable your end users to use your existing IT Service Management platforms such as ServiceNow and Atlassian's Jira Service Management to manage and operate your AWS cloud infrastructure at scale.
Getting started with AWS Service Management Connector is easy. You can install the connector for free from ServiceNow Store/Atlassian Marketplace respectively or using the installation files available in the public documentation. Once the installation is complete, create the IAM users with the required permissions and add the access key and secret access key of the users back into the platform. Validate if the connections are successful and you are ready to go!
AWS Service Management Connector is available for free for all AWS customers. Additional pricing implications can be found on the Pricing page.
The integration features are available in all commercial and GovCloud AWS Regions where AWS Support, AWS Service Catalog, AWS Config, AWS Systems Manager, AWS Health Dashboard, AWS Systems Manager Incident Manager, AWS Systems Manager Change Manager and AWS Security Hub services are available.
AWS Service Management Connector aligns to Information Technology Infrastructure Library (ITIL*), IT service management frameworks and common IT standard operating procedures.
Yes. The connectors for ServiceNow and Atlassian's Jira Service Management are certified by the respective vendors and recertified based on the vendors criteria.
Connectors currently don’t support AWS Organizations. Customers would need to manage the IAM users and permissions on their AWS Accounts and onboard the credentials back into the respective ITSM platforms to setup the integrations.
We recommends following the principle of Least Privilege for IAM permissions. The permissions required for the integrations are listed in our public documentation. Customers also have access to boilerplate CloudFormation templates that helps setup the permissions and infrastructure for available integrations for setting up a proof of concept(POC) in a sandbox or dev environment. Once the POC is successful, scope down the permissions accordingly for your QA and PROD environments.
AWS Service Management Connector(SMC) for ServiceNow is scoped application developed and managed by AWS. If you would like to customize the connector, you can download and install the connector using the Update Set provided with the public documentation. The Update Set will provide you write access to all code components of the connector. Please note that the customizations needs to be tested thoroughly in a dev/sandbox environment, before production deployment. Additionally, the customizations needs to be managed and owned by the customer and should be factored in during version upgrades.
Yes. The customer has the ability to use custom workflows with their AWS Service Catalog portfolios and products. You can also set individual workflows on portfolios as well. For more information, see Validating AWS Service Catalog integration.
Yes. The AWS Config integration with the AWS Service Management Connector for ServiceNow allows customers to use Aggregators. The aggregators should be configured in the connector with the exact name and region information. Once the aggregator is setup, the connector will use the aggregator configuration for fetching resource information from all accounts and regions that are configured in the aggregator. For more information, see Configuring synchronization of AWS Config data using an Aggregator in ServiceNow CMDB.
AWS Service Management Connector releases new versions based on customer feedback at least twice a year and more depending on need. While upgrading to a newer version of SMC, please ensure to test the integrations in a dev or sandbox environment. If additional customizations have been added to the connector code, please ensure to review and merge the conflicts accordingly.