- Le plus récent
- Le plus de votes
- La plupart des commentaires
Have you tried using the Amazon Cloudwatch agent to acquire more information? You might also try using Amazon Inspector if you suspect a malicious actor. Another option is to use an Application Performance Monitoring Tool if you cannot instrument your application, or Amazon X-Ray, if you can instrument your code.
As you've already found, an EC2 instance launched in a Public Subnet can be assigned a public IP address but the association only lasts as long as the instance is running. This is fine for testing/infrequent processing activities but not an advisable approach when running production/critical infrastructure. I would recommend you associate an Elastic IP address with your instance which will allow you to retain the same IP across any future restart/termination events.
It's also worth you reviewing the EC2 Best Practices to ensure your infrastructure is reliable and secure.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an