7 ms·
Cloud.gov
- cj 4y ago(Off topic): this page linked at the bottom of cloud.gov is quite interesting. Visitor analytics for government sites. https://analytics.usa.gov/ https://analytics.usa.gov/
- ethbr0 4y agoAlso at the bottom of cloud.gov, and not surprising: "Built by 18F" Neat work on the architectural and regulatory compliance as a service angle, especially for smaller organizations and teams!
- bXVsbGVy 4y agoM̶o̶r̶e̶ ̶i̶m̶p̶r̶e̶s̶s̶i̶v̶e̶ ̶i̶s̶ ̶t̶h̶e̶ ̶l̶a̶c̶k̶ ̶o̶f̶ ̶g̶o̶o̶g̶l̶e̶ ̶a̶n̶a̶l̶y̶t̶i̶c̶s̶.̶ I was wrong. They are are using GA.
- tehlike 4y ago"The Google Analytics account that powers analytics.usa.gov is experiencing issues with realtime reporting. Realtime data may be inaccurate."
- tdlowden 4y agohttps://issuetracker.google.com/issues/228201905?pli=1 https://issuetracker.google.com/issues/228201905?pli=1
- emsixteen 4y agoYou sure? Mentions sampling limits for GA on the page.
- bXVsbGVy 4y agoThanks for pointing this out. I looked for the domain of fetched resources, and assumed they weren't. It seems they are using, but from their own domain.
- patrickmcnamara 4y agoThe vast majority of people using US gov websites are not in the US? It says 92.5% are international. Huh.
- bobthepanda 4y agoThat doesn’t really surprise me, I don’t know that I visit .gov sites quite often, but people located internationally probably do lots of things that would require it (e.g. visas & immigration, talking to the embassy)
- Hooray_Darakian 4y agoThis is going to be a god send for a lot of smaller gov agencies.
- asn1parse 4y agoi agree
- junofan 4y agoIt’s been around for 7 years, so I wonder what adoption is like in the present day.
- jason-phillips 4y ago> This is going to be a god send for a lot of smaller gov agencies. Not quite. It's not exactly a pain-free experience in any way, shape or form.
- loceng 4y agoCan this, how does this, get captured by industry leading it to become relatively stagnant with high prices?
- MOARDONGZPLZ 4y agoCloud.gov was really promising when it was announced years ago, but in practice there ended up being so many differing security requirements and security boundary tensions between them and purported customers of them that they didn’t end up having any real impact because while some could use them, many could not, and those who could often found it easier to just not use them. There were also issues getting needed performance out of underlying Cloud Foundry infra and highly delayed updates, including security patches I believe. Truly a great idea and noble thinking, but government problems are rarely about the actual infrastructure and almost always about the bureaucracy surrounding things, as was the case with Cloud.gov. I think this is partially proven by its current customer list, which seems to be largely smaller or discrete projects of agencies rather than wholesale agencies moving to their PaaS, despite Cloud.gov being around since I believe at least 2015-2016.
- newsclues 4y agoSo we need BaaS? Bureaucracy as a service?
- ccbccccbbcccbb 4y agoFaaF, failure as a feature
- deleted 4y ago[deleted]
- eastbound 4y agoI’m sure AI in charge of organizing a process can build forms and reach BAAS naturally. What I wonder is, to output a mess process, would it be faster than actual government services, or do govt services effectively act as brownian agents?
- newsclues 4y agoWill AI BaaS work for the system or the bureaucracy itself as human systems do?
- ec109685 4y agoGood overviews of how it is put together: https://cloud.gov/docs/technology/iaas/ https://cloud.gov/docs/technology/iaas/ https://cloud.gov/docs/technology/responsibilities/ https://cloud.gov/docs/technology/responsibilities/ Using open source Cloud Foundry as the basis. Seems well thought out. However, I wonder if a better approach would be to offer this PaaS but also lower level baselines that make using AWS easier and more secure so it’s not all or nothing to take advantage of their services.
- jason-phillips 4y ago> However, I wonder if a better approach would be to offer this PaaS but also lower level baselines that make using AWS easier and more secure so it’s not all or nothing to take advantage of their services. That's what I was working on for a little sub-agency. You have to start somewhere, with a menu of cloud services that you'll offer to anyone who wants to deploy their app for the federal government to use. You can make that menu selection larger or smaller depending on what services are on the approved list. Platform One, for example, is PaaS built around Kubernetes deployments. Mine was built using a much larger approved list of services (Kubernetes, Fargate, and so on) that an entity could select to deploy their app/service.
- InvaderFizz 4y agoConsidering this is only for FedRAMP Low/Medium, I'm not sure why any contractor or agency would pick this over AWS GovCloud, where finding people already familiar with the platform is easy.
- atonse 4y agoIt’s FedRAMP High: https://cloud.gov/docs/technology/iaas/ https://cloud.gov/docs/technology/iaas/
- wslack 4y agoThere are different levels at the infra/platform/application layer. cloud.gov is built on top of AWS IaaS (though the PaaS could also be deployed on other infra).
- InvaderFizz 4y agoJust because you can run High workloads on AWS GovCloud, doesn't mean that Cloud.gov can run High. From their own front page: > We’re a great fit when: > - Your applications are Moderate impact level or lower
- atonse 4y agoI stand corrected!
- bluedino 4y agoI haven't used AWS's version, but the gov version of Azure is terrible. Missing so many features and limited in so many ways and there are so many "gotchas". And no matter how many times you tell a vendor that's what you have they won't admit their product isn't compatible until the second or third time they try to implement.
- Bajeezus 4y agoI worked on government projects at Azure for years. Their US Government cloud is a second-class citizen. Getting the average engineer to care about problems with their their offerings in government clouds relative to the commercial cloud is like pulling teeth.
- kyawzazaw 4y agoSeems like this is by https://www.gsa.gov/ https://www.gsa.gov/
- vcryan 4y agoAs someone who runs 20+ cloud based government applications it is unclear to me how this is easier to secure, more performant, or cheaper than AWS. My first impression is this adds a lot of risks and unknowns in a critical area where there are existing and well-known best practices.
- bXVsbGVy 4y agoIt still is AWS. The AWS GovCloud partition to me more precise. https://cloud.gov/docs/technology/iaas/ https://cloud.gov/docs/technology/iaas/
- vcryan 4y agoI'll have to look closer, if there is cost savings I would consider it. We put a lot of effort into achieving AWS "Well Architected" so I'd hate to end up in a lesser position by going in a potentially lesser known, lesser tested, lesser supported approach.
- fn-mote 4y agoIt seems like someone with an application up and running on AWS isn't really the target audience. (Although I'm still trying to figure out who _is_ the target audience, here.)
- jimmoffet 4y agoYou need a low/moderate impact web app, you only need bread and butter infrastructure, django/ruby/node app, postgres, redis, basic autoscaling. You (your agency) does not have experience doing this (for example, you’ve never built something on remote-hosted infrastructure before, you’ve never built anything that wasn’t locked to windows before, you’ve never done anything that wasnt hardcore waterfall before, etc). You wouldn’t know where to start if someone asked you to build a web app that would be easy to find technical talent to support going forward (you just assume this means a building into a Microsoft product). You don’t know why open source software makes your life easier when maintaining a software system. More charitably, you want try this “agile development” thing that everyone is talking about, and you need air cover to keep your IT dept from demanding that you give a contractor 500k-1.5m to put up a “secure” boilerplate, ‘hello world’ modern web app deployment that will kick off your agile dev process, which ought to take one person a week to deploy and another person a week to lock down. There are a surprising number of agencies and departments that meet the above description, but either they don’t know what cloud.gov is, or equally likely, their IT department would rather spend a lot more money on a contractor and feel like they have more control. There is zero incentive to take a chance, even if you can be reasonably sure you’ll get as good or better infrastructure for 1/5 or 1/10th the cost. No one will be impressed that you saved the money and you’ll live in fear for years that something will go wrong and you won’t get promoted because you chose a scary new thing and it backfired. They’re (IT) also likely to understand a “web app” as something tightly coupled to their existing systems (meaning they cannot imagine their existing systems securely communicating with an external, independent API, even they themselves built it) which pretty much excludes all modern software practice and excludes using cloud.gov to build additional capability. If a potential client already knows how to build, deploy, secure and get their IT dept to authorize an aws-hosted modern web server, they’re not (at least right now) a target audience for cloud.gov, but I don’t think that describes most agencies or departments
- anomie 4y agoThe UK equivalent has just announced it’s closing down for many of the reasons people comment here - https://gds.blog.gov.uk/2022/07/12/why-weve-decided-to-decommission-gov-uk-paas-platform-as-a-service/ https://gds.blog.gov.uk/2022/07/12/why-weve-decided-to-decom...
- junofan 4y agoIt seems like this product could be better (less risky) as a set of shared config files or something.
- ris 4y agoYou are not the only one to have this thought. The problem is - who comes and fixes the mess when the inevitable customizations needed have been done by a contractor who is now long gone? It seems like a great idea at the beginning, but at some point someone ends up responsible for a fleet of AWS accounts that have diverged in different odd ways. Who is that someone? Individual departments? A centralized department? The latter sounds nice except for the lack of appetite (on both sides of the atlantic) for doing what's necessary to recruit and keep SREs as actual government employees rather than just contracting everything out...
- severalbadgers 4y agoI don't think it ever quite works in practice. Letting teams come pick up the config module off the shelf in January is all well and good, but when the maintainers of the module issue a security fix in October how can you ensure the consumers apply it? On top of that, how can the maintainers know if a change they make will be safe in the environments of the consumers? IMO you either offer the whole service (i.e. a PaaS), or you form technical groups within the organisation which regularly share their learnings and experiences. Sharing code (aside from the smallest modules) when you don't have control or influence over the consuming team just doesn't work in the long run.
- deleted 4y ago[deleted]
- victor106 4y agohttps://cloud.gov/docs/deployment/frameworks/ https://cloud.gov/docs/deployment/frameworks/ Not supported cloud.gov cannot run applications that use .NET Framework, or application binaries that require access to Microsoft Windows kernel or system APIs. Interesting that most container/cloud environments don't support .Net framework
- kenniskrag 4y ago.net core is not supported?
- jason-phillips 4y agoYes, but dollars to donuts they support Dot Net Core.
- cgrealy 4y ago.Net Core* is supported > cloud.gov supports applications written in Go, Java, Node.js, .NET Core... .Net framework is tied to Windows, and is now considered legacy tech. Both AWS and Azure support Windows containers if you really need them, but they're nowhere near as easy to use as Linux. * I'd assume that .Net 5/6/7 are also supported (insert rant about dumb MS naming conventions).
- fomine3 4y agoJust use VM for legacy application.
- AlbertCory 4y agoWhile in Google's Patent Litigation dep't, I had a case (not a suit) about Google's Gov Cloud product. Without divulging too many details: the government is quite reasonably a bit sticky about where the data is stored physically.
- aejnsn 4y agoWhile Cloud.gov had great fanfare years ago when introduced. Underneath it’s just Pivotal/CloudFoundry buildpacks and standardized security assurances. It’s exorbitantly costly for lower scale projects. Most three-letter agencies have their own security review processes on top of these assurances anyway. So the time-savings expected are quickly diminished. Someone could do very well for our governments’ efficiency to STOP the redundant overhead in security controls currently. Preventing security teams becoming a gatekeeping police department and staffing/hiring with those more inclined to automate (SecOps) rather than to interpret policy inconsistently would be excellent.