i try to access some s3-items (json-files) from an neo4j-database they is running in a EC2-machine.
I have some problems to understand, what is meaned with "endpoint" and "port" in the APOC-Manual.
Screenshot from APOC Manual
I downloaded all in the picture described Plugins and my ec2 is running in a VPC.
I'm new in AWS, sorry for stupid asking :/
and thanks for your reply.
Based on the comments, the issue was using incorrect standard-endpoint than the required one.
Related
I'm currently trying to set up an Airflow environment via MWAA. I've gone through the create environment steps twice with both ending at the page listing Airflow environments with a banner saying I was successful. However, for the past 2 days, this environments page has just shown Loading Environments, as shown below. I also see a (0) for the environment number.
So far, I've added 2 interfaces for ECR and VPC for the API and the environment but no luck. Has anyone else run into this issue or have any clue what might be happening? Thanks!
Were you able to find the solution to this issue? I had similar issues when I tried to set up the first-time MWAA on AWS Account.
https://github.com/awslabs/aws-support-tools/tree/master/MWAA
Here's a link to how to verify if all the resources are set up correctly for MWAA. If you run the script mentioned on the repo you should be able to see where the issue lies.
I'm newbie in AWS, with my free tier account I'm trying to build my nodeJS project with AWS CodeBuild but I get this error:
Build failed to start The build failed to start. The following error occured: Cannot have more than 0 builds in queue for the account
I followed the simple aws tutorial, leaving all default settings for let aws create all service, image etc for me.
Also I stored source code in a AwsCodeCommit repository.
Could anybody help me?
In my case, there was a security vulnerability in my account and AWS automatically raised a support ticket and suspended all resources that were linked to it. I had to fix it and then on chat with aws support they resumed my service.
I've seen a lot of answers around the web suggesting to call support, which is a great idea, but I was actually able to get around this on my own.
As the root user I went in and put in a current credit card. The one that was currently there was expired. I then deleted my CodeBuild project and create a new one. Now my builds work! It makes sense that AWS just needed a valid payment method before it allowed me to use premium services.
My solution may not work for you, but sure I hope it does!
My error was Project-level concurrent build limit cannot exceed the account-level concurrent build limit of 1 when I tried to increase the Concurrent build limit under checkbox Restrict number of concurrent builds this project can start in CodeBuild Project Configuration. I resolved it by writing to support to increase the limit. They increased it to 20 and it works now as expected. They increased it even though I'm on Basic plan on AWS if anyone's wondering.
My solution was to add new service role name and the concurrent build to 1. This worked
I think your issue is resolved at the moment. Any way I faced the same issue. In my case I had a "code build project" connecting to a GitHub repository. And then I added AWS Access Key and Secret hard coding the buildspec.yml file. With this AWS identified it as an unauthorized login. So they added security restrictions to the resources while opening a support issue. In such a case you can look for the emails from AWS in which they explain the reason for this behavior and the steps to get this corrected.
I have an EC2 instance running at AWS with some standard webpages. Since a few days the server replies with "AWS!" instead of delivering the index.page. Checking the source code of this page:
<html><body><script type="text/javascript" src="http://gc.kis.v2.scr.kaspersky-labs.com/XXXXX/main.js" charset="UTF-8"></script>AWS!</body></html>
On this instance Kaspersky is not installed. I didnt found any hints on Google so far - maybe someone has made a similiar experience and give me a hint why my index-page is not shown anymore (the code was not changed). Maybe AWS has undergone a change?
Any hint is very appreciated.
Issue fixed, stdunbar & John pointed into the right direction. DNS entry was wrong.
So here's the deal, I'm trying to run a little webmail server for testing purposes off amazon's EC2 server, I'm looking at their guide for setting the hostname, and the directory they mention /etc/sysconfig/ doesn't exist, let alone the file I'd be expected to edit, when I go to the actual hostname file (as if I was running the server) cd /etc/ then nano hostname I can read but I don't have write permission, so when I go to save the file it tells me I don't have the permissions, so I looked it up, and it says to edit /etc/sysconfig/network which would be fine and dandy, if the directory actually existed. Pretty new to all of this, so if I missed anything that could help you figure out what's going on please let me know! Thanks in advance!
It sounds like the base AMI you are using for your instance is not one of Amazon's AMI's. What AMI is the instance based on?
I'm having a django project that should be deployed on Amazon's EC2. There are various tutorials on installing django on EC2, but I think it'll always be a time consuming step to generate a new AMI image with your whole application... So I was thinking that it should also be possible to deploy it on the persistent storage, EBS?
But I'm wondering if that would have any disadvantages because there are no tutorials describing that out there... So if anybody is having some ideas on that or having any other tutorials on how to deploy new versions in an easy fast way to EC2 please let me know!
I used Bitnami Djangostack 1.2.3 (I'm not associated with bitnami in any way).
http://bitnami.org/stack/djangostack
The EC2 image is "ami-18fb0f71", described as "bitnami-djangostack-1.2.3-0-linux-ubuntu-10.04-ebs".
This is an EBS backed instance, but I can't comment on advantages/disadvantages of this.
I found some of the pertinent configuration files in these locations:
/opt/bitnami/apache2/conf/httpd.conf
/opt/bitnami/apps/django/conf/django.conf
The file served by default (as configured in httpd.conf) is '/opt/bitnami/apache2/htdocs/index.html'.
You can get a bit of support here:
http://bitnami.org/forums/forums/djangostack
I think it should be fine. At the least, you can experiment: get an EBS-backed instance, install django, stop the instance (not terminate!) and snapshot the volume (for backup).
Restart the instance, and see.