#CloudFormations

[missedmilemarkers]

[brahamand]

"Like the vast sky above, your potential knows no bounds. Let your dreams soar high, rooted in the strength of your origins, and watch as they bloom into reality across the wide open fields of possibility."

[artboomboom]

Cloud photo that I took a few weeks ago. We get some great cloud dynamics here.

[stochastique-blog]

You can be someone else

“Every sunset is an opportunity to reset” 🐰 -Richie Norton

#sky #plant #skyscrapper #cloudsandsky #skydivinglife #skybeauty #infrastructure #crazyclouds #paintedskies #cloud #skyporn #clouds #bluesky #cloudporn #skyline #afterglow #plantstyling #cloudsporn #skylight #plantasdeinterior #cloudformations #plantabaixa #landscape #nature #sunset #view #city #night #dawn https://www.instagram.com/p/CaPmvr1J3mO/?utm_medium=tumblr

[fuckyeahfluiddynamics]

Hole Punch Clouds

At times altocumulus cloud cover is pierced by circular or elongated holes, filled only with the wispiest of virga. These odd holes are known by many names: cavum, fallstreak holes, and hole punch clouds.  (Image credit: M. Garrison; research credit: A. Heymsfield et al. 2010 and A. Heymsfield et al. 2011; via NASA Earth Observatory) Read the full article

[photoart-naegele]

Cloudformation

[notumbusbumbus]

Blue Fish Bowl

Blue Fish Bowl, by Notty Bumbo, 2013

[govindhtech]

IaC Generator To Import SCPs And RCPs Into CloudFormation

Import SCPs and RCPs from current AWS organisations into Cloud Formation architecture as a code generator. AWS Organisations customers often manually set up resource control policies (RCPs) and service control policies (SCPs) using the AWS Management Console or AWS CLI.

This manual process may become onerous as the company grows and adds policies. It may limit visibility into all SCPs and RCPs, their targets, and update efficiency. Without visibility and access limits, it's hard to track who's making changes and how. CloudFormation can simplify rule management with rollback, policy validation via Hooks, and history preserving. Git sync may also synchronise stacks with Git repository source code. Git sync lets you deploy, configure, and update CloudFormation stacks using pull requests and version tracking. When you alter the deployment file or template, CloudFormation updates the stack.

CloudFormation IaC generator

This article shows how to import SCPs and RCPs into AWS CloudFormation templates using the CloudFormation infrastructure as a code generator (IaC generator). The IaC generator automates SCP and RCP administration at scale. Important: CloudFormation imports current policies, not recreates them.

Solution overview This article provides a command-line tool to locate SCPs and RCPs in your firm and automate policy import into CloudFormation templates.

The end-to-end flow is shown in the previous graphic:

Start the tool: Both the management account and the administrator account can run the software, automating following steps. Determine corporate SCPs and RCPs: The tool initially requests policies from the Organisations service via API. Total SCPs and RCPs are tallied. Determine AWS Control Tower RCPs, SCPs, and targetless policies: The utility finds AWS Control Tower SCPs and RCPs and outputs a list. Their policy titles begin with “aws-guardrails-” to identify SCPs. AWS Control Tower-Controls- prefixes RCP policy names identify them. Policies without targets: The tool lists SCPs and RCPs without accounts, roots, or OUs. These policies may be duplicates or reallocated. IaC generator scan: You will be asked if you want to import policies into CloudFormation templates using the resource scan. If you click “yes,” the tool will utilise the IaC generator to launch a CloudFormation resource scan to retrieve policy name, targets, tags, etc. Use scanned policy resources to construct a template: The program creates CloudFormation templates from policy resources. Any policies without objectives will be in the template. Review procedure: Use the CloudFormation IaC generator to preview the template after generation. Create CloudFormation stacks using templates: After reviewing templates, import them into CloudFormation stacks to deploy. Remember that CloudFormation policies are imported, not rebuilt. Templates reflect current policies and qualities.

Thinking before applying the solution

Consider these factors before applying the solution.

