Automated bucket policy management arrangements

US10489144B1 · US · B1

Patent metadata
FieldValue
Publication numberUS-10489144-B1
Application numberUS-201916518424-A
CountryUS
Kind codeB1
Filing dateJul 22, 2019
Priority dateJul 22, 2019
Publication dateNov 26, 2019
Grant dateNov 26, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Arrangements for automatically implementing bucket policy management making it automatic that all affected members are always completely and consistently informed of changes to a policy code as they occur, and making it automatic that a complete and accurate historical record is maintained regarding all policy code changes as they occur over time.

First claim

Opening claim text (preview).

The invention claimed is: 1. A non-transitory, computer-readable storage medium embodying a bucket policy management program which, when executed, causes computer to implement bucket policy management operations for bucket policy code changes, the bucket policy management operations comprising: monitoring for receipt into a topic, of a payload indicative of a bucket policy code change submitted per request of a committer; and triggering an automatic bucket policy management handling designated for the topic, the bucket policy management handling including automatically: determining, from the payload, a Uniform Resource Locator (URL) path to a repository location where the bucket policy code is stored; determining, from the payload, details of the committer who requested the bucket policy code change; determining, from the payload, whether a type of the bucket policy code change is a new bucket policy code or an updated bucket policy code; utilizing the URL path to fetch the bucket policy code from the repository location, and if checking a predetermined validation of the bucket policy code is successful: determining a bucket name of a bucket for holding the bucket policy code; storing a backup copy of any existing bucket policy code in the bucket having the bucket name; and updating the existing bucket policy code in the bucket with the bucket policy code of the bucket policy code change; and notifying a team collaboration hub service of predetermined information selected from a list including: the bucket policy code change; the details of the committer who requested the bucket policy code change; the type of the bucket policy code change; whether validation of the bucket policy code was successful; and the bucket name of the bucket holding the bucket policy code. 2. The storage medium as claimed in claim 1 , wherein the payload is configured to comprise payload content detailing at least: the URL path to the repository location where the bucket policy code is stored; details of the committer who requested the bucket policy code change; and whether a type of the bucket policy code change is a new bucket policy code or an updated bucket policy code. 3. The storage medium as claimed in claim 2 , wherein the determining of the URL path, the details of the committer and the type of the bucket policy code change is determined by parsing, from the payload content: the URL path to the repository location where the bucket policy code is stored; details of the committer who requested the bucket policy code change; and whether the type of the bucket policy code change is a new bucket policy code or an updated bucket policy code. 4. The storage medium as claimed in claim 1 , wherein the payload is configured to comprise content detailing at least: the URL path to the repository location where the bucket policy code is stored; details of the committer who requested the bucket policy code change; whether a type of the bucket policy code change is a new bucket policy code or an updated bucket policy code; and, a bucket name of a bucket for holding the bucket policy code. 5. The storage medium as claimed in claim 4 , wherein the determining of the URL path, the details of the committer, the type of the bucket policy code change and the bucket name, is determined by parsing, from the payload content: the URL path to the repository location where the bucket policy code is stored; details of the committer who requested the bucket policy code change; whether the type of the bucket policy code change is a new bucket policy code or an updated bucket policy code; and, the bucket name of the bucket for holding the bucket policy code. 6. The storage medium as claimed in claim 1 , wherein the bucket policy management program is implemented as an Amazon Web Services (AWS) Lambda function which is triggered to execute responsive to the receipt into the topic, of the payload indicative of the bucket policy code change submitted per request of the committer. 7. The storage medium as claimed in claim 1 , the bucket policy management operations further comprising: if the checking of the predetermined validation of the bucket policy code is unsuccessful, providing a communication to the committer informing of an unsuccessful validation. 8. A bucket policy management method to implement bucket policy management operations for bucket policy code changes, the bucket policy management method comprising: monitoring for receipt into a topic, of a payload indicative of a bucket policy code change submitted per request of a committer; and triggering an automatic bucket policy management handling designated for the topic, the bucket policy management handling including automatically: determining, from the payload, a Uniform Resource Locator (URL) path to a repository location where the bucket policy code is stored; determining, from the payload, details of the committer who requested the bucket policy code change; determining, from the payload, whether a type of the bucket policy code change is a new bucket policy code or an updated bucket policy code; utilizing the URL path to fetch the bucket policy code from the repository location, and if checking a predetermined validation of the bucket policy code is successful: determining a bucket name of a bucket for holding the bucket policy code; storing a backup copy of any existing bucket policy code in the bucket having the bucket name; and updating the existing bucket policy code in the bucket with the bucket policy code of the bucket policy code change; and notifying a team collaboration hub service of predetermined information selected from a list including: the bucket policy code change; the details of the committer who requested the bucket policy code change; the type of the bucket policy code change; whether validation of the bucket policy code was successful; and the bucket name of the bucket holding the bucket policy code. 9. The bucket policy management method as claimed in claim 8 , wherein the payload is configured to comprise payload content detailing at least: the URL path to the repository location where the bucket policy code is stored; details of the committer who requested the bucket policy code change; and whether a type of the bucket policy code change is a new bucket policy code or an updated bucket policy code. 10. The bucket policy management method as claimed in claim 9 , wherein the determining of the URL path, the details of the committer and the type of the bucket policy code change is determined by parsing, from the payload content: the URL path to the repository location where the bucket policy code is stored; details of the committer who requested the bucket policy code change; and whether the type of the bucket policy code change is a new bucket policy code or an updated bucket policy code. 11. The bucket policy management method as claimed in claim 8 , wherein the payload is configured to comprise content detailing at least: the URL path to the repository location where the bucket policy code is stored; details of the committer who requested the bucket policy code change; whether a type of the bucket policy code change is a new bucket policy code or an updated bucket policy code; and, a bucket name of a bucket for holding the bucket policy code. 12. The bucket policy management method as claimed in claim 11 , wherein the determining of the URL path, the details of the committer, the type of the bucket policy code change and the bucket name, is determined by parsing, from the payload content: the URL path to the repository location where the bucket policy code is stored; details of the committer who requested the bucket poli

Assignees

Inventors

Classifications

  • Staff planning in a project environment · CPC title

  • G06F8/65Primary

    Updates (security arrangements therefor G06F21/57) · CPC title

  • Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10489144B1 cover?
Arrangements for automatically implementing bucket policy management making it automatic that all affected members are always completely and consistently informed of changes to a policy code as they occur, and making it automatic that a complete and accurate historical record is maintained regarding all policy code changes as they occur over time.
Who is the assignee on this patent?
Capital One Services Llc
What technology area does this patent fall under?
Primary CPC classification G06Q10/063118. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Nov 26 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 3 related publications on this page (citations in our corpus or others sharing the same primary CPC).