Hello everyone, sorry I have been MIA for a while. Things are about to get loud and busy. Stay tuned!

Cross-domain reasoning: The missing skill that turns AI prompting into genuine insight. I wrote this Substack in an effort to help people understand the real power in a prompt, “reasoning + iteration = power 👍 https://open.substack.com/pub/karmalane1/p/are-your-prompts-too-confined?r=53vulf&utm_medium=ios

Welcome to the community! This is a space for builders, consultants, and career-changers who are serious about mastering AI systems with security-first thinking. Whether you’re already implementing AI workflows or just starting your cybersecurity journey, you’re in the right place. 👇 Comment below and tell us: - Where you’re from - What you’re currently building or learning - What you’re hoping to master here Can’t wait to learn and grow together 💡

Hey everyone, do post your intro and what you do so we can make sure we have the right audience and the contents we will create will be aligned.

Hey everyone. Im a noob to AI. I ran thru this how-to a couple of times, and have an api, which was created in AWs api gateway. https://builder.aws.com/content/2nF0CBYXKZdaSaCG758grnAkSSH/deploying-ai-agent-apis-on-aws-the-easiest-way The api looks like this: https://zz9v42px6a.execute-api.us-east-2.amazonaws.com/prod/chat I tried connecting to it like this: wscat -c wss://zz9v42px6a.execute-api.us-east-2.amazonaws.com/prod/chat error: Unexpected server response: 403 <<<<my error Ive since deleted the stack Any thoughts? I have no idea what Im doing again : ) What I would like to do is finish this stack with creating a front-end to communicate with the agent. The agent uses a generative AI Large Language Model (LLM) on AWs Bedrock.