Closed Bug 1151942 Opened 11 years ago Closed 11 years ago

Access to lorax s3 bucket

Categories

(Infrastructure & Operations :: IT-Managed Tools, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pmac, Assigned: fox2mike)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/903] )

We'll be launching a static site using the s3 bucket "lorax". Please give me admin access to this bucket (I'm pmac) so that I can tweak the web-hosting settings for the bucket.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/903]
Component: WebOps: Engagement → WebOps: IT-Managed Tools
Assignee: server-ops-webops → smani
pmac, I've created a new lorax-s3 group with perms and added you to the group. Let me know if it works for you, else please reopen the bug and we can debug.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Still getting "Permission denied" when trying to view the bucket.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Yeah. Definitely not working. What do you think :fox2mike?
Flags: needinfo?(smani)
(In reply to Paul McLanahan [:pmac] from comment #3) > Yeah. Definitely not working. What do you think :fox2mike? Sweet. Haha, I'll poke at this a bit today.
Flags: needinfo?(smani)
:fox2mike Any update on this? :pmac Bryan enabled the domain today, but direct linking is giving the error below. I assume you need access to address this This XML file does not appear to have any style information associated with it. The document tree is shown below. <Error> <Code>AccessDenied</Code> <Message>Access Denied</Message> <RequestId>F22FB01658571BE4</RequestId> <HostId> h+hWkqZ2uM8Xzm6fN4FKmenz/nKBPzm6mR8bQ7DyMcmy5hpnPu8P2z+6hsMrSfMRy3LDgQ2WzXM= </HostId> </Error>
Flags: needinfo?(smani)
Flags: needinfo?(pmac)
Right. That's the error I need to deal with via the console.
Flags: needinfo?(pmac)
Confirmed with :pmac this is working now
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Flags: needinfo?(smani)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.