View a markdown version of this page

Deleting a service-linked role for WorkSpaces Secure Browser - Amazon WorkSpaces Secure Browser

Amazon WorkSpaces Secure Browser will no longer be open to new customers starting October 29, 2026. If you would like to use Amazon WorkSpaces Secure Browser, sign up prior to that date. Existing customers can continue to use the service as normal. For more information, see Amazon WorkSpaces Secure Browser availability change.

Deleting a service-linked role for WorkSpaces Secure Browser

If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it.

Note

If the WorkSpaces Secure Browser service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again.

To delete WorkSpaces Secure Browser resources used by the AWSServiceRoleForAmazonWorkSpacesWeb
  • Choose from one of the following options:

    • If you use the console, delete all of your portals on the console.

    • If you use the CLI or API, disassociate all of your resources (including browser settings, network settings, user settings, trust stores, and user access logging settings) from your portals, delete these resources, and then delete the portals.

To manually delete the service-linked role using IAM

Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForAmazonWorkSpacesWeb service-linked role. For more information, see Deleting a Service-Linked Role in the IAM User Guide.