Skip to main content

More Info:

Ensure that PubSub Subscriptions have set expiration

Risk Level

Low

Address

Operational Excellence, Cost Optimization

Compliance Standards

CBP

Triage and Remediation

Remediation

Using Console

To remediate the misconfiguration of PubSub Subscriptions not having set expiration for messages in GCP using GCP console, you can follow the below steps:
  1. Open the GCP console and navigate to the Pub/Sub section.
  2. Select the Subscription that you want to remediate.
  3. Click on the “Edit” button for the selected Subscription.
  4. In the “Edit Subscription” window, scroll down to the “Message retention duration” section.
  5. Set the message retention duration to the desired value. This value should be based on how frequently the Subscription is polled and how long it takes to process the messages.
  6. Click on the “Save” button to save the changes.
By following these steps, you will remediate the misconfiguration of PubSub Subscriptions not having set expiration for messages in GCP using GCP console.

To remediate the issue of PubSub subscriptions not having set expiration for messages in GCP using GCP CLI, you can follow the below steps:
  1. Open the Cloud Shell in your GCP console.
  2. Run the following command to list all the subscriptions in your project:
  3. Choose the subscription for which you want to set the expiration time for messages.
  4. Run the following command to set the expiration time for messages in the chosen subscription:
    Replace <subscription-name> with the name of the chosen subscription and <duration> with the duration for which you want to set the expiration time for messages. The duration should be in the format of n[d|h|m|s] where n is the number of days, hours, minutes or seconds. For example, to set the expiration time for messages in a subscription named my-subscription to 7 days, run the following command:
  5. Verify that the expiration time for messages has been set for the chosen subscription by running the following command:
    Replace <subscription-name> with the name of the chosen subscription. The output should display the expiration time for messages in the subscription.
By following these steps, you can remediate the issue of PubSub subscriptions not having set expiration for messages in GCP using GCP CLI.
To remediate the issue of PubSub subscriptions not having set expiration for messages in GCP using Python, you can follow the below steps:
  1. First, you need to identify the subscription(s) that do not have set expiration for messages. You can use the following command to list all subscriptions in a project:
    This will give you a list of all subscriptions in your project.
  2. Once you have identified the subscription(s) that need to be remediated, you can use the Google Cloud Pub/Sub client library for Python to set the message expiration time for each subscription. Here is a sample Python script that sets the message expiration time for a subscription:
    Replace <PROJECT_ID> and <SUBSCRIPTION_NAME> with your project ID and subscription name respectively.
  3. Run the Python script to set the message expiration time for the subscription(s) that need to be remediated.
    This will update the subscription(s) with the message expiration time and print the updated subscription information.
By following these steps, you can remediate the issue of PubSub subscriptions not having set expiration for messages in GCP using Python.

Additional Reading: