issue with route 53

Question

Hello, good morning, first time working with aws but having some issues. I created a s3 bucket, enabled the website hosting, public access was enabled, i then created a route 53 zone, create a record, but when i go to add my s3 endpoint, it simply says no resources found, which i cant understand, its the same exact region north europe, all seems to be enabled, so i dont know how it can say no resources found.

If there's anything i can try please let me know.

Thank you

If there's anything i can try please let me know.

Thank you

Pandurangaswamy · Accepted Answer

Hi  mayasntos,

Please Follow Below Steps and once go through below documentation link it will be helpful to you to resolve your issue .

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/RoutingToS3Bucket.html

https://docs.aws.amazon.com/AmazonS3/latest/userguide/how-to-page-redirect.html

**Verify S3 Bucket Settings:**

* Ensure the bucket name matches the domain name (e.g., if your domain is example.com, the bucket name should be example.com).
* Double-check that static website hosting is enabled in the S3 bucket settings. In the S3 Management Console, under your bucket's properties, confirm that "Static website hosting" is enabled and that you have set the index document (e.g., index.html).

**Bucket Policy:**
Make sure the bucket policy allows public read access. Here's an example bucket policy:

```
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "PublicReadGetObject",
      "Effect": "Allow",
      "Principal": "*",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::your-bucket-name/*"
    }
  ]
}
```
Replace your-bucket-name with the actual name of your bucket.

**DNS Configuration in Route 53:**

* Ensure you have created a hosted zone for your domain in Route 53.
* Add an "A" record for your domain. Use the "Alias" feature to link the record to your S3 bucket. When you select the alias target, it should show your S3 website endpoint if configured correctly. If it's not showing, ensure the region and bucket name are correct.

**Check S3 Endpoint Configuration:** The endpoint for your S3 bucket website should follow this format: http://your-bucket-name.s3-website-your-region.amazonaws.com. Ensure you're using the correct format and region.

**AWS Region:** Confirm that both the S3 bucket and the Route 53 hosted zone are in the same AWS region. While S3 buckets are globally unique, the Route 53 alias target should match the S3 website endpoint for the specific region.

**Domain Registration and NS Records:** Ensure your domain is registered correctly and that the Name Server (NS) records provided by Route 53 are correctly set at your domain registrar. Sometimes propagation of DNS changes can take time, so if you've just made these changes, there might be a delay.

kranthi putti · Answer

Hello,
If you're unable to associate your S3 bucket endpoint with a Route 53 record, here are some quick steps to troubleshoot:

**1.Confirm Region:** Ensure both your S3 bucket and Route 53 hosted zone are in the same AWS region.

**2.Check Bucket Policy:** Verify your S3 bucket policy allows access from Route 53.

```
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "Service": "route53.amazonaws.com"
            },
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::your-bucket-name/*"
        }
    ]
}

```

**3.DNS Propagation:** Allow some time for DNS propagation after creating the Route 53 record.

**4.Permissions:** Ensure your IAM user or role has permissions to associate S3 buckets with Route 53 records.

**5.Test Endpoint Access:** Manually verify your S3 bucket's website endpoint accessibility.

**6.Review Route 53 Settings:** Double-check Route 53 record settings for accuracy.

If issues persist, provide more details for further assistance.

Sandeep · Answer

Bucket and Record Name Match:
  
* Route 53 only finds S3 buckets that have the exact same name as the record you're trying to create.
*  For example, if your S3 bucket is named "mywebsite" and your Route 53 record is "www.mywebsite.com," it won't find a match.
*   Make sure both names are identical.

Record Type:

* When creating the record in Route 53, ensure you're selecting the correct record type.
* For website hosting with S3, you typically want an A record that points to the S3 website endpoint..

Here are some resources that might be helpful:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/RoutingToS3Bucket.html

https://docs.aws.amazon.com/AmazonS3/latest/userguide/how-to-page-redirect.html

mayasntos · Answer

thank you so much for your help, it  seems it solved for now! seems the issue was bucket not having the same name as the route 53 record

issue with route 53

Relevant content