If you have enabled policy management delegation for AWS Organisations, execute this solution with the delegated administrator account. If not, execute the solution using the management account. Note: Delegated administrator member accounts should handle organisation policies. The CloudFormation templates will not import SCPs and RCPs (with or without targets) since they should be managed by AWS Control Tower. Changes to AWS Control Tower resources outside of AWS Control Tower might cause drift and unanticipated effects. Fully access SCP and RCP on AWSCloudFormation stacks cannot import AWS managed policies like FullAWSAccess RCP. If you surpass CloudFormation template size limitations, several templates may be produced. The program automatically divides material into many templates as needed, making it easy to meet quotas and import content. Note that templates automatically set the following properties. Maintain deletion policy. This allows policies to remain even if the stack is deleted. Change Replace to Delete. Revisions to the policy allow removal of the physical ID.

Recommended next steps

The figure shows two possible future steps.

After integrating rules into a CloudFormation stack, experts recommend retaining templates in a private Git repository. Manage imported policies with a continuous integration and delivery (CI/CD) pipeline and the Policies folder the tool automatically generates in the current local directory where the created templates were downloaded. Git repository version control allows pull requests, branch management, and history tracking. This process helps your team examine, update, and apply policies with better cooperation and control. Set up a CI/CD pipeline to automate CloudFormation stack updates to ensure regular and reliable updates. One suggestion is to install CloudFormation Hooks. CloudFormation Hooks can verify policies' syntax, security, and vulnerability reduction.

In conclusion

By integrating your AWS Organization's RCPs and SCPs into CloudFormation, you can manage and automate AWS governance efficiently. After import, you can maintain and change policies in CloudFormation to ensure company-wide consistency and version control. The program also creates a Policies folder in your current directory with downloaded templates for use as a central repository and with a continuous integration/continuous delivery pipeline. CloudFormation Hooks can test SCPs and RCPs against policy language and best practices to improve policy management. Centralising policy changes reduces misconfiguration and improves governance automation.

[techahead-software-blog]

Infrastructure as Code (IaC) in DevOps: The Key to Streamlined DevOps Infrastructure Management

DevOps has undoubtedly been one of the most transformative trends in the development industry in recent years. Currently, there are thousands of DevOps job openings listed in the US. 74% of companies, including giants like Amazon, Facebook, Netflix, Walmart, and NASA, have already embraced DevOps practices.

The global Infrastructure as Code (IaC) market was valued at $0.8 billion in 2022 and is expected to surge to $2.3 billion by 2027, experiencing a compound annual growth rate (CAGR) of 24% during this period.

A core principle of DevOps is maximizing automation, which naturally extends to infrastructure management. Embracing Infrastructure as Code in DevOps is essential to fully align with the DevOps methodology.

Infrastructure as Code (IaC) is a software engineering practice that enables the management and provisioning of infrastructure resources through code. This involves writing code to define and configure components like virtual machines, networks, storage, and other resources required for systems or applications.

With IaC, teams no longer manually set up infrastructure through graphical interfaces or command-line inputs. Instead, they write configurations in code, using declarative languages or configuration files. They can version, review, and test this code like any other software.

This approach marks a major shift in IT infrastructure management. Traditionally, configuring servers, networks, and storage was time-intensive and prone to errors. However, Infrastructure as Code in DevOps has streamlined this process, reducing manual effort and enhancing consistency.

Let’s delve deeper into understanding IaC and its benefits to streamline DevOps infrastructure management.

Key Takeaways:

Infrastructure as Code enables the management of IT infrastructure through code, enhancing automation and consistency

IaC eliminates manual configuration, reducing errors and enabling faster environment provisioning

Integrating IaC into CI/CD pipelines ensures infrastructure evolves alongside application code for faster, more reliable deployments

IaC boosts reliability, scalability, disaster recovery, and cost efficiency, making it indispensable for modern DevOps practices

What is Infrastructure as Code?

Infrastructure as Code (IaC) refers to the practice of managing and provisioning IT infrastructure through code. Traditionally, configuring servers, storage, or networks was manual, time-consuming, and prone to errors. With the Infrastructure as Code approach, teams automate these processes, reducing risks and boosting efficiency.

IaC allows developers and IT teams to write code that manages infrastructure just as they would manage software. This means teams version-control, test, and continuously improve the infrastructure just like any application. They create stable environments that are easy to deploy, ensuring consistency and repeatability.

How Does Infrastructure as Code Work in DevOps?

In a DevOps or DevSecOps environment, the Infrastructure as Code approach is key to automating and managing infrastructure with precision. By treating infrastructure as code, organizations can achieve higher efficiency, scalability, and security across their IT operations. Let’s dive deeper into each of the stages:

Infrastructure Definition

