Sign up for our newsletter!
Stay informed on the latest DevOps news
DevOps.com
Latest
Articles
Features
Most Read
News
News Releases
Topics
AI
Continuous Delivery
Continuous Testing
Cloud
Culture
DataOps
DevSecOps
Enterprise DevOps
Leadership Suite
DevOps Practice
ROELBOB
DevOps Toolbox
IT as Code
Videos/Podcasts
Techstrong.tv Podcast
Techstrong.tv - Twitch
DevOps Unbound
Webinars
Upcoming
Calendar View
On-Demand Webinars
Library
Events
Upcoming Events
On-Demand Events
Sponsored Content
Related Sites
Techstrong Group
Cloud Native Now
Security Boulevard
Platform Engineering
Techstrong Research
DevOps Dozen
DevOps TV
Techstrong TV
Techstrong.tv Podcast
Techstrong.tv - Twitch
Media Kit
About
Sponsor
AI
Cloud
CI/CD
Continuous Testing
DataOps
DevSecOps
DevOps Onramp
Platform Engineering
Low-Code/No-Code
IT as Code
More
Serverless on AWS
Builder Community Hub
Application Performance Management/Monitoring
Culture
Enterprise DevOps
ROELBOB
Blogs
ROELBOB
Making Mush
Making Mush
By:
ROELBOB
on
November 28, 2022
Leave a Comment
« Five Great DevOps Job Opportunities
4 Best Practices for Entertainment App Testing »
×
IaC Maturity, Modernization, and Cloud Migration
Step
1
of
7
14%
How would you best describe your organization's current level of maturity with respect to infrastructure as code (IaC)?
(Required)
Initial (basic or trial implementations; or just starting with IaC)
Developing (IaC implementations in place)
Intermediate (significant use of IaC)
Advanced (adoption, or planned adoption, of IaC for most or all environments)
Full (IaC a core part of development, deployment, and operations)
Don’t know
How do you typically audit or discover existing infrastructure?
(Required)
Use of existing IaC state files
No consistent auditing or discovery method
Manual review of consoles
Combination of manual review and automated tools
Automated scanning tools
Other
What are the biggest challenges you face in ensuring compliance and governance for your IaC-based deployments? (Select up to three)
(Required)
Infrastructure configuration drift
Lack of standardized policies
Amount of time required for audits
Inconsistent application of policies across environments
Insufficient training or expertise
Lack of visibility into the infrastructure
Difficulty keeping up with compliance standards
Lack of policy enforcement automation
Difficulty enforcing policies
How helpful would it be to your organization to be able to automatically generate infrastructure as code (e.g., from existing resources, from application code, or based on architectural designs)?
(Required)
Extremely helpful
Very helpful
Moderately helpful
Somewhat helpful
Not helpful
Now, think about cloud-to-cloud migration projects. What are the biggest challenges your team faces with cloud-to-cloud migrations? (Select up to three)
(Required)
Need for extensive scripting
Projects require too much time and cost
Lack of infrastructure-as-code expertise
Inconsistencies from environment to environment
Translating infrastructure-as-code from environment to environment
Unclear or missing resource-policy mapping
Too many manual error corrections needed
Ensuring security or compliance during migration
Need for manual resource discovery
Configuration mapping is too complex
Don’t know
Which of the following would most help streamline your cloud-to-cloud migrations? (Select up to three)
(Required)
Standardization of infrastructure-as-code deployments
Translation of existing infrastructure as code to destination environments
Automated generation of infrastructure as code
Automated resource-policy mapping
Clear architectural visualizations
Elimination of repetitive manual tasks
Consistent governance and compliance standards
Don’t know
Translation of policies and security protocols
Support for manually created resources
Which of the following best describes how cloud-to-cloud migrations impact your team’s productivity?
(Required)
Don’t know
They reduce our productivity significantly while we perform them
They increase the amount of automation we need
We haven’t done any cloud-to-cloud migrations
They create process bottlenecks we must work around, at least temporarily
They have no effect on our productivity or automation
Δ
