# Ensure SNS Subscriptions Do Not Use HTTP Endpoints

- Source: https://support.icompaas.com/support/solutions/articles/62000233556-ensure-sns-subscriptions-do-not-use-http-endpoints
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [AWS New Checks](https://support.icompaas.com/support/solutions/folders/62000169206)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability**

-   **Level 2**

#### **Description**

Amazon SNS supports HTTP and HTTPS endpoints for delivering messages. However, HTTP endpoints transmit data in plaintext, making them vulnerable to interception and unauthorized access. To enhance security, all SNS subscriptions should use HTTPS endpoints instead of HTTP.

#### **Rationale**

-   Enhanced Security: HTTPS encrypts data in transit, protecting it from interception and unauthorized access.
    
-   Compliance: Meets regulatory requirements for secure data transmission.
    
-   Risk Mitigation: Reduces the risk of data breaches and man-in-the-middle attacks.
    

#### **Impact**

**Pros:**

-   Ensures secure communication between SNS and subscribed endpoints.
    
-   Reduces the risk of data interception and tampering.
    
-   Aligns with compliance and security standards.
    

**Cons:**

-   Requires configuration changes to migrate from HTTP to HTTPS endpoints.
    
-   May require additional setup for HTTPS certificates.
    

#### **Default Value**

By default, SNS subscriptions can use HTTP endpoints if explicitly configured.

#### **Pre-Requisite**

IAM Permissions:

-   sns:ListSubscriptions
    
-   sns:GetSubscriptionAttributes
    
-   sns:SetSubscriptionAttributes
    
-   AWS CLI installed and configured.
    

#### **Remediation**

#### **Test Plan:** 

**Using AWS Console:**

1.  Sign in to the AWS Management Console.
    
2.  Navigate to the SNS Dashboard.
    
3.  Select Subscriptions from the left-hand menu.
    
4.  Check the Protocol column for each subscription and identify any using HTTP.
    

**Using AWS CLI:**

1.  List All SNS Subscriptions:  
    
    aws sns list-subscriptions --query "Subscriptions\[\*\].{Protocol:Protocol,SubscriptionArn:SubscriptionArn}"
    
2.  Identify Subscriptions Using HTTP:  
    
    aws sns get-subscription-attributes --subscription-arn <subscription-arn> --query "Attributes.Protocol"
    

#### **Implementation Steps:** 

**Using AWS Console:**

1.  Sign in to the AWS Management Console.
    
2.  Navigate to the SNS Dashboard.  
    ![](https://support.icompaas.com/assets/kb/7f37fbb1c670d125.png)
    
3.  Select the subscription using an HTTP endpoint.  
    ![](https://support.icompaas.com/assets/kb/42f43f5e34e98d5c.png)
    
4.  Edit the subscription to replace the HTTP endpoint with an HTTPS endpoint.
    
5.  Save the changes.
    

**Using AWS CLI:**

1.  Update the Subscription to Use HTTPS:  
    
    aws sns set-subscription-attributes --subscription-arn <subscription-arn> --attribute-name Protocol --attribute-value https
    
2.  Verify the Changes:  
    
    aws sns get-subscription-attributes --subscription-arn <subscription-arn> --query "Attributes.Protocol"
    

#### **Backout Plan**

#### **Using AWS Console:**

1.  #### If switching to HTTPS causes any issues, sign in to the AWS Management Console.
    
2.  #### Navigate to Amazon SNS, select Subscriptions, and find the subscription with the incorrect HTTPS endpoint.  
    ![](https://support.icompaas.com/assets/kb/602e6dda7d6ec79f.png)![](https://support.icompaas.com/assets/kb/b76224a040fb215d.png)
    
3.  #### Change the endpoint back to HTTP if necessary (although this is not recommended for security reasons).
    
4.  #### Save the changes and verify that the subscription is functioning as expected.
    

#### **Using AWS CLI:**

1.  #### If there are issues with the HTTPS endpoint, you can revert the changes by setting the endpoint back to HTTP (not recommended):  
    
    aws sns set-subscription-attributes --subscription-arn <SUBSCRIPTION\_ARN> --attribute-name Endpoint --attribute-value "http://unsecure-endpoint.com" --region <REGION>
    
2.  #### Verify the changes have been reverted:  
    
    aws sns get-subscription-attributes --subscription-arn <SUBSCRIPTION\_ARN> --region <REGION>
    

#### **References**

-   [Amazon SNS HTTP/HTTPS Endpoints Documentation](https://docs.aws.amazon.com/sns/latest/dg/sns-http-https-endpoint-as-subscriber.html)
    
-   [AWS Security Best Practices for SNS](https://docs.aws.amazon.com/sns/latest/dg/sns-security-best-practices.html)
    
-   [AWS CLI - SNS Subscription Attributes](https://docs.aws.amazon.com/cli/latest/reference/sns/get-subscription-attributes.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
