End of support notice: On March 31, 2027, AWS will end support for AWS Service Management Connector. After March 31, 2027, you will no longer be able to access the AWS Service Management Connector console or AWS Service Management Connector resources. For more information, see [AWS Service Management Connector end of support](https://docs.aws.amazon.com/smc/latest/ag/smc-end-of-support.html). 

# What is AWS Service Management Connector?


AWS Service Management Connector and its integration connectors enable you to provision, manage, and operate native AWS resources and capabilities in familiar IT Service Management (ITSM) 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.

For an interactive introduction to AWS Service Management Connector, review the [ServiceNow Connector workshop](https://catalog.us-east-1.prod.workshops.aws/workshops/d40750d7-a330-49be-9945-cde864610de9/en-US/5-itsm/getting-started) in the *AWS workshop studio*. 

# AWS Service Management Connector end of support


End of support notice: As of March 31, 2026, AWS Service Management Connector is no longer available to new customers. If you are an existing customer, you can continue using the service until March 31, 2027. After March 31, 2027, you will no longer be able to access AWS Service Management Connector functionality.

We recommend migrating to AWS Partner solutions or building direct SDK integrations.

## Migration options


AWS Partner solutions  
Explore qualified partners through the [AWS Partner Solution Finder](https://partners.amazonaws.com/) to find partners with ServiceNow, Atlassian, and AWS integration expertise.

Direct SDK Integration  
Build native integrations using AWS SDKs and APIs for AWS Config, Service Catalog, Security Hub CSPM, Support, and Systems Manager. For more information, see the following API documentation:  
+ [AWS Service Catalog API Reference](https://docs.aws.amazon.com/servicecatalog/latest/dg/API_Reference.html)
+ [AWS Config API Reference](https://docs.aws.amazon.com/config/latest/APIReference/Welcome.html)
+ [AWS Security Hub CSPM API Reference](https://docs.aws.amazon.com/securityhub/1.0/APIReference/Welcome.html)
+ [Support API Reference](https://docs.aws.amazon.com/awssupport/latest/user/about-support-api.html)
+ [AWS Systems Manager API Reference](https://docs.aws.amazon.com/systems-manager/latest/APIReference/Welcome.html)

AWS native alternatives  
For Security Hub CSPM specifically, AWS provides native integrations with Jira Cloud and ServiceNow:  
+ [Jira Cloud integration with AWS Security Hub](https://docs.aws.amazon.com/securityhub/latest/userguide/jiracloud.html)
+ [ServiceNow integration with AWS Security Hub](https://docs.aws.amazon.com/securityhub/latest/userguide/servicenow.html)

This change does not impact AWS Config, AWS Service Catalog, AWS Security Hub CSPM, Support, or AWS Systems Manager.

# Security in AWS Service Management Connector
Security in AWS Service Management Connector

Service Management Connector uses the roles and permissions that an IAM user requires to access your specific AWS resources and services. Service Management Connector requires two IAM user roles, *SyncUser* and *EndUser*, to perform various integration operations. For more information, see your chosen Connector to identify the IAM permissions for a specific integration.

Service Management Connector is not within the scope of any AWS compliance programs. Using Service Management Connector to access a service does not alter that service’s compliance.

 **Encryption at rest** — Service Management Connector does not store any customer data. The connector installs Tables and Schemas on third-party platforms that can store credentials in the platform’s database. All credentials are encrypted and masked to comply with platform best practices. 

 **Encryption in transit** — By default, AWS encrypts all data transmitted between external platforms and Service Management Connector by sending data through a HTTPS/TLS connection.