- Newest
- Most votes
- Most comments
AWS Amplify does not provide a way to directly change the IP address for a custom domain that you have configured with your Amplify app. The IP address associated with your custom domain is managed by AWS and can change dynamically.
However, here are a few points regarding custom domains with AWS Amplify:
-
When you configure a custom domain in Amplify, AWS creates and manages the required DNS records and routing to map your domain to the Amplify hosting environment.
-
The IP address that your custom domain resolves to is essentially the IP address of the AWS CloudFront distribution that Amplify provisions for your app's hosting.
-
This CloudFront IP can change over time as AWS manages and updates their infrastructure behind the scenes.
-
You cannot directly configure or change the IP address associated with your custom domain in Amplify. It is dynamically assigned by AWS.
If having a static IP address is a hard requirement for your use case, then AWS Amplify may not be the best solution. You would need to explore other hosting options like:
- Using an Elastic Load Balancer (ELB) or Amazon Lightsail instance with a static IP assigned.
- Hosting your app on an EC2 instance with an Elastic IP.
- Using a third-party hosting provider that offers static IP addresses.
However, these options add complexity and likely additional costs compared to the fully managed Amplify service.
In most cases, the dynamic IP addressing used by Amplify's CloudFront distributions should not cause any issues, as modern DNS resolvers and clients handle IP changes gracefully. But if you have specific requirements around static IP addresses, you may need to look beyond Amplify. Sources: [1] [Remove default AWS Amplify domain | AWS re:Post] (https://repost.aws/questions/QU8_YYIdAIQ5Wkw3SO29EPBQ/remove-default-aws-amplify-domain)
[2] [Amplify Custom Domain using AWS Certificate | AWS re:Post] (https://repost.aws/questions/QUTiB6uD9PQi20ELrJPMdRbw/amplify-custom-domain-using-aws-certificate)
[3] [How to configure subdomain using amplify application created in AWS with domain hosted in Hostinger? | AWS re:Post] (https://repost.aws/questions/QUjVqR7tqnSDK4WTjB_ZWmRA/how-to-configure-subdomain-using-amplify-application-created-in-aws-with-domain-hosted-in-hostinger)
If you are still facing this issue, I would consider filing an AWS abuse report as well about the resource in question & the appearance of that IP you were provisioned on the SpamHaus list. This should help you get traction with support. https://repost.aws/knowledge-center/report-aws-abuse
You can also recreate the domain, which will give you a new CloudFront CDN with it's own new IP. This is not ideal but an option.
Relevant content
- asked 2 years ago
- asked 3 months ago
- asked 3 years ago
- asked 3 years ago
