-
Create the agent Configure the agent Optionally run the agent interactively
-
To generate an AWS Access Key and Secret Access Key for use with Terraform, you need to create an IAM user or use an existing user with programmatic access. Here’s a step-by-step guide: 1. Sign in to the AWS Management Console 2. Navigate to the IAM Management Console 3. Create a New IAM User (Optional, if a new user is required) Steps to create a new user: 4. Assign Permissions to the User 5. Review and Create 6. Retrieve the Access Key and Secret Once the user is created: Important: If you lose the secret key, you will need to…
-
Problem: Received the following error when I ran terraform apply: PS C:\ProgramFiles\terraform\Getting-Started-Terraform\globo_web_app> terraform apply “m3.tfplan”aws_vpc.app: Creating…aws_vpc.app: Still creating… [10s elapsed]aws_vpc.app: Creation complete after 15s [id=vpc-04258121c850ef748]aws_internet_gateway.app: Creating…aws_subnet.public_subnet1: Creating…aws_security_group.nginx_sg: Creating…aws_internet_gateway.app: Creation complete after 1s [id=igw-0e84f7d79f374bc0f]aws_route_table.app: Creating…aws_route_table.app: Creation complete after 1s [id=rtb-0077afeba70ce1a48]aws_security_group.nginx_sg: Creation complete after 4s [id=sg-0fc28a57927d7dc2c]aws_subnet.public_subnet1: Still creating… [10s elapsed]aws_subnet.public_subnet1: Creation complete after 12s [id=subnet-0c3c2b30409fdb905]aws_route_table_association.app_subnet1: Creating…aws_instance.nginx1: Creating…╷│ Error: creating EC2 Instance: operation error EC2: RunInstances, https response error StatusCode: 400, RequestID: 67800c36-cf57-4816-b919-6d5ae4e0c4f5, api error Unsupported: Your requested instance type (t3.micro) is not supported in your requested Availability Zone (us-east-1e). Please retry your request by not specifying an Availability Zone or choosing us-east-1a,…
-
I was trying to run a Terraform script against my free tier AWS account. then issued the terraform plan command from my local machine: PS C:\ProgramFiles\terraform\Getting-Started-Terraform\globo_web_app> terraform plan -out m3.tfplan Received the below error: Error: reading SSM Parameter (/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2): operation error SSM: GetParameter, https response error StatusCode: 400, RequestID: 80e64eb4-9cb4-4c15-b608-92b4f00e9876, api error AccessDeniedException: User: arn:aws:iam::590183791234:user/terraform-user is not authorized to perform: ssm:GetParameter on resource: arn:aws:ssm:us-east-1::parameter/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2 because no identity-based policy allows the ssm:GetParameter action││ with data.aws_ssm_parameter.amzn2_linux,│ on main.tf line 15, in data “aws_ssm_parameter” “amzn2_linux”:│ 15: data “aws_ssm_parameter” “amzn2_linux” { It turned out I had to attach the AmazonSSMReadOnlyAccess policy as below: 1.…
-
In Azure, CRM Functions typically refer to custom functions or serverless functions integrated with a CRM (Customer Relationship Management) system, such as Microsoft Dynamics 365 CRM, to enhance its capabilities. Azure provides various tools, such as Azure Functions, to develop and host these customizations or integrations. Here’s an overview of Azure CRM Functions and their use: 1. What Are Azure CRM Functions? Azure CRM Functions are serverless, event-driven components built using Azure Functions to extend the functionality of a CRM platform. They enable developers to perform specific tasks or workflows triggered by events or data changes in a CRM system,…
-
What is EDL (External Dynamic List) URL Filtering? External Dynamic List (EDL) URL Filtering is a feature used in modern security systems, such as firewalls, to dynamically control access to URLs based on lists maintained externally. Instead of manually adding or updating URL entries in the firewall’s policy, administrators can reference a dynamic list hosted externally. These lists are often used for security, compliance, or traffic management purposes. Key Features of EDL-based URL Filtering: How Does EDL URL Filtering Work? Example in Palo Alto Networks: Palo Alto Networks firewalls have robust support for EDLs. Here’s how you might use it…
-
What is VNet Peering in Azure? VNet Peering is a feature in Microsoft Azure that allows you to connect two or more Azure Virtual Networks (VNets) to enable seamless communication between them. It acts as a private connection between VNets, providing low-latency and high-bandwidth connectivity. Key Features of VNet Peering: Use Cases of VNet Peering: What is a Landing Zone in Azure? A Landing Zone in Azure is a predefined environment designed to host your cloud workloads in a secure, scalable, and manageable way. It is part of the Microsoft Cloud Adoption Framework (CAF) and serves as a foundation for…
-
The error -bash: lsof: command not found indicates that the lsof command is not installed on your system. To use lsof, you need to install it first. Steps to Install lsof Run the following command to install lsof: Run: After installation, verify that lsof is available: After lsof is installed, you can run: If you are unable to install software due to restrictions or package manager issues, you can use netstat (if available) as an alternative:
-
The host and nslookup commands in Linux are both used for DNS (Domain Name System) lookups, but they have some differences in functionality, output style, and use cases. Here’s a detailed comparison: 1. host Command Examples: Output: Output: 2. nslookup Command Examples: Output: Run nslookup without arguments to enter an interactive shell: Output: Key Differences Feature host nslookup Output Concise and human-readable Detailed and verbose Interactivity Non-interactive Interactive mode available Custom DNS Server Not directly supported Supported (e.g., nslookup <domain> <server>) Ease of Use Simpler for quick lookups Useful for troubleshooting Deprecation Actively used Deprecated in favor of dig Which…
-
I0619 16:01:26.910703 1 main.go:223] Handling node with IPs: map[172.18.0.4:{}] I0619 16:01:26.910839 1 main.go:227] handling current node I0619 16:01:26.910881 1 main.go:223] Handling node with IPs: map[172.18.0.2:{}] I0619 16:01:26.910905 1 main.go:250] Node my-cluster-worker has CIDR [10.244.1.0/24] I0619 16:01:26.911141 1 main.go:223] Handling node with IPs: map[172.18.0.3:{}] I0619 16:01:26.911174 1 main.go:250] Node my-cluster-worker2 has CIDR [10.244.2.0/24] I0619 16:01:36.934685 1 main.go:223] Handling node with IPs: map[172.18.0.4:{}] I0619 16:01:36.934837 1 main.go:227] handling current node I0619 16:01:36.934895 1 main.go:223] Handling node with IPs: map[172.18.0.2:{}] I0619 16:01:36.934951 1 main.go:250] Node my-cluster-worker has CIDR [10.244.1.0/24] I0619 16:01:36.935279 1 main.go:223] Handling node with IPs: map[172.18.0.3:{}] I0619 16:01:36.935343 1 main.go:250] Node…