Here, teams write all components of the infrastructure, such as virtual machines, databases, and network settings, as code. Instead of manual configuration, teams use high-level languages like YAML, JSON, or HCL to describe these elements. This allows developers to define the exact infrastructure requirements consistently. A well-defined infrastructure through code means that environments can be replicated across development, testing, and production without discrepancies, ensuring consistency and reducing the likelihood of errors.

Versioning

One of the biggest advantages of the Infrastructure as Code is the ability to version control the infrastructure. Using platforms like Git, teams can store their infrastructure code in repositories. This brings traceability, as every change is tracked, and you can see who made it, when, and why. Versioning also empowers teams to roll back to previous configurations if something goes wrong during updates or deployments. This ensures stability and gives teams the confidence to make frequent changes without fear of breaking infrastructure.

Automated Provisioning

When it comes to provisioning infrastructure, tools like Terraform, AWS CloudFormation, or Ansible play a crucial role. They read the code that defines the infrastructure and automatically create the necessary resources. Whether it’s launching servers, setting up databases, or configuring entire networks, these tools automate every step. This eliminates manual setup, reducing human errors and speeding up deployment times. Automated provisioning also ensures that the infrastructure is consistently deployed across different environments, maintaining reliability.

CI/CD Integration

In modern DevOps practices, infrastructure must keep up with the fast pace of software releases. With Infrastructure as Code, integration with Continuous Integration/Continuous Deployment (CI/CD) pipelines is seamless. As developers push updates to the application code, the corresponding infrastructure changes can also be tested and deployed automatically. This means that infrastructure evolves alongside the application, staying up-to-date and scalable. The automation in CI/CD pipelines ensures faster, more reliable deployments, enabling businesses to rapidly adapt to changes or scale their infrastructure as needed.

By leveraging Infrastructure as Code, organizations can not only automate infrastructure provisioning but also create resilient, scalable, and secure environments that evolve effortlessly with their applications.

Benefits of IaC in DevOps

The Infrastructure as Code (IaC) model offers transformative benefits in the DevOps lifecycle. Let’s explore these advantages further in detail:

Reliability and Consistency

One of the primary challenges in traditional IT environments is inconsistent configurations across various environments, such as development, testing, and production. With IaC, infrastructure is written as code, ensuring that the same configuration is applied consistently. This eliminates environment-specific bugs and ensures uniform behavior across all stages. It addresses the “it works on my machine” issue, where an application behaves correctly in development but fails in other environments. By standardizing configurations, IaC reduces errors and enhances system stability over time.

Scalability 

IaC makes scaling infrastructure remarkably simple. In a traditional setup, scaling meant manually adding resources like servers, storage, or network configurations—a process that could take hours or days. With IaC, this is achieved by updating the code. Whether scaling up for increased workloads or scaling down during periods of lower demand, these changes can be made instantly. Tools like Terraform or AWS CloudFormation ensure that the infrastructure dynamically adapts based on changes in the code, allowing businesses to scale rapidly without delays or errors.

Speed and Efficiency

IaC accelerates the deployment process. Traditionally, setting up infrastructure involved multiple manual tasks—configuring servers, installing software, and managing network settings—all of which could take significant time. IaC automates these steps, enabling the infrastructure to be provisioned in minutes, not days. This allows development teams to focus on building and deploying applications rather than managing infrastructure. The increased speed and reduced overheads lead to more rapid development cycles and faster time-to-market.

Version Control and Auditing

Every infrastructure change is recorded in version control systems (VCS) like Git. This means that every modification—whether it’s adding a server or tweaking a network configuration—is documented and traceable. Teams can see exactly who made what change and when. This level of transparency helps in auditing and troubleshooting. Additionally, in the event of a problem, teams can revert to a previous version of the infrastructure with ease, minimizing risks during updates or deployments.

Disaster Recovery and Rollback

In the event of a failure, the recovery process is vastly simplified with IaC. If an infrastructure change leads to unexpected issues, teams can easily roll back to the last known stable version of the infrastructure code stored in the version control system. This rollback capability is crucial for minimizing downtime and preventing prolonged disruptions. IaC ensures faster recovery and improves resilience, making it a powerful tool in disaster recovery planning.

Cost Management

