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) made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Martyna Wojtas (Inactive) made changes -
            Labels New: bamboo-bugs-grooming
            Pawel Skierczynski made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 2652687 ] New: JAC Bug Workflow v3 [ 3382802 ]
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]
            Bugfix Automation Bot made changes -
            Support reference count Original: 1 New: 2
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Krystian Brazulewicz made changes -
            Component/s New: S3 storage [ 38898 ]
            Krystian Brazulewicz made changes -
            Occurrence Factor New: 10% [ 12830 ]
            Status Original: Needs Triage [ 10030 ] New: Open [ 1 ]
            Alexey Chystoprudov made changes -
            Component/s New: Artifacts [ 11229 ]

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

                Created:
                Updated:
                Resolved: