amazon-ec2

Is there an AWS inbound policy that interferes with “Authorization: Bearer {token}” data? [duplicate]

倖福魔咒の 提交于 2020-08-10 20:21:06
问题 This question already has answers here : Authorization Credentials Stripped — django, elastic beanstalk, oauth (4 answers) Closed last month . The question above is the thread associated with these links. Link 1, Link 2 It's like this when I understand my current situation. Request.user cannot be identified from EC2 instance created via AWS EB. The reason is that the Authorization: Bearer {token} provided during data communication is not being delivered to the EC2 instance. However, this

How do I create a AWS security group and use it in different .tf files?

戏子无情 提交于 2020-08-10 20:01:10
问题 As the title says, if I'm using terraform/aws/layers/bastion/main.tf to create an EC2 instance, I know I can also create a security group within this same main.tf file for the bastion instance to use, but what if I wanted to create a security group that can be used in a different file? For example, if terraform/aws/layers/worker/main.tf needed to use the same security group as bastion/main.tf how would I go about this? bastion/main.tf provider "aws" { region = var.region } resource "aws

AWS - Unable to make API calls to EC2 server via Application Load Balancer (ALB)

白昼怎懂夜的黑 提交于 2020-08-10 19:15:10
问题 I am trying to deploy a MERN Stack app to AWS but I am kinda stuck now. Current Progress: ALB is set up with a valid SSL Certificate issued by AWS. ALB URL: https://xyz.alb.com/ Also, ALB has three listeners: a. HTTP [80] b. HTTPS [443] c. HTTPS [5000] (For accessing ec2 backend server, is this right?) EC2 instance public IP: 78.45.43.23 (Say) (I can access my server on 78.45.43.23:5000/api/) I have whitelisted, ALB, https://xyz.alb.com in my server CORS (Node) [Important]. Problem Statement:

AWS - Unable to make API calls to EC2 server via Application Load Balancer (ALB)

生来就可爱ヽ(ⅴ<●) 提交于 2020-08-10 19:14:30
问题 I am trying to deploy a MERN Stack app to AWS but I am kinda stuck now. Current Progress: ALB is set up with a valid SSL Certificate issued by AWS. ALB URL: https://xyz.alb.com/ Also, ALB has three listeners: a. HTTP [80] b. HTTPS [443] c. HTTPS [5000] (For accessing ec2 backend server, is this right?) EC2 instance public IP: 78.45.43.23 (Say) (I can access my server on 78.45.43.23:5000/api/) I have whitelisted, ALB, https://xyz.alb.com in my server CORS (Node) [Important]. Problem Statement:

Cannot access s3 from application running on EKS EC2 instance, IAM assume role permissions issue

隐身守侯 提交于 2020-08-09 18:41:20
问题 NOTE: similar question asked here, but no proper solution provided. I setted up an EKS cluster via eksctl tool with single EC2 node. Deploy a Pod inside the EC2 node, this Pod writes the logs into s3 bucket. All worked fine when I used IAM user with key and secret. But now I want this Pod to use IAM Role instead. This Pod uses a newly created role with AmazonS3FullAccess permissions named prod-airflow-logs . According to the Docs, I also added "ec2.amazonaws.com" in this role's trust

React app (in a docker container) cannot access API (in a docker container) on AWS EC2

痞子三分冷 提交于 2020-08-05 10:10:12
问题 my question in a nutshell... Within the context of AWS EC2 hosting, what do I need to do to allow my frontend container to fetch from an endpoint on my backend container, locally? Details: I have 2 Docker containers running via docker-compose. Locally, they work fine and I am able to query the backend container (which is a node app) from my frontend container (a React app) using: http://localhost:3000/someendpoint After moving everything onto an AWC EC2 instance I am no longer able to connect

Terraform config isn't using output from other file for already created resource, instead tries to recreate it and fails (security group id)

只愿长相守 提交于 2020-07-23 06:53:05
问题 In terraform/aws/global/vpc/security_groups.tf I have the below code to create my bastion security group, and the output.tf file as well which is below. But in terraform/aws/layers/bastion/main.tf (code also below) I reference that security group as I need its security group ID to create my EC2 instance, the issue I have is that rather than getting the ID from the already existing security group created by the /vpc/security_groups.tf config it tries to create the whole security group and the

Terraform config isn't using output from other file for already created resource, instead tries to recreate it and fails (security group id)

为君一笑 提交于 2020-07-23 06:51:17
问题 In terraform/aws/global/vpc/security_groups.tf I have the below code to create my bastion security group, and the output.tf file as well which is below. But in terraform/aws/layers/bastion/main.tf (code also below) I reference that security group as I need its security group ID to create my EC2 instance, the issue I have is that rather than getting the ID from the already existing security group created by the /vpc/security_groups.tf config it tries to create the whole security group and the

Coturn AWS EC2 problems running

孤人 提交于 2020-07-23 06:28:31
问题 I'm trying to setup and run coturn TURN server on my EC2 instance which is on ubuntu. I have installed coturn package and trying to run the server using command line only and here is my command - sudo turnserver -a -syslog -o -n -u [My_Username]:[My_Password] -f -p 3478 -L [AWS_Internal_IP] -X [AWS_External_IP] -r [AWS_External_IP] -v --no-dtls --no-tls -—no-cli I get turnserver invalid option -- '?' and the server does not run. Please help. 回答1: You should configure coturn in config file (

HTTPS on EC2 instance running python project

十年热恋 提交于 2020-07-23 06:16:07
问题 I'm having considerable difficulty getting HTTPS to resolve on my EC2 instance, which runs a python project. The request just times out (ERR_CONNECTION_TIMED_OUT). HTTP runs ok, however. The steps I've taken are as follows. I've created a certificate in ACM for the following domains: *.mywebsite.com and mywebsite.com I've setup Route 53 as follows: Routing policy on the A records is Simple. I've gone into the Listener for my Load Balancer for my EC2 instance and CHANGED the port from 80 (HTTP