Effective resource management is critical for cost control, especially in cloud computing. IaC allows organizations to create temporary environments for specific tasks, such as testing new features. Once testing is completed, these environments can be automatically de-provisioned to avoid incurring unnecessary costs. This level of flexibility ensures that resources are only utilized when necessary, optimizing cloud spending and preventing resource wastage. The ability to automate provisioning and decommissioning through code significantly enhances cost efficiency.

Overall, the Infrastructure as Code approach drives consistency, efficiency, and scalability across IT operations, making it indispensable for modern DevOps practices. It empowers teams to innovate faster while maintaining robust control over infrastructure, ensuring that businesses can scale seamlessly and respond quickly to changing demands.

Common Tools for Infrastructure as Code

DevOps team rely on four main types of Infrastructure as Code in DevOps tools to streamline operations. Each tool serves a distinct purpose in automating and managing infrastructure.

Configuration Management Tools

Configuration management tools focus on automating software installation and managing configurations on existing servers. By ensuring uniform setups across all servers, they eliminate manual errors and configuration drifts.

Puppet

Puppet shares many similarities with Chef, standing out among Infrastructure as Code in DevOps tools. It’s integral to countless CI/CD pipelines that DevOps engineers rely on. Puppet uses a Domain Specific Language (DSL) based on Ruby, allowing you to declare the desired state of your infrastructure and its functionalities. It then automatically determines the most efficient path to achieve the specified configuration.

If there are any deviations from this desired state, Puppet actively monitors and corrects these changes, restoring the infrastructure to its intended setup. This powerful open-source solution supports major cloud platforms like Google Cloud Platform (GCP), Microsoft Azure, and Amazon Web Services (AWS), enabling seamless automation across diverse environments.

Key Features:

Puppet employs a Ruby DSL for defining system configurations, making scripting more intuitive and powerful.

It offers an extensive module library through Puppet Forge, enhancing functionality and customization.

Puppet’s idempotent nature ensures that applying a configuration repeatedly yields consistent results, boosting stability.

Chef

Chef is a powerful automation platform that converts Infrastructure as Code in DevOps into reality. It enables the automation of building, deploying, and managing IT infrastructure, providing organizations with precise control over configurations. This control drives greater agility and operational efficiency in IT processes, empowering teams to innovate rapidly.

Key Features:

Chef utilizes a Ruby-based DSL to script system configurations, streamlining the automation process.

It automated server configuration and deployment, reducing manual intervention and potential errors.

Chef supports infrastructure testing with tools like ChefSpec and InSpec, ensuring reliable code quality.

Policy as Code: It allows teams to define policies and configurations as code, enhancing transparency and consistency across deployments,

Ansible

Ansible serves as a versatile IT automation engine, ideal for application deployment, configuration management, and orchestration tasks. Although not a traditional Infrastructure as Code in DevOps tool, ANsible’s adaptability allows it to provision IaC resources using various collections. This capability bridges the gap between IT automation and IaC, offering a unified approach to managing both software and infrastructure with a single toolset.

Key Features:

Ansible operates without requiring agents on target nodes, simplifying the automation process.

YAML-based automation: It leverages YAML to define tasks, making configurations straightforward and readable.

Modular design: Ansible’s modular structure supports reusable modules, enhancing flexibility for diverse automation scenarios.

SaltStack

SaltSTack, commonly referred to as Salt, is a robust Python-based tool specializing in Infrastructure as Code in DevOps. It’s designed for efficient configuration management and remote command execution, excelling in both Cloud engineering and on-premises environments.

Key Features:

Advance Orchestration Capabilities: SaltStack supports intricate orchestration and configuration management across diverse environments, ensuring seamless infrastructure automation.

Remote Command Execution: It allows direct command execution on remote systems, streamlining control over distributed infrastructure.

Event-Driven Automation: SaltStack reacts to various system events, triggering automated responses to ensure dynamic and responsive infrastructure management.

Server Templating Tools

Server templating tools allow teams to create reusable templates that define a server’s configuration. These templates act as blueprints, standardizing how new servers are built and ensuring they meet predefined specifications.

Vagrant

Vagrant streamlines the creation and management of virtual machines, enhancing Infrastructure as Code in DevOps practices by ensuring consistent environments. It allows DevOps engineers to easily share VM setups, promoting seamless collaboration and reducing environment-related issues.

Key Features:

Platform Compatibility: Integrates with VirtualBox, VMware, Docker, AWS, and other major platforms for versatile virtual machine deployment.

Simplified Configuration: Uses a straightforward Vagrantfile to define and configure environments, making setup intuitive and user-friendly.

