I'm trying to create a cloud profile to start an EC2 instance in TeamCity. But I get Failed to connect to Amazon EC2. null (Service: AmazonEC2; Status Code: 400; Error Code: 400 Bad Request; Request ID: null) There is no any explanations about this. As you can see I have changed serverURL to https://google.com, but it produces the same error even when using the correct TeamCity server.
I checked outbound connections of the EC2 instance where TeamCity is deployed and it's fine. Also tried by changing the region.
Any thoughts?
Cheers!
Related
I have deployed a Spring Boot application onto a Google Kubernetes Engine workload. First, I pushed an image to Artifact Registry. Then, I ran the image using the docker run command in the gcloud command line. My GET request worked perfectly fine then, but once I deployed the image to a Kubernetes workload, the same GET request to the LoadBalancer returned a 500 Internal Server HTTP error.
Everytime I try going on Google's Error Reporting, it tells me to setup Error Reporting, but I don't really understand how to, and besides I thought HTTP errors automatically went to Error Reporting.
I'm sorry if there's too many extra details, I mainly want to know how to see the cause of an HTTP 500 error on a GKE deployment?
I am trying to use spring config server with cross account as I am deploying config server in kubernetise with aws backed.
but due to DefaultAWSCredentialsProviderChain I am unable to get connected to s3 bucket and gets 403 error.
In DefaultAWSCredentialsProviderChain as per logs WebIdentityTokenCredentialsProvider try to get credentials get 403 error.
but when I am try to connect with my awss3 client with STSAssumeRoleSessionCredentialsProvider it gets connect.
Is there any way so that I can provide STSAssumeRoleSessionCredentialsProvider instead of DefaultAWSCredentialsProviderChain
I have configured WSO2 API Manager 4.0.0 in an AWS EC2 which runs on Amazon Linux 2. I am following this WSO2 documentation to setup my first API. I am accessing the API Manager's Dev Portal via my local machine. I am in Step 3 : Invoking my API.
When I click the Execute button under Try Out for GET requests, I get a 200 OK response, but with an error saying TypeError: Failed to fetch. I have attached a screenshot here.
I feel that the request URL mentioned here ( https://localhost:8243/hello/1.0.0 ) should have the EC2 server's IP address, instead of localhost , but I cannot find a way to modify that. What am I doing wrong here?
Output
Browser's Inspect Console Tab
The Swagger was not able to make the invocation, as it is getting refused. Try updating the API Gateway Environment configurations in the deployment.toml to the Hostnames / IP address (publicly accessible) of the EC2 instance.
Following is a sample TOML configuration of API Gateway Environments. Update the <change-this> with appropriate hostnames.
[[apim.gateway.environment]]
...
ws_endpoint = "ws://<change-this>:9099"
wss_endpoint = "wss://<change-this>:8099"
http_endpoint = "http://<change-this>:${http.nio.port}"
https_endpoint = "https://<change-this>:${https.nio.port}"
websub_event_receiver_http_endpoint = "http://<change-this>:9021"
websub_event_receiver_https_endpoint = "https://<change-this>:8021"
Once the configurations are done, restart the server and invoke the API from the Devportal Swagger UI.
I have an AWS API Gateway endpoint that uses lambda proxy integration to retrieve data from an AWS RDS instance.
I use a yaml file to re-deploy the api, Once the API is re-deployed, The endpoint, illustrated above, throws an "Internal Server Error" every time I re-deploy the api.
The error goes off if I uncheck and then check the lambda proxy integration option/tick-box on the endpoint. This manual step is cumbersome and extremely unintuitive and can raise serious production issues.
Anyone facing similar issue know how to solve it without the additional "unchecking and checking" (manual) step?
What change in YAML can solve this problem ?
Under your AWS::ApiGateway::Method resource, make your Integration.Type as AWS_PROXY
https://docs.aws.amazon.com/apigateway/api-reference/resource/integration/#type
I am using the Ruby SDK to interface with the Dropbox Core API. Locally, I am having no issues using the API in any way. On my AWS server, however, the DB API returns a 500 internal server error every time. This is not a sporadic issue, as it has occurred consistently, across on multiple days.
For reference, here is some sample code which works locally, but results in a 500 error on my EC2 instance:
session = DropboxSession.new(<app key>, <app secret>)
session.set_access_token(<access token>, <access token secret>)
client = DropboxClient.new(session, 'dropbox')
client.account_info
The error I'm getting:
DropboxError: Dropbox Server Error: #<Net::HTTPInternalServerError:0x000000067f9cd8> - {"error": "Internal Server Error"}
Anyone see this before / have any insight into what is going on here? Would really appreciate some help on this :)