Primus Learning is a platform born out of a revolutionary ideology aimed at transforming education from the traditional degree-centric model to a more practical hands-on model. At Primus Learning, we are aimed at excellence.
Getting this error after clicking create instance: You're signed in with an AWS account that was provided by AISPL. These accounts cannot create Amazon Connect instances. Sign in using an account provided by AWS, and then try to create an instance. Please contact support if you need further assistance.
I loved your video and tried using the script you shared to pull all resources from my AWS account. However, the script only gave me an empty file. Initially, I thought the issue might be due to my resources not being tagged. So, I manually created a tag called env:qa and applied it to an EC2 instance to test. I confirmed the instance was tagged correctly, but when I ran the script again, it still returned an empty list. What I’m looking for is a script that can pull every resource in my account, whether it’s tagged or not. I’d appreciate any help you can provide to get this working. Thanks in advance!
Please ensure your lambda function has the right permissions to describe all the resources including ec2. Once that's done, you should be able to pull the resources, just grant admin access and see if that works. You could use the next script to tag the resources you want and test out with that.
I loved your video and tried using the script you shared to pull all resources from my AWS account. However, the script only gave me an empty file. Initially, I thought the issue might be due to my resources not being tagged. So, I manually created a tag called env:qa and applied it to an EC2 instance to test. I confirmed the instance was tagged correctly, but when I ran the script again, it still returned an empty list. What I’m looking for is a script that can pull every resource in my account, whether it’s tagged or not. I’d appreciate any help you can provide to get this working. Thanks in advance!
This may be failing because the role you're using doesn't have permissions to describe the services. Please ensure you have those permissions or better still just use the admin role. Another thing could be to use the second script to tag the resources before querying them one more time. Hope this helps.
All good until the pipeline is initiated, it seems the modules are outdated and there are some dependencies that are deprecated, I tried updating the version to 4.0.0 but still the same output: terraform apply -auto-approve [33m���[0m[0m [33m���[0m [0m[1m[33mWarning: [0m[0m[1mArgument is deprecated[0m [33m���[0m [0m [33m���[0m [0m[0m with module.myapp-vpc.aws_eip.nat, [33m���[0m [0m on .terraform/modules/myapp-vpc/main.tf line 1013, in resource "aws_eip" "nat": [33m���[0m [0m1013: vpc = [4mtrue[0m[0m [33m���[0m [0m [33m���[0m [0muse domain attribute instead [33m���[0m[0m [31m���[0m[0m [31m���[0m [0m[1m[31mError: [0m[0m[1mUnsupported argument[0m [31m���[0m [0m [31m���[0m [0m[0m on .terraform/modules/myapp-vpc/main.tf line 35, in resource "aws_vpc" "this": [31m���[0m [0m 35: [4menable_classiclink[0m = null # github.com/hashicorp/terraform/issues/31730[0m [31m���[0m [0m [31m���[0m [0mAn argument named "enable_classiclink" is not expected here. [31m���[0m[0m [31m���[0m[0m [31m���[0m [0m[1m[31mError: [0m[0m[1mUnsupported argument[0m [31m���[0m [0m [31m���[0m [0m[0m on .terraform/modules/myapp-vpc/main.tf line 36, in resource "aws_vpc" "this": [31m���[0m [0m 36: [4menable_classiclink_dns_support[0m = null # github.com/hashicorp/terraform/issues/31730[0m [31m���[0m [0m [31m���[0m [0mAn argument named "enable_classiclink_dns_support" is not expected here. [31m���[0m[0m [31m���[0m[0m [31m���[0m [0m[1m[31mError: [0m[0m[1mUnsupported argument[0m [31m���[0m [0m [31m���[0m [0m[0m on .terraform/modules/myapp-vpc/main.tf line 1246, in resource "aws_default_vpc" "this": [31m���[0m [0m1246: [4menable_classiclink[0m = null # github.com/hashicorp/terraform/issues/31730[0m [31m���[0m [0m [31m���[0m [0mAn argument named "enable_classiclink" is not expected here. [31m���[0m[0m [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy to EKS) Stage "Deploy to EKS" skipped due to earlier failure(s) Seem the tutorial is no longer deployable, why are modules used, isn't it more logical to use a template definition for the resource definitions as they are unlikely to change or if changed are more easy to troubleshoot.
I can't connect prisma to supabase. PS D:\dev ext\project> npx prisma db push Environment variables loaded from .env Prisma schema loaded from prisma\schema.prisma Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-us-west-1.pooler.supabase.com:6543" No reaction after this, and the table doesn't update too.
Hi, i have clone your code from git to computer. and then i push git code to my account. but i apply file application.yaml can't run. please help to check.rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.43.208.105:8081: i/o timeout"
AWS Control Tower can't create your account due to potential drift in your landing zone. Check your landing zone and try using the advanced account provisioning method to create your account. I am getting this error.
As a content creator myself, I'm always on the lookout for inspiration and tips to improve my own videos. This video was an absolute goldmine of valuable information, and I'm in awe of your presentation skills. The way you structured the content and kept it concise while still delivering maximum value is commendable. Your personality shines through, and it's evident that you're genuinely passionate about what you do. I'll be implementing some of your techniques into my own videos, and I'm confident it will make a significant difference. Thank you for being such an incredible source of inspiration!
gRPC is widely used for communication between internal microservices majorly due to its high performance and its polyglot nature. It uses HTTP/2 as its transfer protocol and inherits the benefits like binary framing from HTTP/2. I didn't consider it for this scenario and could probably work well. Will take a look at it.
brother u always do awesome job i wanna request you to plz do some migration projects how I can 'migrate on prem workloads to aws from azure to aws, for on prem db to aws