Extensive Ecosystem: Offers a variety of preconfigured boxes for different operating systems, accelerating deployment with ready-to-use templates.

Orchestration Tools

Orchestration tools manage the coordination between different infrastructure components, ensuring seamless interactions in complex environments. They help 

Automate workflows

Enabling multiple services to communicate

Work together efficiently

Kubernetes

Kubernetes act as specialized controllers that expand the Kubernetes API to handle complex stateful applications, advancing Infrastructure as Code in DevOps. Major cloud platforms like AWS, Microsoft Azure, Google Cloud, and Oracle Cloud Infrastructure offer tailored K8s operators to efficiently provision infrastructure resources.

Key Features:

Kubernetes API Extension: Enhances the Kubernetes API to manage specific application needs, improving operational flexibility.

Automated Lifecycle Management: Simplifies the management of complex stateful applications, ensuring seamless operation within Kubernetes clusters.

Custom Resource Definition: Empowers teams to create and manage custom resources in Kubernetes, boosting control over infrastructure setups.

Operator Development Support: Facilities building new operators, promoting innovation in infrastructure automation.

Provisioning Tools

Provisioning tools focus on the initial creation and configuration of infrastructure components like servers, networks, and storage. They automate the setup process, ensuring a faster and more reliable infrastructure deployment.

Terraform

Terraform stands as a leading tool in Infrastructure as Code in DevOps, enabling seamless infrastructure management across multiple cloud platforms using a straightforward declarative language.

Key Features:

Immutable Infrastructure Elements: Ensures consistent configurations, reducing the risk of drift in infrastructure settings.

State Management: Tracks infrastructure state to maintain stability and manage resource dependencies efficiently.

Multiple-cloud Support: Offers compatibility with various cloud providers, enabling diverse infrastructure management.

Modular Design: Promotes reusability and efficiency by allowing the creation of modular code components.

AWS CloudFormation

AWS CloudFormation offers a unified approach to defining and provisioning infrastructure within AWS cloud services, leveraging Infrastructure as Code in DevOps to streamline cloud resource management. This service, tailored exclusively for AWS, ensures a smooth and automated deployment experience, keeping pace with AWS’s latest features and services.

Key Features:

AWS Integration: Seamlessly aligns with AWS services, delivering optimizing support for a wide range of resources.

Declarative Templates: Utilizes JSON or YAML formats to simplify infrastructure definitions.

Change Management: Offers preview capabilities to assess and manage changes before applying them to your infrastructure.

Stack Organization: Groups resources into manageable stacks, enhancing clarity and ease of resource handling.

Comprehensive Resource Support: Extensively support AWS resources, ensuring compatibility with the latest offerings.

These tools play a critical role in Infrastructure as Code in DevOps, enhancing automation, efficiency, and consistency in managing IT infrastructure. They empower teams to build, deploy, and scale environments effortlessly, driving innovation and accelerating development cycles.

Best Practices for Implementation of IaC in DevOps

Let’s delve deeper into the best practices for implementing Infrastructure as Code in DevOps, enhancing each point to maximize its effectiveness in a DevOps environment:

Leverage Version Control

Integrating IaC configurations into version control systems like Git is crucial. This practice not only prevents rework by storing every infrastructure update but also provides a clear audit trail of changes. It allows multiple team members to collaborate seamlessly, managing access, tracking revisions, and rolling back to a previous state if needed. Version control acts as both a safeguard and a robust change management system

Automate Testing

Automated testing is vital to maintaining the integrity of your infrastructure setup. Use tools like Terratest to test Terraform modules or AWS Config to check resource compliance against best practices. Automated tests catch issues early, preventing faulty configurations from disrupting deployments. By validating infrastructure before it’s deployed, you ensure that changes won’t lead to instability or errors in production environments.

Modularize Code

Modularization means breaking IaC code into distinct, reusable components. Instead of having a monolithic script, create small, independent modules that focus on specific tasks. This modular approach simplifies updates since you only need to modify individual parts without affecting the entire codebase. It also promotes code reusability, making it easier to scale your infrastructure by reusing proven modules.

Integrate CI/CD Pipelines

Integrating IaC into your CI/CD pipeline is essential for the continuous delivery of infrastructure changes. By embedding testing, validation, and deployment of IaC into the CI/CD process, you ensure that the infrastructure code is automatically validated before deployment. This integration keeps infrastructure and application code in sync, reducing discrepancies and accelerating delivery cycles.

