Going cloud native in a highly regulated context presents challenges of its own. In this talk, Jez Humble will share with you the platform created by the cloud.gov team at 18F, and the benefits it brought to federal agencies seeking to use the cloud.
More details:
https://confengine.com/agile-india-2019/proposal/8525/cloud-native-in-the-us-federal-government
Conference link: https://2019.agileindia.org
in kuwait௹+918133066128....) @abortion pills for sale in Kuwait City
Cloud Native in the US Federal Government by Jez Humble at #AgileIndia2019
1. cloud native in the us federal government
@jezhumble #agileindia2019
2. what cloud.gov is
continuous delivery refresher
why we built cloud.gov
implementation
principles for building a paas
agenda
3. @jezhumble
what is continuous delivery?
The ability to get changes—features, configuration changes, bug
fixes, experiments—into production or into the hands of users
safely and quickly in a sustainable way.
https://continuousdelivery.com/
4. @jezhumble
increase software quality and stability
make releases painless, low risk events
reduce time to market
increase customer and employee satisfaction
reduce cost of ongoing software development
why continuous delivery?
10. Records Management
Records Schedule
Privacy Act
Paperwork Reduction Act
Section 508 and Accessibility Standards
Federal Acquisition Regulation
Anti-deficiency Act
Economy Act
E-Government Act
Computer Matching Act
National Cyber Protection System
Guidance for Agency Use of Third-Party Websites and Applications
Social Media and Web-Based Interactive Technologies
Office of Management Budget Circular A-130 Appendix 3
Federal Information Security and Management Act
Federal Information Processing Standard (FIPS) 199
Federal Information Processing Standard (FIPS) 200
Federal Information Processing Standard (FIPS) 140-2
Special Publication 800-37
Special Publication 800-53 Revision 4
Special Publication 800-60 Volume 1
Special Publication 800-60 Volume 2
11. Special Publication 800-18
Special Publication 800-137
Special Publication 800-171
Special Publication 800-133
Special Publication 800-95
EINSTEIN Compliance
FedRAMP
OMB Guidance on third party websites and applications
OMB Memo M-14-04
OMB Memo M-15-01
Trusted Internet Connection 2.o Reference Architecture
Pages in total:
4006
12. My friend, you can clearly see the
intention of FIPS 140-2 Annex A was to
deprecate SHA-1 on the lunar new
year...
29. push-button deployments
teams can deploy into a production-like environment from day 1
architectural paradigm designed for distributed systems
templates for all your compliance documentation
most of the controls taken care of at the platform level
what this gets you
35. IaaS “one account to rule them all” trade-offs
• Hard to deal with multi-tenancy & provide a real cloud
• Significantly higher ongoing maintenance costs
• Hard to manage sprawl
• One-size-fits-all platform solution
36. IaaS multiple accounts trade-offs
• Can give teams direct control over each account
• Potentially need to instantiate shared services in each account
• Still some issues with multi-tenancy
37. PaaS trade-offs
• You only need to ATO once
• RBAC built-in - deals with multi-tenancy
• Good practices baked in
• Lower maintenance & operational costs
• One-size-fits-all solution
38. use native cloud primitives
everything must be self-service
design your platform for multi-tenancy
principles for building a paas
39. use native cloud primitives
everything must be self-service
design your platform for multi-tenancy
everything must be reproducible from version control
principles for building a paas
40.
41. use native cloud primitives
everything must be self-service
design your platform for multi-tenancy
take care of compliance at the platform layer
everything must be reproducible from version control
principles for building a paas