Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-19805

403 errors connecting to S3 Artifact Handler, even if not used

XMLWordPrintable

      Summary

      During Artifact Expiry, logs show multiple 403 "Access Denied" errors accessing AWS S3, even if the S3 Handler is not used.

      Steps to Reproduce

      1. Setup Elastic agents with valid AWS credentials
      2. Enable S3 Artifact Handler
      3. Immediately disable S3 Artifact Handler
      4. Run build expiry/deletion jobs

      Expected Results

      No error 403 connecting to S3 as it was not used for any artifacts

      Actual Results

      The below exception is thrown in the atlassian-bamboo.log file:

      2018-03-30 17:48:08,475 ERROR [DelayedDeletionThread] [BambooPluginUtils] class com.atlassian.bamboo.build.artifact.S3ArtifactHandler was unable to delete artifacts for PROJ-PLAN-JOB
com.amazonaws.services.s3.model.AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: <id-hash>; S3 Extended Request ID: <ext-id-hash>), S3 Extended Request ID: <ext-id-hash>
	at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1639)
	... (truncated)

      Workaround

      Remove the S3 Bucket Name from the Bandana table:

      1. Stop Bamboo
      2. Backup the database
      3. Find the Artifact Handler Configurations 
        select SERIALIZED_DATA from BANDANA where BANDANA_KEY = 'artifactHandlersConfiguration';
      4. Find the S3 Artifact Handler bucketName value 
           <entry>
     <string>custom.artifactHandlers.comAtlassianBambooPluginArtifactHandlerRemote:S3ArtifactHandler:bucketName</string>
     <string>bucket-name-here</string>
   </entry>
      5. Remove the bucket-name-here string, so that section is: 
           <entry>
     <string>custom.artifactHandlers.comAtlassianBambooPluginArtifactHandlerRemote:S3ArtifactHandler:bucketName</string>
     <string>bucket-name-here</string>
   </entry>
      6. Start Bamboo

            [BAM-19805] 403 errors connecting to S3 Artifact Handler, even if not used

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 23 June 2020

            Hi,

            Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,

            Bamboo Team

            Martyna Wojtas (Inactive) added a comment - Atlassian Update - 23 June 2020 Hi, Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Bamboo Team

              Unassigned Unassigned
              ezeidan Ellie Z (they/them)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: