automation and orchestration
REST (Representational State Transfer)
-communication method used by APIs ○ REST uses standard HTTP methods, status codes, URIs, and MIME types for interactions ○ Primarily uses JSON for data transfer ○ Lightweight protocol suitable for integrating with existing websites
Benefits of Automation and Orchestration
-efficienccy -scalability -standardization -employee retention -reaction time -workforce multiplier
ways to automate security
-implementing guardrails (Guardrails are automated safety controls to protect against insecure infrastructure configurations) -managing security groups -enabling and disabling services and access -automating permission management
CURL
A tool for transferring data to or from a server using various supported protocols
Runbook
Automated version of a playbook with defined interaction points for human analysis
Integration
Combining subsystems or components into a single, functioning system
Orchestration
Coordinated execution of multiple automated tasks for a specific outcome or workflow
Areas to Automate in Onboarding
Creation of documentation records Scheduling training Provisioning equipment Managing access rights Distributing checklists Collecting feedback
API (Application Programming Interface)
Set of rules and protocols used for building and integrating application software Enable software developers to access functions or features of another application programmatically
Continuous Delivery (CD)
○ Automated testing and build processes ○ CD stops short of automatic production deployment ○ CD is part of the release process ○ Full deployment process is automated only to a certain stage ■ Doesn't deploy into the production environment automatically ○ Deployment to production environment is a manual business decision ○ Allows flexibility in timing, market conditions, and stakeholder readiness
SOAP (Simple Object Access Protocol)
○ SOAP has a structured message format in XML ○ Known for robustness, additional security features, and transaction compliance ○ Suitable for enterprise-level web services with complex transactions and regulatory compliance requirements
Benefits of CI/CD
● Adapting to changing market demands more quickly ● Efficient workflow from development to deployment ● Improves code quality, streamlines deployment processes, and allows flexible production release ● Reduces deployment risks and enhances software reliability
User Provisioning
● Collecting information ● Creating accounts ● Assigning roles and access ● Sending notifications ● Conducting synchronization and updates
Continuous Integration (CI)
● Developers merge code changes frequently in a central repository ● Automated build process verifies each check-in and detects problems during integration ● Automation tools manage code integration, provide notifications for conflicts or errors ● Automated tests ensure software quality after integration ● Developers receive feedback on detected issues to make necessary corrections ● Release ○ Process of finalizing and preparing new software or updates ○ Enabling software installation and usage ● Deployment ○ Involves automated process of software releases to users ○ Actual installation of software in a new environment
Resource Provisioning
● Requirements analysis ● Resource allocation ● Configuration ● Verification and auditing ● Gathering feedback
Six steps in the ticket creation process
● Users submit requests through channels (e.g., email, web form, support portal) ● Automation tool generates tickets based on predefined criteria ● Capture essential information from user submissions ● Categorize tickets based on content or source ● Assign priority based on predefined rules and criteria ● Automated notification sent to relevant support team or technician
