By using AWS re:Post, you agree to the Terms of Use

Questions tagged with Amazon Route 53

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Static domain for API Gateway connected to ELB and ECS with Apollo Client

## Prerequisites Currently we have deployed API Gateway that is connected to ECS instance with Elastic Load Balancer. API Gateway is functioning correctly and we can invoke the instance with the generated invoke URL: Note: ECS instance is running Apollo Client for Graph QL access, so we access the client using ``` {invoke_url}/graphql ``` and this works as expected. ![Enter image description here](/media/postImages/original/IM6u1TLNmrSF-BQphWxNyMsQ) *** ## Setting up the custom domain: We follow the instructions provided in https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html **Step-by-step** 1. We have already purchased a domain which we use for our services + SSL certificate. 2. We want to use subdomain.domain.com to direct to the API Gateway 3. We go to the API Gateway and setup a custom domain: ![Enter image description here](/media/postImages/original/IMXlJTri-USeOXsQ0AQYrLfA) 4. Next, we create an A Record alias that points to the generated API Gateway domain name that was created in the step 3. ![Enter image description here](/media/postImages/original/IMbHYRx4ujS_qiwsFELGr9Zw) 5. We setup the API Mapping to point to the existing API Gateway API: ![Enter image description here](/media/postImages/original/IM7WYW6pkQS5yca00hs-KlEg) All done? This is where we get stuck. According to the documentation, this should be enough but what we receive from the **API Gateway domain generated in step 3** ![Enter image description here](/media/postImages/original/IMJOBwVz4GRwCp36D0bixd9A) **subdomain.domain.com which was set in Route53 to point to the API Gateway** ![Enter image description here](/media/postImages/original/IMxhO1TxqLRNuQsvytlH5ZEQ) *** # The question In order to achieve the desired result of being able to access the API Gateway using custom domain: What did we do wrong and what to do to get it working? Can provide extra information if needed.
0
answers
0
votes
23
views
asked a month ago

Amplify S3 bucket missing?

Good Evening, I setup my amplify app through the ui, connected it to my gitlab, route53 with routing my purchased domain from google. I am getting an error now that I am at the limit for free tier storage. My website is less than 500 mb. I tried searching for the S3 bucket that I guess was automagically created but there are zero S3 buckets listed for my account. From what I have been able to find online it looks like amplify keeps all versions of the website. How do I access an S3 bucket to remove extra versions of the website if it doesn't show on my S3 bucket list? ** edit ** Here is the amplify get-app details. I also ran the jobs and looked at the artifacts, none of the jobs create an artifact. My app is pure css, html, javascript so nothing gets built. I also tried the s3api list-buckets command => empty. And the cloudformation describe-stacks command => empty. From everything I can see, there is not a single storage item associated with my amplify instance and yet I am getting the notification that it is running out of space. ``` { "app": { "appId": "an id", "appArn": "arn:aws:amplify:us-east-2:long number:apps/an id", "name": "bosonstudioswebsite", "tags": {}, "repository": "https://gitlab.com/mywebsite", "platform": "WEB", "createTime": "2021-05-09T16:00:24.489000-04:00", "updateTime": "2022-05-15T01:13:05.078000-04:00", "environmentVariables": {}, "defaultDomain": "an id.amplifyapp.com", "enableBranchAutoBuild": false, "enableBranchAutoDeletion": false, "enableBasicAuth": false, "customRules": [ { "source": "https://bosonstudios.com", "target": "https://www.bosonstudios.com", "status": "302" }, { "source": "/<*>", "target": "/index.html", "status": "404-200" } ], "productionBranch": { "lastDeployTime": "2022-08-13T13:12:36.782000-04:00", "status": "SUCCEED", "thumbnailUrl": "its here", "branchName": "master" }, "buildSpec": "version: 1\nfrontend:\n phases:\n # IMPORTANT - Please verify your build commands\n build:\n commands: []\n artifacts:\n # IMPORTANT - Please verify your build output directory\n baseDirectory: /\n files:\n - '**/*'\n cache:\n paths: []\n", "customHeaders": "", "enableAutoBranchCreation": false, "repositoryCloneMethod": "SSH" } } ```
2
answers
0
votes
28
views
asked a month ago