| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Subject/Summary | Timestamp | Name | Institution | Feature request | Use case | Implementing this request would increase the ease of use of AWS at my institution | Implementing this request would increase adoption of AWS at my institution | Implementing this request would increase security of AWS at my institution | Implementing this request is necessary to fulfill a legal/regulatory/security requirement | Anything else to add? (Optional) | Indicate your Support | Comments | Quarter Submitted | Status | |||||||||||||||
2 | Access to accurate cost and usage data at no cost | 7/13/2022 15:13:11 | Rick Rhoades | Penn State | Ability to use 3rd party cost visibility tools with timely, accurate cost and usage data regardless of contract type (direct/reseller), which should be provided at no cost. | Customers using the current Net+ AWS agreement via DLT are unable to be provided with accurate CUR data that represents the discounts included with this program. Use of standard AWS services work but, do not reflect these discounts as well. The current solution AWS Billing Conductor (ABC), appears to have been developed for reseller use but has been pushed to the customer to set up/support/fund. While many, including PSU, believe billing data should be provided free of charge, it's likely that all Higher Ed organizations cannot/will not pay the outragous prices that accompanies ABC. | 5 | 3 | 1 | No | Mike Warfe - CWRU Matthew Rich - Northwestern | 2022 Q2 | ||||||||||||||||||
3 | Azuay | 7/14/2022 9:40:27 | Freddy Sumba | CEDIA | Use cloud computing services like machine learning tools to find academics and research trends in Latin America countries and provide and framework for data driven decision to governs, universities and another institutions. | A case use could be a pool of resources for machine learning that researchers of latin American countries can access. The application of IA in the industry for Researchers in in Ecuador has a limitation to use public clouds. The cost cover can be according the project and case use. Like CEDIA we can schedule all projects through PMP teams. | 5 | 5 | 5 | No | 2022 Q2 | Investigating Solutions on top of AWS (Ronin, Service Workbench, etc.) | ||||||||||||||||||
4 | Seamless Intercloud Provider Communications | 7/14/2022 10:07:40 | Gerard Shockley | Boston University | Add the capability to seamlessly peer from/to other cloud providers used in higher education services. | Ability to peer from Azure, GCP, Other directly to AWS via supported methods (TGW, etc.) | 5 | 4 | 4 | No | Rick Rhoades - PSU | 2022 Q2 | Unlikely | |||||||||||||||||
5 | Custom Landing Page for Non-AWS experts | 7/14/2022 10:15:28 | John Heartlein | Saint Louis University | It would be nice if non-technical end users could have an organizational landing page with explanations of services, examples of common use cases, and a method for those users to deploy certain services without needed AWS and DevOPs experience. AWS marketing makes AWS sound like an "easy" solution, but once many researchers get into it, they realize they need significant amounts of assistance navigating AWS and getting it configured before they can conduct their research. They aren't used to the pay-as-you go model and usually end up backing away from AWS due to the complications. At my organization, our research computing group and IT staff don't have enough people to give white-glove service to every researcher that might otherwise try AWS. | Researchers, Faculty, Students, etc. | 4 | 5 | 4 | No | Annelie Rugg - UCLA | 2022 Q2 | Submitted | |||||||||||||||||
6 | Simplified S3 storage pricing | 7/14/2022 10:23:20 | John Bailey | Washington University in St. Louis | Provide a new tier of S3 storage called "AWS S3 Flat Rate" storage that charges ONLY for data consumed, and does NOT charge a separate fee for reads & writes. This would allow customers to accurately estimate the real-world charges for utilizing S3 without having to perform a POC. | AWS customers cannot accurately calculate S3 costs until they begin using the service. This is because the API call (read/write) charges vary wildly based on a number of factors such as how a data source (like a server backup system) interacts with S3. | 5 | 4 | 2 | No | 2022 Q2 | Submitted | ||||||||||||||||||
7 | Subsidizing security frameworks on behalf of other AWS accounts | 7/14/2022 10:55:51 | Kyle Weeks | University of Minnesota | Centralized security service costs in the Organization | It is difficult to create a secure landing zone for researchers when additional security frameworks are policy driven which they may not even be aware of through Security Hub, Config, and so forth. These items are managed from the Org, SecurityHub, ControlTower and add an additional cost to the individual AWS account. It would be ideal to be able to centralize Org costs of this nature to a central delegated AWS account such as with the delegated security hub process in order to meet governance, and allow researchers to not worry about this in their grant writing. | 5 | 5 | 5 | No | Joel Daves - UCAR Matthew Rich - Northwestern | 2022 Q2 | Launched - Can be done with Billing Conductor | |||||||||||||||||
8 | Cost Anomaly Comments for Historical Tracking | 7/14/2022 11:04:45 | Ken Flerlage | Bucknell University | As someone who helps to manage AWS costs, I LOVE the cost anomaly feature. I've recently noticed that anomalies are stored for historical purposes and you can mark whether or not the anomaly was correct. I understand that this is primarily to help AWS improve the feature, but I think this can be helpful for users as well. I'd like to have the ability to add notes to each anomaly. This could then be used when researching future similar anomalies--is it the same as we saw before or something new? This is a minor feature, but could be very helpful. | As someone who helps to manage AWS costs, I LOVE the cost anomaly feature. I've recently noticed that anomalies are stored for historical purposes and you can mark whether or not the anomaly was correct. I understand that this is primarily to help AWS improve the feature, but I think this can be helpful for users as well. I'd like to have the ability to add notes to each anomaly. This could then be used when researching future similar anomalies--is it the same as we saw before or something new? This is a minor feature, but could be very helpful. | 4 | 1 | 1 | No | Annelie Rugg - UCLA | 2022 Q2 | Submitted | |||||||||||||||||
9 | 7/14/2022 11:53:32 | Shannon K Spurling | University of Missouri- MOREnet | A tool where the AWS hosted service can be defined by IP address or DNS name, and the outside client IP/hostname can be given. The tool would show the current return path with RTT's, and maybe give a list of potential return peers in order of ranking. The page could be static, just so long as a traceroute back to the client IP is given. | When researching reported issues from users concerning reachability and latency/jitter when connecting to an AWS hosted service, return path information is very difficult to obtain. Many times, I have found asymmetric routing is causing the issue. | 5 | 5 | 5 | No | 2022 Q2 | Launched March 2023: https://aws.amazon.com/about-aws/whats-new/2023/03/amazon-vpc-reachability-analyzer-3-networking-services/ | |||||||||||||||||||
10 | Tracking Credits | 7/15/2022 8:58:21 | Sam Porter | UMD | A mechanism to notify designated university officials about AWS Credit awards, to report on credits awarded to university faculty, and provide institutions the opportunity to have some oversight over how credits are being used or to what AWS accounts they are being applied. | Tracking cloud credits, and how they are used, are critical to the Conflict of Interest processes on campus, and wraps up into legal and contractual requirements for researchers and the institution. Researchers can apply and receive credits with little to no involvement from the institution, often leaving administrators with little to no knowledge about them. Researchers should not be applying credits to (or using) non-university AWS accounts without permission to ensure compliance with appropriate laws, etc. | 4 | 3 | 4 | Yes | 2022 Q2 | Launched February 2023: Alert can be set up using Cloud Trail and the "redeempromocode" item. | ||||||||||||||||||
11 | Programatic Invoice Reporting | 7/15/2022 11:05:27 | Joel Daves | UCAR/NCAR | Either change CUR to use the same rounding algorithms the invoice processor does when providing monthly per account cost reporting, or provide a CUR like API to access the actual invoice data in a similar manner. | Currently the CUR per-account results use a different rounding process then AWS uses to calculate invoices. As a result monthly CUR per-account values may differ from invoice values +/- 0.01 which makes CUR reporting invalid for audit purposes. Invoice data can be exported, but only in a per-item format which puts the burden of processing/sanitizing that data back on the user who may not be capable of doing so. It would be beneficial if AWS could either utilize the same rounding process on the CUR calculations, or to provide an API for the exporting of invoice data, with the same options as the CUR to allow for straightforward and accurate access to per account invoice summaries. | 4 | 1 | 1 | No | 2022 Q2 | Submitted | ||||||||||||||||||
12 | Internal end-points for access to AWS services | 7/15/2022 18:21:58 | Michael Hogarth, MD | University of California, San Diego | Ability for users to access AWS computing services through an "internal" endpoint rather than the AWS console (which is a public endpoint). | An essential requirement for using protected health information (PHI) for clinical research is to maintain privacy and security. Historically, healthcare PHI has been given to researchers directly for computing on their respective laptops/computers. This meant risk of data loss and breach, along with unknown transfers to 3rd parties. We created a 'computing enclave environment' in AWS in order to "bring the researcher to the data" rather than furnishing the data to the researcher. Furthermore, this enclave has significantly reduced risk of inappropriate sharing by allowing us to "disconnect" it from the Internet. We employ AWS WorkSpaces as a means for access. This has been very helpful in reducing risk and allowing researchers to gain the scalability and reliability of computing in AWS. However, a *significant* problem is the requirement to have all users "come in" to AWS services (like Athena, SageMaker, Comprehend Medical, etc..) through a public-facing console rather than the WorkSpace. To allow access through the WorkSpace can be done but requires a costly and convoluted routing. It would be a significant improvement to have internally routed access points to these services and their respective user UIs while not requiring console routing. | 5 | 5 | 5 | No | 2022 Q2 | Launched - May, 2023: https://aws.amazon.com/about-aws/whats-new/2023/05/aws-management-console-private-access/ | ||||||||||||||||||
13 | LTI for integration of student AWS workspaces with Canvas and other LMS | 7/18/2022 12:17:55 | Annelie Rugg | UCLA Humanities Technology | Simplify allocation of AWS workspaces to students via the LMS for instructors who teach data science, digital humanities, media studies, etc but do not have the AWS knowledge and/or the time/access to institutional AWS accounts to manage access for students to the proper sandbox space for their students' learning and project needs. Without this, institutions must allocate specialized developer resources to work with central IT services to create this integration with the LMS or outside the LMS, creating another login and platform for the students to have to navigate and learn. OR, intrepid students go off and create their own AWS spaces that are usually not covered by institutional security and privacy protections. | For a course in data science, digital humanities, digital media or computer science, the instructor would like to be able to configure and provision controlled access to an AWS "sandbox" or project workspace for each student in a class to conduct "labs" and/or create projects/assignments for instructor review, commentary, grading. And to do so without having to know anything about allocating AWS resources or manage accounts/access. | 3 | 3 | 5 | No | 2022 Q2 | Investigating AWS built solution on top of AWS services. | ||||||||||||||||||
14 | Multi-payer | 7/18/2022 19:23:14 | Clifford Kravit | UCLA | Ability to have a landing zone (Control Tower / Organizations) with multiple payers setup while still including the accounts in the Enterprise Discount Program. It would be useful to be able to select the payers to assign to specific accounts. That way billing can be handled directly by the account "holders" and not have to be a separate FTE for IT. | From a centralized standpoint, having to do AWS billing and related tasks for all accounts is a full time job, putting costs and challenges on our organization that only exist because the AWS accounts fall under a single Payer within the Landing Zone (AWS Organizations). Also, only the accounts that fall in that Organization can receive our Enterprise Discount. Accounts created outside of it do not get those discounts. | 3 | 4 | 1 | No | 2022 Q2 | Submitted | ||||||||||||||||||
15 | TLS-enabled memcached in Elasticache | 7/19/2022 13:52:14 | Stephen Rosen | University of Chicago | Use the memcached service as provided by Elasticache in a HIPAA-compliant organization. | Globus, at the University of Chicago, has several applications with a 5-10 year history built with memcached and operating in a compliance environment including HIPAA and BAAs. Rewriting applications to use redis is nontrivial, and sharing caches is not implemented due to limited development resources and the need to use TLS-protected channels for cached information. | 3 | 1 | 2 | Yes | 2022 Q2 | Launched August 2022 - https://aws.amazon.com/about-aws/whats-new/2022/08/amazon-elasticache-memcached-hipaa-eligible/ | ||||||||||||||||||
16 | AppSync for FedRamp in AWS East/West | 7/19/2022 16:22:41 | Rachana Ananthakrishnan | University of Chicago | Synchronizing configuration information across multiple servers that are used to move data. Provide cloud backup of the configuration information for disaster recovery. | Globus (www.globus.org) is a data management platform, widely used by institutions in the research ecosystem (universities, national labs, independent research institutes). Globus uses AWS AppSync for a key capability of synchronizing configuration information, and providing backup and recovery for the configuration. With increasing compliance requirements (FedRAMP, StateRAMP, FedRAMP), Globus platform is required to meet these standards. AppSync is not supported for FedRAMP on AWS East/West, making this not an option at present. | 3 | 5 | 4 | Yes | 2022 Q2 | Submitted | ||||||||||||||||||
17 | Control Tower - Automation,Bulk Actions, and CLI/API | 7/21/2022 17:45:13 | Joel Daves | UCAR/NCAR | There are a lot of potentially good things about AWS Control Tower, but overall the offering is miserable to work with due the inability to perform multiple actions at once or trigger an action to queue through multiple resources, and the inability to interact with control tower programmatically or via CLI. We've moved a large amount of functionality, such as guardrails, to the control tower customizations application, which has its own set of issues or to pulumi-based applications, but even basic tasks such as a control tower version update require manually walking though OU's via the GUI and individually updating them one at a time. Even though nested OUs were introduced, actions only apply to the current OU, and the children have to be acted upon separately. I may end up having to move everything to pulumi and extract us from it completely as it requires more and more effort as our usage grows. | 5 | 1 | 2 | No | -Bulk actions: let us select multiple resources (OUs, accounts, etc) and have an action perform sequentially through them if parallel processing isn't possible. Even allowing an action to trickle down through a nested OU structure would be a huge win as I'm not sure exactly what nested OU's gain us outside of allowing us to map them out as a pretty tree. -CLI/API: I have no idea why this service is restricted to the GUI console. While some actions can be handled via careful manipulation of service catalog objects, there's too much that is only accessible via the console. -Guardrails: I honestly don't know where to start. Outside of the core required guardrails, we stopped using this functionality directly through control tower as it was a nightmare to work with. | 2022 Q2 | CLI/API - Some Launched, some still in progress Bulk Actions - Submitted | ||||||||||||||||||
18 | Security Hub - filter/view by Security Standard (e.g CIS, HIPAA) | 8/9/2022 11:28:24 | Shelley Rossell | University of Chicago | Need to be able to easily demonstrate for auditors, CISO, etc. overall organizational compliance by standard, such as CMMC, HIPAA, etc. that are applied in the environment--to all or only some accounts. | The delegated Security Hub account pulls Config compliance results from the member accounts but there is no easy way to view by particular standard/applied conformance pack. For example, we applied the HIPPA pack to a particular account, and there's no means to filter to only see those results. | 4 | 3 | 4 | No | Investigating | |||||||||||||||||||
19 | Centrally manage Conformance Pack deployment | 8/9/2022 11:41:55 | Shelley Rossell | University of Chicago | Want to centrally manage conformance pack deployment to targeted accounts (e.g. HIPAA to our HIPAA OU) and CMMC to additional select OUs/accounts within the Org. No central means to do this from the Org management account or delegated Security Hub account or to view which compliance standards (Conformance Packs) are applied to what accounts. | Easily view and manage what Conformance Packs are deployed to OUs, accounts, etc. within the Organization | 5 | 3 | 4 | No | Submitted | |||||||||||||||||||
20 | ||||||||||||||||||||||||||||||
21 | ||||||||||||||||||||||||||||||
22 | ||||||||||||||||||||||||||||||
23 | ||||||||||||||||||||||||||||||
24 | ||||||||||||||||||||||||||||||
25 | ||||||||||||||||||||||||||||||
26 | ||||||||||||||||||||||||||||||
27 | ||||||||||||||||||||||||||||||
28 | ||||||||||||||||||||||||||||||
29 | ||||||||||||||||||||||||||||||
30 | ||||||||||||||||||||||||||||||
31 | ||||||||||||||||||||||||||||||
32 | ||||||||||||||||||||||||||||||
33 | ||||||||||||||||||||||||||||||
34 | ||||||||||||||||||||||||||||||
35 | ||||||||||||||||||||||||||||||
36 | ||||||||||||||||||||||||||||||
37 | ||||||||||||||||||||||||||||||
38 | ||||||||||||||||||||||||||||||
39 | ||||||||||||||||||||||||||||||
40 | ||||||||||||||||||||||||||||||
41 | ||||||||||||||||||||||||||||||
42 | ||||||||||||||||||||||||||||||
43 | ||||||||||||||||||||||||||||||
44 | ||||||||||||||||||||||||||||||
45 | ||||||||||||||||||||||||||||||
46 | ||||||||||||||||||||||||||||||
47 | ||||||||||||||||||||||||||||||
48 | ||||||||||||||||||||||||||||||
49 | ||||||||||||||||||||||||||||||
50 | ||||||||||||||||||||||||||||||
51 | ||||||||||||||||||||||||||||||
52 | ||||||||||||||||||||||||||||||
53 | ||||||||||||||||||||||||||||||
54 | ||||||||||||||||||||||||||||||
55 | ||||||||||||||||||||||||||||||
56 | ||||||||||||||||||||||||||||||
57 | ||||||||||||||||||||||||||||||
58 | ||||||||||||||||||||||||||||||
59 | ||||||||||||||||||||||||||||||
60 | ||||||||||||||||||||||||||||||
61 | ||||||||||||||||||||||||||||||
62 | ||||||||||||||||||||||||||||||
63 | ||||||||||||||||||||||||||||||
64 | ||||||||||||||||||||||||||||||
65 | ||||||||||||||||||||||||||||||
66 | ||||||||||||||||||||||||||||||
67 | ||||||||||||||||||||||||||||||
68 | ||||||||||||||||||||||||||||||
69 | ||||||||||||||||||||||||||||||
70 | ||||||||||||||||||||||||||||||
71 | ||||||||||||||||||||||||||||||
72 | ||||||||||||||||||||||||||||||
73 | ||||||||||||||||||||||||||||||
74 | ||||||||||||||||||||||||||||||
75 | ||||||||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||||||
77 | ||||||||||||||||||||||||||||||
78 | ||||||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||||||
100 |