Document Infrastructure Thoroughly

Comprehensive documentation is the backbone of effective Infrastructure as Code in DevOps. Detailing configurations, architectural decisions, and setup procedures aids in knowledge sharing across the team. Proper documentation simplifies troubleshooting and onboarding, helping new team members understand the infrastructure’s architecture and its dependencies quickly.

Implementing these best practices fortifies Infrastructure as Code in DevOps by enhancing collaboration, minimizing risks, and ensuring scalable and consistent deployments. This structured approach to managing IT infrastructure accelerates development cycles and drives innovation in dynamic cloud environments.

Conclusion

Infrastructure as Code (IaC) has significantly reshaped the way DevOps operates. It empowers teams to manage IT infrastructure with the same speed and precision as software development—using automation for consistent results. This approach enables organizations to streamline processes, creating scalable and efficient workflows while managing their infrastructure with ease. This strategy is particularly crucial for Infrastructure as Code in DevOps, especially in web application development, where rapid delivery and infrastructure reliability are non-negotiable.

In this DevOps landscape, employing Infrastructure as Code in DevOps ensures that teams build high-quality applications while maintaining a resilient, scalable, and secure infrastructure. By adopting the right tools and following best practices, teams can harness IaC to create and manage infrastructures that support swift software delivery cycles.

Relying on IaC isn’t just an option in today’s agile, cloud-first environment; it’s essential for staying competitive. If you’re a DevOps professional yet to incorporate Infrastructure as Code in DevOps into your workflow, now is the time to act.

Have a web or mobile app development project that demands expert developers? Connect with us for a free technical consultation.

Source URL: https://www.techaheadcorp.com/blog/infrastructure-as-code-iac-in-devops-the-key-to-streamlined-devops-infrastructure-management/#h-common-tools-for-infrastructure-as-code

[vastedge330]

Cloud Automation is crucial for optimizing IT operations in multi-cloud environments. Tools such as Ansible, Terraform, Kubernetes, and AWS CloudFormation enable businesses to streamline workflows, automate repetitive tasks, and enhance infrastructure management. These solutions provide efficiency and scalability, making them indispensable for modern cloud management.

[alsanda-151651]

AWS Devops Services 

Software delivery in cloud settings may be automated, scaled, and managed more efficiently with the help of AWS DevOps services. Among these services is infrastructure as code (IaC), which lets programmers use version-controlled scripts to define and maintain infrastructure. Software releases are made fast and dependable by automating the testing and deployment of applications through continuous integration and continuous delivery (CI/CD) pipelines. Applications can operate reliably in a variety of contexts thanks to the management of microservices made possible by containerization and orchestration technologies. Teams can take proactive measures to resolve problems by using real-time insights into application performance that are provided by monitoring and logging services. Auto-scaling, which modifies resources in response to demand to maintain highly available and economical applications, is another crucial part of AWS DevOps services. Teams can comply with industry requirements by using automated controls and real-time auditing to include security and compliance in the DevOps workflow. Version control systems and collaboration tools are also essential since they let teams collaborate easily and monitor changes to infrastructure and code. With the help of these AWS DevOps services, businesses can create, launch, and maintain apps effectively, promoting an innovative and continuous improvement culture.

[infosectrain03]

Juggling numerous services for the IT infrastructure can be quite a challenge. Dealing with multiple AWS resources might eat up valuable time that could be spent on developing applications. The solution is AWS CloudFormation.

[ukeyong]

Kelvin-Helmhotz wave clouds. Embrace the breathtaking beauty of Kelvin-Helmholtz wave clouds and let them inspire you to soar to new heights in life.

[theartofjdb]

Taking pictures of the sky can be quite engaging due to the interesting and unique cloud formations. Each formation is different, providing a continuous variety that makes observing the sky an activity where one can always encounter something new.

“Blue Sky’s 0040” 2/2025 iPhone 15 Pro Ultra Wide 13mm Photography

This is my intellectual property and may not be copied or used without permission.

No AI was used in the creation of this cranial incarnation or photography.

#TheArtOfJDB #JDB #Photography #CloudPhotography #BlueSkies #Clouds #Nephology #CloudFormations

[notumbusbumbus]

Dragons of Evermore, by Notty Bumbo, 2015, photoimpressionism