IP Library › Granted Patent US 10,489,144
Granted Patent B1
US 10,489,144 · App. 16/518,424 · Granted Nov 26, 2019

Automated bucket policy management arrangements

Inventors: Rexwell Minnis (Tysons Corner, VA); Lane Martin (Richmond, VA); Warner Emdee (Midlothian, VA)
Assignee: Capital One Services, LLC
G06F8/65G06F8/71G06Q10/063118
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,489,144
App. No.
16/518,424
Granted
Nov 26, 2019
Kind
B1
Abstract

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.

Claims (54)

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 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.

13. The bucket policy management method as claimed in claim 8 , wherein at least a portion of the bucket policy management method is implemented via 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.

14. The bucket policy management method as claimed in claim 8 , 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.

15. A system configured to automatically implement bucket policy management operations for bucket policy code changes, the system comprising:

at least one hardware processor and memory arrangement configured to:

monitor for receipt into a topic, of a payload indicative of a bucket policy code change submitted per request of a committer; and

trigger 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.

16. The system as claimed in claim 15 , 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.

17. The system as claimed in claim 16 , 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.

18. The system as claimed in claim 15 , 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.

19. The system as claimed in claim 18 , 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.

20. The system as claimed in claim 15 , the at least one hardware processor and memory arrangement further configured to:

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.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 23, 2019
From: MINNIS, REXWELL; MARTIN, LANE; EMDEE, WARNER
To: CAPITAL ONE SERVICES, LLC
Reel/Frame 049828/0977 →
Cited By (1)
US 12,578,961